Kinda worried that botnets are gaming the system, even with funded ABN.
They have 3m+ hashpower and still gain top subsidy even with a 63% hashrate penalty.
and 65+ machines
Yeah, I see the non funded guys are solving 65% of the blocks, and diff did rise above 7000 recently. I think we should let it play out for 30 days and in the mean time we can discuss it. I'm open to hearing any opinions. On one hand it just means that non funded miners are willing to take a penalty to keep mining, and it sort of points to our funded miners not having as many mining machines (which makes sense as they are different people - probably investors vs. miners). The question is, are we really seeing "bot-net" activity; I would think not really, as those are the miners that just want to mine (as compared to a nefarious group that wants to copy biblepay out to 300 machines in a school, etc). These miners do have to create pool accounts and show up in the leaderboard. So we have to think of are we creating a fair environment for everyone and are the newbies happy also. |
|
|
|
Dave_bbp asked about shrinkdebug - its called "-shrinkdebugfile=1" now. Please try that.
Thanks, will try that. I think I tested every combination yesterday with the 4.c version and for me the only way to mine without random (silent) crashes is the compatibility mode. So it looks like this: dual workerID + compatibility mode: no problems, but always stays at the funded ABN (doesn't change back, even with unlocked wallet and enough abnweight) dual workerID + legacy Win10: random silent crashes 1 worker ID + compatibilty mode: no problems, runs with non-funded ABN 1 workerID + legacy Win10: random silent crashes btw: I don't have a restored wallet. Today in the evening I'm gonna try the 4.d version.  Ok, to revisit the govobj data-- When you erased the chain data, did you also delete all of your .dat files btw? Its worth at least doing this at least once to rule it out (IE manually delete the .dat files like mnc* and gov* and mnp* and then start with -erasechain=1). Then move to step 2. 2) If you have another silent crash after deleting the .dat files, and trying 4d version: At that point you will need to go into our testnet thread and run the Testnet version for windows against prod. It has a stack trace feature and it should tell us why windows10 is crashing for you. (If it doesnt work, we will have to work through the process of getting the stacktrace set up on windows 10 for you). 3) This brings up another issue: Does your wallet have a CPK? If not, can you please create one with 'exec cpk nickname'? That could be the silent crash. 4) Regarding switching back from funded abn to non- Ill test that on my dev node; I remember specifically testing that and it was working, will get back. 4b) On the non-switch, please ensure your workerid=non_funded (IE=0), and workeridfunded=funded (IE = 1) in the pool? Two distinct workerids? 4c) When it continues to mine in funded mode, does the poolinfo3 show the workerid name you expect? |
|
|
|
What I wanted to share today is something just as powerful as miracles: the authority that God gives us. As believers, we don't need to learn to fight the flesh to protect ourselves, when we know God's word intimately. When you know your authority as a Christian, you can most certainly rebuke the root cause of the attack, and nothing will by any means hurt you. I share this in the spirit of raising your faith. None of this will be true if you don't believe the word of God, and it won't be true if you don't lean on the word of God with full faith. Put on the Full Armor of God: https://wiki.biblepay.org/Full_Armor_of_God |
|
|
|
|
BiblePay
1.4.4.2d - Leisure Upgrade
- Add split denominated GSC transmissions for more versatile change
** Mac, Windows and Linux are ready for download **
|
|
|
|
|
Dave_bbp asked about shrinkdebug - its called "-shrinkdebugfile=1" now. Please try that.
|
|
|
|
I wonder if both cases of our windows 10 crash came from restored wallets with orphaned CPKs?
that's a possibility! I have dual-mining set up and configured, funded ABN kicked right on (because of low weight obviously) So I will watch for the transition from funded to non-funded when my weight re-ups. CPK is created (exec cpk nickname) in RPC, how can I keep a track of the address for that? Its in your address book, under Christian-Public-Key. |
|
|
|
|
I wonder if both cases of our windows 10 crash came from restored wallets with orphaned CPKs?
|
|
|
|
Ok, and one thing that appears weird in your sentgsc report is you don't show any ABNs over the last 7 days. But I believe you said you were testing/spending ABNs. Was this wallet imported with non-conventional commands, or is it the original wallet? Do you have a CPK? Did you 'exec cpk your_nickname' (as I dont see you in the leaderboard). Or long shot, did you join pog and then unjoin, and maybe unjoin your cpk? The sentgsc report uses the CPK to find ABNs and GSCs. (Also, do you have a Christian-Public-Key) set up in your address book? Finally, one more clue - if you go to coin control (click Send Money | Coin Control) - if its not enabled you can enable coin control in Settings. Please see your coins listed by address. Notice how your 397,179 coin has a depth of (most likely 1) now? That means it was spent on something. You should be able to find out on what - but if you cant I can help you with RPC commands, etc. EDIT: Could you please paste your public Christian-public-key receive address? Let me do some reporting from the pool side? I see what you're saying here and I might know the issue actually. I did create a CPK nickname, and join POG before. Since then I've unjoined POG and I no longer see my CPK, or many other of my recieve addresses in my wallet anymore. I did import my wallet from a backup at one point because of a corrupted wallet.dat during an upgrade. So, it appears that my wallet.dat is still recieving transmissions from old recieving keys that are most likely tagged in the wallet itself, but not showing on QT. (I only have 1 recieving key as of now and that was the one created to recieve coin from SouthXchange. Ok, that explains the wonkiness then. Sorry if I came across as harsh, I just want to make sure people don't get the impression we are hiding any BBP in hidden ABNs or doing anything funny here  . So, in your case, I highly recommend backing up wallet.dat, creating a brand new wallet.dat, then copy the receive address key from the new one to the clipboard, then send all your balance to your new wallet, and create a brand new exec cpk nickname (you dont necessarily have to join pog)- but this would ensure you have a good CPK address book entry tied to one CPK in the wallet. This is because it would be highly questionable for us to test ABN and edge cases with a wallet that has been modified etc. I was thinking this is the most simple fix. I will try it out! As for sending to a new wallet, if I created a mobile (android) wallet and wrote the phrase down, can I go into my phone and get the (new) wallet.dat from there and move it to my PC? No, the mobile wallet is in a different format, plus its easier to just work with the files right in front of you (in contrast to sending them over the network etc). EDIT: You can do this by closing BBP, renaming wallet.dat to wallet.dat_old, starting bbp, get the new key to the clipboard, close bbp, copy wallet.dat to wallet.dat_new, rename wallet.dat_old back to wallet.dat, starting, send the money to your key by pasting the clipboard value, close bbp, and move to your new wallet.dat, and restart. Or you can send the BBP to your mobile wallet, and delete your old wallet.dat file and then send it from your mobile back to your PC. I went with the first method, hiding the old wallet.dat and then using a new one. Encrypted and backed up, all coins stored on new wallet. What's the best method to insure I get a CPK? Since you will be starting with a new wallet.dat, there is no mistake that can be made. You start over and follow the start guide: https://wiki.biblepay.org/Quick_Start |
|
|
|
Ok, and one thing that appears weird in your sentgsc report is you don't show any ABNs over the last 7 days. But I believe you said you were testing/spending ABNs. Was this wallet imported with non-conventional commands, or is it the original wallet? Do you have a CPK? Did you 'exec cpk your_nickname' (as I dont see you in the leaderboard). Or long shot, did you join pog and then unjoin, and maybe unjoin your cpk? The sentgsc report uses the CPK to find ABNs and GSCs. (Also, do you have a Christian-Public-Key) set up in your address book? Finally, one more clue - if you go to coin control (click Send Money | Coin Control) - if its not enabled you can enable coin control in Settings. Please see your coins listed by address. Notice how your 397,179 coin has a depth of (most likely 1) now? That means it was spent on something. You should be able to find out on what - but if you cant I can help you with RPC commands, etc. EDIT: Could you please paste your public Christian-public-key receive address? Let me do some reporting from the pool side? I see what you're saying here and I might know the issue actually. I did create a CPK nickname, and join POG before. Since then I've unjoined POG and I no longer see my CPK, or many other of my recieve addresses in my wallet anymore. I did import my wallet from a backup at one point because of a corrupted wallet.dat during an upgrade. So, it appears that my wallet.dat is still recieving transmissions from old recieving keys that are most likely tagged in the wallet itself, but not showing on QT. (I only have 1 recieving key as of now and that was the one created to recieve coin from SouthXchange. Ok, that explains the wonkiness then. Sorry if I came across as harsh, I just want to make sure people don't get the impression we are hiding any BBP in hidden ABNs or doing anything funny here . So, in your case, I highly recommend backing up wallet.dat, creating a brand new wallet.dat, then copy the receive address key from the new one to the clipboard, then send all your balance to your new wallet, and create a brand new exec cpk nickname (you dont necessarily have to join pog)- but this would ensure you have a good CPK address book entry tied to one CPK in the wallet. This is because it would be highly questionable for us to test ABN and edge cases with a wallet that has been modified etc. I was thinking this is the most simple fix. I will try it out! As for sending to a new wallet, if I created a mobile (android) wallet and wrote the phrase down, can I go into my phone and get the (new) wallet.dat from there and move it to my PC? No, the mobile wallet is in a different format, plus its easier to just work with the files right in front of you (in contrast to sending them over the network etc). EDIT: You can do this by closing BBP, renaming wallet.dat to wallet.dat_old, starting bbp, get the new key to the clipboard, close bbp, copy wallet.dat to wallet.dat_new, rename wallet.dat_old back to wallet.dat, starting, send the money to your key by pasting the clipboard value, close bbp, and move to your new wallet.dat, and restart. Or you can send the BBP to your mobile wallet, and delete your old wallet.dat file and then send it from your mobile back to your PC. |
|
|
|
Rob,
i'll add it as a feature request on github later, but mining for me is a pain currently with how ABN consolidates the coins.
I did a bankroll and split a million bbp utxo into smaller chunks with the intention of letting them age. I look later and everything was consolidated onto the cpk address.
Is there any way to have the ABN transaction bankroll into chunks?
Yes, that sounds like a good idea, we should do that. Yes, please add the issue so I don't forget about it, but Ill add it to my list now. |
|
|
|
Ok, and one thing that appears weird in your sentgsc report is you don't show any ABNs over the last 7 days. But I believe you said you were testing/spending ABNs. Was this wallet imported with non-conventional commands, or is it the original wallet? Do you have a CPK? Did you 'exec cpk your_nickname' (as I dont see you in the leaderboard). Or long shot, did you join pog and then unjoin, and maybe unjoin your cpk? The sentgsc report uses the CPK to find ABNs and GSCs. (Also, do you have a Christian-Public-Key) set up in your address book? Finally, one more clue - if you go to coin control (click Send Money | Coin Control) - if its not enabled you can enable coin control in Settings. Please see your coins listed by address. Notice how your 397,179 coin has a depth of (most likely 1) now? That means it was spent on something. You should be able to find out on what - but if you cant I can help you with RPC commands, etc. EDIT: Could you please paste your public Christian-public-key receive address? Let me do some reporting from the pool side? I see what you're saying here and I might know the issue actually. I did create a CPK nickname, and join POG before. Since then I've unjoined POG and I no longer see my CPK, or many other of my recieve addresses in my wallet anymore. I did import my wallet from a backup at one point because of a corrupted wallet.dat during an upgrade. So, it appears that my wallet.dat is still recieving transmissions from old recieving keys that are most likely tagged in the wallet itself, but not showing on QT. (I only have 1 recieving key as of now and that was the one created to recieve coin from SouthXchange. Ok, that explains the wonkiness then. Sorry if I came across as harsh, I just want to make sure people don't get the impression we are hiding any BBP in hidden ABNs or doing anything funny here . So, in your case, I highly recommend backing up wallet.dat, creating a brand new wallet.dat, then copy the receive address key from the new one to the clipboard, then send all your balance to your new wallet, and create a brand new exec cpk nickname (you dont necessarily have to join pog)- but this would ensure you have a good CPK address book entry tied to one CPK in the wallet. This is because it would be highly questionable for us to test ABN and edge cases with a wallet that has been modified etc. |
|
|
|
Ok, and one thing that appears weird in your sentgsc report is you don't show any ABNs over the last 7 days. But I believe you said you were testing/spending ABNs. Was this wallet imported with non-conventional commands, or is it the original wallet? Do you have a CPK? Did you 'exec cpk your_nickname' (as I dont see you in the leaderboard). Or long shot, did you join pog and then unjoin, and maybe unjoin your cpk? The sentgsc report uses the CPK to find ABNs and GSCs. (Also, do you have a Christian-Public-Key) set up in your address book? Finally, one more clue - if you go to coin control (click Send Money | Coin Control) - if its not enabled you can enable coin control in Settings. Please see your coins listed by address. Notice how your 397,179 coin has a depth of (most likely 1) now? That means it was spent on something. You should be able to find out on what - but if you cant I can help you with RPC commands, etc. EDIT: Could you please paste your public Christian-public-key receive address? Let me do some reporting from the pool side? |
|
|
|
Good morning, Rob! So far no crashes on the new client, however my ABN has all been eaten and there are no blocks on pool with my name to show proof of it. exec sentgsc also shows nothing. This is what I see in RPC.
09:56:24

getmininginfo
09:56:24

{
"blocks": 131877,
"currentblocksize": 3924,
"currentblocktx": 2,
"difficulty": 4693.118496139644,
"errors": "",
"pooledtx": 2,
"chain": "main",
"genproclimit": 7,
"networkhashps": 546824.3943490735,
"hashps": 114236.3860311637,
"minerstarttime": "07-14-2019 23:54:02",
"hashcounter": 5599995588,
"pooledtx": 2,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "Pool mining with eyeseven; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-15-2019 13:53:34; RMC_07-15-2019 13:53:38; RMC_07-15-2019 13:53:43; RMC_07-15-2019 13:54:06; RMC_07-15-2019 13:53:43; RMC_07-15-2019 13:53:37; RMC_07-15-2019 13:56:14; ",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
09:56:27

exec sentgsc
09:56:27

{
"Total": 0
}
09:56:30

exec getabnweight
09:56:30

{
"Command": "getabnweight",
"version": 2.5,
"weight": 36073.44414351852,
"total_required": 401154
}
09:56:37

exec createabn 125000 1
09:56:37

{
"Command": "createabn",
"xml": "",
"err": "Sorry, your coin-age is too low to create an anti-botnet transaction.",
"age_data": "0.9870(0.00),194171.3572(83596.91),2507.4500(7426.55),558.0000(1512.18),1000.0000(713.53),1000.0000(722.49),534.8400(3184.28),693.0000(442.74),1000.0000(4717.65),1000.0000(4715.35),0.9914(0.00),194712.4421(131455.39),1000.0000(2714.46),",
"vin_coin_age_data": "\nGetVINCoinAge: ",
"coin_age_data_pre_select": "1000.0000(2.74)=[2738.39] depth=581, <ROW>1000.0000(0.75)=[747.87] depth=160, <ROW>5.2559(7.17)=[35.87] depth=1525, <ROW>0.9840(4.19)=[0.00] depth=890, <ROW>1000.0000(16.52)=[16524.72] depth=3459, <ROW>969.1900(12.99)=[12583.46] depth=2736, <ROW>0.9781(0.01)=[0.00] depth=0, <ROW>397178.0678(0.01)=[3443.13] depth=0, <ROW>",
"total_audited_weight": 0,
"tx_create_error": "Sorry, your coin-age is too low to create an anti-botnet transaction."
}
1) Please paste any long command outputs within code tags - thanks. I just added them above for an example. 2) Other than ABNs spending coin-age, and GSCs spending coin-age, you can also spend coin age by Spending BBP. Notice how your 397,178 was spent one block ago. What was it spent on? (This lowered your coin age down to 36k). Apologies for the code tags! I'm not sure what it was spent on, my balance never leaves my wallet or moves in any way shape or form unless its mined coins moving from pool to my wallet. Do you want to check? You can click on the transaction list in QT in descending order by date, and see what the 397,179 was spent on. If it was a GSC you just accidentally sent without realizing it, you can rerun exec sentgsc in 6 blocks (transactions take about 5 to confirm and age). |
|
|
|
Good morning, Rob! So far no crashes on the new client, however my ABN has all been eaten and there are no blocks on pool with my name to show proof of it. exec sentgsc also shows nothing. This is what I see in RPC.
09:56:24

getmininginfo
09:56:24

{
"blocks": 131877,
"currentblocksize": 3924,
"currentblocktx": 2,
"difficulty": 4693.118496139644,
"errors": "",
"pooledtx": 2,
"chain": "main",
"genproclimit": 7,
"networkhashps": 546824.3943490735,
"hashps": 114236.3860311637,
"minerstarttime": "07-14-2019 23:54:02",
"hashcounter": 5599995588,
"pooledtx": 2,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "Pool mining with eyeseven; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-15-2019 13:53:34; RMC_07-15-2019 13:53:38; RMC_07-15-2019 13:53:43; RMC_07-15-2019 13:54:06; RMC_07-15-2019 13:53:43; RMC_07-15-2019 13:53:37; RMC_07-15-2019 13:56:14; ",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
09:56:27

exec sentgsc
09:56:27

{
"Total": 0
}
09:56:30

exec getabnweight
09:56:30

{
"Command": "getabnweight",
"version": 2.5,
"weight": 36073.44414351852,
"total_required": 401154
}
09:56:37

exec createabn 125000 1
09:56:37

{
"Command": "createabn",
"xml": "",
"err": "Sorry, your coin-age is too low to create an anti-botnet transaction.",
"age_data": "0.9870(0.00),194171.3572(83596.91),2507.4500(7426.55),558.0000(1512.18),1000.0000(713.53),1000.0000(722.49),534.8400(3184.28),693.0000(442.74),1000.0000(4717.65),1000.0000(4715.35),0.9914(0.00),194712.4421(131455.39),1000.0000(2714.46),",
"vin_coin_age_data": "\nGetVINCoinAge: ",
"coin_age_data_pre_select": "1000.0000(2.74)=[2738.39] depth=581, <ROW>1000.0000(0.75)=[747.87] depth=160, <ROW>5.2559(7.17)=[35.87] depth=1525, <ROW>0.9840(4.19)=[0.00] depth=890, <ROW>1000.0000(16.52)=[16524.72] depth=3459, <ROW>969.1900(12.99)=[12583.46] depth=2736, <ROW>0.9781(0.01)=[0.00] depth=0, <ROW>397178.0678(0.01)=[3443.13] depth=0, <ROW>",
"total_audited_weight": 0,
"tx_create_error": "Sorry, your coin-age is too low to create an anti-botnet transaction."
}
1) Please paste any long command outputs within code tags - thanks. I just added them above for an example. 2) Other than ABNs spending coin-age, and GSCs spending coin-age, you can also spend coin age by Spending BBP. Notice how your 397,178 was spent one block ago. What was it spent on? (This lowered your coin age down to 36k). |
|
|
|
Maybe this is a known issue, but i get a runtime error when opening the leaderboard.
"This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
Then biblepay crashes.
Mart
I tried to reproduce it with both synced and out-of-sync clients and I could not do it. Is this happeening consistently or randomly? After startup or at any moment? I think i know why it happened, although i don't see why this would relate to that. Today i logged in on my vps and was in shock that i had around 9 million bbp and was mining around 7480 bbp each 10 minutes. First i thought this was real, but later I realised that something is not okay here. Difficulty was around 2, so probably i was mining on a different chain for like 2 weeks... I think that this caused it somehow. After that i reindexed all the blocks and now it shows, a more normal bbp amount, but still it doesn't match with the transaction list. Very strange. Mart EDIT: copied a backup wallet file and now it is correct for so far i remember. That wallet got corrupt too i think.... It seems similar to what happened to me. There should be something in common that had caused it. PD: However, it seems I am not mining anymore: {
"blocks": 131873,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 7834.995703879642,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 3,
"networkhashps": 535584.1039374968,
"hashps": 0,
"minerstarttime": "07-15-2019 10:40:32",
"hashcounter": 0,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
"poolinfo5": "Internal ABN: Invalid 1563197230; ",
"abninfo": "No block to mine... Please wait... 1563197290; No block to mine... Please wait... 1563197294; No block to mine... Please wait... 1563197297; ",
"gsc_errors": "low abn weight 0",
"poolmining": false,
"pool_url": "https://pool.biblepay.org/",
"required_abn_weight": 125000
}
And the config file: gen=1
genproclimit=3
minersleep=0
pool=https://pool.biblepay.org
workerid=My old and unique username under workers in 'pool' website.
In this case it looks like its the low ABN weight. (You either must increase abn weight, or mine against a Funded pool worker - one that is created with "1" in the pool for funded). Please paste 'exec getabnweight 125000' and we can see if your abn weight is too low to mine? Thank you for your work, and help. This is the output: {
"Command": "getabnweight",
"version": 2.5,
"weight": 99568.23384259258,
"total_required": 179548,
"weight 125000.00": 99568.23384259258,
"total_required 125000.00": 179548
}It seems for me that I need to create a new worker with a funded ABN? For how long? Yeah, so this is showing that you have 99,568 ABN weight, but 125,000 is required. So what you can do is either add more bbp, or wait for this coin-age to age longer, or add a Funded worker to the pool and change your "workerid=" to the funded workerid. See this guide to see how to add a funded worker: https://wiki.biblepay.org/Quick_Start |
|
|
|
|
BiblePay
1.4.4.2c-Leisure Upgrade
- Enhance exec sentgsc report to include ABN info; show 7 days of
history
(This is the same version announced yesterday). Mac/Linux/Windows have been released.
** NOTE: Great news on Windows-10 debugging the prior crash (that we hope is already resolved).
We have a stacktrace feature coming out in the next version that will potentially point us to the exact root cause. Please let us know if it reappears in 1442c **
|
|
|
|
Maybe this is a known issue, but i get a runtime error when opening the leaderboard.
"This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
Then biblepay crashes.
Mart
I tried to reproduce it with both synced and out-of-sync clients and I could not do it. Is this happeening consistently or randomly? After startup or at any moment? I think i know why it happened, although i don't see why this would relate to that. Today i logged in on my vps and was in shock that i had around 9 million bbp and was mining around 7480 bbp each 10 minutes. First i thought this was real, but later I realised that something is not okay here. Difficulty was around 2, so probably i was mining on a different chain for like 2 weeks... I think that this caused it somehow. After that i reindexed all the blocks and now it shows, a more normal bbp amount, but still it doesn't match with the transaction list. Very strange. Mart EDIT: copied a backup wallet file and now it is correct for so far i remember. That wallet got corrupt too i think.... Great, glad you are back on now. Btw, on the wallet, although its possible it got corrupted, the more likely scenario is when you mined on a fork you deposited a lot of inbound/outbound tx's that are now orphans. You can usually clean them up with -zapwallettxes=1. But since you restored from the backup, the internal -rescan=1 probably took care of it already. (It does this automatically when it realizes it needs a rescan). |
|
|
|
Maybe this is a known issue, but i get a runtime error when opening the leaderboard.
"This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
Then biblepay crashes.
Mart
I tried to reproduce it with both synced and out-of-sync clients and I could not do it. Is this happeening consistently or randomly? After startup or at any moment? I think i know why it happened, although i don't see why this would relate to that. Today i logged in on my vps and was in shock that i had around 9 million bbp and was mining around 7480 bbp each 10 minutes. First i thought this was real, but later I realised that something is not okay here. Difficulty was around 2, so probably i was mining on a different chain for like 2 weeks... I think that this caused it somehow. After that i reindexed all the blocks and now it shows, a more normal bbp amount, but still it doesn't match with the transaction list. Very strange. Mart EDIT: copied a backup wallet file and now it is correct for so far i remember. That wallet got corrupt too i think.... It seems similar to what happened to me. There should be something in common that had caused it. PD: However, it seems I am not mining anymore: {
"blocks": 131873,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 7834.995703879642,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 3,
"networkhashps": 535584.1039374968,
"hashps": 0,
"minerstarttime": "07-15-2019 10:40:32",
"hashcounter": 0,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
"poolinfo5": "Internal ABN: Invalid 1563197230; ",
"abninfo": "No block to mine... Please wait... 1563197290; No block to mine... Please wait... 1563197294; No block to mine... Please wait... 1563197297; ",
"gsc_errors": "low abn weight 0",
"poolmining": false,
"pool_url": "https://pool.biblepay.org/",
"required_abn_weight": 125000
}
And the config file: gen=1
genproclimit=3
minersleep=0
pool=https://pool.biblepay.org
workerid=My old and unique username under workers in 'pool' website.
In this case it looks like its the low ABN weight. (You either must increase abn weight, or mine against a Funded pool worker - one that is created with "1" in the pool for funded). Please paste 'exec getabnweight 125000' and we can see if your abn weight is too low to mine? |
|
|
|
|
Show Posts
