Any explorer is normal running now? I saw official explorer latest info shown on 03 Mar and no more information after this day.
I got the info blocks is "107393" currently, is that in correct chain?
It looks like explorer.biblepay.org is still syncing. No unfortunately I believe Slovakia shut his down. TheSnat was building a backup explorer, Im not sure if its done and ready for beta yet, Snat? Not quite yet, it's been having trouble with all the forks, I will see where it's at. edit: client crashed again, need to re-sync .. |
|
|
|
So now someone knows what is the correct number block currently?  It looks like this chain is the most: "height": 107158, "hash": "5b75ec85f8288341a3f3837d20a7e824b8c9e22ac1fc049432020acf4bbc3312", But let me see if my sancs have all gone to agreement yet. All my clients are on this chain now . Throwing some extra miners on it as well. |
|
|
|
Ok it makes a little more sense now, I believe I see the lions share of the problem (IE bigger than reorganizing).
Ive got two nodes that dont agree here, both consider one of the forks valid but node 2 is following a shorter chain.
Looking at the log on node2, it feels the list of sanctuaries is different than node1. Another words, it has a view of sanctuary payments that differs from other parts of our network.
So basically the sanctuary payment is enforced with a hard rule - and this can cause a fork. We need to either A) Sync all the sancs, or B) Temporarily not enforce that sancs get paid properly.
Ill work on B at a network level now.
Sancs: Please try to sync to the top so your data can synchronize.
We will need to know what the "top" is.. I have 3 different chains i'm seeing |
|
|
|
We have next fork now, its the end.
Same here, Different machines show different fork blocks after update to 1.1.9.9g version. After such a long time, it still failed to return on the right block, which is worrying.  I gave some power on correct chain(about 40% all), we must waiting .... wchich one is correct, i have wallets on blocks 107049, 107076 and 107021 107076 in most cases few wallets unable to connect peers good question ... hard to say which is the "real" chain at this point |
|
|
|
What happen with my BPP?
At 12.03 i have more than 40k bpp. Today i start 1.1.9.9g wallet and i have only 4 763 bpp.
I tried to restore the wallet from 2019-03-12-13, but the balance is the same
There's a good chance you were on the fork while earning those coins .. You can try to use the rescan option in "wallet repair" section of the menu |
|
|
|
We had a feature in called HealthCheckup that would only reboot in the circumstance (where the block spacing > one hour, has not been checked for an hour, and the side chain has more work than the main chain, and the main chain diff is low);
This feature normally will only Reboot Once, but what happened in 1199, since the users on a version < 1199 are still adhering to pog rules, that chain still continues to remain longer (IE with more work), so hence the continual re-assessment and re-boot nuisance.
(Another words, the feature would have worked in normal circumstances, if rebooting caused the client to jump on the longer chain after resyncing but it cant because the longer is invalid now).
So in light of this Im making a new leisure now; the old version is still fine for others once the main chain gets longer.
Compiling...
Are there any "known good" seed nodes currently? |
|
|
|
I made the assumption that our LIMITED_STRING was enough to prevent any effects of memory corruption, and for that I apologize to everyone.
In the future we wont base any production code on any untrusted user entered field ever again.
In my mind, the most effect the nickname could have had in the map was : Swear word (and we added code to remove those) and length, sorry guys.
In Evolution we will check every outside entry point in the smart contract processor.
I appreciate the candor, and yes not trusting any user input is a great default state.. (intentionally or not User's are most often the cause of systems going awry) I'll admit I didn't consider special characters having an impact either.. |
|
|
|
"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.
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. |
|
|
|
Who is <NICKNAME>PoG @('_')@ Monkey</NICKNAME>?
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? |
|
|
|
BBP & GRC are the only coins listed on C-CEX. I'll thank him for being so loyal to us.
I see the BBP price is recovering on c-cex (since we are the only coin to buy - possibly).
Could people trying to exit C-CEX exchange? |
|
|
|
Sun can you please help us with something, can you please tell me tomorrow if everyone is on the main chain and if we should re-open southexchange?
Just try to get a feel that all sancs and the main network are synced.
How would I know if everyone is on the main chain? Maybe informal poll on discord? |
|
|
|
"Users are not allowed to have multiple accounts in SouthXchange. Those ignoring this warning risk having their accounts and funds seized."
Interesting, i'm surprised its that big a deal? Possibly folks buying/selling to boost coin volume? |
|
|
|
DOGE is being delisted on c-cex; you may want to sell it or withdraw it.
Wow that's surprising... I think they will delist everything as there is no volume. Well.. just looked over there and 10k volume for the day 10% of that was on DOGE, so curious why de-listing now. Do you think the "vacation" last summer took its toll on the exchange? |
|
|
|
Yes I will announce it here if I remember. Problem is that I deposit and withdraw during forks. I have created ticket with transactions ids. Unfortunately some of them are not on correct chain  Any not on the correct chain should be back in your wallet on the proper chain, since the tx never "occurred" |
|
|
|
DOGE is being delisted on c-cex; you may want to sell it or withdraw it.
Wow that's surprising... |
|
|
|
Bad News, CryptoBridge wants 0.25 BTC to update to latest mandatory version 1.1.8.9
Unfortunate, but I do understand the reasoning... (still is cheaper than the .5? they were asking before..) Hopefully things are stabilizing, looking forward to the next phase of bbp. |
|
|
|
More than likely the person that had inside information that deposits were re-enabled  I don't think it qualifies as insider information if its posted publicly? Let's play nice and not assume ill intent. |
|
|
|
250 confirmations?? that's like 30 hours lol Yeah crazy.. Tested sending some coin over, so far they are not seeing the TX... troubling It finally registered, I guess it doesn't show till it clears.. |
|
|
|
|
Show Posts
