Bitcoin Forum
March 29, 2020, 07:36:42 PM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 [769] 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 ... 863 »
  Print  
Author Topic: BiblePay | 10% to Orphan-Charity | POBH CPU | Sanctuaries (Masternodes)  (Read 210435 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic. (345 posts by 33 users deleted.)
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 07:08:37 PM
 #15361

On the topic of wallet links, there is a wallet page (with latest release version):
https://www.biblepay.org/wallet/

I do think on the menu, some links (like this one) are getting kind of hidden with the current design
some of the first level and second level menu items are actually links
vs just the leaf/end submenu items being the only links


Yeah, the wallet menu on the home page is not good - primarily because the hashes were just added to it.

Someone suggested another level being added to it to clean it up. 

To simplify things we could probably move the hashes to the wallet page (so they auto-update like our object tag does for the biblepay version on that page) and leave them only there permanently, at least it would would simplify the top level home page quite a bit.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1585510602
Hero Member
*
Offline Offline

Posts: 1585510602

View Profile Personal Message (Offline)

Ignore
1585510602
Reply with quote  #2

1585510602
Report to moderator
jsheets1970
Newbie
*
Offline Offline

Activity: 60
Merit: 0


View Profile
August 28, 2019, 07:27:50 PM
 #15362

Also. I am trying to do the pool mining.  Here is my Conf:

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.



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..
nsummy
Full Member
***
Offline Offline

Activity: 812
Merit: 115


View Profile
August 28, 2019, 07:28:10 PM
 #15363

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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.
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 07:29:59 PM
 #15364

Also. I am trying to do the pool mining.  Here is my Conf:

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.



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.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 07:35:14 PM
 #15365

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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 <ENTER> between each row and re-save and restart.

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.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 07:42:04 PM
 #15366

Also. I am trying to do the pool mining.  Here is my Conf:

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.



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.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
jsheets1970
Newbie
*
Offline Offline

Activity: 60
Merit: 0


View Profile
August 28, 2019, 07:43:43 PM
 #15367

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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 <ENTER> between each row and re-save and restart.

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,  <ROW>59889.9484(3.99)=[238993.85] depth=849,  <ROW><TOTALREQ>61324.58</TOTALREQ><TOTALAGE>239663</TOTALAGE>",
  "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
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 07:46:49 PM
 #15368

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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 <ENTER> between each row and re-save and restart.

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,  <ROW>59889.9484(3.99)=[238993.85] depth=849,  <ROW><TOTALREQ>61324.58</TOTALREQ><TOTALAGE>239663</TOTALAGE>",
  "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.



🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
jsheets1970
Newbie
*
Offline Offline

Activity: 60
Merit: 0


View Profile
August 28, 2019, 07:50:27 PM
 #15369

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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 <ENTER> between each row and re-save and restart.

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,  <ROW>59889.9484(3.99)=[238993.85] depth=849,  <ROW><TOTALREQ>61324.58</TOTALREQ><TOTALAGE>239663</TOTALAGE>",
  "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
nsummy
Full Member
***
Offline Offline

Activity: 812
Merit: 115


View Profile
August 28, 2019, 08:04:29 PM
 #15370

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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 <ENTER> between each row and re-save and restart.

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  Grin  Thanks!
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 08:07:36 PM
 #15371

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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 <ENTER> between each row and re-save and restart.

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,  <ROW>59889.9484(3.99)=[238993.85] depth=849,  <ROW><TOTALREQ>61324.58</TOTALREQ><TOTALAGE>239663</TOTALAGE>",
  "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
Thats very unusual; the only suggestion I have is to delete all the *.dat files in %appdata%\biblepayevolution including peers and banlist but never wallet.dat, and restart with the erasechain=1 switch.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 08:09:19 PM
 #15372

Also. I am trying to do the pool mining.  Here is my Conf:

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": "<MT>ABN</MT><abnmsg><nonce>320a036e4bc93bc38c048c1c9a2005a2c0c29831c11fd632d70fe739cf96b429</nonce><ppk>ppk</ppk></abnmsg><abnsig>IEfxcMe+61odCZHt7yBjVBzkt/JiCb/nnOeMdw8qea6NR5AbP0v1IGYbjDgGGLPdZF41yR/HH/CbwCkkDSAnROg=</abnsig><abncpk>B7vyYsLLpR1D59fGqGHNWLN5chDkeP9TGp</abncpk><abnwgt>125000</abnwgt>",
  "err": "",
  "coin_age_data_selected": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "success": "c9820885d38ed10aded2cb2b3589d10cd4b01136bc644464631907724e9525d3",
  "coin_age_data_pre_select": "1.0510(170.28)=[170.28] depth=34762,  <ROW>1.0320(170.44)=[170.44] depth=34794,  <ROW>22.5742(191.78)=[4219.07] depth=39098,  <ROW>157.7800(168.80)=[26502.18] depth=34469,  <ROW>198.7185(169.87)=[33633.69] depth=34674,  <ROW>290.1681(179.03)=[51918.01] depth=37339,  <ROW>321.2411(179.03)=[57467.87] depth=36929,  <ROW><TOTALREQ>992.56</TOTALREQ><TOTALAGE>174082</TOTALAGE>",
  "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 <ENTER> between each row and re-save and restart.

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


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
cuarc001
Newbie
*
Offline Offline

Activity: 98
Merit: 0


View Profile WWW
August 28, 2019, 09:46:50 PM
 #15373

Some miners tell you if the system clock is drifting out of sync. Does the BBP client do this?
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 28, 2019, 09:49:30 PM
 #15374

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.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
cuarc001
Newbie
*
Offline Offline

Activity: 98
Merit: 0


View Profile WWW
August 29, 2019, 12:45:46 AM
 #15375

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.
JakubKO
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
August 29, 2019, 06:23:27 AM
 #15376

Also. I am trying to do the pool mining.  Here is my Conf:

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.
nsummy
Full Member
***
Offline Offline

Activity: 812
Merit: 115


View Profile
August 30, 2019, 08:49:09 PM
 #15377

Also. I am trying to do the pool mining.  Here is my Conf:

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.
nsummy
Full Member
***
Offline Offline

Activity: 812
Merit: 115


View Profile
August 30, 2019, 08:53:32 PM
 #15378

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
MIP
Newbie
*
Offline Offline

Activity: 361
Merit: 0


View Profile
August 31, 2019, 04:08:50 PM
 #15379

Apollon Network

 confirmed me that BBP is finally enabled in their MN hosting platform.
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
August 31, 2019, 11:06:37 PM
 #15380

Apollon Network

 confirmed me that BBP is finally enabled in their MN hosting platform.

Great news!

Will test this network asap.

Thanks.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
Pages: « 1 ... 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 [769] 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 ... 863 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!