BiblePay
1.4.4.6 - Leisure Upgrade
- Fix reindex process (MIP)
- Show correct maturity icon for superblock transactions in transaction
list UI in QT
- Add exec register (this is to be explained in a future release) - for
BMS
- Add BIO URL for Cameroon One in listchildren
- Move 'sendgscc' to a dedicated RPC command.
Add ability to send a single GSC transmission (sendgscc campaign_name
donation_amt) - this sends a specific GSC transmission.
Add ability to send a customized foundation donation amount for POG
(sendgscc POG donation_amount).
- Modify BiblePay miner to only send an automatic tithe if it is
conceptually profitable. (The GSC creator will check the ROI, and only
send the automatic tithe if the ROI > 0.01). Note: You may still
forcefully send a tithe regardless of profitability with sendgscc.
- Fix bug in PDS where BiblePay will forget a PDS value after one year
(increased PDS storage duration to 7 years).
** This is our Windows release **
** MIP will notify when Linux/MAC is ready **
Footnotes:
1. If you belong to multiple campaigns, now when you send a Healing diary entry from the UI from sendcoinsentry, POG will not be sent as a second transaction (only Healing will be sent).
2. If you would like to manually send a POG transaction (with a tithe) for a specific tithe amount, you can now do this: 'sendgscc pog tithe_amount'. The wallet will only send one transaction for the amount specified (therefore you don't need to change any keys).
3. The wallet will no longer automatically tithe unless it believes it will be profitable.
4. PDS means Persisted Data Cache. This just means BiblePay will not forget your CPK nickname or prayers for 7 years (or other PDS settings).
5. Press ctrl-f5 to refresh the biblepay.org web page before downloading. If you ever receive the old version (1.4.4.5<) please clear your browser cache.
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 100. (Read 243376 times)
September 02, 2019, 09:26:50 AM
September 01, 2019, 02:58:11 PM
I have discovered a feature that everyone probably wants:
Prevent the wallet from automatically tithing if its unprofitable.
I'm creating a feature now where the wallet will only send the tithe for POG for that day if it believes the tithe will be profitable. (Otherwise you will save the coin age).
You will still be able to manually force a tithe with 'sendgscc'.
We will also make it so you can send one individual campaign transmission with sendgscc (in contrast to automatically sending all of them). This is useful if you want to say for example send one for cameroon-one and not for POG (saving your coin age for POG later).
EDIT: You will also be able to manually specify the donation (tithe) amount from sendgscc. (In contrast to changing the key, sending a tithe, changing the key and restarting).
We have a few other leisure features we will try to combine and release within the next few days (as a leisure upgrade).
One for example being some cosmetic changes Cameroon will ask for (the format of the BIO, etc).
Prevent the wallet from automatically tithing if its unprofitable.
I'm creating a feature now where the wallet will only send the tithe for POG for that day if it believes the tithe will be profitable. (Otherwise you will save the coin age).
You will still be able to manually force a tithe with 'sendgscc'.
We will also make it so you can send one individual campaign transmission with sendgscc (in contrast to automatically sending all of them). This is useful if you want to say for example send one for cameroon-one and not for POG (saving your coin age for POG later).
EDIT: You will also be able to manually specify the donation (tithe) amount from sendgscc. (In contrast to changing the key, sending a tithe, changing the key and restarting).
We have a few other leisure features we will try to combine and release within the next few days (as a leisure upgrade).
One for example being some cosmetic changes Cameroon will ask for (the format of the BIO, etc).
August 31, 2019, 06:18:52 PM
Great news coming up later this week!
1) We are moving into the big leagues and will be listed on Tokok soon, a $260,000,000 ($260MM) dollar per day exchange. Let's hope this adds volume and liquidity and helps our orphans over the long run! Our integration fee has been paid and integration has started. I'll keep everyone posted once I find the date of the airdrop and go-live.
https://coinmarketcap.com/exchanges/tokok/
One nice thing about Tokok is they support multiple languages, 2fa, and you can trade immediately without filling out extra paperwork.
2) Cameroon-One deployed most of their IT solution to Prod, and we have successfully tested 2 integration tests. We are in the final round. They are trying to create orphan bios internally. Once that is complete we can move to prod. I believe we will be going live with Cameroon One around Wednesday or so!
1) We are moving into the big leagues and will be listed on Tokok soon, a $260,000,000 ($260MM) dollar per day exchange. Let's hope this adds volume and liquidity and helps our orphans over the long run! Our integration fee has been paid and integration has started. I'll keep everyone posted once I find the date of the airdrop and go-live.
https://coinmarketcap.com/exchanges/tokok/
One nice thing about Tokok is they support multiple languages, 2fa, and you can trade immediately without filling out extra paperwork.
2) Cameroon-One deployed most of their IT solution to Prod, and we have successfully tested 2 integration tests. We are in the final round. They are trying to create orphan bios internally. Once that is complete we can move to prod. I believe we will be going live with Cameroon One around Wednesday or so!
August 31, 2019, 06:14:42 PM
I'm sure this has been mentioned in the 700+ pages before but what is up with the insane amount of network traffic the wallet causes? Obviously I know its saving the blocks, but the TX traffic is off the charts? Is it because of the cpu mining? I have had the wallet open for a few days and its sent 2 GB and received 225. Is that normal? Looks like its sending out at 100 KB/s
The pool miner only uses a couple K per hour, so mining is not consuming bandwidth.
When you say 225 with no suffix, do you mean you received 225 meg in "a few days", please clarify?
You can run Dash or Bitcoin side by side BiblePay for a few days and do a baseline and send us the comparison if you think we are hogging more than normal, let me know the comparison results of this.
Edit: One thing you can also test is running with the switch litemode=1. Do a comparison between both with and without to produce a baseline for us.
August 31, 2019, 06:06:37 PM
Apollon Network
confirmed me that BBP is finally enabled in their MN hosting platform.
confirmed me that BBP is finally enabled in their MN hosting platform.
Great news!
Will test this network asap.
Thanks.
August 31, 2019, 11:08:50 AM
Apollon Network
confirmed me that BBP is finally enabled in their MN hosting platform.
confirmed me that BBP is finally enabled in their MN hosting platform.
August 30, 2019, 03:53:32 PM
I'm sure this has been mentioned in the 700+ pages before but what is up with the insane amount of network traffic the wallet causes? Obviously I know its saving the blocks, but the TX traffic is off the charts? Is it because of the cpu mining? I have had the wallet open for a few days and its sent 2 GB and received 225. Is that normal? Looks like its sending out at 100 KB/s
August 30, 2019, 03:49:09 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Hey sir,
try minersleep=1 to your conf. file.
The issue ended up being my biblepay.conf I had to delete it and recreate it and everything worked.
August 29, 2019, 01:23:27 AM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Hey sir,
try minersleep=1 to your conf. file.
August 28, 2019, 07:45:46 PM
Good to know. I know the BURST QBundle Wallet is something low like 30 seconds and can be a real pain on over committed systems. However, I hadn't seen it on this wallet yet. I think the systems tend to check in with the auto settings before hitting the 5 minute mark correcting themselves. Glad to see it more forgiving than others.
August 28, 2019, 04:49:30 PM
Some miners tell you if the system clock is drifting out of sync. Does the BBP client do this?
On boot, if you have 0 connections (due to hangups from peers), there will be a System Time error in the log.
Once you have connections, no, you can keep mining until you drift off more than the allowable block timestamp window, then the block would be rejected.
August 28, 2019, 04:46:50 PM
Some miners tell you if the system clock is drifting out of sync. Does the BBP client do this?
August 28, 2019, 03:09:19 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
Here is the output:
Code:

{
"Command": "createabn",
"xml": "ABN 320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429 ppk IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg= B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp 125000 ",
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
I checked the debug log and don't see any errors. Just a mention that the miner is starting. Wallet is also unlocked.
Things look OK from what I see - you have a valid self funded ABN.
You are mining, except your pool mining is not working.
What HPS are you mining at now btw, is it > 50K?
I don't see you hitting the pool. I see your workerid was set up correctly as self funded.
The biblepay.conf looks OK.
One thing I would suggest is copying the values out to notepad, recreate your biblepay.conf natively on your machine, be sure to manually press
Ive heard of a few reports where people are somehow saving the biblepay conf with the wrong crlf delimiters for the platform.
That might be why biblepay cant see your pool settings.
On a side note, you can test that by entering: genproclimit=10 in the biblepay conf, restart the core wallet and see if you are mining on 10 threads.
That means its reading your file.
Deleting and recreating the biblepay.conf fixed the issue. I'll admit I thought that was a crazy fix and it would never work, but I am pleasantly surprised
Thanks!Great!
Yes and the other one that gets people is the system time. If the time is off by more than 5~ mins or so the system will start disconnecting from peers.
So please remember that everyone! To sync, your clock must be right also.
August 28, 2019, 03:07:36 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
Here is the output:
Code:

{
"Command": "createabn",
"xml": "ABN 320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429 ppk IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg= B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp 125000 ",
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
I checked the debug log and don't see any errors. Just a mention that the miner is starting. Wallet is also unlocked.
Things look OK from what I see - you have a valid self funded ABN.
You are mining, except your pool mining is not working.
What HPS are you mining at now btw, is it > 50K?
I don't see you hitting the pool. I see your workerid was set up correctly as self funded.
The biblepay.conf looks OK.
One thing I would suggest is copying the values out to notepad, recreate your biblepay.conf natively on your machine, be sure to manually press
Ive heard of a few reports where people are somehow saving the biblepay conf with the wrong crlf delimiters for the platform.
That might be why biblepay cant see your pool settings.
On a side note, you can test that by entering: genproclimit=10 in the biblepay conf, restart the core wallet and see if you are mining on 10 threads.
That means its reading your file.
Hmmm.. So nothing changed in the configuration file.. JS4A_nonFund was working fine and now this. It actually shows a hash rate of 60K roughly. Here is all of the information. NOTE this is Unix so not sure if your report takes unix versus windows into account.
14:38:15
getmininginfo
14:38:15
{
"blocks": 141264,
"currentblocksize": 6017,
"currentblocktx": 5,
"difficulty": 2597.454714352067,
"errors": "",
"pooledtx": 4,
"chain": "main",
"genproclimit": 5,
"networkhashps": 441124.3315571712,
"hashps": 55350.11507858223,
"minerstarttime": "08-28-2019 19:15:21",
"hashcounter": 75753828,
"pooledtx": 4,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
"gsc_errors": "",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
14:40:05
exec getabnweight 125000 1
14:40:05
{
"Command": "getabnweight",
"version": 2.7,
"weight": 240342.0501041666,
"total_required": 204140,
"coin_age_data_pre_select": "1434.6309(0.47)=[668.83] depth=103,
"weight 125000.00": 239662.6823263889,
"total_required 125000.00": 61324
}
2019-08-28 19:39:19
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:20 ERROR: invalid header received
2019-08-28 19:39:20 ProcessMessages(headers, 2593 bytes) FAILED peer=21
2019-08-28 19:39:21 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:21 ERROR: invalid header received
2019-08-28 19:39:21 ProcessMessages(headers, 2593 bytes) FAILED peer=22
2019-08-28 19:39:22 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:22 ERROR: invalid header received
2019-08-28 19:39:22 ProcessMessages(headers, 2593 bytes) FAILED peer=23
2019-08-28 19:39:23 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:23 ERROR: invalid header received
2019-08-28 19:39:23 ProcessMessages(headers, 2593 bytes) FAILED peer=24
2019-08-28 19:39:24 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:24 ERROR: invalid header received
2019-08-28 19:39:24 ProcessMessages(headers, 2593 bytes) FAILED peer=25
That other reply was for NSummy; for you just ensure you disagree with this hash:
14:39:53

getblockhash 141295
14:39:53

5b2c67deaa0a9d2a460f42b485b6deffe47d6e0e9c20a319904a6735e69d290e
and if so just restart with the erasechain=1.
ABN's do not work at all if you are out of sync. They completely hose out with multiple errors, and, the pool rejects 90% of the work too.
Would appear to be hung up at 141264. UGH
August 28, 2019, 03:04:29 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
Here is the output:
Code:

{
"Command": "createabn",
"xml": "ABN 320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429 ppk IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg= B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp 125000 ",
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
I checked the debug log and don't see any errors. Just a mention that the miner is starting. Wallet is also unlocked.
Things look OK from what I see - you have a valid self funded ABN.
You are mining, except your pool mining is not working.
What HPS are you mining at now btw, is it > 50K?
I don't see you hitting the pool. I see your workerid was set up correctly as self funded.
The biblepay.conf looks OK.
One thing I would suggest is copying the values out to notepad, recreate your biblepay.conf natively on your machine, be sure to manually press
Ive heard of a few reports where people are somehow saving the biblepay conf with the wrong crlf delimiters for the platform.
That might be why biblepay cant see your pool settings.
On a side note, you can test that by entering: genproclimit=10 in the biblepay conf, restart the core wallet and see if you are mining on 10 threads.
That means its reading your file.
Deleting and recreating the biblepay.conf fixed the issue. I'll admit I thought that was a crazy fix and it would never work, but I am pleasantly surprised
Thanks! August 28, 2019, 02:50:27 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
Here is the output:
Code:

{
"Command": "createabn",
"xml": "ABN 320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429 ppk IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg= B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp 125000 ",
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794,
22.5742(191.78)=[4219.07] depth=39098,
157.7800(168.80)=[26502.18] depth=34469,
198.7185(169.87)=[33633.69] depth=34674,
290.1681(179.03)=[51918.01] depth=37339,
321.2411(179.03)=[57467.87] depth=36929,
|
992.56 174082 ",
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
I checked the debug log and don't see any errors. Just a mention that the miner is starting. Wallet is also unlocked.
Things look OK from what I see - you have a valid self funded ABN.
You are mining, except your pool mining is not working.
What HPS are you mining at now btw, is it > 50K?
I don't see you hitting the pool. I see your workerid was set up correctly as self funded.
The biblepay.conf looks OK.
One thing I would suggest is copying the values out to notepad, recreate your biblepay.conf natively on your machine, be sure to manually press
Ive heard of a few reports where people are somehow saving the biblepay conf with the wrong crlf delimiters for the platform.
That might be why biblepay cant see your pool settings.
On a side note, you can test that by entering: genproclimit=10 in the biblepay conf, restart the core wallet and see if you are mining on 10 threads.
That means its reading your file.
Hmmm.. So nothing changed in the configuration file.. JS4A_nonFund was working fine and now this. It actually shows a hash rate of 60K roughly. Here is all of the information. NOTE this is Unix so not sure if your report takes unix versus windows into account.
14:38:15
getmininginfo
14:38:15
{
"blocks": 141264,
"currentblocksize": 6017,
"currentblocktx": 5,
"difficulty": 2597.454714352067,
"errors": "",
"pooledtx": 4,
"chain": "main",
"genproclimit": 5,
"networkhashps": 441124.3315571712,
"hashps": 55350.11507858223,
"minerstarttime": "08-28-2019 19:15:21",
"hashcounter": 75753828,
"pooledtx": 4,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
"gsc_errors": "",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
14:40:05
exec getabnweight 125000 1
14:40:05
{
"Command": "getabnweight",
"version": 2.7,
"weight": 240342.0501041666,
"total_required": 204140,
"coin_age_data_pre_select": "1434.6309(0.47)=[668.83] depth=103,
"weight 125000.00": 239662.6823263889,
"total_required 125000.00": 61324
}
2019-08-28 19:39:19
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:20 ERROR: invalid header received
2019-08-28 19:39:20 ProcessMessages(headers, 2593 bytes) FAILED peer=21
2019-08-28 19:39:21 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:21 ERROR: invalid header received
2019-08-28 19:39:21 ProcessMessages(headers, 2593 bytes) FAILED peer=22
2019-08-28 19:39:22 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:22 ERROR: invalid header received
2019-08-28 19:39:22 ProcessMessages(headers, 2593 bytes) FAILED peer=23
2019-08-28 19:39:23 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:23 ERROR: invalid header received
2019-08-28 19:39:23 ProcessMessages(headers, 2593 bytes) FAILED peer=24
2019-08-28 19:39:24 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:24 ERROR: invalid header received
2019-08-28 19:39:24 ProcessMessages(headers, 2593 bytes) FAILED peer=25
That other reply was for NSummy; for you just ensure you disagree with this hash:
14:39:53

getblockhash 141295
14:39:53

5b2c67deaa0a9d2a460f42b485b6deffe47d6e0e9c20a319904a6735e69d290e
and if so just restart with the erasechain=1.
ABN's do not work at all if you are out of sync. They completely hose out with multiple errors, and, the pool rejects 90% of the work too.
Would appear to be hung up at 141264. UGH
August 28, 2019, 02:46:49 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
Here is the output:
Code:

{
"Command": "createabn",
"xml": "ABN 320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429 ppk IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg= B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp 125000 ",
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794, 22.5742(191.78)=[4219.07] depth=39098, 157.7800(168.80)=[26502.18] depth=34469, 198.7185(169.87)=[33633.69] depth=34674, 290.1681(179.03)=[51918.01] depth=37339, 321.2411(179.03)=[57467.87] depth=36929, 992.56 174082 ",
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794, 22.5742(191.78)=[4219.07] depth=39098, 157.7800(168.80)=[26502.18] depth=34469, 198.7185(169.87)=[33633.69] depth=34674, 290.1681(179.03)=[51918.01] depth=37339, 321.2411(179.03)=[57467.87] depth=36929, 992.56 174082 ",
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
|
|
{
"Command": "createabn",
"xml": "
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
I checked the debug log and don't see any errors. Just a mention that the miner is starting. Wallet is also unlocked.
Things look OK from what I see - you have a valid self funded ABN.
You are mining, except your pool mining is not working.
What HPS are you mining at now btw, is it > 50K?
I don't see you hitting the pool. I see your workerid was set up correctly as self funded.
The biblepay.conf looks OK.
One thing I would suggest is copying the values out to notepad, recreate your biblepay.conf natively on your machine, be sure to manually press
Ive heard of a few reports where people are somehow saving the biblepay conf with the wrong crlf delimiters for the platform.
That might be why biblepay cant see your pool settings.
On a side note, you can test that by entering: genproclimit=10 in the biblepay conf, restart the core wallet and see if you are mining on 10 threads.
That means its reading your file.
Hmmm.. So nothing changed in the configuration file.. JS4A_nonFund was working fine and now this. It actually shows a hash rate of 60K roughly. Here is all of the information. NOTE this is Unix so not sure if your report takes unix versus windows into account.
14:38:15
getmininginfo
14:38:15
{
"blocks": 141264,
"currentblocksize": 6017,
"currentblocktx": 5,
"difficulty": 2597.454714352067,
"errors": "",
"pooledtx": 4,
"chain": "main",
"genproclimit": 5,
"networkhashps": 441124.3315571712,
"hashps": 55350.11507858223,
"minerstarttime": "08-28-2019 19:15:21",
"hashcounter": 75753828,
"pooledtx": 4,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
"gsc_errors": "",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
14:40:05
exec getabnweight 125000 1
14:40:05
{
"Command": "getabnweight",
"version": 2.7,
"weight": 240342.0501041666,
"total_required": 204140,
"coin_age_data_pre_select": "1434.6309(0.47)=[668.83] depth=103,
"weight 125000.00": 239662.6823263889,
"total_required 125000.00": 61324
}
2019-08-28 19:39:19
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:20 ERROR: invalid header received
2019-08-28 19:39:20 ProcessMessages(headers, 2593 bytes) FAILED peer=21
2019-08-28 19:39:21 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:21 ERROR: invalid header received
2019-08-28 19:39:21 ProcessMessages(headers, 2593 bytes) FAILED peer=22
2019-08-28 19:39:22 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:22 ERROR: invalid header received
2019-08-28 19:39:22 ProcessMessages(headers, 2593 bytes) FAILED peer=23
2019-08-28 19:39:23 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:23 ERROR: invalid header received
2019-08-28 19:39:23 ProcessMessages(headers, 2593 bytes) FAILED peer=24
2019-08-28 19:39:24 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:24 ERROR: invalid header received
2019-08-28 19:39:24 ProcessMessages(headers, 2593 bytes) FAILED peer=25
That other reply was for NSummy; for you just ensure you disagree with this hash:
14:39:53

getblockhash 141295
14:39:53

5b2c67deaa0a9d2a460f42b485b6deffe47d6e0e9c20a319904a6735e69d290e
and if so just restart with the erasechain=1.
ABN's do not work at all if you are out of sync. They completely hose out with multiple errors, and, the pool rejects 90% of the work too.
August 28, 2019, 02:43:43 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
Here is the output:
Code:

{
"Command": "createabn",
"xml": "ABN 320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429 ppk IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg= B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp 125000 ",
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794, 22.5742(191.78)=[4219.07] depth=39098, 157.7800(168.80)=[26502.18] depth=34469, 198.7185(169.87)=[33633.69] depth=34674, 290.1681(179.03)=[51918.01] depth=37339, 321.2411(179.03)=[57467.87] depth=36929, 992.56 174082 ",
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794, 22.5742(191.78)=[4219.07] depth=39098, 157.7800(168.80)=[26502.18] depth=34469, 198.7185(169.87)=[33633.69] depth=34674, 290.1681(179.03)=[51918.01] depth=37339, 321.2411(179.03)=[57467.87] depth=36929, 992.56 174082 ",
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
|
|
{
"Command": "createabn",
"xml": "
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
I checked the debug log and don't see any errors. Just a mention that the miner is starting. Wallet is also unlocked.
Things look OK from what I see - you have a valid self funded ABN.
You are mining, except your pool mining is not working.
What HPS are you mining at now btw, is it > 50K?
I don't see you hitting the pool. I see your workerid was set up correctly as self funded.
The biblepay.conf looks OK.
One thing I would suggest is copying the values out to notepad, recreate your biblepay.conf natively on your machine, be sure to manually press
Ive heard of a few reports where people are somehow saving the biblepay conf with the wrong crlf delimiters for the platform.
That might be why biblepay cant see your pool settings.
On a side note, you can test that by entering: genproclimit=10 in the biblepay conf, restart the core wallet and see if you are mining on 10 threads.
That means its reading your file.
Hmmm.. So nothing changed in the configuration file.. JS4A_nonFund was working fine and now this. It actually shows a hash rate of 60K roughly. Here is all of the information. NOTE this is Unix so not sure if your report takes unix versus windows into account.
14:38:15
getmininginfo
14:38:15
{
"blocks": 141264,
"currentblocksize": 6017,
"currentblocktx": 5,
"difficulty": 2597.454714352067,
"errors": "",
"pooledtx": 4,
"chain": "main",
"genproclimit": 5,
"networkhashps": 441124.3315571712,
"hashps": 55350.11507858223,
"minerstarttime": "08-28-2019 19:15:21",
"hashcounter": 75753828,
"pooledtx": 4,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "ABN: OK; ABN: OK; ABN: OK; ABN: OK; ABN: OK; ",
"gsc_errors": "",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 125000
}
14:40:05
exec getabnweight 125000 1
14:40:05
{
"Command": "getabnweight",
"version": 2.7,
"weight": 240342.0501041666,
"total_required": 204140,
"coin_age_data_pre_select": "1434.6309(0.47)=[668.83] depth=103,
"weight 125000.00": 239662.6823263889,
"total_required 125000.00": 61324
}
2019-08-28 19:39:19
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000
CSuperblockManager::IsGSCSuperblockTriggered - Height 141265.000000, Votes 27.000000, Required Votes 18.000000, Status 1.000000ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:20 ERROR: invalid header received
2019-08-28 19:39:20 ProcessMessages(headers, 2593 bytes) FAILED peer=21
2019-08-28 19:39:21 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:21 ERROR: invalid header received
2019-08-28 19:39:21 ProcessMessages(headers, 2593 bytes) FAILED peer=22
2019-08-28 19:39:22 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:22 ERROR: invalid header received
2019-08-28 19:39:22 ProcessMessages(headers, 2593 bytes) FAILED peer=23
2019-08-28 19:39:23 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:23 ERROR: invalid header received
2019-08-28 19:39:23 ProcessMessages(headers, 2593 bytes) FAILED peer=24
2019-08-28 19:39:24 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:39:24 ERROR: invalid header received
2019-08-28 19:39:24 ProcessMessages(headers, 2593 bytes) FAILED peer=25
August 28, 2019, 02:42:04 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
is everything ok after the superblock was generated.. Started getting alerts from my miners like this
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=4
2019-08-28 19:18:00 Misbehaving: 23.95.70.118:40000 peer=3 (0 -> 20)
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=3
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=13
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=8
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=18
2019-08-28 19:18:00 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:00 ERROR: invalid header received
2019-08-28 19:18:00 ProcessMessages(headers, 2269 bytes) FAILED peer=15
2019-08-28 19:18:01 ERROR: AcceptBlockHeader: block 70a5ba2a33f04880bbad605d2463cd835704086c11a0bb988d952908ba48e3ed is marked invalid
2019-08-28 19:18:01 ERROR: invalid header received
2019-08-28 19:18:01 ProcessMessages(headers, 2269 bytes) FAILED peer=16
I have tried zapping wallet and no changes..
Ill run my new hash report. Hang on.
So in this case appears to be isolated to your node thank Goodness (sorry, not good for you, good for the Body).
Yeah, no sancs disagree with each other, all GSC health is equal, and the report agrees with chainz:
14:39:53

getblockhash 141295
14:39:53

5b2c67deaa0a9d2a460f42b485b6deffe47d6e0e9c20a319904a6735e69d290e
If you are out of sync just restart the node with this switch:
-erasechain=1
This next release, we will have a quick sync option for faster syncing.
August 28, 2019, 02:35:14 PM
Also. I am trying to do the pool mining. Here is my Conf:
Output is this for mining info:
I have created the worker on the pool site. Any clue why this isn't working?
Code:
addnode=explorer.biblepay.org
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
pool=https://pool.biblepay.org
workerid=iowaiowa
gen=1
genproclimit=1
Output is this for mining info:
Code:
"blocks": 141280,
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
"currentblocksize": 6255,
"currentblocktx": 3,
"difficulty": 4812.805875096818,
"errors": "",
"pooledtx": 1,
"chain": "main",
"genproclimit": 1,
"networkhashps": 483287.588282664,
"hashps": 0.5556035973711518,
"minerstarttime": "08-28-2019 17:57:19",
"hashcounter": 257,
"pooledtx": 1,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolinfo5": "",
"abninfo": "",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 125000
I have created the worker on the pool site. Any clue why this isn't working?
Could you please paste the output of 'exec createabn 125000'?
Adding 'minersleep=-1' to your config will also help speed up the miner.
On a side note, if you tail the end of debug.log and search for 'miner' there is probably an error (that is supposed to be bubbled to getmininginfo however).
EDIT2: You may need to run with an unlocked wallet for now (we have a new command for headless unlocking that you can script if you want); but this unlocked wallet allows the core to create an ABN for the miner.
Here is the output:
Code:

{
"Command": "createabn",
"xml": "ABN 320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429 ppk IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg= B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp 125000 ",
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794, 22.5742(191.78)=[4219.07] depth=39098, 157.7800(168.80)=[26502.18] depth=34469, 198.7185(169.87)=[33633.69] depth=34674, 290.1681(179.03)=[51918.01] depth=37339, 321.2411(179.03)=[57467.87] depth=36929, 992.56 174082 ",
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,1.0320(170.44)=[170.44] depth=34794, 22.5742(191.78)=[4219.07] depth=39098, 157.7800(168.80)=[26502.18] depth=34469, 198.7185(169.87)=[33633.69] depth=34674, 290.1681(179.03)=[51918.01] depth=37339, 321.2411(179.03)=[57467.87] depth=36929, 992.56 174082 ",
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
|
|
{
"Command": "createabn",
"xml": "
"err": "",
"coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,
"success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
"coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,
"audited_weight": 175807.7228347543,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 58067.31, Age: 180.90, Amount: 321.00, TxTime: 1551390951...Output #1, Weight: 170.28, Age: 170.28, Amount: 1.00, TxTime: 1552308157...Output #2, Weight: 33634.66, Age: 169.87, Amount: 198.00, TxTime: 1552343341...Output #3, Weight: 4218.95, Age: 191.77, Amount: 22.00, TxTime: 1550451304...Output #4, Weight: 170.44, Age: 170.44, Amount: 1.00, TxTime: 1552294251...Output #5, Weight: 53043.13, Age: 182.91, Amount: 290.00, TxTime: 1551217091...Output #6, Weight: 26502.95, Age: 168.81, Amount: 157.00, TxTime: 1552435222..."
}
I checked the debug log and don't see any errors. Just a mention that the miner is starting. Wallet is also unlocked.
Things look OK from what I see - you have a valid self funded ABN.
You are mining, except your pool mining is not working.
What HPS are you mining at now btw, is it > 50K?
I don't see you hitting the pool. I see your workerid was set up correctly as self funded.
The biblepay.conf looks OK.
One thing I would suggest is copying the values out to notepad, recreate your biblepay.conf natively on your machine, be sure to manually press
Ive heard of a few reports where people are somehow saving the biblepay conf with the wrong crlf delimiters for the platform.
That might be why biblepay cant see your pool settings.
On a side note, you can test that by entering: genproclimit=10 in the biblepay conf, restart the core wallet and see if you are mining on 10 threads.
That means its reading your file.
Jump to: