seems to work fine with max 2 connections, will add hardcoded suprnova ip tbh my pings all returned the "real" 149 ip, not sure why it connected to some other one mined a block successfully and newer blocks on top synced, will monitor over the next 24 hrs edit: well, that wasnt a success: [
{
"addr" : "149.202.78.181:29100",
"services" : "00000003",
"lastsend" : 1490130416,
"lastrecv" : 1490130418,
"bytessent" : 1244,
"bytesrecv" : 6952,
"blocksrequested" : 0,
"conntime" : 1490130415,
"version" : 99008,
"subver" : "/Satoshi:3.0.0.8/",
"inbound" : false,
"startingheight" : 25713,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "76.74.170.36:29100",
"services" : "00000003",
"lastsend" : 1490130417,
"lastrecv" : 1490130417,
"bytessent" : 296,
"bytesrecv" : 6056,
"blocksrequested" : 0,
"conntime" : 1490130416,
"version" : 99008,
"subver" : "/Satoshi:3.0.0.9/",
"inbound" : false,
"startingheight" : 25713,
"banscore" : 0
}
]
|
|
|
|
Second is inner node, our vps.
You are fine also using only
maxconnection=1 , our vps
alright, will test with max connection 2 and suprnova + hardcoded vps, hopefully no fork  interesting: one node is using .9, i suppose its suprnova: [
{
"addr" : "37.19.53.219:29100",
"services" : "00000003",
"lastsend" : 1490125084,
"lastrecv" : 1490125085,
"bytessent" : 1128,
"bytesrecv" : 6661,
"blocksrequested" : 0,
"conntime" : 1490125084,
"version" : 99010,
"subver" : "/Satoshi:3.0.1/",
"inbound" : false,
"startingheight" : 25684,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "76.74.170.36:29100",
"services" : "00000003",
"lastsend" : 1490125085,
"lastrecv" : 1490125086,
"bytessent" : 235,
"bytesrecv" : 5133,
"blocksrequested" : 0,
"conntime" : 1490125085,
"version" : 99008,
"subver" : "/Satoshi:3.0.0.9/",
"inbound" : false,
"startingheight" : 25684,
"banscore" : 0
}
]
|
|
|
|
Some files to exclude... wallet as minimum.  Only one wallet copy anought... Copy peers and blockchain. wallet will be included, afaik this is necessary for the keypool (if all those addr are used it generates new ones and they cant be used with old wallet dats) Make 2 or 3 copies sequentially day by day. yeah, i want to automate  including it doesnt have a downside? Try to add --coinbase-addr=<ADDR>, then it should not over fill the keypool? or keypool=999, or something like that, (takes long time to open wallet) I have mined solo blocks with cpuminer, it never forked..... Most important, don connect bad peers, use only vps & suprmova! Delete peers.dat and then: addnode=https://suprnova.cc:29100 maxconnections=2 yes, using the coinbase mining option will not fill the keypool, but my current infrastructure doesnt have my wallet-miner-agent deployed yet (its not finished) so the miner mines using generic options (getwork) for now about the maxconnections: if i add the suprnova node, whats the second connection? this might fix my problem as well |
|
|
|
Some files to exclude... wallet as minimum. Only one wallet copy anought... Copy peers and blockchain. wallet will be included, afaik this is necessary for the keypool (if all those addr are used it generates new ones and they cant be used with old wallet dats) Make 2 or 3 copies sequentially day by day. yeah, i want to automate including it doesnt have a downside? |
|
|
|
Some files to exclude... wallet as minimum. Only one wallet copy anought... Copy peers and blockchain. wallet will be included, afaik this is necessary for the keypool (if all those addr are used it generates new ones and they cant be used with old wallet dats) |
|
|
|
May be I'll repeat my thought from Zcash forum...
If devs are going to create a PoW cryptocurrency, their main task should be to provide the community of miners with source code and binaries of P2Pool adapted to their newly created crypto. Otherwise it looks a bit scammy: the crypto is just created, almost nobody has wallets and mining SW, but just take a look - you can already mine our super-crypto at suprnova! And literally nowhere else. So come and mine it! Faster!..
But devs often doesn't care about it. So as a result we have a centralization, we have stolen blocks, 50% underpaying... So does it mean that devs are agree that miners will have such a negative experience? Looks so...
also fix solo mining, will help as well |
|
|
|
This link for you! https://mega.nz/#!iNIEmDIA!Kg9gUHuyIeTxBw0cMUy5qVdCqORay5IiG9ZDmIUvkXY Use copy\past And use 7zip. thanks! came back this morning to find it synced and with 32 peers, will wait with mining for forking fix though Now close the wallet and make zip file from whole hexx folder, next time you recover it fast Stuck issue is somehow related to a known 0.8 bug, i may have temp solution but it needs alot lot of time used to add patch into hexx code. In other words, core must be updated. will creating a zip and successfully restoring also work if the wallet didnt get closed? im thinking about scheduling a job to create a zip every x hrs and move them somewhere (hexx-2017-03-21-17-54-02.zip, hexx-2017-03-21-18-54-02.zip, and so on) im not constantly monitoring the wallet etc, im able to check it about once a day and there might be successfully created blocks before it forked so i want to get the closest backup to that fork if this doesnt work ill have to wait with mining |
|
|
|
This link for you! https://mega.nz/#!iNIEmDIA!Kg9gUHuyIeTxBw0cMUy5qVdCqORay5IiG9ZDmIUvkXY Use copy\past And use 7zip. thanks! came back this morning to find it synced and with 32 peers, will wait with mining for forking fix though |
|
|
|
most of your peers are .9 or did i miss something?
Wait 5 minutes. I give you a link to archive whith my hexx catalog. Fresh HEXX , but without wallet.dat thanks it would be great to block old clients either by default or via option, wallet stuck again |
|
|
|
|
most of your peers are .9 or did i miss something?
|
|
|
|
btw i often see such logs: 2017-03-20 22:44:59 ERROR: CTransaction::CheckTransaction() : COIN SPEND TX IN ZQ_GOLDWASSER DID NOT VERIFY!
2017-03-20 22:44:59 ERROR: CheckBlock() : CheckTransaction failed
2017-03-20 22:44:59 ERROR: ProcessBlock() : CheckBlock FAILED
2017-03-20 22:44:59 Misbehaving: 94.142.139.29:29100 (0 -> 100) DISCONNECTING
2017-03-20 22:44:59 disconnecting node 94.142.139.29:29100
2017-03-20 22:44:59 Added time data, samples 15, offset -15 (+0 minutes)
2017-03-20 22:44:59 nTimeOffset = +0 (+0 minutes)
2017-03-20 22:44:59 Moving 94.181.44.53:29100 to tried
2017-03-20 22:44:59 receive version message: /Satoshi:3.0.0.9/: version 99008, blocks=25203, us=130.83.137.28:51749, them=94.181.44.53:29100, peer=94.181.44.53:29100
2017-03-20 22:45:05 Added 24 addresses from 94.181.44.53: 14 tried, 770 new
2017-03-20 22:45:16 received block 48ad058eb5e6b4fe070b6ff1d0edd62b8acc00bd0061d7d3488a72065650ea57
2017-03-20 22:45:16 ProcessBlock: ORPHAN BLOCK, prev=7abcf24eca5ff09fb14a2a0b8b568f087dadb92a52c5adaec84cda072ac02e74
2017-03-20 22:45:33 accepted connection 79.135.242.98:56232
2017-03-20 22:45:33 send version message: version 99010, blocks=24468, us=130.83.137.28:29100, them=79.135.242.98:56232, peer=79.135.242.98:56232
2017-03-20 22:45:33 Added time data, samples 16, offset +0 (+0 minutes)
2017-03-20 22:45:33 receive version message: /Satoshi:3.0.1/: version 99010, blocks=25204, us=130.83.137.28:29100, them=163.87.1.111:29100, peer=79.135.242.98:56232
2017-03-20 22:45:58 accepted connection 92.137.65.64:55991
2017-03-20 22:45:58 disconnecting node 92.137.65.64:55991
2017-03-20 22:46:10 received block 0760429ce253c009366746f3645b8415c69d6bc4bb1a4ee4176f263ab376461f
2017-03-20 22:46:10 ProcessBlock: ORPHAN BLOCK, prev=48ad058eb5e6b4fe070b6ff1d0edd62b8acc00bd0061d7d3488a72065650ea57
2017-03-20 22:46:47 received block c164ad14e691faea22a88f8ee55a7d5adfbd683a8f028ef4fada81f922555c80
2017-03-20 22:46:47 ERROR: CTransaction::CheckTransaction() : Error: Node does not have mint zerocoin to verify, please wait until
2017-03-20 22:46:47 ERROR: CheckBlock() : CheckTransaction failed
2017-03-20 22:46:47 ERROR: ProcessBlock() : CheckBlock FAILED
2017-03-20 22:46:47 received block b16bbb824d614b9ba7f5d2aa306d7ff8999aaf8e8d9ed26305d6d0559f8e7331
2017-03-20 22:46:47 ERROR: CTransaction::CheckTransaction() : Error: Node does not have mint zerocoin to verify, please wait until
2017-03-20 22:46:47 ERROR: CheckBlock() : CheckTransaction failed
2017-03-20 22:46:47 ERROR: ProcessBlock() : CheckBlock FAILED
2017-03-20 22:46:47 received block 472e74f601cdbbeb581068817189ca9709535e52b166e4b8c6bfbc44985f7881
2017-03-20 22:46:47 ERROR: CTransaction::CheckTransaction() : Error: Node does not have mint zerocoin to verify, please wait until
2017-03-20 22:46:47 ERROR: CheckBlock() : CheckTransaction failed
2017-03-20 22:46:47 ERROR: ProcessBlock() : CheckBlock FAILED
2017-03-20 22:46:47 received block b06cda54cea9aee01deaafb1787e6de499faa4a7ed0a57e79bbb5ce6942d77ab
2017-03-20 22:46:47 ERROR: CTransaction::CheckTransaction() : Error: Node does not have mint zerocoin to verify, please wait until
2017-03-20 22:46:47 ERROR: CheckBlock() : CheckTransaction failed
2017-03-20 22:46:47 ERROR: ProcessBlock() : CheckBlock FAILED
2017-03-20 22:46:47 received block 5654084dfc8ec9816f383121e1d6666ad5aeffd55585cd004de21dca98c476ae
2017-03-20 22:46:49 connection from 76.74.170.36:38325 dropped (banned) does that mean other peers are on a different fork? i have moved the wallet.dat and started over with a fresh copy of the chain files, hexx folder cleared, so it should not be me who is working on a fork? |
|
|
|
nah no backup, luckily i had moved most of my funds to exchange already, only about 50 hexx on wallet Lucky, i will tip you the 50!Dont lose the wallet, i will buy it!!!!!!!!!!!! 100HXX Btw. I have zcoin solo version.. Useless at its hashrate , but still. i still have the wallet file, i have gone through some calculations, the exact amount had to be 37.5XX (including the latest forked block reward) i can pm you a link for the wallet dat file, afaik its unencrypted zcoin solo version is a modified version of the (current) zcoin src to enable proper solo mining? i agree it might not be profitable currently, but working solo support is always a good thing, will tip you back  |
|
|
|
nah no backup, luckily i had moved most of my funds to exchange already, only about 50 hexx on wallet |
|
|
|
Pm log and i will seek it soon.
Zcoin has all these problems and more, most of related to 0.8 old core.
Updates needed.
log is appended in my original post at the bottom, yeah i already suspected its a zcoin issue, thanks for the support Do this for now: Zip whole hxx folder. When corrupted or something you have insta backup near last block! Zcoin 5days chain dl, i did learn to do it.. every day. Im away for a while, then will look more. Edit: It is a fork! So there is another user stuck at your chain.. haha damn also, when clearing the hexx folder besides wallet.dat and pasting the chain files from github after some time when the wallet (possibly) reaches my forked block i get this:  after clicking ok it crashes / force closes |
|
|
|
Pm log and i will seek it soon.
Zcoin has all these problems and more, most of related to 0.8 old core.
Updates needed.
log is appended in my original post at the bottom, yeah i already suspected its a zcoin issue, thanks for the support |
|
|
|
Use hexx.suprnova.cc
i would like to solo mine, and rather not use a pool |
|
|
|
sometimes the wallet gets stuck for me (3.0.1.0 windows), it recognizes that there are newer blocks but doesnt sync, peer count is 1 in that case (usually more), upnp for portforwarding is enabled
Never seen wallet getting stuck at top of chain. You mean like when starting after 24hours? i mean:  just restarted the wallet (had to kill it via task manager), 8 connections but syncing doesnt move forward, stays on block 24916 you need debug logs? it seems to be the time my wallet mined a block edit: its slowly loosing peer connections, now back to 5 and reducing further That tells you forked! You have more than 1 hxx wallet at your homenetwork? Debug needed to confirm fork. nope, only this single one, the same computer runs a zcoin syncing wallet as well (16 weeks to go), but that cant be the problem? also: how to prevent this forking? |
|
|
|
it did happen multiple times, i would like to get it fixed rather to restart from bootstrap every time it happens |
|
|
|
sometimes the wallet gets stuck for me (3.0.1.0 windows), it recognizes that there are newer blocks but doesnt sync, peer count is 1 in that case (usually more), upnp for portforwarding is enabled
Never seen wallet getting stuck at top of chain. You mean like when starting after 24hours? i mean: just restarted the wallet (had to kill it via task manager), 8 connections but syncing doesnt move forward, stays on block 24916 you need debug logs? it seems to be the time my wallet mined a block edit: its slowly loosing peer connections, now back to 5 and reducing further edit2: i have copied the last few hours of debug log over here: http://pastebin.com/KAJYerJx |
|
|
|
|
sometimes the wallet gets stuck for me (3.0.1.0 windows), it recognizes that there are newer blocks but doesnt sync, peer count is 1 in that case (usually more), upnp for portforwarding is enabled
|
|
|
|
|
Show Posts
