Seems like I am not the only one having issues with the new ABN requirement (which I do like by the way). But that said, who has figured out how this works? I have this 22:01:36  exec getabnweight
22:01:36

{
"Command": "getabnweight",
"weight": 290486.3869212963,
"total_required": 420620
}
And then this

{
"blocks": 127403,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 1429.968292932392,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 60,
"networkhashps": 195562.9268588838,
"hashps": 0,
"minerstarttime": "06-24-2019 02:56:55",
"hashcounter": 0,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_06-24-2019 03:01:09; RM_06-24-2019 03:01:08; RMC_06-24-2019 03:01:08; RMC_06-24-2019 03:01:08; RMC_06-24-2019 03:01:08; RMC_06-24-2019 03:01:09; RMC_06-24-2019 03:01:09; RMC_06-24-2019 03:01:09; RMC_06-24-2019 03:01:09; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:09; RMC_06-24-2019 03:01:09; RMC_06-24-2019 03:01:09; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:10; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:11; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:12; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:13; RMC_06-24-2019 03:01:14; RMC_06-24-2019 03:01:14; RMC_06-24-2019 03:01:14; RMC_06-24-2019 03:01:14; RMC_06-24-2019 03:01:14; RMC_06-24-2019 03:01:14; ",
"poolinfo3": "",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 256000
}
Is there a change to the conf file that must be done? Clearly I have enough ABN. Any chance there is a bug in the code where if weight is not the same as total_required then we get this error?? Could you please paste long pieces of data inside surrounding ' [ c o d e ] data [ / c o d e ] ' tags in the future to keep the forum cleaner - thanks, I appreciate it. On this issue, first confirm that it is still happening - after 6 blocks after your post? 2) Could you please paste the output of 'exec getabnweight 256000 1'? The only error reported to me so far is when the user finds a block, they are out for 6 confirms. Lets hone in on is it that, or are you still out after 6? If we find its out after 6, we can glean more info from the output on #2. |
|
|
|
> As far as 1 click mining, we might be able to do that with a pool, please get ahold of Lict or make BiblePool #2 and front the abn weight for us.
With pool.biblepay.org , do we lose our bbp stake if anyone in the pool finds a block? looking at my input, it seems wallet combined 2 x 256k and made one of the outputs 387k. I'm still using 1.4.3.5
Nope, you only lose your stake in the pool if you are the pool miner who found the block. I love that too. 2) There really is not 2 outputs of 256k with 387k, there is a smaller one that was not enough, then a bigger one that made it > 256k. |
|
|
|
BiblePay
1.4.3.6 - Leisure Upgrade
** Mac & Linux are compiling **
Mac & Linux versions ready Nothing changes after upgrade .... Why will shown "Insufficient funds" even I have enough abnweight and BBP? "Command": "getabnweight", "weight": 1021959.761631944, "total_required": 499999 Log Info: ***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::Insufficient funds. ***** 2019-06-24 10:01:05 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0) The latest version didn't change the ABN reqs as I believe this is just a reporting issue (this version changed the error message displayed for one case, and fixed the lag(s) etc). But anyway for this particular problem lets try to hone in on it to get to the root of it, as maybe we need to make the ABN selector more conservative, so we don't report misleading errors to the users. Could you please paste the output of this: exec getabnweight 256000 1 Thanks. Also, could you please confirm that you are not able to mine after 6 blocks after your post? |
|
|
|
ROB overloading 0%  Most likely you are probably not mining. If you look at getmininginfo, it is probably 0 hps now. You must keep > 256K abn weight in your wallet; with 100K you probably only had enough to solve 1 block, now you have to wait 24 hrs. |
|
|
|
Rob,
Do I need 2 separate wallets to participate in both POG and HEALING ?
for some reason my prominence in HEALING was always 0
No just one wallet and one CPK. To score Healing points you have to add a Diary entry. To do that go to the QT send-money UI, click diary entry checkbox, add a diary entry in the prayer line, and click send (it sends 1 BBP to the foundation). Then check it in about 6 blocks. You do have to join healing with : exec join HEALING |
|
|
|
btw, i did zapwallettxses=1 and before
{
"Command": "getabnweight",
"weight": 1336.469490740741,
"total_required": 3301,
"weight 256000.00": 1336.469490740741,
"total_required 256000.00": 3301
}
after
{
"Command": "getabnweight",
"weight": 643047.4759837964,
"total_required": 2491453,
"weight 256000.00": 262569.1148958333,
"total_required 256000.00": 3357
}
and machine with zapwalle... starts mining. other 2 are saying abn low (same wallet)
i dont understand from where weight came here, because i hit block few block ago and now i had almost whole amount <6 confirm. with more confirmations there is only 35 bbp (about 930 conf)
EDIT:
right now i hit another block and:
{
"Command": "getabnweight",
"weight": 443744.6247222222,
"total_required": 2488053,
"weight 256000.00": 443585.7959259259,
"total_required 256000.00": 2488018
}
2019-06-23 23:39:23
ABN Tx Total Bal 2484901.173169, Needed 2488018.753275, ABNWeight 443585.795926
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.keypool reserve 1171
2019-06-23 23:39:23 antibotnetsignature failed on tx 24b9bd0408919ef439286d3478910689b55e7082a5501a37422e40c92b48700d with purported coin-age of 0.000000
2019-06-23 23:39:23 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 23:39:23
ABN Tx Total Bal 2484901.173169, Needed 2488018.753275, ABNWeight 443585.795926
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 810923c7a3378372942a4991a928239a9bbd8299adfcdfb104302733723bc41b with purported coin-age of
0.000000
2019-06-23 23:39:23 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 23:39:23 keypool return 1173
2019-06-23 23:39:24 keypool reserve 1173
2019-06-23 23:39:24
ABN Tx Total Bal 2484901.173169, Needed 2488018.753275, ABNWeight 443585.795926
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx c6bf99cf916cd85a0169ec7cd96be3e7a0050391fd8125be9ace76fa86afea82 with purported coin-age of
0
When you hit a block your spent UTXOs not only have to age again, they have to be 6 confirms deep to count again. So it makes sense that your ABN weight drops drastically and you receive the ABN errors after you solve blocks. does it mean I'm getting sort of penalized for solving the blocks ?  ABN Tx Total Bal XXXXXXX.988375, Needed XXXXXXX.872920, ABNWeight 329843.194954 keypool reserve 1868
2019-06-24 00:45:04 keypool return 1868
2019-06-24 00:45:04
ABN Tx Total Bal XXXXXXX.988375, Needed XXXXXXX.872920, ABNWeight 329843.194954 keypool reserve 1868
2019-06-24 00:45:04 keypool return 1868
2019-06-24 00:45:04
ABN Tx Total Bal XXXXXXX.988375, Needed XXXXXXX.872920, ABNWeight 329843.194954 keypool reserve 1868
2019-06-24 00:45:05 keypool return 1868
2019-06-24 00:45:05
ABN Tx Total Bal XXXXXXX.988375, Needed XXXXXXX.872920, ABNWeight 329843.194954 keypool reserve 1868
2019-06-24 00:45:05 keypool return 1868
2019-06-24 00:45:05
ABN Tx Total Bal XXXXXXX.988375, Needed XXXXXXX.872920, ABNWeight 329843.194954 keypool reserve 1868
2019-06-24 00:45:06 keypool return 1868
2019-06-24 00:45:06
ABN Tx Total Bal XXXXXXX.988375, Needed XXXXXXX.872920, ABNWeight 329843.194954 keypool reserve 1868
2019-06-24 00:45:06 keypool return 1868
2019-06-24 00:45:06 Memorizing prayers tip height 127384 @ time 1561337106 deserialized height 0 ...Finished MemorizeBlockChainPrayers @ 1561337106 UpdateTip: new best=53ab52e28d6cee7f62026441608770c55acd55ba4af181630e7632e47a223888 height=127385 version=0x2000000c log2_work=59.49081031 tx=1081418 date='2019-06-24 00:45:05' progress=1.000000 cache=0.1MiB(0txo)
2019-06-24 00:45:06 {PNB}: ACC
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.antibotnetsignature failed on tx 4255869427dd9d03dc85a9f8154bbf57ed2197d5d196c3df9e69c5dd9ecc2fcf with purported coin-age of 0.000000
2019-06-24 00:45:07
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.antibotnetsignature failed on tx 4255869427dd9d03dc85a9f8154bbf57ed2197d5d196c3df9e69c5dd9ecc2fcf with purported coin-age of 0.000000
2019-06-24 00:45:07
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.antibotnetsignature failed on tx 4255869427dd9d03dc85a9f8154bbf57ed2197d5d196c3df9e69c5dd9ecc2fcf with purported coin-age of 0.000000
2019-06-24 00:45:08
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.keypool keep 1861
2019-06-24 00:45:21
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.Memorizing prayers tip height 127385 @ time 1561337165 deserialized height 0 ...Finished MemorizeBlockChainPrayers @ 1561337165 UpdateTip: new best=d0417ce2248577d8691667e6924805eaf90bc7bccd1ef3f9d9ea9d04e8ec77bf height=127386 version=0x2000000c log2_work=59.49081187 tx=1081419 date='2019-06-24 00:46:05' progress=1.000000 cache=0.1MiB(0txo)
2019-06-24 00:46:06
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.antibotnetsignature failed on tx d5f7bd1195894a855f2b4fc2fa6109de14b45eece78fb5eccf484b0a77e20652 with purported coin-age of 0.000000
2019-06-24 00:46:06 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-24 00:46:06
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.antibotnetsignature failed on tx d5f7bd1195894a855f2b4fc2fa6109de14b45eece78fb5eccf484b0a77e20652 with purported coin-age of 0.000000
2019-06-24 00:46:06 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-24 00:46:06
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.antibotnetsignature failed on tx d5f7bd1195894a855f2b4fc2fa6109de14b45eece78fb5eccf484b0a77e20652 with purported coin-age of 0.000000
2019-06-24 00:46:06 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-24 00:46:06
Sort of, but not penalized much (just 6 blocks). You have 329K weight, so if you wait 1-5 more blocks, your miner will come back online. Its just a matter of the ABN coin selector to have the capability to use a coin that is > 5 in depth. EDIT: The new version will spam much less. |
|
|
|
btw, i did zapwallettxses=1 and before
{
"Command": "getabnweight",
"weight": 1336.469490740741,
"total_required": 3301,
"weight 256000.00": 1336.469490740741,
"total_required 256000.00": 3301
}
after
{
"Command": "getabnweight",
"weight": 643047.4759837964,
"total_required": 2491453,
"weight 256000.00": 262569.1148958333,
"total_required 256000.00": 3357
}
and machine with zapwalle... starts mining. other 2 are saying abn low (same wallet)
i dont understand from where weight came here, because i hit block few block ago and now i had almost whole amount <6 confirm. with more confirmations there is only 35 bbp (about 930 conf)
EDIT:
right now i hit another block and:
{
"Command": "getabnweight",
"weight": 443744.6247222222,
"total_required": 2488053,
"weight 256000.00": 443585.7959259259,
"total_required 256000.00": 2488018
}
2019-06-23 23:39:23
ABN Tx Total Bal 2484901.173169, Needed 2488018.753275, ABNWeight 443585.795926
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.keypool reserve 1171
2019-06-23 23:39:23 antibotnetsignature failed on tx 24b9bd0408919ef439286d3478910689b55e7082a5501a37422e40c92b48700d with purported coin-age of 0.000000
2019-06-23 23:39:23 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 23:39:23
ABN Tx Total Bal 2484901.173169, Needed 2488018.753275, ABNWeight 443585.795926
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 810923c7a3378372942a4991a928239a9bbd8299adfcdfb104302733723bc41b with purported coin-age of
0.000000
2019-06-23 23:39:23 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 23:39:23 keypool return 1173
2019-06-23 23:39:24 keypool reserve 1173
2019-06-23 23:39:24
ABN Tx Total Bal 2484901.173169, Needed 2488018.753275, ABNWeight 443585.795926
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx c6bf99cf916cd85a0169ec7cd96be3e7a0050391fd8125be9ace76fa86afea82 with purported coin-age of
0
When you hit a block your spent UTXOs not only have to age again, they have to be 6 confirms deep to count again. So it makes sense that your ABN weight drops drastically and you receive the ABN errors after you solve blocks. |
|
|
|
it wasnt mandatory or?
now after one from 2 immature blocks had 102 confirmations, mining started and after few minutes i hit block
2019-06-23 22:39:44
ABN Tx Total Bal 2477090.799074, Needed 2477013.405647, ABNWeight 895150.140174 keypool reserve 1120
2019-06-23 22:39:44 keypool return 1120
2019-06-23 22:39:44
ABN Tx Total Bal 2477090.799074, Needed 2477013.405647, ABNWeight 895150.140174 keypool reserve 1120
2019-06-23 22:39:44 keypool return 1120
2019-06-23 22:39:44
ABN Tx Total Bal 2477090.799074, Needed 2477013.405647, ABNWeight 895150.140174 keypool reserve 1120
2019-06-23 22:39:44 keypool return 1120
but now
{
"Command": "getabnweight",
"weight": 1336.469490740741,
"total_required": 3301,
"weight 256000.00": 1336.469490740741,
"total_required 256000.00": 3301
}
so if i understand this, 3301 should be usable coins in wallet, but i can see only about 35, others are only with 1 confirmation yet. so after abn will be high enough i will have same problem like before, that i will be missing +- 3301 bbp for abn tx
I think the issue here is our diff has been dropping below 1000. We allow anyone to mine blocks with diff < 1000. As far as the zapwallettxes freeing up some weight, I don't think its really helping - Im fairly positive that all it did was unlock some coins that would have been freed in a couple more blocks anyway. What we need to do in that case is wait until you are sure you cant mine for 7 blocks straight, run the 'exec getabnweight 256000 1' command, and compare the UTXO set to the wallet and then open an issue with the exact missing coin. But don't do this yet until you are sure you prove an issue exists (as I havent seen one on my wallet yet). All I noticed that was a little funny was after I sent my exec gscc today I had to wait a few more blocks for the miner to restart but it did restart automatically. |
|
|
|
|
BiblePay
1.4.3.6 - Leisure Upgrade
- Ensure exec analyze analyzes the correct height range
- Ensure Leaderboard summary and detail owed amounts match, and refer to
the (promince % * superblock total)
- Remove jerky update to Leaderboard GUI and allow it to respect the
users sort column
- Remove UI laginess caused by the BiblePay miner
- Improve miner.cpp's efficiency (mine for a minute at a time before
checking for changes, and update the GUI once every 10 seconds, and
ensure thread interruption point allows a graceful exit when program is
ending). Ensure CreateNewBlock does not cause blocking to the UI.
- Remove log spam
- Add ABN error message for cases where balance is less than required
amount due to confirmations < 6
- Enforce GSC protocol version
** Mac & Linux are compiling **
|
|
|
|
ROB unlock yes  I see you are hashing at a very fast 149K hps, so I dont see a problem here, what made you say you are not mining? |
|
|
|
Is the wallet locked? Now paste getmininginfo also. Please answer both questions and wait for getmininginfo to populate before pasting. |
|
|
|
im lost with BBP again....... dont understand nothing
new user must be dead with bbp.......
i cant mine, why?
Please paste getmininginfo. If it says Low abn weight, that means you have no abn weight. If so paste 'exec getabnweight' what is this again? WE WANT EASY COIN FOR PPL FROM AFRICA!!!!!!!!!! IT WAS YOUR CONCEPT....... THIS COIN IS ONLY FOR FEW USERS WHAT WE SEE ..... WE WANT 1 CLICK MINING COIN HOLY HEAVEN The baby cannot be birthed before being born. (Isaiah 66 9). And we want help and participation and holiness from your end, please consider doing your part to improve this community. As far as 1 click mining, we might be able to do that with a pool, please get ahold of Lict or make BiblePool #2 and front the abn weight for us. |
|
|
|
im lost with BBP again....... dont understand nothing
new user must be dead with bbp.......
i cant mine, why?
Please paste getmininginfo. If it says Low abn weight, that means you have no abn weight. If so paste 'exec getabnweight' |
|
|
|
Ok, now I have problem with low ABN again even if my abnweight is more than 256k. Now I found this in log: 2019-06-23 19:49:47 keypool return 2344
2019-06-23 19:49:47 keypool return 2345
2019-06-23 19:49:47 keypool reserve 2344
2019-06-23 19:49:47
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324 keypool reserve 2345
2019-06-23 19:49:47
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.keypool return 2346
2019-06-23 19:49:47 antibotnetsignature failed on tx f4ced749f1c1eaec7f9c79dd2dd2ffdb20a1604c902f7ce47b7d9926049a5f1c with purported coin-age of 0.000000
2019-06-23 19:49:47 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 19:49:47
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 52b553fbba0b42c505ab032ebb3d79479b899c15f43de5e7bc10e736082d8efa with purported coin-age of 0.000000
2019-06-23 19:49:47 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 19:49:48 keypool reserve 2346
2019-06-23 19:49:48
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 034ad2e99cc07ac2e319c7c28dbcd6e57b6ba3e0982e48dbbdb54c5f72a56347 with purported coin-age of 0.000000
2019-06-23 19:49:48 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
So unfortunately this didn't lead to any new revelations (to improve ABN) yet. Although this looks strange: ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, This means the wallet itself, when counting confirmed transactions (coinbases that are confirmed, and all tx's to yourself deeper than 6 confirms) calculates a balance of 1.9229MM, while the ABN coin selector seeks coins of depth 5+ that it would need 1.9267MM to make 256k weight, meaning there is one coin in your wallet (about 4K, probably a reward) that is not quite old enough to be used by ABN. So by now the miner is probably mining again. Ill try to improve this message. EDIT: Btw Orbis you can type 'exec getabnweight 256000 1' to see the details of the coins selected to arrive @ 256k. |
|
|
|
Ok, now I have problem with low ABN again even if my abnweight is more than 256k. Now I found this in log: 2019-06-23 19:49:47 keypool return 2344
2019-06-23 19:49:47 keypool return 2345
2019-06-23 19:49:47 keypool reserve 2344
2019-06-23 19:49:47
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324 keypool reserve 2345
2019-06-23 19:49:47
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.keypool return 2346
2019-06-23 19:49:47 antibotnetsignature failed on tx f4ced749f1c1eaec7f9c79dd2dd2ffdb20a1604c902f7ce47b7d9926049a5f1c with purported coin-age of 0.000000
2019-06-23 19:49:47 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 19:49:47
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 52b553fbba0b42c505ab032ebb3d79479b899c15f43de5e7bc10e736082d8efa with purported coin-age of 0.000000
2019-06-23 19:49:47 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 19:49:48 keypool reserve 2346
2019-06-23 19:49:48
ABN Tx Total Bal 1922976.605973, Needed 1926795.382894, ABNWeight 492864.375324
CreateNewBlock::Unable to add ABN because Sorry, your balance is lower than the required ABN transaction amount.antibotnetsignature failed on tx 034ad2e99cc07ac2e319c7c28dbcd6e57b6ba3e0982e48dbbdb54c5f72a56347 with purported coin-age of 0.000000
2019-06-23 19:49:48 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
Yep, thats it, thanks Orbis! I've got the jerkiness and log spam fixed, but let me take a look at this issue and see if we can address it for tonights release. |
|
|
|
After ABN re-enable, it seem have a serious problem that wallet is really laggy when POBH mode, and it is not working as CPU usage is 0%. I have checked the message and shown "low abn weight 0", however I confirmed the value is over 256000 of abnweight in wallet.
I have try to reindex or restarting with -zapwallettxes=1, but problem is not resolved..
Reference the "networkhashps" and "difficulty" from explorer , it seem really have a problem with POBH...
Yeah, I believe the jerkiness will be fixed in the next few hours, but I really do think it only happens when you run out of coin age (I know you have more than 256k, but its possible your only coin is tied up by one of the other mining threads). Could you please check your log for this: ::Unable to add ABN because CreateABN::Fail::Insufficient funds. See if you have an error like this, and if thats it then this can be mitigated in the next version. Im removing the log spam right now. No relevant ABN information found from the log... Even I set walletpassphrase and do an unlock step still not work and really laggy... There has to be, if we don't create a block to mine, the miner writes: CreateNewBlock::Unable to add ABN..... (etc). Please search again. In the mean time please run the miner on one thread and the laginess will be much less until the next version comes out. I would like to know what error you have, so we can make the next version better. |
|
|
|
GSC actually doesn't spend sanctuary funds. I think maybe the problem is you forgot to restart the sanc and ensure the coins were locked?
They get locked during the service startup phase (when you type masternode status, if it shows "Started" with an IP, thats when they are locked).
I'm sure, that I restarted sanc and all of my wallets. When I looked on it in my WIN QT wallet, they were "locked". I made it like this: Stopped mining and daemon, copy masternode.conf to VPS, start wallet, unlock and it starts mining. Nevermind. It looks that those locked coins was some problem in this, because now it is mining as it should. Now I need just to decide If I want to have sanc, or want to mine, because in my case it is not working side by side. But like you sayd, maybe I just don't know how to set it up correctly. No, I didnt mean to imply your skills or set up  -- I mean for some reason your cold wallet didnt go into the service startup phase that autolocks the coins. But I see we do skip over that particular collateral and in my personal case I have not accidentally spent any and last night I set myself up with an unlocked wallet and let it send gscs and mine, so I think that part is working properly - for the most part. But we can continue to work through anything that is a long term issue. |
|
|
|
I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).
(Ill take care of this spam ASAP).
EDIT: Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)? Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.
I solved last block more than 150 blocks before. And I turned off sending GSC, so my last was around 350 block ago. Please investigate the log and scrape the actual error. I didn't found any other error except those ABN logs. But I think, that I found some connection with sanctuaries. I bought BBP to have enough BBP for sanc. So I have created sanc and put my masternode.conf file to my VPS in faith that my VPS avoid sending locked BBPs. Few blocks away some of my VPS solved block and used locked BBPs to satisfy ABN tx. It destroyed sanc, but my abnweight was enough to solve another block after 8 blocks after first (now I have almost 0 abnweught). It looks, that even if I had enough abnweight with sanc, that was just in some counterpart with sanc. Yes, I know that I can create new wallet not related with sanc, but I want to have only one wallet. And Sunk, after block 127000 you can look who solved the block. It's the same as it was with CPID before. GSC actually doesn't spend sanctuary funds. I think maybe the problem is you forgot to restart the sanc and ensure the coins were locked? They get locked during the service startup phase (when you type masternode status, if it shows "Started" with an IP, thats when they are locked). EDIT: Just to clarify though Im referring to cold sancs. |
|
|
|
After ABN re-enable, it seem have a serious problem that wallet is really laggy when POBH mode, and it is not working as CPU usage is 0%. I have checked the message and shown "low abn weight 0", however I confirmed the value is over 256000 of abnweight in wallet.
I have try to reindex or restarting with -zapwallettxes=1, but problem is not resolved..
Reference the "networkhashps" and "difficulty" from explorer , it seem really have a problem with POBH...
Yeah, I believe the jerkiness will be fixed in the next few hours, but I really do think it only happens when you run out of coin age (I know you have more than 256k, but its possible your only coin is tied up by one of the other mining threads). Could you please check your log for this: ::Unable to add ABN because CreateABN::Fail::Insufficient funds. See if you have an error like this, and if thats it then this can be mitigated in the next version. Im removing the log spam right now. |
|
|
|
I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).
(Ill take care of this spam ASAP).
EDIT: Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)? Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.
I solved last block more than 150 blocks before. And I turned off sending GSC, so my last was around 350 block ago. Please investigate the log and scrape the actual error. |
|
|
|
|
Show Posts
