|
|
|
|
|
|
|
You get merit points when someone likes your post enough to give you some. And for every 2 merit points you receive, you can send 1 merit point to someone else!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
capulo
Newbie
 Offline
Activity: 491
Merit: 0
|
 |
June 21, 2019, 05:55:03 AM |
|
Block 127000 is here . Is abn activated now?
I didn't notice anything in the debug log to say I lacked aged bbp even though the wallet has 0 balance.
hm? i have only "blocks": 126835, |
|
|
|
|
|
sunk818
|
|
June 21, 2019, 06:40:12 PM |
|
Block 127000 is here . Is abn activated now?
I didn't notice anything in the debug log to say I lacked aged bbp even though the wallet has 0 balance.
hm? i have only "blocks": 126835, I am writing from the future.  Block 127,000 is coming up! |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 22, 2019, 01:38:24 AM |
|
74,000 views per day, not bad! Interesting info. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 22, 2019, 01:41:21 AM |
|
Block 127000 is here . Is abn activated now?
I didn't notice anything in the debug log to say I lacked aged bbp even though the wallet has 0 balance.
hm? i have only "blocks": 126835, I am writing from the future. Block 127,000 is coming up! Yep, its really coming up this time! |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 22, 2019, 02:34:17 AM |
|
Block 127000 is here . Is abn activated now?
I didn't notice anything in the debug log to say I lacked aged bbp even though the wallet has 0 balance.
hm? i have only "blocks": 126835, I am writing from the future. Block 127,000 is coming up! Yep, its really coming up this time! I see the heat miners ran the diff up to 220K for the last block before ABN! |
|
|
|
dave_bbp
Jr. Member
Offline
Activity: 405
Merit: 3
|
|
June 22, 2019, 02:57:49 PM |
|
Somehow I can't get my miners to work on the pool.
I copied a fresh wallet without a password on all of them and sent 256k there a couple of hours ago. The wallets don't have any password. However when I start the clients the "getmininginfo" output always shows "gsc_errors: low abn weight 0". Is there any additional requirement?
|
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 22, 2019, 03:03:12 PM |
|
Somehow I can't get my miners to work on the pool.
I copied a fresh wallet without a password on all of them and sent 256k there a couple of hours ago. The wallets don't have any password. However when I start the clients the "getmininginfo" output always shows "gsc_errors: low abn weight 0". Is there any additional requirement?
You just have to have ABN weight in the block, lets look at possible issues. Its unlocked and unencrypted so that makes it easier. Type: exec getabnweight See if its > 256k? If its not you need a little more age. 256k = 1 day of coin age * 256,000 bbp. (Or you can temporarily send more to it). Another tip: If your wallet is not mining (IE 0 hps in getmininginfo), you can look in the log and scan for "biblepayminer" or "ABN", and it should have some type of error in there. PS: That explains why our diff dropped! |
|
|
|
dave_bbp
Jr. Member
Offline
Activity: 405
Merit: 3
|
|
June 22, 2019, 03:51:44 PM |
|
You just have to have ABN weight in the block, lets look at possible issues.
Its unlocked and unencrypted so that makes it easier.
Type: exec getabnweight
See if its > 256k?
If its not you need a little more age. 256k = 1 day of coin age * 256,000 bbp.
(Or you can temporarily send more to it).
Another tip: If your wallet is not mining (IE 0 hps in getmininginfo), you can look in the log and scan for "biblepayminer" or "ABN", and it should have some type of error in there.
PS: That explains why our diff dropped!
Ah I see, that makes sense. So the abnweight=256k is a coin age weight, not just an amount. Right now getabnweight gives about 60k, so either I wait until tomorrow, or I send more coins now and reduce the waiting time. But it would also be possible the other way round, right? Let's say I now pull off 128k from this wallet and wait for 2 days, the result is the same and the risk of the unlocked wallet is reduced (if there is any at all...). Nice to know that.  |
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 22, 2019, 08:51:04 PM |
|
At first I was cautious about commenting on ABN when the diff dropped, but I want to say that I think we made the right decision with ABN.
I'm looking at the pool, and with the low difficulty, we are really solving blocks fast now. We just hit 31 blocks solved (and we've only been on ABN half a day) meaning with this trajectory we should hit 50 blocks by tomorrow morning.
That's good because it means the people being rewarded are the long-term Biblepayers (in contrast to mining pools who jump in and sell the coins).
I might be making an early assessment, but this feels very good that the rewards are going to our own miners and the diff is still low.
This reminds me of our second month (August 2017) when it felt as if all the coins went to our miners, and then we 'assumed' someone jumped on with 300 PCs in Japan and the diff skyrocketed. With ABN, that risk is mitigated (unless they buy coins for every PC and hold them to mine with).
|
|
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 22, 2019, 10:06:07 PM |
|
I think ABN is a good change. It does mitigate the botnet. Does anyone wanting to participating in BBP need to buy on exchange or do bounty (orphan letter writing) to get BBP?
So, with ABN is the required weight always 256k BBP per block? I guess it fluctuates with the difficulty? Higher diff means you need to stake more BBP of enough min coin age? I found a block, but it spent 600k BBP since the coins weren't in smaller denominations. In between PoG and PoBH, not sure how my coins should be set up. Since my CPU is 0 hash, I'll guess I'll run BOINC again when the CPU percentage if near 0%.
There's a lot of ABN spam on 1.4.3.5:
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
antibotnetsignature failed on tx xxxxx with purported coin-age of 0.000000
ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
I'll look at the log spam ASAP, hopefully within the next 36 hours, and we can make a mainnet release to reduce log spam, fix the leaderboard erratic behavior, the detail amount issue, and look at the github permissions. On the ABN weight used: It actually is always 256k (except when the block is late or when diff is < 1000, then the ABN requirement is 0), but the reason we take more ABN weight in certain circumstances is if we use a coin with more coin age than 256k then your weight is higher in that block. |
|
|
|
orbis
Newbie
Offline
Activity: 150
Merit: 0
|
|
June 23, 2019, 09:46:32 AM |
|
I think ABN is a good change. It does mitigate the botnet. Does anyone wanting to participating in BBP need to buy on exchange or do bounty (orphan letter writing) to get BBP?
So, with ABN is the required weight always 256k BBP per block? I guess it fluctuates with the difficulty? Higher diff means you need to stake more BBP of enough min coin age? I found a block, but it spent 600k BBP since the coins weren't in smaller denominations. In between PoG and PoBH, not sure how my coins should be set up. Since my CPU is 0 hash, I'll guess I'll run BOINC again when the CPU percentage if near 0%.
There's a lot of ABN spam on 1.4.3.5:
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
antibotnetsignature failed on tx xxxxx with purported coin-age of 0.000000
ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
I'll look at the log spam ASAP, hopefully within the next 36 hours, and we can make a mainnet release to reduce log spam, fix the leaderboard erratic behavior, the detail amount issue, and look at the github permissions. On the ABN weight used: It actually is always 256k (except when the block is late or when diff is < 1000, then the ABN requirement is 0), but the reason we take more ABN weight in certain circumstances is if we use a coin with more coin age than 256k then your weight is higher in that block. Hi, yesterday I solved 3 blocks after 127000, but after that something changed and now, I'm not able to mine. My abnweight is 1225238, but my miner still have "gsc_errors": "low abn weight 0". When is my miner running (eg on my WIN QT wallet with 8 threads), wallet is really laggy and I have really problems to write command in debug console. And yes, log is full of ABN spam and something is there something like this: 2019-06-23 09:40:02
CreateNewBlock::Unable to add ABN because CreateABN::Fail::Insufficient funds.antibotnetsignature failed on tx 73def57d702cbbbfb077473aef33aa6c7f72b27587d1766c1e3e7b3bbc0f3cf1 with purported coin-age of 0.000000
2019-06-23 09:40:02 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 09:40:32 keypool return 2337
2019-06-23 09:40:33 keypool reserve 2337 |
|
|
|
|
pagalo
Newbie
Offline
Activity: 52
Merit: 0
|
|
June 23, 2019, 10:39:09 AM |
|
Hello, all miners works at 0% CPU
I have the following conf.
addnode=explorer.biblepay.org
gen=1
genproclimit=1
poolport=80
workerid=
pool=https://pool.biblepay.org
minersleep=0
tithe=10
tithing=10
nickname=pagalo
getmininginfo result
{
"blocks": 127260,
"currentblocksize": 1593,
"currentblocktx": 1,
"difficulty": 2816.816655473472,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 375372.1147512915,
"hashps": 0,
"minerstarttime": "06-23-2019 10:22:28",
"hashcounter": 0,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "WORKER ID EMPTY IN CONFIG FILE; ",
"gsc_errors": "low abn weight 0",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 256000
}
exec getabnweight
{
"Command": "getabnweight",
"weight": 483488.1748842592,
"total_required": 1479267
}
Do I have to change anything?
Thanks
|
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 23, 2019, 02:15:13 PM
Last edit: June 23, 2019, 02:38:36 PM by bible_pay |
|
I think ABN is a good change. It does mitigate the botnet. Does anyone wanting to participating in BBP need to buy on exchange or do bounty (orphan letter writing) to get BBP?
So, with ABN is the required weight always 256k BBP per block? I guess it fluctuates with the difficulty? Higher diff means you need to stake more BBP of enough min coin age? I found a block, but it spent 600k BBP since the coins weren't in smaller denominations. In between PoG and PoBH, not sure how my coins should be set up. Since my CPU is 0 hash, I'll guess I'll run BOINC again when the CPU percentage if near 0%.
There's a lot of ABN spam on 1.4.3.5:
CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
antibotnetsignature failed on tx xxxxx with purported coin-age of 0.000000
ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
I'll look at the log spam ASAP, hopefully within the next 36 hours, and we can make a mainnet release to reduce log spam, fix the leaderboard erratic behavior, the detail amount issue, and look at the github permissions. On the ABN weight used: It actually is always 256k (except when the block is late or when diff is < 1000, then the ABN requirement is 0), but the reason we take more ABN weight in certain circumstances is if we use a coin with more coin age than 256k then your weight is higher in that block. Hi, yesterday I solved 3 blocks after 127000, but after that something changed and now, I'm not able to mine. My abnweight is 1225238, but my miner still have "gsc_errors": "low abn weight 0". When is my miner running (eg on my WIN QT wallet with 8 threads), wallet is really laggy and I have really problems to write command in debug console. And yes, log is full of ABN spam and something is there something like this: 2019-06-23 09:40:02
CreateNewBlock::Unable to add ABN because CreateABN::Fail::Insufficient funds.antibotnetsignature failed on tx 73def57d702cbbbfb077473aef33aa6c7f72b27587d1766c1e3e7b3bbc0f3cf1 with purported coin-age of 0.000000
2019-06-23 09:40:02 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock: (code 0)
2019-06-23 09:40:32 keypool return 2337
2019-06-23 09:40:33 keypool reserve 2337 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. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 23, 2019, 02:17:49 PM
Last edit: June 23, 2019, 02:39:43 PM by bible_pay |
|
Hello, all miners works at 0% CPU
I have the following conf.
addnode=explorer.biblepay.org
gen=1
genproclimit=1
poolport=80
workerid=
pool=https://pool.biblepay.org
minersleep=0
tithe=10
tithing=10
nickname=pagalo
getmininginfo result
{
"blocks": 127260,
"currentblocksize": 1593,
"currentblocktx": 1,
"difficulty": 2816.816655473472,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 375372.1147512915,
"hashps": 0,
"minerstarttime": "06-23-2019 10:22:28",
"hashcounter": 0,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "WORKER ID EMPTY IN CONFIG FILE; ",
"gsc_errors": "low abn weight 0",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 256000
}
exec getabnweight
{
"Command": "getabnweight",
"weight": 483488.1748842592,
"total_required": 1479267
}
Do I have to change anything?
Thanks
EDIT: if you are not pool mining, ensure the wallet is unlocked. Scan the log file for any errors related to "ABN". You have enough ABN weight. Try restarting with -zapwallettxes=1 first then try mining again. EDIT2: If you just sent out a GSC transmission, the wallet cant recycle your abn weight until that transmission is in a block. |
|
|
|
orbis
Newbie
Offline
Activity: 150
Merit: 0
|
|
June 23, 2019, 03:16:44 PM |
|
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. |
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 23, 2019, 05:09:02 PM
Last edit: June 23, 2019, 05:20:46 PM by bible_pay |
|
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. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
June 23, 2019, 05:10:13 PM
Last edit: June 23, 2019, 05:29:56 PM by bible_pay |
|
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. |
|
|
|
eternalenvoy
Newbie
Offline
Activity: 56
Merit: 0
|
|
June 23, 2019, 05:59:21 PM |
|
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...
|
|
|
|
|
|
