Amen.
Amen to your remark too, Tom, thanks for your support.You guys are the highest caliber people I ever met; people who stab others in the back when they are drowning.
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 197. (Read 243436 times)
March 13, 2019, 02:15:09 PM
You guys are the highest caliber people I ever met; people who stab others in the back when they are drowning.
March 13, 2019, 01:39:15 PM
Who is PoG @('_')@ Monkey ?
Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.
Thanks.
So far we have found a corrupted scriptPubKey on the PoG Monkey record.
All exchanges are disabled.
From what I can see preliminarily, the bad POG record is causing the core client to go into a condition where it ends up corrupting the reply messages to other nodes exacerbating the problem for people who are trying to resync.
Let me continue to do more testing. Most likely we will need a mandatory upgrade release with a safer/more stable environment while we wait for Evolution. We may have to disable POG and move to POBH temporarily, we're checking.
Waiting to see the outcome of this.. If you have to drop POG temporarily, how does this affect the PODC vote?
The PODC retirement vote is winning by 100, so we only have 80 more blocks before it would be retired anyway.
Nothing changes... as far as that goes. The governance module should come back up and we will see if any changes are occuring to that vote over the next 10 days (IE governance does not go away).
The only thing that changes is blocks pay 50-50 to POW - Sanctuary (IE 5000 to POW/5000 to Sanc after governance escrow %) for a while, until Evolution.
Sorry, but this is ridiculous. May I remind you that the proposal was not just simply "retire PODC?" but actually "retire PODC in favour of POG?"! So by all that is right, if you now make the (rushed) decision to simply bury POG for good, then this whole proposal/vote has no more legitimacy whatsoever!
So what you're saying now is, we not only give up on POG (which more and more seems to have been in beta stage at best), but also simultaneously bury the ONE system that has worked for more than a year now? And we're going back to our good old trusty botnet-mining?
I hate to say it, but I'm afraid as soon as any exchange is gonna open up our trading again (that is if there is still an exchange patiently enough ...) this coin will dump hard.
March 13, 2019, 12:59:13 PM
if all it took was a nickname to crash the code then the dev should be glad to know it
March 13, 2019, 12:44:03 PM
"StopCrashingBiblePay", that is such a Christian way to be Sun. It figures it was you as you are hiding behind being Christian but not acting like one.
Thanks for taking our chain down Sun; thats one thing Ive always disliked is hackers in prod.
Thanks for taking our chain down Sun; thats one thing Ive always disliked is hackers in prod.
I do think this should have been tested in testnet early on (special characters etc in the text fields). I am curious how this is different than tx message strings(Would this have a similar effect).
I cannot say it was malicious (with intent to crash the chain), I suspect it was only a matter of time before someone/something did this.
I do think we can add some tests to testnet next time around with this knowledge.
March 13, 2019, 12:36:23 PM
Who is PoG @('_')@ Monkey ?
You don't sanitize the nicknames? Maybe make the parser smarter and filter out anything non-alphanumeric between
Who is PoG @('_')@ Monkey ?
Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.
I've had the nicknames:
Code:
PoG @('_')@ MonkeyCode:
StopCrashingBiblePay
Code:
((̲̅ ̲̅(̲̅C̲̅r̲̅a̲̅y̲̅o̲̅l̲̲̅̅a̲̅( ̲̅((>
There's some cool 1 line ascii art here: https://1lineart.kulaone.com/#/
If you want, I can list all the nicknames I used.
Why, is that even relevant or important?
"StopCrashingBiblePay", that is such a Christian way to be Sun. It figures it was you as you are hiding behind being Christian but not acting like one.
Btw, stop trying to form hate groups on discord and move users over to your own private channels.
People's messages are not being deleted if they follow the guidelines here.
Your messages won't be deleted if they are respectful and helpful and contain the Full truth (not half truths as yours and Nokos have been).
Also, Please stop being disrespectful on our forum.
Thanks for taking our chain down Sun; thats one thing Ive always disliked is hackers in prod.
Rob you are being very disrespectful. I know for sure that Sun in not hacking network and he did not bring chain down on purpose. You really need to man up and admit that developers have pushed faulty code into production in a rush. This is what bring the chain down.
What comes to those nicks I see them very differently
Code:
PoG @('_')@ MonkeyCode:
StopCrashingBiblePay
One more thing. Rob do not judge people by rumors. Sun is NOT creating hate groups. We are discussing about the things that bother us and we have right to opinions even they are not aligned with yours.
March 13, 2019, 11:56:17 AM
Who is PoG @('_')@ Monkey ?
Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.
Thanks.
So far we have found a corrupted scriptPubKey on the PoG Monkey record.
All exchanges are disabled.
From what I can see preliminarily, the bad POG record is causing the core client to go into a condition where it ends up corrupting the reply messages to other nodes exacerbating the problem for people who are trying to resync.
Let me continue to do more testing. Most likely we will need a mandatory upgrade release with a safer/more stable environment while we wait for Evolution. We may have to disable POG and move to POBH temporarily, we're checking.
Waiting to see the outcome of this.. If you have to drop POG temporarily, how does this affect the PODC vote?
The PODC retirement vote is winning by 100, so we only have 80 more blocks before it would be retired anyway.
Nothing changes... as far as that goes. The governance module should come back up and we will see if any changes are occuring to that vote over the next 10 days (IE governance does not go away).
The only thing that changes is blocks pay 50-50 to POW - Sanctuary (IE 5000 to POW/5000 to Sanc after governance escrow %) for a while, until Evolution.
March 13, 2019, 11:52:59 AM
Who is PoG @('_')@ Monkey ?
You don't sanitize the nicknames? Maybe make the parser smarter and filter out anything non-alphanumeric between
Who is PoG @('_')@ Monkey ?
Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.
I've had the nicknames:
Code:
PoG @('_')@ MonkeyCode:
StopCrashingBiblePay
Code:
((̲̅ ̲̅(̲̅C̲̅r̲̅a̲̅y̲̅o̲̅l̲̲̅̅a̲̅( ̲̅((>
There's some cool 1 line ascii art here: https://1lineart.kulaone.com/#/
If you want, I can list all the nicknames I used.
Why, is that even relevant or important?
"StopCrashingBiblePay", that is such a Christian way to be Sun. It figures it was you as you are hiding behind being Christian but not acting like one.
Btw, stop trying to form hate groups on discord and move users over to your own private channels.
People's messages are not being deleted if they follow the guidelines here.
Your messages won't be deleted if they are respectful and helpful and contain the Full truth (not half truths as yours and Nokos have been).
Also, Please stop being disrespectful on our forum.
Thanks for taking our chain down Sun; thats one thing Ive always disliked is hackers in prod.
March 13, 2019, 11:23:36 AM
March 13, 2019, 09:30:33 AM
Who is PoG @('_')@ Monkey ?
Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.
Thanks.
So far we have found a corrupted scriptPubKey on the PoG Monkey record.
All exchanges are disabled.
From what I can see preliminarily, the bad POG record is causing the core client to go into a condition where it ends up corrupting the reply messages to other nodes exacerbating the problem for people who are trying to resync.
Let me continue to do more testing. Most likely we will need a mandatory upgrade release with a safer/more stable environment while we wait for Evolution. We may have to disable POG and move to POBH temporarily, we're checking.
Waiting to see the outcome of this.. If you have to drop POG temporarily, how does this affect the PODC vote?
March 13, 2019, 09:12:55 AM
Who is PoG @('_')@ Monkey ?
Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.
Thanks.
So far we have found a corrupted scriptPubKey on the PoG Monkey record.
All exchanges are disabled.
From what I can see preliminarily, the bad POG record is causing the core client to go into a condition where it ends up corrupting the reply messages to other nodes exacerbating the problem for people who are trying to resync.
Let me continue to do more testing. Most likely we will need a mandatory upgrade release with a safer/more stable environment while we wait for Evolution. We may have to disable POG and move to POBH temporarily, we're checking.
March 13, 2019, 08:59:32 AM
Adding to this (hi again everyone, been a while). Getting a lot of crashes here too. Let me know if there's something I can provide to help debug that you might not have already.
March 13, 2019, 07:56:31 AM
Who is PoG @('_')@ Monkey ?
Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.
March 13, 2019, 07:56:16 AM
My wallet was crashing a couple nights back only on one system. Multiple reinstalls and deleting contents failed. I had to pull a wallet backup from another system just to get the wallet to not crash. Then it wouldn't find peers. I had to copy my peers.dat file from the other system as well. After that, my client was working fine. Since Microsoft pushed out updates last night, both my wallets were down for applying the updates. No idea if they are happy today yet. Will find out after work.
March 13, 2019, 07:55:51 AM
fyi ... my Win 10 wallet 64bit v1098 is freezing up with message "biblepay-qt.exe is not responding".
March 13, 2019, 07:37:05 AM
Who is PoG @('_')@ Monkey ?
March 13, 2019, 07:11:51 AM
My wallet also shuts down as of this morning. Below is the error message it gives. Last night it was acting very slow and would stall. (Ubuntu 16.04)
https://i.imgur.com/hEI1I8q.png
https://i.imgur.com/hEI1I8q.png
March 13, 2019, 06:22:13 AM
** BIBLEPAY UPDATE **
I'm looking into the problem now...
I'm looking into the problem now...
March 13, 2019, 02:57:06 AM
same here, all wallets crashed or 100% cpu and not responding
unable to start wallet - crashed after while
unable to start wallet - crashed after while
March 13, 2019, 02:54:07 AM
In my case, my sancs are still running, but daemon process take 99% of the CPU and don't respond to RPC commands.
Edit: If I kill daemon process and restart, I get this in debug.log
Then it starts shutdown sequence.
Edit: If I kill daemon process and restart, I get this in debug.log
Code:
2019-03-13 08:03:45 init message: Loading block index...
2019-03-13 08:03:45 Opening LevelDB in /home/ubuntu/.biblepaycore/blocks/index
2019-03-13 08:03:45 Opened LevelDB successfully
2019-03-13 08:03:45 Using obfuscation key for /home/ubuntu/.biblepaycore/blocks/index: 0000000000000000
2019-03-13 08:03:45 Opening LevelDB in /home/ubuntu/.biblepaycore/chainstate
2019-03-13 08:03:45 Opened LevelDB successfully
2019-03-13 08:03:45 Using obfuscation key for /home/ubuntu/.biblepaycore/chainstate: 1eb34d7f65bff2b2
2019-03-13 08:03:45 LoadBlockIndexGuts 1552464225.000000 Last Checkpoint Height 63000 block 10000.000000 @ 1552464226.000000 1552464226059.000000 block 20000.000000 @ 1552464226.000000 1552464226801.000000 block 30000.000000 @ 1552464228.000000 1552464228100.000000 block 40000.000000 @ 1552464229.000000 1552464229914.000000 block 50000.000000 @ 1552464232.000000 1552464232195.000000 block 60000.000000 @ 1552464235.000000 1552464235061.000000 block 70000.000000 @ 1552464238.000000 1552464238651.000000 block 80000.000000 @ 1552464242.000000 1552464242992.000000 block 90000.000000 @ 1552464247.000000 1552464247160.000000 block 100000.000000 @ 1552464252.000000 1552464252359.000000 block 110000.000000 @ 1552464258.000000 1552464258150.000000 Finished 1552464258.000000 LoadBlockIndexDB: last block file = 6
2019-03-13 08:04:18 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=14128, size=104215345, heights=93253...106877, time=2019-01-04...2019-03-13)
2019-03-13 08:04:18 Checking all blk files are present...
2019-03-13 08:04:18 LoadBlockIndexDB: transaction index enabled
2019-03-13 08:04:18 LoadBlockIndexDB: address index disabled
2019-03-13 08:04:18 LoadBlockIndexDB: timestamp index disabled
2019-03-13 08:04:18 LoadBlockIndexDB: spent index disabled
2019-03-13 08:04:18 Finished Loading Block Index 1552464258.000000 LoadBlockIndexDB: hashBestChain=1765036da402f00ac8d6bdce3d1a1493284d5fec9c7a8f9ac63179459019bc2e height=106733 date=2019-03-12 12:08:54 progress=0.998181
2019-03-13 08:04:18 init message: Verifying blocks...
2019-03-13 08:04:18 Verifying last 288 blocks at level 3
2019-03-13 08:04:20 No coin database inconsistencies in last 289 blocks (4518 transactions)
2019-03-13 08:04:20 block index 34361ms
2019-03-13 08:04:20 init message: Loading wallet...
2019-03-13 08:04:20 nKeysLeftSinceAutoBackup: 1001
2019-03-13 08:04:20 nFileVersion = 1010905
2019-03-13 08:04:20 Keys: 1016 plaintext, 0 encrypted, 1016 w/ metadata, 1016 total
2019-03-13 08:04:20 wallet 63ms
2019-03-13 08:04:20 init message: Activating best chain...
2019-03-13 08:04:20 [CPID], [VERIFYCPIDSIGNATURE]: End To End CPID Verification Failed, Address does not match advertised public key for CPID 98ae76096c897e844bbfd0f2b4aa207c, Advertised Addr , Addr B82SF1Mhsh1VHtMn1J6p3STwgNYSmJmV5D (elapsed 1552464260.000000)UpdateTip: new best=5f506d71920f0769803df5d2da6ac5d37d43a6ed74a2b12a7ea4ef1c4e8c5ed0 height=106734 log2_work=59.187758 tx=905790 date=2019-03-12 12:13:05 progress=0.998187 cache=0.2MiB(232tx)
2019-03-13 08:04:21 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2019-03-13 08:04:21
ERROR: Found invalid chain with higher work (ChainState database corruption likely)
2019-03-13 08:03:45 Opening LevelDB in /home/ubuntu/.biblepaycore/blocks/index
2019-03-13 08:03:45 Opened LevelDB successfully
2019-03-13 08:03:45 Using obfuscation key for /home/ubuntu/.biblepaycore/blocks/index: 0000000000000000
2019-03-13 08:03:45 Opening LevelDB in /home/ubuntu/.biblepaycore/chainstate
2019-03-13 08:03:45 Opened LevelDB successfully
2019-03-13 08:03:45 Using obfuscation key for /home/ubuntu/.biblepaycore/chainstate: 1eb34d7f65bff2b2
2019-03-13 08:03:45 LoadBlockIndexGuts 1552464225.000000 Last Checkpoint Height 63000 block 10000.000000 @ 1552464226.000000 1552464226059.000000 block 20000.000000 @ 1552464226.000000 1552464226801.000000 block 30000.000000 @ 1552464228.000000 1552464228100.000000 block 40000.000000 @ 1552464229.000000 1552464229914.000000 block 50000.000000 @ 1552464232.000000 1552464232195.000000 block 60000.000000 @ 1552464235.000000 1552464235061.000000 block 70000.000000 @ 1552464238.000000 1552464238651.000000 block 80000.000000 @ 1552464242.000000 1552464242992.000000 block 90000.000000 @ 1552464247.000000 1552464247160.000000 block 100000.000000 @ 1552464252.000000 1552464252359.000000 block 110000.000000 @ 1552464258.000000 1552464258150.000000 Finished 1552464258.000000 LoadBlockIndexDB: last block file = 6
2019-03-13 08:04:18 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=14128, size=104215345, heights=93253...106877, time=2019-01-04...2019-03-13)
2019-03-13 08:04:18 Checking all blk files are present...
2019-03-13 08:04:18 LoadBlockIndexDB: transaction index enabled
2019-03-13 08:04:18 LoadBlockIndexDB: address index disabled
2019-03-13 08:04:18 LoadBlockIndexDB: timestamp index disabled
2019-03-13 08:04:18 LoadBlockIndexDB: spent index disabled
2019-03-13 08:04:18 Finished Loading Block Index 1552464258.000000 LoadBlockIndexDB: hashBestChain=1765036da402f00ac8d6bdce3d1a1493284d5fec9c7a8f9ac63179459019bc2e height=106733 date=2019-03-12 12:08:54 progress=0.998181
2019-03-13 08:04:18 init message: Verifying blocks...
2019-03-13 08:04:18 Verifying last 288 blocks at level 3
2019-03-13 08:04:20 No coin database inconsistencies in last 289 blocks (4518 transactions)
2019-03-13 08:04:20 block index 34361ms
2019-03-13 08:04:20 init message: Loading wallet...
2019-03-13 08:04:20 nKeysLeftSinceAutoBackup: 1001
2019-03-13 08:04:20 nFileVersion = 1010905
2019-03-13 08:04:20 Keys: 1016 plaintext, 0 encrypted, 1016 w/ metadata, 1016 total
2019-03-13 08:04:20 wallet 63ms
2019-03-13 08:04:20 init message: Activating best chain...
2019-03-13 08:04:20 [CPID], [VERIFYCPIDSIGNATURE]: End To End CPID Verification Failed, Address does not match advertised public key for CPID 98ae76096c897e844bbfd0f2b4aa207c, Advertised Addr , Addr B82SF1Mhsh1VHtMn1J6p3STwgNYSmJmV5D (elapsed 1552464260.000000)UpdateTip: new best=5f506d71920f0769803df5d2da6ac5d37d43a6ed74a2b12a7ea4ef1c4e8c5ed0 height=106734 log2_work=59.187758 tx=905790 date=2019-03-12 12:13:05 progress=0.998187 cache=0.2MiB(232tx)
2019-03-13 08:04:21 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2019-03-13 08:04:21
ERROR: Found invalid chain with higher work (ChainState database corruption likely)
Then it starts shutdown sequence.
March 13, 2019, 02:17:58 AM
Same to me
Jump to: