True, but to be fair BTC is older and vastly more recognized. You’re right though, PoW is better at distribution than PPC’s hybrid proof; my argument was insubstantial.
I agree that diluting shares to fund whatever – just a custodian vote away – is quite a slippery slope. Fiscal discipline is easier to maintain when all your income is revenue.
2 Likes
For those interested in testing my new BKS datafeed:
URL: https://raw.githubusercontent.com/Cybnate/BKS-datafeed/master/Cybnate-main.json
Signature URL: https://raw.githubusercontent.com/Cybnate/BKS-datafeed/master/Cybnate-sig.txt
Signature address: 8U4ptdMup2MQ1uwVNNYqYv4btzmFyAuDju
The feed is setup to only vote for the motion in the OP. I will set up a thread for the BKS datafeed later.
4 Likes
You are amazing! 
1 Like
I will also display my feeds in this thread since you started here 
added, nothing happened? How to use these link?
I am generating my own feeds now. I noticed that “getvote” generates parkrates, which should not be there since B&C Exchange does not deal with rates. (cc @sigmike )
1 Like
08:59:02
{
“custodians” : [
],
“parkrates” : [
],
“motions” : [
“f8bcd3d068a6b35c92902a8d57e0e773e4e35352”
],
“fees” : {
}
}
08:59:51
getvote
08:59:51

{
“custodians” : [
],
“parkrates” : [
],
“motions” : [
“f8bcd3d068a6b35c92902a8d57e0e773e4e35352”
],
“fees” : {
}
}
before and after adding cybnate datafeed, getvote results are same.
More generally some commands in the debug window related to parking remain.
I have created my BCExchange’s data feeds for those that would like to follow me.
I have included the motion to stop the sale of BKS here.
2 Likes
The motion is close to 40% total and close to 80% in the last 100 blocks.
If nothing changes significantly, it will pass in approximately 1,200 blocks or 20 hours from now.
bcexchanged getinfo
{
"version" : "v3.0.0-unk-beta",
"protocolversion" : 2000000,
"blocks" : 55921,
"moneysupply" : 208717.6845,
[...]
}
bcexchanged getmotions
[...] "f8bcd3d068a6b35c92902a8d57e0e773e4e35352" : {
"blocks" : 3962,
"block_percentage" : 39.62,
"sharedays" : 80757,
"shareday_percentage" : 33.54490058
}
}
bcexchanged getmotions 55921 100
{
"f8bcd3d068a6b35c92902a8d57e0e773e4e35352" : {
"blocks" : 79,
"block_percentage" : 79.0,
"sharedays" : 1753,
"shareday_percentage" : 79.07081642
}
}
There is only one motion on the BCE blockchain at the moment 
Update:
bcexchanged getinfo
"version" : "v3.0.0-unk-beta",
"protocolversion" : 2000000,
"walletversion" : 1,
"blocks" : 56901,
"moneysupply" : 208727.302,
[...]
bcexchanged getmotions
{
[...] "f8bcd3d068a6b35c92902a8d57e0e773e4e35352" : {
"blocks" : 4759,
"block_percentage" : 47.59,
"sharedays" : 100161,
"shareday_percentage" : 40.74500456
}
}
bcexchanged getmotions 56899 100
{
"f8bcd3d068a6b35c92902a8d57e0e773e4e35352" : {
"blocks" : 80,
"block_percentage" : 80.0,
"sharedays" : 1924,
"shareday_percentage" : 84.23817863
}
}Question: do share days destroyed still play a role (at Nu / at BCE)?
While this might not play a role for this motion (it’s going to pass - maybe not until 23:59 UTC today - anyway unless the voting behaviour changes drastically), I find it necessary to have a regulation for it.
I’m aware of a motion to stop share days being taken into account at Nu.
I’m not sure whether that change is already active.
I thought so and assumed BCE wouldn’t take share days into account as well.
I’m not talking about share days being reported by the wallet application!
If nobody can point me to a policy which determines criteria for BCE motions to pass, I’m going to create a motion draft for it as soon as I find the time (and have more than my mobile phone to do that…).
There is an open issue “Give all votes the same weight” in NuBits repository but development team didn’t have enough time I suppose. And so many complicated protocol changes.
It looks like the time zone of the bcblockexcplorer is UTC+2.
If this assumption is correct, the last block yesterday was 57948
The status of the motion by that block was:
bcexchanged getmotions 57948
[...] "f8bcd3d068a6b35c92902a8d57e0e773e4e35352" : {
"blocks" : 5607,
"block_percentage" : 56.07,
"sharedays" : 121831,
"shareday_percentage" : 47.87975728
}
}And now it is:
bcexchanged getinfo
{
[...]
"blocks" : 58649,
"moneysupply" : 208743.7922,
[...]
}
bcexchanged getmotions 58649
[...]
"f8bcd3d068a6b35c92902a8d57e0e773e4e35352" : {
"blocks" : 6159,
"block_percentage" : 61.59,
"sharedays" : 134854,
"shareday_percentage" : 58.59090554
}
}So depending on whether the share days play a role, the motion passed yesterday or today.
I’m on the fence how to treat this.
As a motion does nothing by protocol, a protocol change to effectively ignore share days isn’t required.
On the other hand the RPC command still lists the share days and it might be counterintuitive to see share days of motions, but not having them regarded.
The safe way might be to regard blocks and share days for this motion and decide for BCE what has once been decided for Nu: whether or not to regard share days.
Following this interpretation
- accepting offers to purchase BKS ends on the 5th day from now: 2015-08-21
- not requested BKS will be burned on the 7th day from now: 2015-08-23
- requested but not paid BKS will be burned on the 14th day from now: 2015-08-30
1 Like
Motion f8bcd3d068a6b35c92902a8d57e0e773e4e35352 has passed at block 58377, which occurred on August 16, 2015 UTC.
The motion text states:
This motion confirms BlockShareholders’ desire to cease the sale of undistributed BKS. At 23:59 UTC on the 5th day after this motion passes no new buy offers will be accepted by B&C Exchange. For purposes of accounting, this time will be defined as the time a message is received by B&C Exchange, not when the message was sent. At 23:59 UTC on the 7th day after this motion passes all undistributed BKS that have not been requested for purchase will be burned. At 23:59 UTC on the 14th day after this motion passes all undistributed BKS will be burned, including those that had been reserved for purchase, but no payment was sent.
Accordingly, the sale of undistributed BlockShares held in our possession will stop soon. There are three important dates specified by the motion.
August 21, 2015 (23:59 UTC) - We will stop accepting offers to purchase BlockShares. For purposes of accounting, this time will be defined as the time a message is received by B&C Exchange, not when the message was sent. If you are planning on making a final purchase, please don’t leave it until the last minute, as we will not extend this deadline for any reason. This date is five days after the motion passed.
August 23, 2015 (23:59 UTC) - Any BlockShares that have not been requested for purchase by August 21, 2015 will be burned. We will post details of the burn transaction publicly so that all shareholders can verify it was completed. This date is seven days after the motion passed.
August 30, 2015 (23:59 UTC) - Any BlockShares remaining that have not been paid for - including those that were requested for purchase but not paid for - will be burned. At this point, all undistributed BlockShares will have been destroyed as per the motion. This date is fourteen days after the motion passed.
We will provide regular updates on total fundraising as we approach these milestone dates.
Link to Bitcointalk: https://bitcointalk.org/index.php?topic=1033773.msg12157272#msg12157272
1 Like
Looking at the steep rise of the number of sold BKS/gathered money in the last days.
I consider the motion to stop the BKS sale a full success and want to congratulate the BKS holders to the decision of stopping the sale with a lead time.
5 Likes
Looks like stopping the sale not only surged the funds gathered, but “improved” the BKS price (which would have had an upper limit with the sale going on…):
http://imgur.com/mdGhHJj
Now 4.92USD and 2.7kUSD vol. traded
1 Like