Author

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 145. (Read 243386 times)

full member
Activity: 770
Merit: 100
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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  Huh

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.

full member
Activity: 770
Merit: 100
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  Huh
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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'

newbie
Activity: 150
Merit: 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, I'll take a look on that. It looks, that after a while mining starts again. Maybe after those 4k are old enough.
BTW: "total_required 256000.00": 1268252
full member
Activity: 770
Merit: 100
im lost with BBP again....... dont understand nothing

new user must be dead with bbp.......

 i cant mine, why?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Ok,
now I have problem with low ABN again even if my abnweight is more than 256k.
Now I found this in log:
Code:
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.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Ok,
now I have problem with low ABN again even if my abnweight is more than 256k.
Now I found this in log:
Code:
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.

newbie
Activity: 150
Merit: 0
Ok,
now I have problem with low ABN again even if my abnweight is more than 256k.
Now I found this in log:
Code:
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)
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.

newbie
Activity: 56
Merit: 0
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...
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords

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

newbie
Activity: 150
Merit: 0

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.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.  
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.

newbie
Activity: 150
Merit: 0
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.
newbie
Activity: 56
Merit: 0
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...
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.


full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
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.

So does this mean somebody with big bbp amount will get all the blocks? I got two blocks too and now nothing. Maybe we just lucky and our hash power is not strong? I think some people have 50 machines with 8 cores ... so 400 processors.


No, it doesnt mean that.  

I for example only have 3.9 mm coinage free and Ive been mining non stop and Im only using 1 machine and Im 10% of the pool-weight, so its possible to mine continuously if you drop more bbp into the mining equation.

Yeah if you had 400 processors you would probably need half of the BBP on the market.

But first of all our investors generally lock coins into sancs so this game is for people with free biblepay.

Lets not jump to quick conclusions - The difference between ABN and no ABN is this:  You live with a botnet and a bunch of rich people with hardware, and solve 1 block per month with a difficulty of 90,000.  Or you live with internal BiblePay users and solve a block a day with diff of 9000.  In the 2nd camp you maintain a free balance of 1 mil.  Which is better?  To me its like night and day.   Additionally there are a lot of factors other than ABN that make block solving fair - the fairness of POW is still in the equation.

newbie
Activity: 150
Merit: 0
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.
Jump to: