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

kaicrypzen

hero member

Activity: 1344

Merit: 656

Quote from: VerusCoin on May 29, 2018, 12:42:12 PM

Quote from: kaicrypzen on May 29, 2018, 09:45:12 AM

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?

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.

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.

VerusCoin

member

Activity: 175

Merit: 12

Quote from: kaicrypzen on May 29, 2018, 09:45:12 AM

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?

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.

jl777B

full member

Activity: 476

Merit: 133

Quote from: kostepanych2 on May 29, 2018, 09:49:28 AM

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

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

Why?

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

kostepanych2

full member

Activity: 1274

Merit: 105

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

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

Why?

kaicrypzen

hero member

Activity: 1344

Merit: 656

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?

sheldon76

newbie

Activity: 2

Merit: 0

Quote from: BTC-BTC-BTC on May 29, 2018, 07:10:12 AM

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

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

poplar1987

newbie

Activity: 36

Merit: 0

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?

BTC-BTC-BTC

legendary

Activity: 1582

Merit: 1001

www.neutroncoin.com

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

Decker

member

Activity: 121

Merit: 61

Code:

Found block 11531 
mining reward 384.00000000 VRSC!
  hash: 00000000071686ea98f7bc67aea1179ec4d7f756ef58b3c558e75c97919d137d  
target: 000000000974c900000000000000000000000000000000000000000000000000
- timelocked until block 833946
Block 11531 added to chain

Mined a block, seems all is ok ...

kostepanych2

full member

Activity: 1274

Merit: 105

Quote from: VerusCoin on May 29, 2018, 01:25:43 AM

Quote from: kostepanych2 on May 29, 2018, 12:49:47 AM

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

Checking all right now. Thank you...

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

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:

Code:

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
call komodo_args.(D:\wallet\Agama-win32-x64\resources\app\assets\bin\win64\komodod.exe) NOTARY_PUBKEY.()
>>>>>>>>>> VRSC: p2p.27485 rpc.27486 magic.e2588aad 3797453485 0 coins
..Assertion failed!

Program: D:\wallet\Agama-win32-x64\resources\app\assets\bin\win64\komodod.exe
File: main.cpp, Line 3327

Expression: !setBlockIndexCandidates.empty()
VRSC exited with code 3, crashed?

Old version worked without problems.

VerusCoin

member

Activity: 175

Merit: 12

Quote from: kostepanych2 on May 29, 2018, 12:49:47 AM

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

Checking all right now. Thank you...

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

kostepanych2

full member

Activity: 1274

Merit: 105

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

VerusCoin

member

Activity: 175

Merit: 12

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.

buzzkillb

sr. member

Activity: 1021

Merit: 324

Thanks for posting the id's to check against.

sLEl

newbie

Activity: 42

Merit: 0

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?

jl777B

full member

Activity: 476

Merit: 133

Quote from: Decker on May 28, 2018, 07:43:56 AM

2 x Intel Xeon E5-2620v4 produce only 6.2MHash/s:

Code:

  "difficulty": 21696440726.16575,
  "genproclimit": 30,
  "localhashps": 6289304.848066298,
  "networkhashps": 4760488078,

seems diff is too high ...

there are thousands of systems mining. hence a high diff

jl777B

full member

Activity: 476

Merit: 133

Quote from: prague on May 28, 2018, 07:34:05 AM

Tried to mine, found a block, I see this transaction in history, but balance is seems to be 0 (even immature) and I can't export private key for generated address bXJUNCLdie1oHc622ZfhpQuc4twM2zFthN. Is it normal?

Found block 10113
mining reward 384.00000000 VRSC!
hash: 00000000040cc89f33726a57f4389239c3188a626ef5c53147290d26da2b5f13
target: 0000000004775300000000000000000000000000000000000000000000000000
- timelocked until block 662128
Block 10113 added to chain

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

prague

newbie

Activity: 23

Merit: 4

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

Quote from: prague on May 28, 2018, 07:34:05 AM

Tried to mine, found a block, I see this transaction in history, but balance is seems to be 0 (even immature) and I can't export private key for generated address bXJUNCLdie1oHc622ZfhpQuc4twM2zFthN. Is it normal?

Found block 10113
mining reward 384.00000000 VRSC!
hash: 00000000040cc89f33726a57f4389239c3188a626ef5c53147290d26da2b5f13
target: 0000000004775300000000000000000000000000000000000000000000000000
- timelocked until block 662128
Block 10113 added to chain

Decker

member

Activity: 121

Merit: 61

2 x Intel Xeon E5-2620v4 produce only 6.2MHash/s:

Code:

  "difficulty": 21696440726.16575,
  "genproclimit": 30,
  "localhashps": 6289304.848066298,
  "networkhashps": 4760488078,

seems diff is too high ...

sLEl

newbie

Activity: 42

Merit: 0

I'm running Agama on 3 PCs and updated the wallets on all 3, but I don't have the Mining tab where I can check h/s and threads on one of them. Screenshot: https://snag.gy/D9KqRA.jpg Is it normal behaviour?

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