I suspect a lot comes down to how one views the vested balances. I view them as just as legitimate as other BTS, fungible or not. Others seem to take the view that because these BTS are not liquid, then somehow they are in a second class. Obviously I disagree.
Part of the reason they were made vesting was to ensure we retained our devs.
The result is that as part of the merger many people (including the large Dev fund) are taking a long-term vested interest in things.
Do you really want Toast, Adam, and I to have instant access to a large percentage of all new funds or do you want us vesting with a long time horizon?
We failed to retain Toast, Adam/FMV is crowd-funding separately and BM is focusing on another DAC.
There is also speculation there has been a lot of selling by key parties... https://bitsharestalk.org/index.php/topic,22098.msg287894.html#msg287894
So in addition to all of the above, by continuing the merger we may also be inadvertently (though I'm sure they will disagree) funding other DACs at our expense.
We are the single largest holder of PTS by far. Giving a large stake to PTS and AGS would be massively in our favor.
I understand your POV and perhaps it is the correct one, but continuing the merger is not a competitive/successful business strategy for BTS at this stage imo so it is worth discussing.
I am highly conflicted by this proposal. My gut reaction is that ending the vesting early is breaking a contract, a breach of trust. On the other hand as is pointed out above the primary reason for vesting the ownership was to retain the people those shares were granted to. The contract was flawed, in that it didn't stipulate the retention of vesting rights were contingent on continued allegiance to the granting party (BTS chain).
Nobody can predict the future with perfect accuracy. I've been around since before the merger so I am well aware of the mistakes made along the way, as dannotestein, empirical and others have outlined here. BM / Stan / CNX have been between a rock and a hard place many times trying to keep the vision alive and sustain the team to carry it out. Major contributors have left the team along the way (Toast, Vikram, Nathan, ...) so their efforts in keeping the team together have their limitations, as does the patience of those who remain to see the BitShares vision of a truly decentralized DEX and platform for growth come to fruition and wider adoption.
Unlike other projects BitShares is highly transparent and the tough decisions are not hidden away from public scrutiny. That characteristic is a double-edged sword. I see the decision to end vesting early as a highly controversial move, and one with good points to consider on both sides. I have no stake in the vesting, just to provide full disclosure, so perhaps that taints my judgment. Can anyone claim total objectivity on this matter? Not very likely anyone reading this can.
It is clear that the source of funds have dried up to continue development and even maintenance to sustain the ongoing cost of the dev team. I see this decision as a matter of survival of the BitShares ecosystem, and as such the early termination of the merger vesting shares represents a significant resource (126Million BTS - 6 months @ 700K / day, or ~$500K @ $0.004 / BTS) that could be applied toward putting the crucial, final touches on the great work BM's team brought into existence, like funding xeroc's efforts to document this work so others can easily build on it.
I find empirical's points highly compelling, and although ending the vesting early will definitely have negative effects, so will allowing it to continue, such as funding work on other chains (tho not directly).
We also need to consider what can realistically be accomplished using this $500K pool if it becomes available. How will we organize to prioritize what work must be done to polish up this ecosystem to attract adoption? Marketing, development or maintenance? Who is qualified to do any development deemed necessary? I don't think it's healthy for the long term success of BitShares to look to an exclusive group of devs as the only ones who can contribute to the code base. We need to promote the opposite perspective, than anyone can contribute, and make it easy for them to do so. We need good conventions, practices of code review and procedures for proposing and adopting the contributions made. Much of that is already in place in the form of worker proposals. The community must step up to the challenge of organizing itself to set priorities, milestones and goals to achieve our objectives. We need solid project planing and a roadmap to rally the community and focus our resources. Can leadership like this emerge from within the community or will it languish and falter? Once again this community is given the opportunity to be responsible for itself and not rely on someone else to make decisions. It took quite awhile before a committee was wiling to take on the role of leadership. Will it be the same now, or will we embrace responsibility?
There are many projects that depend on the continuation of the BitShares ecosystem, each of which provides plenty of reasons to be hopeful for the future of BitShares. I feel the same about many of the people who continue to believe in the vision and promise of a freer future and remain dedicated to seeing that vision made into reality.