what happend?
my pc is win10 and ver:1.4.4.4
"poolinfo5": "Internal ABN: Invalid 1563959825; ",
"abninfo": "Received a stale block from the pool... Please wait... ;
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 112. (Read 243386 times)
July 24, 2019, 04:23:46 AM
July 23, 2019, 10:47:46 PM
We need 2 more sancs in testnet to test LLMQs then ChainLocks:
https://forum.biblepay.org/index.php?topic=391.msg6230#msg6230
Please join.
https://forum.biblepay.org/index.php?topic=391.msg6230#msg6230
Please join.
This testing in testnet could not be having some impact on the pool mining could it? Seems as if the leaderboard is barren and miners are either unable to connect or the pool is not showing them connected.
July 23, 2019, 10:07:39 PM
*** HAPPY SECOND BIRTHDAY, BIBLE PAY! ***
https://pool.biblepay.org/SAN/Mission/SecondBirthdayBiblePay.jpg
May this year bring you the rich blessings promised to the Gentiles and God's chosen people, and may we as a community bring God fruit worthy of repentance and salvation.
Each year, I will attempt to make the cake higher as we add more successful features.
https://pool.biblepay.org/SAN/Mission/SecondBirthdayBiblePay.jpg
May this year bring you the rich blessings promised to the Gentiles and God's chosen people, and may we as a community bring God fruit worthy of repentance and salvation.
Each year, I will attempt to make the cake higher as we add more successful features.
Congrats on 2 years and here is to many many more!! Nice work Rob and team!
July 23, 2019, 08:58:45 PM
We need 2 more sancs in testnet to test LLMQs then ChainLocks:
https://forum.biblepay.org/index.php?topic=391.msg6230#msg6230
Please join.
https://forum.biblepay.org/index.php?topic=391.msg6230#msg6230
Please join.
July 23, 2019, 11:15:16 AM
Also everyone, tomorrow is the 2 year anniversary of BiblePay!
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
Awesome! 2 years might not sound like a lot, but in the crypto-sphere - in my opinion - that makes us veterans
Thank you Jaap for your inspiring words! You beat me to the punch. This calls for a Birthday Cake.
Thank you Loyal BiblePay Veterans - and All Users - for making us who and what we are!
Thank you God for getting us this far, and may we be a blessing for your Kingdom, Jesus!
May we bear good Christian fruit for you over the Long Term.
Of course, thanks to everyone that is involved for giving this project time and energy, but we wouldn't be here without you Rob: thank you for your astonishing dedication! It's an inspiration.
July 23, 2019, 09:14:14 AM
The explorer looks like its doing well now
http://explorer.biblepay.org/
https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/
https://chainz.cryptoid.info/bbp/
Great! So the whole time, I make the assumption that the internal BiblePay node was synced, but due to the bug in processing empty coinbases, we generally broke the iquidis explorer regularly. LOL.
This is a great step forward though, it should help us ensure we are fork free for long periods of time.
Lets shoot for being fork free until Chain Locks is deployed, and then fork free forever.
We need 100% accuracy going forward.
July 23, 2019, 09:08:19 AM
*** HAPPY SECOND BIRTHDAY, BIBLE PAY! ***
May this year bring you the rich blessings promised to the Gentiles and God's chosen people, and may we as a community bring God fruit worthy of repentance and salvation.
Each year, I will attempt to make the cake higher as we add more successful features.
May this year bring you the rich blessings promised to the Gentiles and God's chosen people, and may we as a community bring God fruit worthy of repentance and salvation.
Each year, I will attempt to make the cake higher as we add more successful features.
July 23, 2019, 09:04:22 AM
Also everyone, tomorrow is the 2 year anniversary of BiblePay!
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
Awesome! 2 years might not sound like a lot, but in the crypto-sphere - in my opinion - that makes us veterans
Thank you Jaap for your inspiring words! You beat me to the punch. This calls for a Birthday Cake.
Thank you Loyal BiblePay Veterans - and All Users - for making us who and what we are!
Thank you God for getting us this far, and may we be a blessing for your Kingdom, Jesus!
May we bear good Christian fruit for you over the Long Term.
July 23, 2019, 08:54:10 AM
Rob, I worry I'm in a lose lose situation,
if I'm honest with you I believe I am going to upset you, and by not responding I've upset you
Is it okay for me to be fully honest with you?
If so, I will write back soon
To everyone else, the core of the conversation is about moderation in the Discord
if I'm honest with you I believe I am going to upset you, and by not responding I've upset you
Is it okay for me to be fully honest with you?
If so, I will write back soon
To everyone else, the core of the conversation is about moderation in the Discord
Well - its not just about Discord because I've worked with you on all kinds of things from advice for DAHF, exchange implementations, helping me with BLOOM, the wikis and previous features - but Discord was just the issue that came up last month when MIPs call was reversed. But we can talk about it via Email because some parts of things I discuss with you arent public knowledge yet.
I always wanted you to be honest with me and never have changed. Im sorry that the perception was somehow created that I want to be glorified in some way with only positive information or surround myself with people that are loving. The truth of the matter is I surround myself with intelligent advisors that tend to make good calls and these resonate with me (over the LONG term) and they also resonate with God (in that I bring issues to God in the prayer closet) and some go and some stay. I admitted PODC dragged everyone through something that the Holy spirit did not necessarily approve of (in the way we implemented it) and changed course to be more aligned with God's policies and as you can see Ive been very persistent and supportive.
So yes, I invite you to first open up a conversation with me about this problem and then we will move on to the other topics. And yes I want you to be brutally honest. Just like I was when I mentioned the problem (or my perception of it) to you. I want to work with you, absolutely, and thats why Im being persistent because of how much time you have invested in this project and how valuable and committed you have been over the long term.
July 23, 2019, 08:49:19 AM
Also everyone, tomorrow is the 2 year anniversary of BiblePay!
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
Awesome! 2 years might not sound like a lot, but in the crypto-sphere - in my opinion - that makes us veterans
July 22, 2019, 10:10:10 PM
Also everyone, tomorrow is the 2 year anniversary of BiblePay!
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
Original Bitcointalk ANN:
https://bitcointalksearch.org/topic/biblepay-new-coin-launch-official-thread-2042657
July 22, 2019, 10:08:43 PM
Rob, I worry I'm in a lose lose situation,
if I'm honest with you I believe I am going to upset you, and by not responding I've upset you
Is it okay for me to be fully honest with you?
If so, I will write back soon
To everyone else, the core of the conversation is about moderation in the Discord
if I'm honest with you I believe I am going to upset you, and by not responding I've upset you
Is it okay for me to be fully honest with you?
If so, I will write back soon
To everyone else, the core of the conversation is about moderation in the Discord
July 22, 2019, 09:22:55 PM
The explorer looks like its doing well now
http://explorer.biblepay.org/
https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/
https://chainz.cryptoid.info/bbp/
July 22, 2019, 04:12:49 PM
BiblePay
1.4.4.4 - Leisure Upgrade
- Remove log spam
- Upgrade BiblePay Pool protocol to v2.0 (Upgrade busywait to mutex, add
two-way comm and handling of reply commands, add pool deadline support,
allow funded & non-funded mining at the same time per user)
- Handle bad nBits in pool mined blocks gracefully (and ddos
gracefully), and remove Pool log spam
- Disconnect nodes who spam us with bad block headers
** Pool Miners: please upgrade within 7 days **
1.4.4.4 - Leisure Upgrade
- Remove log spam
- Upgrade BiblePay Pool protocol to v2.0 (Upgrade busywait to mutex, add
two-way comm and handling of reply commands, add pool deadline support,
allow funded & non-funded mining at the same time per user)
- Handle bad nBits in pool mined blocks gracefully (and ddos
gracefully), and remove Pool log spam
- Disconnect nodes who spam us with bad block headers
** Pool Miners: please upgrade within 7 days **
July 22, 2019, 12:21:05 PM
Had a random no error crash on one machine this morning. Saw this as the last entry in my debug log, any thoughts? Thanks!
2019-07-22 15:07:07
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:07:08
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:10:24 MASTERNODEPAYMENTSYNC -- Sent Masternode payment votes to peer=193
2019-07-22 15:07:07
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:07:08
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:10:24 MASTERNODEPAYMENTSYNC -- Sent Masternode payment votes to peer=193
Thats actually the pool error Im working on now; that will be eliminated in this new version.
Its harmless though and should not cause a crash, or the node to go out of sync.
July 22, 2019, 11:51:31 AM
Had a random no error crash on one machine this morning. Saw this as the last entry in my debug log, any thoughts? Thanks!
2019-07-22 15:07:07
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:07:08
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:10:24 MASTERNODEPAYMENTSYNC -- Sent Masternode payment votes to peer=193
2019-07-22 15:07:07
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:07:08
ContextualCheckBlockHeader::FAILED incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000ERROR: TestBlockValidityLite: Consensus::ContextualCheckBlockHeader: bad-diffbits, incorrect proof of work at 133375, block.nbits 469826094.000000, next work 469809611.000000 (code 16)
2019-07-22 15:10:24 MASTERNODEPAYMENTSYNC -- Sent Masternode payment votes to peer=193
July 22, 2019, 09:21:56 AM
** Today's Goal **
- We are currently running 1.4.4.3.
- We successfully support funded and non funded mining. I think the ABN endeavor is turning out to be a success, as we are attracting new users, and this environment is satisfying both newbies who do not want to hold bbp and satisfying old-timers who want to provide the ABNs.
- The pool is still running in protocol v1.0.
- Some log spam exists related to ABN/funded mining activing, checkblock errors due to stale blocks from the pool, and some nodes seem to get banned occasionally.
Proposed Solution:
- Release pool mining protocol version 2.0. This allows funded or non-funded mining in the pool without limitations, and provides more accurate health info.
- Remove log spam.
- Ensure blocks from the pool are not causing log spam issues. Address any pool checkblockvaliditylite errors. Ensure miners are not being d-dossed for bad block nBits or blockheaders.
I will notify when the new version is ready. This is a leisure upgrade.
** Near Term Future **
- Update the roadmap goals for Q3. Share the BiblePay goals (as related to Christian Spaces/HTML5) with the forum.
- Make the users aware of a new project we will implement towards the end of the year and how they can help with this project.
- We are currently running 1.4.4.3.
- We successfully support funded and non funded mining. I think the ABN endeavor is turning out to be a success, as we are attracting new users, and this environment is satisfying both newbies who do not want to hold bbp and satisfying old-timers who want to provide the ABNs.
- The pool is still running in protocol v1.0.
- Some log spam exists related to ABN/funded mining activing, checkblock errors due to stale blocks from the pool, and some nodes seem to get banned occasionally.
Proposed Solution:
- Release pool mining protocol version 2.0. This allows funded or non-funded mining in the pool without limitations, and provides more accurate health info.
- Remove log spam.
- Ensure blocks from the pool are not causing log spam issues. Address any pool checkblockvaliditylite errors. Ensure miners are not being d-dossed for bad block nBits or blockheaders.
I will notify when the new version is ready. This is a leisure upgrade.
** Near Term Future **
- Update the roadmap goals for Q3. Share the BiblePay goals (as related to Christian Spaces/HTML5) with the forum.
- Make the users aware of a new project we will implement towards the end of the year and how they can help with this project.
July 21, 2019, 08:23:27 PM
Two of my machines that I started with -erasechain=1 yesterday have again come out of sync. I'm doing erasechain again but I'm wondering if this is caused by explorer.biblepay.org being stuck?
Let's try to find the root cause. Do you happen to have the log of one of the machines before it went out of sync?
B) Is this machine running with litemode=1?
We need to see if the machine is having trouble getting gov data.
Do you have tons of banned peers in the peers list?
They're not running in litemode, I'll try that if it happens again. I'll also get a copy of the logs and check the banned peers too and let you know. Thanks!
July 21, 2019, 03:32:24 PM
If anyone is interested in Ken Peters "I saw the Tribulation" (and personally, I think it is very valuable and prophetic), I found this transcript of it:
https://z3news.com/w/ken-peters-tribulation/
Keep in mind he saw this in 1980 which is even more fascinating.
https://z3news.com/w/ken-peters-tribulation/
Keep in mind he saw this in 1980 which is even more fascinating.
July 21, 2019, 01:27:23 PM
https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/
Updated explorer to latest version, performed an erasechain, its synced back up now
I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)
Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features
Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257
http://explorer.biblepay.org/
Updated explorer to latest version, performed an erasechain, its synced back up now
I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)
Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features
Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257
This is more related to some prior projects - not iquidis, but its worth a try, could you try this in the config:
rpcthreads=500
litemode=1
And resync?
I was under the impression with Evo we were communicating much faster with Iquidis (I remember you said there is a big difference), but apparently iquidis gets hung occasionally.
So also could you clarify if the node itself is stuck 200 blocks behind, or is it iquidis that ceases to sync? (If its not the node, there is no need to resync the entire chain, if its iquidis we would just resync the iquidis database. But the rpc settings might help if its too dumb to recover). Maybe the daemon is dying, maybe research how to persistenly keep the daemon running also.
The daemon is running fine, its fully synced, checked blockhashes
(Theres a crontab firing every 5 minutes to make sure its running and restart it if it isnt)
I checked mongodb, log file was 5.3GB, not sure if that is slowing things down, deleted it
I edited the mongod.conf file to try to limit the logging [set quiet to enabled]
(easy worst case I can add a crontab to just delete the log file every day)
Running everything again, everything is going, but the website is not updating with latest blocks, weird,
but if you type in a block number it will show/load it
I started looking into the indexing process more, and it fires off and then disappears quick,
I sent the output to a file, theres an error in Iquidus
Code:
/home/explorer/lib/explorer.js:310
if (vout[0].scriptPubKey.type == 'nonstandard') {
^
TypeError: Cannot read property 'scriptPubKey' of undefined
at /home/explorer/lib/explorer.js:310:18
at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
at Object.module.exports.prepare_vout (/home/explorer/lib/explorer.js:284:20)
at /home/explorer/lib/database.js:141:17
at /home/explorer/lib/explorer.js:392:14
at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
at Object.module.exports.prepare_vin (/home/explorer/lib/explorer.js:369:20)
at /home/explorer/lib/database.js:140:15
at Request._callback (/home/explorer/lib/explorer.js:107:14)
at Request.self.callback (/home/explorer/node_modules/request/request.js:187:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.(/home/explorer/node_modules/request/request.js:1044:10)
at emitOne (events.js:77:13)
Looks like its happening in the 3rd parameter, an anonymous function, getting passed into syncLoop()
prepare_vout():
https://github.com/iquidus/explorer/blob/master/lib/explorer.js#L310
syncLoop():
https://github.com/iquidus/explorer/blob/c8ac131aed4f065b4f327ec379eaef2a006e5f50/lib/explorer.js#L169
Looks like this guy ran into similar issue
https://github.com/iquidus/explorer/issues/60
and posted this solution: https://github.com/cryptorex/bitcoinz-explorer/commit/267a0dfd8015bc90488b2b53ae9c49be2da83bff
Ill try adding it and report back
===
Iquidus Block Explorer Guide
https://www.reddit.com/r/BiblePay/comments/7elm7r/iquidus_block_explorer_guide/
===
Options:
1. Try to pinpoint the bug
2. Reset the mongo database to last backup and sync from there
3. Reset the mongo database entirely and sync from the beginning
4. Retire the explorer
5. Change URL to point to Chainz
6. Find and setup 2nd explorer service
1) Can you try applying this .js patch to the code right above the .type == 'nonstandard' in explorer.js and burn it in?
https://github.com/DeckerSU/explorer/commit/ac74e41c6162871fcaa6973d34f09f1cf3e5a1ce
If it works we can either find zcashs iquidis branch, and use it, or patch it based on a config setting in Iquidis' settings and push it to their github.
2) Are you going to address my comment about the PMs and emails?
Jump to: