SIP 85 has proven controversial. I’d like to offer my own personal thoughts on the process.
Proclamation SIP and Threshold Requirements
Broadly speaking votes which require higher quorum and vote participation (Admin) are required only for contract changes. I would usually think that SIP 85 should not require the higher threshold. However, SIP 85 is actually a rather important vote, and so I appreciate Sacro’s decision to fix a higher threshold.
What makes SIP85 a particularly important vote is that it is perceived to be a decision to distribute assets that Sovryn does not yet have, but that might be of overwhelming importance. If, as many seem to believe, the majority of Sovryn’s future assets would be in the form of BOS, the decision to distribute them as per SIP85, represents a decision for a partial liquidation of Sovryn and should not be taken lightly.
Further, given that BitcoinOS token distribution has not yet been decided, not to mention distribution, a decision taken now that would be incompatible with what other stakeholders decide to do would mean Sovryn’s version of BOS would effectively fork off from the rest of BitcoinOS. This too is a decision not to be taken lightly.
UI bug?
In the V1 dapp UI it is easier to select Admin vs Owner votes. In V2, per John Light’s design spec, Proclamation SIPs default to Admin votes. I think this is incorrect and should be corrected to default to Owner.
Voting Distribution
People have correctly pointed out that the majority of addresses voting ‘NO’ on SIP85 are long term holders, including tokens that originate from founder allocations. Some people think that this is unfair. Everyone has their own personal view of subjective view of fairness. I put more stock into the objective facts:
- The fact that anyone is staking means they are long term committed to the project. The fact that founders are still staking is exactly what you would want to see.
- Founder allocation was always a minority of total allocation. But founders and team tend to be more active and thus a larger % of any active vote. This too is exactly what we desire from committed contributors.
In other words, this is the system we all signed up to, working as designed.
Does Bitocracy favor larger, longer, more active stakers? Yes, by design.
Do founders and active contributors have tokens earned through their contribution? Yes, by design.
Do these founder allocations represent the majority of tokens available for stake? No, not even close.
Do these founder allocations have a majority of VP? Also no, not even close. As designed.
Timing
I have two concerns about the timing of SIP85.
First, I think the SIP itself was premature. There is not yet a final or close to final plan for the distribution of BOS tokens. Sovryn is a privileged party, as it has a fairly certain allocation before any other party - around which all other parties and all other aspects need to be negotiated. SIP 85 proposes to introduce additional unilateral terms, without the context of the rest of the project, distribution plans, GTM, ecosystem bootstrapping requirements, etc.
In what way was this SIP urgent now - in the absence of key context? To me it seems rushed.
Second, the text of all SIPs should be published well before a SIP to allow for debate. Here there was a debate that preceded any text - then the text was published just hours before the SIP. The details of the specific text must be debated and here there was no opportunity for that. As a general rule I think anything but an emergency/highly time sensitive SIP should be rejected on these pro-forma grounds alone.
SIP Announcements
There is a debate about whether all SIPs should be announced on Twitter. Some people feel that the Twitter account should focus on ‘marketing’ and communication for the purposes of user acquisition. Many (most?) SIPs should not be of interest.
My view is all SIPs should be announced on key channels, including Twitter. These channels inform the user and staking community.