To check on the success of this motion, in your wallet go to āhelpā > ādebug windowā > āconsoleā tab. Type this into the command line:
getmotions
This motion should be the third motion listed. It gives two percentages, one is based on blocks and the other on sharedays. Both must be >50% for it to pass (though Nu will be changing this to just the block percentage criteria later if I recall correctly, which B&C will most likely adopt).
Message service should be provided to B&C, so that the vote motion broadcast to everyone. And this message still can be a revenue for B&C by charging fee and stop spam attack.
As the rules for a motion to pass are not enforced by protocol this motion doesnāt depend on the Nu 2.0 source code from which it was forked.
The rule for Nu motions once required indeed more than 50% blocks AND share days destroyed in a rolling window of 10,000 blocks for a motion to pass.
The motion to change that (to only blocks being considered) is from December last year; are share days still relevant?
Itās not stated explicitly in the BCE design (at least I havenāt found it), but I would have expected that BCE started with the most recent version of consensus rules of Nu:
over 50% blocks in a rolling window of 10,000 blocks containing the hash of a motion for the motion to pass
Right. Thank you!
When Iām on my mobile phone Iām often too lazy to research details
I remembered that a motion could pass in as little as roughly 3.5 days if a vast majority were voting for it.
That would be the 5,001 of 10,000 blocks then.
I adjusted my post accordingly.
Excuse my ignorance, but can someone please point me to what to do to get my shares in the wallet. I do have an empty wallet just moved it from pointing to test to production and connecting to 4 or more peers. And are the additional shares already distributed to the rightful owners? This may or may not influence the voting.
Have some difficulties synchronising (stuck at 13075), maybe that is the issue? Can someone please advise the correct block height while we are at it?
My understanding is that BKS have been distributed to NSR holders AND those who bought them from BCE.
So all who have a stake in this DAC so far are able to vote.
Those who have bcexchanged running on Linux (maybe on a RaspberryPi) and want to continuously log the progress of this motion, might be interested in a tiny script I made.
~/bin/getmotion.sh gets execute each time a block is found and logs motion information into a file.
Iām aware that a blockexplorer will soon be available for the BCE blockchain. But this script is able to log more than just the current situation - it logs the status per block and allows to see the progress
If BCE really sells additional 50k BKS at ~$4 each, there will be additional $200k funding, I guess spending it on developing additional features for the intial release will push the release date by quite a few months. I am a believer of releasing early and releasing often in software development. Iād like to see the bear minimum or even a proof-of-concept prototype running, say, in the next month.
Typing getmotions 51641 100 shows that the motion has received votes in 62 of the past 100 blocks, along with over 57% of the share days destroyed. This motion is well on its way to passing if the voting patterns hold.
I donāt wonder as it seems to be the rational economical choice.
Whether additional BKS will be sold at a fixed rate, being sold at exchanges or in (seeded) auctions is a different topic that can be discussed once BCE needs additional funding AND this motion has passed
Whichever one the community decides to use. We purposely didnāt create a B&C Exchange subreddit because the nature of BlockShareholder discussion - namely, long-term voting - is far better suited to a Discourse forum.