BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[oliwer21]

i think botnet is not problem, because this mandatory update was too quick to apply and many blocks are still solved outside of pool - so this must be solo mining.... huge solo mining

What mandatory update?

[1715418378]

1715418378

[1715418378]

1715418378

[1715418378]

1715418378

[1715418378]

1715418378

[togoshigekata]

BiblePay - Mandatory Upgrade v1.0.7.9

- Fix InstantSend Security Bug

Wallet Update Instructions: 
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

This is also a protocol version update, so Sanctuary owners will need to start Sanctuary again after updating

The instant send Signing process is finally fixed in 1.0.8.0 and requires one more leisure upgrade.

1.0.7.9 is OK for now as a miner or as a Sanctuary (its functions are OK).

1.0.8.0 will be required to successfully send IS funds and will be out this afternoon.

Sorry for the inability to test this- we just didn't have the 6 required distinct sanctuaries in testnet when we discovered the vulnerability.  We could have shut down instantsend with a spork, if we were already in prod at the exchanges, but since we were in the midst of an upgrade I decided to go this route.  I apologize for the hassles required in upgrading.

[capulo]

another observation: as there are still not all miners back in pool, i have +50% more hashes as usually
isnt pool a little bit overloaded with 4000+ miners? not only cpu but maybe conectivity or so...

[orbis]

i've updated my workers to 1079 and then to 1080.
Workers with 1079 are working good, but 1080 are still shutting down.
Index rebuild and blockchain rescan didn't work.
Any idea?

[bible_pay]

another observation: as there are still not all miners back in pool, i have +50% more hashes as usually
isnt pool a little bit overloaded with 4000+ miners? not only cpu but maybe conectivity or so...

Both gigabyte and Tiras offered to launch a second pool.  Im working with gigabyte still in PM.  I may double the size of the pool machine soon, as soon as things calm down.

Yeah, its starting to push the limits of the box.

[bible_pay]

1.0.8.0 Windows is out there now for anyone who wants to upgrade to the unofficial version.

I'm doing some more testing with instantsend before I make a release out of it.

[616westwarmoth]

i've updated my workers to 1079 and then to 1080.
Workers with 1079 are working good, but 1080 are still shutting down.
Index rebuild and blockchain rescan didn't work.
Any idea?

Same problem on Linux (masternode) here.

Last few lines of the debug

Code:

$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to ecfd06a3f7218f3f4150ec0631c16e4457a5b13850ade2048e081$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 9294e4d3ad53c118ede068dbbca0f9a434dd05efe3ce221f216bb$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 815c7a5ef013268f1b46c98d3321cddd4c9480604a27fcd86365e$
2018-01-14 19:22:35 ProcessNewBlock : ACCEPTED
2018-01-14 19:22:46 CMasternodeSync::ProcessTick -- nTick 433 nRequestedMasternodeAssets 4 -- asked for all objects, nothing to do
2018-01-14 19:22:46 CActiveMasternode::ManageStateRemote -- NOT_CAPABLE: Invalid protocol version
2018-01-14 19:23:08 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=7f735f7886b41dc36846e076e4802f3102a2845cfa02ad1610aa25f72f362e4f
2018-01-14 19:23:57

Have done the deletion steps as per normal, but will redo it all again and see if that corrects things.

[slovakia]

stop update from 179 to 180

few ppl calling that miners crashing/restarting/cant join to pool

stay on 179

[Freebish86]

Hey BiblePay community, few questions on those BBP coins you cant taste, touch or smell, but helps out those in need.

1.How do I tract down coins that were sent from pool last night on 1/13/18 and didn’t show up in BBP wallet?
2.How do I update to the new wallet version without losing my current BBP coins? Is there an update version button on the current wallet that I am not seeing? Do I have to download new wallet on a different CPU and send coin to the updated wallet?
3. Any update on getting a hard wallet like nano s or Trezor to support BBP coin?

Thanks
Freebish86

[Freebish86]

stop update from 179 to 180

few ppl calling that miners crashing/restarting/cant join to pool

stay on 179

Mine crashed this morning up now says pool is down when type get mining info, but solo mining. Will I even be able to mine BBP coin Solo Mining? How do you even claim solomining coins if the pool is down?

Thanks
Freebish86

[orbis]

Hey BiblePay community, few questions on those BBP coins you cant taste, touch or smell, but helps out those in need.

1.How do I tract down coins that were sent from pool last night on 1/13/18 and didn’t show up in BBP wallet?
2.How do I update to the new wallet version without losing my current BBP coins? Is there an update version button on the current wallet that I am not seeing? Do I have to download new wallet on a different CPU and send coin to the updated wallet?
3. Any update on getting a hard wallet like nano s or Trezor to support BBP coin?

Thanks
Freebish86

Hi,
1. when you update your wallet, you will see those coins.
2. try this Togo's notes: https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
3. no, nothing new

[togoshigekata]

i've updated my workers to 1079 and then to 1080.
Workers with 1079 are working good, but 1080 are still shutting down.
Index rebuild and blockchain rescan didn't work.
Any idea?

Same problem on Linux (masternode) here.

Last few lines of the debug

Code:

$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to ecfd06a3f7218f3f4150ec0631c16e4457a5b13850ade2048e081$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 9294e4d3ad53c118ede068dbbca0f9a434dd05efe3ce221f216bb$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 815c7a5ef013268f1b46c98d3321cddd4c9480604a27fcd86365e$
2018-01-14 19:22:35 ProcessNewBlock : ACCEPTED
2018-01-14 19:22:46 CMasternodeSync::ProcessTick -- nTick 433 nRequestedMasternodeAssets 4 -- asked for all objects, nothing to do
2018-01-14 19:22:46 CActiveMasternode::ManageStateRemote -- NOT_CAPABLE: Invalid protocol version
2018-01-14 19:23:08 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=7f735f7886b41dc36846e076e4802f3102a2845cfa02ad1610aa25f72f362e4f
2018-01-14 19:23:57

Have done the deletion steps as per normal, but will redo it all again and see if that corrects things.

Code:

~/.biblepaycore# tail debug.log
2018-01-14 19:49:09 ProcessNewBlock : ACCEPTED
2018-01-14 19:49:11 UpdateTip: new best=26757576fef122443723e167f03d7f3161cd86bf96573a8ec94e2187386d21dd  height=25714  log2_work=58.683441  tx=53573  date=2018-01-14 19:44:24 progress=0.999986  cache=0.2MiB(439tx)
2018-01-14 19:49:11 CMasternode::UpdateLastPaidBlock -- searching for block with payment to fb1b5c56a513f37c33be64e229d9acfe7486b71f32d043f59022962cda6a0046-1 -- found new 25714.000000
2018-01-14 19:49:11 ProcessNewBlock : ACCEPTED
2018-01-14 19:49:19 CMasternodePing::CheckAndUpdate -- Masternode ping is invalid, block hash is too old: masternode=b29b0c07400304c85de00f5f448a098d143661b9b22b77a843d91acdd3623a2c-0  blockHash=fd80aaacadcff4bafe0bddc82dadc91d16662904747f79bc47b9bca73e9ddd3f
2018-01-14 19:49:19 CMasternodePing::CheckAndUpdate -- Masternode ping is invalid, block hash is too old: masternode=6cdd1a4a7bb2d9b8907d2765f7f54a7ac4ba4aab9cd9b13dcf4d9f0a4bd5faeb-0  blockHash=fd80aaacadcff4bafe0bddc82dadc91d16662904747f79bc47b9bca73e9ddd3f
2018-01-14 19:49:31 CActiveMasternode::ManageStateRemote -- STARTED!
2018-01-14 19:50:49 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=1b94e86f076abac784bbd2558f566e1310e0dce146b471b9f8598a83b34b8d5e
2018-01-14 19:51:17 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=3506ea16a1643956905d1f44733ee982f113db783da32c0a55b7f7f524e82276
2018-01-14 19:51:21 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=7f735f7886b41dc36846e076e4802f3102a2845cfa02ad1610aa25f72f362e4f

Im also experiencing crashing, posted last lines of debug.log

[bible_pay]

i've updated my workers to 1079 and then to 1080.
Workers with 1079 are working good, but 1080 are still shutting down.
Index rebuild and blockchain rescan didn't work.
Any idea?

Same problem on Linux (masternode) here.

Last few lines of the debug

Code:

$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to ecfd06a3f7218f3f4150ec0631c16e4457a5b13850ade2048e081$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 9294e4d3ad53c118ede068dbbca0f9a434dd05efe3ce221f216bb$
2018-01-14 19:22:35 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 815c7a5ef013268f1b46c98d3321cddd4c9480604a27fcd86365e$
2018-01-14 19:22:35 ProcessNewBlock : ACCEPTED
2018-01-14 19:22:46 CMasternodeSync::ProcessTick -- nTick 433 nRequestedMasternodeAssets 4 -- asked for all objects, nothing to do
2018-01-14 19:22:46 CActiveMasternode::ManageStateRemote -- NOT_CAPABLE: Invalid protocol version
2018-01-14 19:23:08 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=7f735f7886b41dc36846e076e4802f3102a2845cfa02ad1610aa25f72f362e4f
2018-01-14 19:23:57

Have done the deletion steps as per normal, but will redo it all again and see if that corrects things.

Code:

~/.biblepaycore# tail debug.log
2018-01-14 19:49:09 ProcessNewBlock : ACCEPTED
2018-01-14 19:49:11 UpdateTip: new best=26757576fef122443723e167f03d7f3161cd86bf96573a8ec94e2187386d21dd  height=25714  log2_work=58.683441  tx=53573  date=2018-01-14 19:44:24 progress=0.999986  cache=0.2MiB(439tx)
2018-01-14 19:49:11 CMasternode::UpdateLastPaidBlock -- searching for block with payment to fb1b5c56a513f37c33be64e229d9acfe7486b71f32d043f59022962cda6a0046-1 -- found new 25714.000000
2018-01-14 19:49:11 ProcessNewBlock : ACCEPTED
2018-01-14 19:49:19 CMasternodePing::CheckAndUpdate -- Masternode ping is invalid, block hash is too old: masternode=b29b0c07400304c85de00f5f448a098d143661b9b22b77a843d91acdd3623a2c-0  blockHash=fd80aaacadcff4bafe0bddc82dadc91d16662904747f79bc47b9bca73e9ddd3f
2018-01-14 19:49:19 CMasternodePing::CheckAndUpdate -- Masternode ping is invalid, block hash is too old: masternode=6cdd1a4a7bb2d9b8907d2765f7f54a7ac4ba4aab9cd9b13dcf4d9f0a4bd5faeb-0  blockHash=fd80aaacadcff4bafe0bddc82dadc91d16662904747f79bc47b9bca73e9ddd3f
2018-01-14 19:49:31 CActiveMasternode::ManageStateRemote -- STARTED!
2018-01-14 19:50:49 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=1b94e86f076abac784bbd2558f566e1310e0dce146b471b9f8598a83b34b8d5e
2018-01-14 19:51:17 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=3506ea16a1643956905d1f44733ee982f113db783da32c0a55b7f7f524e82276
2018-01-14 19:51:21 CInstantSend::CreateEmptyTxLockCandidate -- new, txid=7f735f7886b41dc36846e076e4802f3102a2845cfa02ad1610aa25f72f362e4f

Im also experiencing crashing, posted last lines of debug.log

Ok, this appears to be 1.0.8.0 only -- working on resolving this...

[gorbi]

Where to get version 1.0.7.9?
On BiblePay website: http://biblepay.org/ we have 1.0.8.0.

[bible_pay]

Where to get version 1.0.7.9?
On BiblePay website: http://biblepay.org/ we have 1.0.8.0.

I rolled back to 1.0.7.9 on the official web site.

Please try now.

As far as the bug, I found the issue- we will have this final release out in a few hours.

Linux is ready now if anyone wants the unofficial version for testing (1.0.8.0b).

[joelles]

Where to get version 1.0.7.9?
On BiblePay website: http://biblepay.org/ we have 1.0.8.0.

I rolled back to 1.0.7.9 on the official web site.

Please try now.

As far as the bug, I found the issue- we will have this final release out in a few hours.

Linux is ready now if anyone wants the unofficial version for testing (1.0.8.0b).

hi

thank you, i push update in 10hr to all my machine..

current one is still crash for me, updated 35 vms with rsync and most crash.

[oliwer21]

pool is down?

[togoshigekata]

Where to get version 1.0.7.9?
On BiblePay website: http://biblepay.org/ we have 1.0.8.0.

I rolled back to 1.0.7.9 on the official web site.

Please try now.

As far as the bug, I found the issue- we will have this final release out in a few hours.

Linux is ready now if anyone wants the unofficial version for testing (1.0.8.0b).

Good find Rob! Can't make an omelette without breaking some eggs!

[inblue]

Rob, thank you for the amazing coding work, and even more importantly, for perseverance.

[zthomasz]

somebody just buy about 10 000 000 bbp for 80000$ , isnt this required amount for instant send security bug?

@capulo ... be helpful and post some evidence for this supposed 10-Million BBP / $80,000 transaction.

it was on c-cex, somebody spent few bitcoins to buy many times 700k bbp

Thanks @capulo, I appreciate your reply. I didn't realize c-cex was open for trading BBP.