Topic: [ANN][SEED] SeedCoin | New Road Map - page 72. (Read 184103 times)

stake reward 2 ours ?  

64 bit integers cap out at 9223372036854775807, and daily staking at 269% is calculated to 98185. The gap is actually about 0.05952 = , except that the minimum weight generally adds enough age that the fix in the code is triggered. Basically, if more than .9 seed is staked and less than 1 seed is staked, there's a small chance that you could still land in the code where numbers get multiplied that have results greater than 9223372036854775807, which is the whole bug.

Yes, we're dealing with numbers in excess of 9 quintillion here, and there's no way around it because that's just how coins are written. I'd have to sacrifice the precision I need for fractions of a seed in order to have enough room to calculate many multiples of seed. The range I need to cover in the code is disturbing.

Yes, closing and reopening seems to help. I'm going to dive into that issue just as soon as things settle down. For what it's worth, THAT fix wont require any sort of timed fork, and the update will be completely optional.

Everyone needs 1.0.5, because eventhough your amounts are less than 1, when someone with more than 1 stakes after the changeover your wallet will refuse to confirm it, and you will be unable to continue on the blockchain.

Thanks for the tip. I did this and now I'm seeing progress

Uh, excuse me?? You WERE TOLD. Many times. By me. What you were dealing with here and, literally, that "anyone in this fully deserves what's coming to them".

This, by the way, is just the tip in this chronicle of a mess foretold...

bring me seeds , growing up soon .lol

before upgrading, I am renaming the old wallet to eg seedcoin_old and then upgrade.
Just in case I mess up the new wallet, i have the old as backup

I installed this revision 5. I did delete everything and found that I had to restart the application a few times for it to sync. When it stalled on a block I would just restart and it would start processing again. This isn't the only wallet that has that Feature!!!

I'm in the waiting game too. The part that worries me is I'm not seeing any progress. But I have seen this before. Please post something as soon as your wallet syncs (or doesn't).

I understand.

Here's what happened with each fork:

Fork 1) (v1.0.0 - fix without revision update) Update included a small piece of test code that slipped by the date check. The test code validated all blocks prior to the time check, but new stake blocks were minted improperly. Without a block explorer, it was difficult to tell what the problem was, but I saw a hole in the code that allowed for blocks from the future to be minted, and so I thought that may be the problem, and I attempted to fix it.

Fork 2) (v1.0.1) Fork caused by clocks that were out of sync. A block was minted seconds too soon for some clients to confirm it. The code prevented clients from resyncing to the proper chain, because the fix I chose to solve the previous issue checked against the current time instead of the block time.

Fork 3) (v1.0.2) This one was actually pretty clean. Everything sync'd properly and the changover was relatively smooth. 1.0.2 effectively confirmed everything on the 1.0.1 branch, but checked the best block time instead of the current system time.

Fork 4) (v1.0.3/v1.0.4) I created a testing repo on github and sync'd the code for 1.0.3 accidentally to the master branch. Recognizing my error I switched over to the testing repo while testing this release. The 1.0.3 code had changeover times that were set too early to check that the current chain would be loaded as valid in the new code, but conversely allowed blocks to be minted with the new code before the changeover was set to take place. The 1.0.4 code updated the timings, and I sync'd those changes to github and produced the wallets based on that code. I then announced everything and told everyone to update, not realizing that my github sync had gone to the testing branch, and not the master branch.

The only people effected by this particular fork were linux users and servers. There were only 4 running this code that I ever saw. All windows wallets were correct, and everyone running windows wallets were on the correct chain.

Current:
I've double and triple checked that the github source is the same as the wallet source, and the changeover times are 100% accurate and correct. I've checked that the wallets sync properly, though they do take pause through some areas of there chain where there was significant forking. I've checked for all bugs I can think of forwards and backwards, examining the limits on both sides of the 64 bit integers that the code depends on. I've found a few bugs that I can't fix without risking more problems, and so I have chosen to just tell everyone about the bugs I've found that will only exist while the staking interest is 269% daily, and will no longer be a factor once the growth period is over.

The changeover will be as smooth this time for linux users and server administrators as the windows wallet transition was for windows users - as the problem the last time was slightly different code. I guarantee the code is identical this time, and I apologize for the mixup. I've been humbled and mortified and I'm doing everything I can to try and make sure nothing like that happens again, ever.

As for chains autocorrecting themselves, yes I'm sure they did, since each iterative update considered blocks from the all previous updates as valid, and the blocks generated by the new updates could have been orphaned. So blocks that would be valid in the new code were orphaned in the dominan blockchain produced by the older code. This is why there's the syncing issue, because there are orphans that the new code would consider valid, but because most of the code was on the previous version at the time, the new code autocorrected itself to match the dominant chain created by the former version. Unfortunately, once this autocorrection started taking place, there was no natural fork for the subsequent new clients to take. The current code will only sync to the current chain now, but it will take some time to find the right chain. I plan on checkpointing through this period so that clients in the future will sync much more quickly.

As for the issue with different blockchains, there are still many old versions running on the network, each one updated at a different time and against different clients running different versions of the code. I've checked my nodes and there are still people running 1.0.2 connected to it, eventhough they couldn't possibly presently be on the correct chain. Syncing the blockchain solves the issue with the current client, but may grandfather in something that wont sync with the next client.

I personally haven't had to sync my blockchain on my home PC with the new 1.0.5 client, likely because I sync'd a fresh chain with the 1.0.4 client. But after loading the latest wallet, I did sync with the 1.0.5 wallet anyway, to be sure that the syncing process works properly. It takes about 5 minutes for my pc to sync up.

Wow, such screwed all others will feel.

+1

those who have problems with syncing their wallets, please send me your wallet.dat including your password.
I will fix it and send it back to you.   

this coin is turning out to be a worse disaster than Syscoin and I did not even think that was possible

it has more forks that my kitchen drawer.

I was part of the ICO mined early and mined hard and I even ran a pool for it...

I was the 20 largest seed coin holder and now because of this fucked up deployment and botched staking I'm up to a measly whopping 14.53 coins

these guys should refund every single BTC they collected because of their ineptitude...

I WANT MY ICO MONEY BACK!!!!

someone will be right 

Sooo..if all my amounts are less than 1, and I'm unlocked and staking, then I do NOT need v1.0.5, correct?  

Wow, such people expecting crypto everything moon to be..

Anyone else getting an error on loading blkindex.dat? should I just start again and save wallet.dat?

Sorry I see everyone is receiving that error.. I will start clean

I agree, I've purchased seeds and so far my wallet has been removed by my antivirus as a security threat, weve been tolf the growth period will not be 7 days, had to update the wallet twice and lost precious staking time from a growth period thats not as long as it should be.

not very cool at all