WARNING: I am pretty sure the code only supports 1/5ths of a share, trying to make it do 1/10ths would probably require a rebuilding of the actual node core software as well as maybe some modifying of the scripts we use to build the distribution files.
So file custodians be aware the files I just prepared might not actually work, we might have to re-do the file-preparing using 1/5ths of a share as I am pretty darn sure that is the smallest granularity we coded in from the start.
-MarkM-
Thanks for the heads up Mark! This is how we are fixing the issue:
1. Increase shares from 200 to 400
2. Duplicate assigned shares to all receivers (i.e: 1/10ths to 1/5ths)
3. Redistribute remaining 1/5ths to ensure the new receiver file is paying 1/5ths (tricky part)
For #3 (and after several tests) I found additional 3/5ths of a share needed to be distributed somewhere, so I did as follows:
- Increase Satoshi0x's Marketing duty shares from 1/5th to 2/5ths (well done Dan!)
- Increase develCuy's Earning Factotum shares from 1/5th to 3/5ths (dude you're keeping me very busy!)
I'll give up (again) some fractions of shares in the future, whenever we need to onboard new people.
Changes are ready to deploy. Go go Devcoin!
- develCuy
Um.
New wallet downloads require manual peer node entries or the wallet will not sync.
It is still an old wallet with known vulnerabilities.
Block rewards are down to 2,500 which made the miners give up. It is supposed to be 50k DVC reward per block, but now it is only 2.5k.
We had some days where transactions didn't go through after waiting for hours. Nobody really cared though because there are so few transactions.
See for yourself ... this blockchain is not very secure and the rewards are a fraction of what they are supposed to be
https://chainz.cryptoid.info/dvc/#So I am asking: why is anybody taking shares when the coin is fundamentally broken?
I remember back when you received shares for getting things done.
You should send all of the ongoing shares to a burn address and give out bounties from your own fat wallets to get this project back on track.
As it sits now, someone with a little hash power can set up their own local DNS entries for the receiver hostnames and bypass your ongoing shares forever.
~ctya
Looks like the code just needs to adjust what the expected share amount given to the beneficiary should be. I just turned on my node and its 30 hours behind because this is what happened with the subsidy going down to 2,500: