Topic: [ANN] Verus (VRSC) - zk-SNARK privacy, CPU-mining, 50/50 POW/POS, fair launch - page 34. (Read 49718 times)

Updated to the new wallet.
Deletted all blockchain files and resynced.
And one transaction from 29.05.18 dissapeared...
Why???

Thank you!
When a fork occurs, or even when multiple people find the same block virtually instantly, only one gets accepted. When there are small forks, same thing. When there are larger forks, often the hashpower on the main chain far exceeds the other(s), and sometimes people can mine many, many blocks because there is almost no one on the chain and they lost the main one. I'm not saying that these are exactly the things that happened, just generally what can. Yesterday, as a small coin with fewer stable nodes than most, we got all of our stable nodes blocked, and many people weren't connecting properly. With the different versions coincident, we ended up with at least one large group of miners on one chain forked from the main chain. The people in our community discord helped us connect to them, and they upgraded and the fork resolved, but until people upgrade, possibly clear out their chain folder data while saving their wallet (instructions on our discord (https://discord.gg/VRKMP2S) they may have trouble getting back to the main chain.

We learned a number of things, including that we need more fixed ip nodes in different DCs, and a community member in Europe provided nodes for everyone as we were getting it resolved. I'm spending most of today making sure all is good, and once that is done, back to forward progress

Are you saying that it was also mined by someone else, and that's why it was orphaned, or something else?
Was it normal that I was on another chain despite having installed the (first) update before the deadline? It seems the second update is mandatory to mine on the right/strongest chain, if so, can you please make a(n official) post about it here?
Glad to hear that you are working on fixing issues, not that I doubted it in the first place . Keep up the good work.

Almost certainly that block was mined on a fork that was orphaned. The RPC issue was our nodes getting blocked yesterday, which led to a number of problems. We have addressed that issue, but we are still investigating sync problems right now. If you got up to date on the network and don't see the block, 99.9% (or more) chance that it was just mined on an orphaned chain.

if you didnt update recently, you could be on a fork
check the specific blockhash not just height

My wallet shows 100% sync but always is a few block backward then explorer...

For example wallet shows current block 11856.
Explorer - 11860.

Why?

There is a second update (after https://bitcointalksearch.org/topic/m.38754844) that seems mandatory because otherwise you'll be mining on another chain ... The second update is available on the website.

Yesterday, I updated according to the post. Today, I updated with the second update and all seemed fine, however when I checked one of the last blocks (getblock ) it didn't have the same hash as the one displayed in the block explorer for that block. So I removed all the files in .komodo/VRSC (I'm on Linux) apart from wallet.dat and started Agama, I then had the "RPC connection" error, so I restarted Agama and it was fine, however, the last block I minded is no longer visible. Either I mined it on another chain or I'm missing something. That block was mined at 8:xx AM UTC, does this make sense?

Had same issue; solved by:
- stop Agama
- backup (outside their folder) wallet.dat and VRSC.conf
- delete all remaining files in .komodo/VRSC/
- bring back wallet.dat and VRSC.conf
- start Agama and wait the sync

Basically, you force a reload of all blocks

All rewards over 192 Verus are time locked to mature at a random block between 129,600 and 1,181,520.

So, the miners starting now will get 0 free verus to transfer in quite a long time.

What about the strategy to attract more miners?

The latest wallet I got stuck at block 11353 and close and reopened couple times. Anyone has similar problem?

Mined a block, seems all is ok ...

Yes it's correct. I calculated yesterdays version. But it was updated...

I have an error in windows wallet:
Unable to establish RPC connection! Retries count:28.

Also I see this message in debug log:


Old version worked without problems.

Checking all right now. Thank you...

Checked. They are all correct. I'm thinking you may have tried during an update?

MD5 checksums are wrong at http://veruscoin.io.
Please correct it.

If you are on an old build, please shut down and upgrade to the new builds now at http://veruscoin.io, or from the github. Thank you.

Thanks for posting the id's to check against.

Please advise how to store the wallets? What is the best practice?

• Can it be encrypted?
• The wallet.dat file should be copied to a safe place?
• Store Public + WIF keys?

there are thousands of systems mining. hence a high diff

that is a p2sh address, the actual address is encoded in the OP_RETURN, which has the entire redeemscript

And I don't see this new address bXJUNCLdie1oHc622ZfhpQuc4twM2zFthN in the list of addresses in wallet