This thread is a good place for III to provide factual explanation to PTS/AGS holders!
I'm for the merge. I think BTS will continue to grow despite current disputes.
However I think a promise is a promise and it should be kept.
I think integrity is important and I believe most people will understand the following written "document" as I understood it the first time I saw it.
Any AGS/PTS investor believed in it and it was backed by @Bytemast, @Stan and III.
Thanks to sudo for pointing this out:
Don't forget the beginner's mind
Social Consensus Software License - Version 1.0 - August 10, 2013
Copyright (c) 2013 Invictus Innovations, Inc. All rights reserved.
Redistribution and use in the source and binary forms, with or without modification, are permitted provided that the following condititons are met:
1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3.Neither the name of Invictus Innovations, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
4.The genesis block of any blockchain must allocate 10% of the total lifetime shares ever allocated by the blockchain to the holders of BitShares PTS proportional to the percentage of total BitShares PTS held. Additionally 10% of the total lifetime shares ever allcoated by the blockchain to the holders of BitShares AGS must be allocated in the genesis block.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Now III can explain how is this non-binding promise fulfilled.