Quote from: ctya on Today at 12:55:52 AM

Quote from: develCuy on October 15, 2021, 06:56:26 PM

Quote from: markm on October 15, 2021, 04:54:51 AM

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:

Code:

received block 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb
connection timeout
trying connection 146.52.211.139:52333 lastseen=52278.9hrs
ERROR: ConnectBlock() : Share to beneficiary is insufficient
ERROR: SetBestBlock() : ConnectBlock 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block da21e468d0cdeed0141ea397eb0f919e37a4b1bd49a510998dcdf0b2eb26afd0
ERROR: ConnectBlock() : Share to beneficiary is insufficient
ERROR: SetBestBlock() : ConnectBlock 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block bef0f3e5dcc92e31bcf1ce4a364dad14fa7582470e846b579968c1ffa506085e
ERROR: ConnectBlock() : Share to beneficiary is insufficient
ERROR: SetBestBlock() : ConnectBlock 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 56341a94f8f09385f6767d2eb898cd8c3d382e970ad06af19cc5604f4325d897
ERROR: ConnectBlock() : Share to beneficiary is insufficient
ERROR: SetBestBlock() : ConnectBlock 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 8575c0c5103874604a0d56a38a9db403a1aaa533fcc82ef24d7079093507d6b6
ERROR: ConnectBlock() : Share to beneficiary is insufficient
ERROR: SetBestBlock() : ConnectBlock 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block d2567b0720e46283df537ba958cb57df7de6464b35753631c44639b20af73f99
ERROR: ConnectBlock() : Share to beneficiary is insufficient
ERROR: SetBestBlock() : ConnectBlock 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 900c8410d625c77960e2eb7fa06192fd0e03a20b69fc56074f06f7b93716ba98
ERROR: ConnectBlock() : Share to beneficiary is insufficient
ERROR: SetBestBlock() : ConnectBlock 367d787286695beb08828f6849ef50abb7a8079e45e4538feb65910f266179cb failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED