BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[MIP]

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?

[zupernovato]

I remember Dave_BBP and Gilligan had a Windows10 mining crash issue, please let us know if the last release solved the problem.

In case this answer was for me, I updated my post with more info just now. And yes, Im in windows 10.

Also, please check this out, and see Moving the Wallet section:
https://wiki.biblepay.org/Evolution_Upgrade

Somehow the remote console is stucked, and rejecting any connection that I try, so I won't have access till Monday. However, I assure you that I have followed the steps and that I am running evolution. Even the icons for mined BBPs are different (they are like birds). I am probably not using the last version that you posted here, but the last but one (the last mandatory). Should I do a 'biblepay-qt --erasechain' first of all? I have seen in reddit someone with the same problem as me, but that, after running that command, his BBPs, including the old mined ones in the BOINC era, went to zero (which does not make sense).

Ok, no problem and I wish you the best on recovering it all.  
Technically, the last mandatory 1.4.0.1, is still "good enough" to use and mine on, but we had a GSC issue a couple weeks ago where we recommended everyone upgrade, and to erase the chain (just in case a node tried to go on the lower proto version sanc side).

So yes, if your node doesnt agree with https://chainz.cryptoid.info/bbp/ , please start with
./biblepay-qt -erasechain=1

And let it resync.  Its a wives tail that you will lose all your BBP.  That comes from the very true fact that if you start with 0 legal coins, and mine on a fork 100% of the time, all the BBP mined on the fork will be lost.

But during a resync, all official main-chain BBP is still in the wallet.

Hello. First of all, I updated to 1.4.4.2 and did a clean start (following this guide: https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/, and then, running the client with erasechain option). After resync, the result is what I've been afraid of, a ZERO BBP wallet, including the ones I bought and mined at the BOINC era. Millionary transaction have dissapeared in the log, and I have just one Evolution transaction (it seems that one, or the next one, turned my client to mine into the fork, I dunno how). I do not know what I can do now, I am a bit lost. I still keep a back-up of the pre-evolution wallet.dat, just in case. I think I mined legit pre-evo update.

My config is:

Code:

gen=1
genproclimit=3
minersleep=0
pool=https://pool.purepool.org
workerid=#####

Any help is appreciated, thank you.

[MIP]

Hello. First of all, I updated to 1.4.4.2 and did a clean start (following this guide: https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/, and then, running the client with erasechain option). After resync, the result is what I've been afraid of, a ZERO BBP wallet, including the ones I bought and mined at the BOINC era. Millionary transaction have dissapeared in the log, and I have just one Evolution transaction (it seems that one, or the next one, turned my client to mine into the fork, I dunno how). I do not know what I can do now, I am a bit lost. I still keep a back-up of the pre-evolution wallet.dat, just in case. I think I mined legit pre-evo update.

My config is:

Code:

gen=1
genproclimit=3
minersleep=0
pool=https://pool.purepool.org
workerid=#####

Any help is appreciated, thank you.

Did you copy your wallet.dat file from %appdata%/Biblepaycore to new location %appdata%/Biblepayevolution ?

[MIP]

OK, windows 1.4.4.2c is out there, please test it:

MacOS and Linux binaries also ready.

[zupernovato]

Hello. First of all, I updated to 1.4.4.2 and did a clean start (following this guide: https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/, and then, running the client with erasechain option). After resync, the result is what I've been afraid of, a ZERO BBP wallet, including the ones I bought and mined at the BOINC era. Millionary transaction have dissapeared in the log, and I have just one Evolution transaction (it seems that one, or the next one, turned my client to mine into the fork, I dunno how). I do not know what I can do now, I am a bit lost. I still keep a back-up of the pre-evolution wallet.dat, just in case. I think I mined legit pre-evo update.

My config is:

Code:

gen=1
genproclimit=3
minersleep=0
pool=https://pool.purepool.org
workerid=#####

Any help is appreciated, thank you.

Did you copy your wallet.dat file from %appdata%/Biblepaycore to new location %appdata%/Biblepayevolution ?

I am re-doing the explained steps including this time a copy_paste of the wallet.dat back-up, and a modified config file (I've just discovered that pool.puerpool is closed . Now I am using the main pool with its proper workerid.

EDIT: This second chance made the trick. Now it shows the proper BPPs in my wallet (pre-evolution). Let's see how about the mining . Thank y'all.

[Mart1250]

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....

[zupernovato]

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:

Code:

{
  "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:

Code:

gen=1
genproclimit=3
minersleep=0
pool=https://pool.biblepay.org
workerid=My old and unique username under workers in 'pool' website.

[bible_pay]

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:

Code:

{
  "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:

Code:

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?

[bible_pay]

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).

[zupernovato]

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:

Code:

{
  "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:

Code:

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:

Code:

{
  "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?

[bible_pay]

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 **

[bible_pay]

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:

Code:

{
  "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:

Code:

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:

Code:

{
  "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

[Gilligan_M]

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."
}

[bible_pay]

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.

Code:

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).

[Gilligan_M]

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.

Code:

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.

[bible_pay]

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.

Code:

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).

[Gilligan_M]

http://prntscr.com/ofatf7

Here's what the transaction list shows, no GSC's (only back when I initially tested them.)

[bible_pay]

http://prntscr.com/ofatf7

Here's what the transaction list shows, no GSC's (only back when I initially tested them.)

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?

[Gilligan_M]

http://prntscr.com/ofatf7

Here's what the transaction list shows, no GSC's (only back when I initially tested them.)

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.

[thesnat21]

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?