No need new version because in new client other fork can't be downloaded after 408714 block (already was old version checking)
If you want disconnect other fork, just add to config: banscore=10
Topic: [ANN] "Cubits"(QBT) HI POS Coin v2.1.3-Starbuck UPDATED! - page 9. (Read 69968 times)
Thanks for checking vampirus. 
With other words the main chain is save, right?
Could you create a new client that will ignore/ban connections to other clients on the wrong chain after block 408714 and/or force the download of the main chain in case the old database is used?
With other words the main chain is save, right?
Could you create a new client that will ignore/ban connections to other clients on the wrong chain after block 408714 and/or force the download of the main chain in case the old database is used?
I investigate why fork happened. It was because some users continue use old version after hardfork date and create own fork after block 408714. When they switch to new wallet, they use old database. Their forked blockchain not compatible with main chain and can't destroy it.
I think I'm on the right chain I'm on block 490233.
Now good chain 490036, and bad chain 496785
Wrong chain IPs:
142.68.155.58 Canada
99.192.64.28 Canada
64.71.72.56 United States
Wrong chain IPs:
142.68.155.58 Canada
99.192.64.28 Canada
64.71.72.56 United States
Number of blocks do not matter. Important parameter only cumulative PoS difficulty.
And in our case when too many block different in chains, one can't destroy other.
And in our case when too many block different in chains, one can't destroy other.
How can we help meanwhile? I guess fire up a client and generate as much blocks as possible while connected to 47.20.250.38?
Now good chain 490036, and bad chain 496785
Wrong chain IPs:
142.68.155.58 Canada
99.192.64.28 Canada
64.71.72.56 United States
Wrong chain IPs:
142.68.155.58 Canada
99.192.64.28 Canada
64.71.72.56 United States
I think my node is on the right chain (block 489926 for now).
Cubits was forked.
Good chain 489735 (my chain)
Wrong chain 496500
Why 489735 main chain? Because my wallet online 24/7 and Cryptopia on same chain.
To re-synch: create another Cubits.conf and add only:
addnode=47.20.250.38
maxconnections=1
remove blk0001.dat and blkindex.dat
then re-synch from scratch.
Good chain 489735 (my chain)
Wrong chain 496500
Why 489735 main chain? Because my wallet online 24/7 and Cryptopia on same chain.
To re-synch: create another Cubits.conf and add only:
addnode=47.20.250.38
maxconnections=1
remove blk0001.dat and blkindex.dat
then re-synch from scratch.
Just remembered I had a ver. 1 wallet am I doomed? Can I transfer to the newest wallet?
Been there man. but a few years late i think :p
@Meech
Share a v3 address and I'll send you 5k. Then you can keep the new client and have some additional PoS-Coins in the near future.
@vampirus
May I ask for some API tweaks in the next version?
1) At the moment "getinfo" shows the old PoW-difficulty. As PoW is obsolate, this info is not very useful. I think it's better to have the PoS-difficulty displayed. Or both, as "getdifficulty" does.
2) I really like that "Expected time to earn reward"-info displayed within the Cubitsgui.cpp. Is there any way to get this info via API as well?
Just some thoughts.
Share a v3 address and I'll send you 5k. Then you can keep the new client and have some additional PoS-Coins in the near future.
@vampirus
May I ask for some API tweaks in the next version?
1) At the moment "getinfo" shows the old PoW-difficulty. As PoW is obsolate, this info is not very useful. I think it's better to have the PoS-difficulty displayed. Or both, as "getdifficulty" does.
2) I really like that "Expected time to earn reward"-info displayed within the Cubitsgui.cpp. Is there any way to get this info via API as well?
Just some thoughts.
.
Yea sorry Meech but your alittle late on the redemption train. What did you do mine a bunch and forget about them?
The v2 redemption closed almost three years ago.
Guess there is nothing you can do with v1 anymore.
Eeek! So much for holding on to coins and forgetting you have them.
Yep. I guess I can quit out of the wallet then. It's been staking for several days. Yea sorry Meech but your alittle late on the redemption train. What did you do mine a bunch and forget about them?
Just remembered I had a ver. 1 wallet am I doomed? Can I transfer to the newest wallet?
The v2 redemption closed almost three years ago.
Guess there is nothing you can do with v1 anymore.
.
Yea sorry Meech but your alittle late on the redemption train. What did you do mine a bunch and forget about them?
The v2 redemption closed almost three years ago.
Guess there is nothing you can do with v1 anymore.
Eeek! So much for holding on to coins and forgetting you have them.
Yea sorry Meech but your alittle late on the redemption train. What did you do mine a bunch and forget about them?
Just remembered I had a ver. 1 wallet am I doomed? Can I transfer to the newest wallet?
The v2 redemption closed almost three years ago.
Guess there is nothing you can do with v1 anymore.
Just remembered I had a ver. 1 wallet am I doomed? Can I transfer to the newest wallet?
The v2 redemption closed almost three years ago.
Guess there is nothing you can do with v1 anymore.
Just remembered I had a ver. 1 wallet am I doomed? Can I transfer to the newest wallet?
The v2 redemption closed almost three years ago.
Guess there is nothing you can do with v1 anymore.
Just remembered I had a ver. 1 wallet am I doomed? Can I transfer to the newest wallet?
New version 2.1.3 https://github.com/scificrypto/CubitsV3/releases/download/v2.1.3/cubits.v213.win32.zip
Fixed Coin Control Bug and change Logo.
Fixed Coin Control Bug and change Logo.
Thanks
and I like the reverted logo
New version 2.1.3 https://github.com/scificrypto/CubitsV3/releases/download/v2.1.3/cubits.v213.win32.zip
Fixed Coin Control Bug and change Logo.
Just compiled 2.1.3. on a Raspberry, working fine on Windows as well. Great work as always, thanks! Fixed Coin Control Bug and change Logo.
Will update my node tomorrow.
New version 2.1.3 https://github.com/scificrypto/CubitsV3/releases/download/v2.1.3/cubits.v213.win32.zip
Fixed Coin Control Bug and change Logo.
Fixed Coin Control Bug and change Logo.
Nice catch, I never noticed that. I might work on fixing that one day when I get the time. Thank you for pointing that out
~Cassie
Which one use in wallet, Wallet GFX or 256x256?
I like the 256x256 its very clear and pops.
Not to be anal but the bottom left tag doesnt have the light reflection on the bottom & lower right edge like the top right tag does. But very nice.
Jump to: