what a mess 2.0.2 2.0.3 2.0.5 2.0.6 2.0.7 2.0.8 2.1.0 and now 2.1.1 ?!
OMG it was like 6-7 wallets for 1 week ....
Yes, they could have surrended after the second or third failure, but they has been /will keep working until find the solution. This made me very comfortable about having a nice amount of this coin.
|
|
|
This scam phase is already finished. Everyone of you who has bought WARP over 3k could go back home with your coins. Next acumm level near 500 sat. No more news till next phase are expected...
|
|
|
Very good post, JK, but I think that you can also use kH or use one of the algos as normalization factor considering its value as 1 and dividing all the rest by it. Can you confirm, crackfoo??
|
|
|
Next step of evolution in trollmetamorphose: trolling before announcement! Announcement was done 15th January... I have some of this shit I was not able to dump over 30k satoshis in the first scam, sorry, phase. Shapetwist, do you think you are going to be capable to pump it again over 25k satoshis? When I enter in these scamcoins I need x10 or die
|
|
|
Okay. Just woke up. I just noticed that MN Info page now shows the invaluable block hash! http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.htmlAnd I can confirm that my controller wallet & my MN's matched the blockhash of the MN page. getblockhash 262000 2944973b1001b91f6766d4a672b226427460d06741eefe1f32c21d175608e272 which nodes in conf file, jakiman?
|
|
|
Seems that my fork and the maternode payments fork is at least the same Last half our block (18.30 GMT+1) getblockhash 261725  77bbad43c4ff0232dbd8eb324b332f0331863abc3cd2daa9b86a0ee2baa78ca7 You are on the wrong fork, current block at 13:04 EST is 261716 with the hash of bff7fa213177685cc9fb8da1e5160ae2ce6656208492c065d14a82d9e16ef3bb Seems that I'm on the same fork of all my MN's and of http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.htmlWrong and rigth fork? For the moment I think there is only a lot of forks. 261716 to 261769 in 26 min??? Well, maybe DN_masternode_payments is also in the wrong fork.
|
|
|
Seems that my fork and the maternode payments fork is at least the same Last half our block (18.30 GMT+1) getblockhash 261725  77bbad43c4ff0232dbd8eb324b332f0331863abc3cd2daa9b86a0ee2baa78ca7
|
|
|
My last block, I'm receiving MN's payments so at least my wallet and my MN's seem to be in the same fork...
13:43:29 getblockhash 261412 13:43:29 9d58ffeaa836d7dbb5151d8b33539523eb4c636976197b4d7d06481a7e6756f6
|
|
|
We are in the same chain, jakiman, and seems to be the same that the MN's, but I'm also a bit confused now.
|
|
|
which is the correct block that its up to. i am i on 261357 so is masternode payments page but you lot are higher? whos right?
Yeah, seems my controller wallet is ahead. I'll resync and report back. My MN's are on the right chain I guess then? (below) (same as MN page) getblockhash 261357 a45b5debbef34dfdd92bd8b84b8570ffda24eba7d330ae76a6923307f62e7ff7 Same here, seems like the first in update are forked. Will do the same and inform.
|
|
|
Synced as said, now let's start stacking, finger crossed Edit: Only v2020 peers and no more crazy stacking. Sounds good
|
|
|
11:55:01  getblockhash 260635
11:55:01  3442c235d521c637985ad71893f2c3744780928f7705404d00550c15c5ead769
Could you please share some of the nodes that you're connecting to? I'm stuck on block 260584. I've got there resyncing from scratch (deleting everything except masternodes.conf and wallet.dat) and using this conf file: addnode=108.61.151.69 addnode=173.245.158.8 addnode=coin-server.com addnode=185.86.151.173 addnode=185.86.149.212 addnode=dnetxef3rmouy5qo.onion:989 addnode=dnetxcvx4iqeunnk.onion:989 addnode=dnetxn4m5kfh4xhr.onion:989 addnode=dnetxu5edp35e4rm.onion:989 addnode=y5kcscnhpygvvnjn.onion:989 addnode=5bmhtjvn2jvwpiej.onion:989 addnode=pyfdxkazur3iib7y.onion:989 addnode=ok3ym5zy6m5klimk.onion:989 addnode=i6vpvzk2jxuqqs5f.onion:989 addnode=bgdhpb76fkbw5fmg.onion:989 addnode=gtlqzb5zbws5di7g.onion:989 addnode=f7j2m26rptm5f7af.onion:989 addnode=dnetzj6l4cvo2fxy.onion:989 addnode=s3v3n7xhqafg6sb7.onion:989 With only the nodes thata appear in Ops in this moment. Thanks for nodes, but they don't get me past 259200, unfortunately. Are you trying to sync your controller wallet or your MN's??
|
|
|
11:55:01  getblockhash 260635
11:55:01  3442c235d521c637985ad71893f2c3744780928f7705404d00550c15c5ead769
Could you please share some of the nodes that you're connecting to? I'm stuck on block 260584. I've got there resyncing from scratch (deleting everything except masternodes.conf and wallet.dat) and using this conf file: addnode=108.61.151.69 addnode=173.245.158.8 addnode=coin-server.com addnode=185.86.151.173 addnode=185.86.149.212 addnode=dnetxef3rmouy5qo.onion:989 addnode=dnetxcvx4iqeunnk.onion:989 addnode=dnetxn4m5kfh4xhr.onion:989 addnode=dnetxu5edp35e4rm.onion:989 addnode=y5kcscnhpygvvnjn.onion:989 addnode=5bmhtjvn2jvwpiej.onion:989 addnode=pyfdxkazur3iib7y.onion:989 addnode=ok3ym5zy6m5klimk.onion:989 addnode=i6vpvzk2jxuqqs5f.onion:989 addnode=bgdhpb76fkbw5fmg.onion:989 addnode=gtlqzb5zbws5di7g.onion:989 addnode=f7j2m26rptm5f7af.onion:989 addnode=dnetzj6l4cvo2fxy.onion:989 addnode=s3v3n7xhqafg6sb7.onion:989 With only the nodes thata appear in Ops in this moment.
|
|
|
My wallet is unlocked, but it says "Staking is not active". What would cause this?
If any of the following conditions are met, then the wallet will not activate staking: vNodes.empty() || IsInitialBlockDownload() || pwallet->IsLocked() || !fMintableCoins || nReserveBalance >= pwallet->GetBalance() || !masternodeSync.IsSynced() !masternodeSync.IsSynced means that if a masternode is activated there is no staking on all the addresses of the node? @boris lastest block getblockhash 260600 22eb2b92728af947dda8b3eca84d302fc7ed0a17b0d87a77b33b3eb39a0a9acb Same here.
|
|
|
whats the latest block? 2 have managed to sync to 260203 but further up the block count is higher and so is it on masternode payments page. 2 nodes resynced at 26369 so guess it wasnt.
whats going on??
just them 4 nodes are on different chians. others are stuck at 259200 and all the wallets are on the latest.
18:15:11  getblockhash 260592
18:15:11  86d36ec67837bfdcb782c898b2b76ee2e148a47278e39b1284fd06809c5f47af At least in my fork
|
|
|
getblockhash 260330
e074e7d371953ad6cb34b64100297aafba8e93bf691fa50b5b56eb935c8253f4
Also get the same Same here also, found 5 POS and 1 orphan since the last resync. Things seems to be a bit more stable now, almost all my peers are in v2010
|
|
|
latest
getblockhash 260263
1cc8293791cff93ad2d7d1c9088783839557b2246412c15d3febf35d9b281d69
Coincident after resync with the last node list. 13:39:23  getblockhash 260263
13:39:23  1cc8293791cff93ad2d7d1c9088783839557b2246412c15d3febf35d9b281d69
Will tell you if everythign continues working when I start to stack. Salute
|
|
|
getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4
this is what I get... anyone could confirm please?
I'm updating again, I would tell you as soon as synced again with the new list of nodes of the config file.
|
|
|
Yes, I know, my controller wallet seems to have forked some minutes ago.
|
|
|
Hi all, Could you please check this block to be sure we are all on the same chain? getblockhash 260200 c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12 I hope it's the one Mine also has that hash, so looks good Thank you! great news My controller wallet is on the right chain and now starting up my MNs also. I remember you had a transaction issue, did you get it? I have the older one, looks like the changes are necessary as there are a lot of warnings and errors in the logs after the PoW blocks end. Compiling.... Done ... Let's see... $ darknet-cli getblockhash 259880 f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098
Yay!!! I am up to this block now... does anyone want to confirm I am on the right chain? darknet-cli getblockhash 260209 c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4 Thought scripting everything would be overkill for the small amount of masternodes I have ( < 10 ) , but now considering it... At least I have clusterssh set up now... Time to set up masternodes... I have the same. How can we get rid of orphan transactions in the gui? They are always ontop, so I can't see my recent transactions
interested too... I got a stacking block and it replaced an old orphaned one... Anyone more can take a look at this: getblockhash 259880 f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098 like them but getblockhash 260209 f47f44ca42bf37918cce19e638ba3d7bbf10f6da24510b2eebf17c34c3700a27 Instead of their value. I'm forked???
|
|
|
|