Who is <NICKNAME>PoG @('_')@ Monkey</NICKNAME>?
You don't sanitize the nicknames? Maybe make the parser smarter and filter out anything non-alphanumeric between <nickname> and </nickname>? Who is <NICKNAME>PoG @('_')@ Monkey</NICKNAME>?
Same address has used also StopCrashingBiblePay nick. I remember seeing this at least yesterday. I've had the nicknames: ((̲̅ ̲̅(̲̅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. |
|
|
|
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. |
|
|
|
|
Who is <NICKNAME>PoG @('_')@ Monkey</NICKNAME>?
|
|
|
|
|
** BIBLEPAY UPDATE **
I'm looking into the problem now...
|
|
|
|
Thanks a lot Togo! This is what we need, perseverance! Brothers of Perseverance! Maybe ours should say "SlovakiPay" LOL, JK. Ill definitely check this out and comment. It looks good Togo, its compatible with GIN and GroestlCoin, so it means we have a shot. Ill send you an e-mail. |
|
|
|
Thanks a lot Togo! This is what we need, perseverance! Brothers of Perseverance! Maybe ours should say "SlovakiPay" LOL, JK. Ill definitely check this out and comment. |
|
|
|
Command": "podcupdate",
"PODCUpdate": "Invalid Destination Address"
}
exec associate rosetta_email rosetta_password true "Results": "Error: The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here." Please try it again from the latest version; this was fixed in 1198. |
|
|
|
Command": "podcupdate",
"PODCUpdate": "Invalid Destination Address"
}
exec associate rosetta_email rosetta_password true "Results": "Error: The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here." Does your biblepay.conf have tithe=1 and nickname=supporter setup? If you are doing PoG, some people have been able to do PoDC update by using utxooverride=your-stake-amount , then move that BBP amount to your rosetta address (or non-tithe address) then do an exec associate again . There's some weirdness sometimes when you try to use PoDC and PoG together. You're not the first to report this. |
|
|
|
|
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).
|
|
|
|
Rob, when will you notify Southexchange to allow BBP ?
I did a little test yesterday and confirmed we were in sync. I sent them a message last night, and c-cex also. Hopefully we will reopen within 24 hours. CoinExchange should still be open btw. |
|
|
|
|
Thank you all for supporting BiblePay, and God Bless EVERYONE!
|
|
|
|
What are you going to do about the crashing masternodes? I sent you Valgrind logs as you requested but no response. Investors are losing MN payments as this node crashes daily.
Could you provide a link to where you sent me valgrind logs and there was no reply? Additionally I have a lot of sancs on 2 providers and Im not seeing crashes. I'm an investor too, and I don't see instability. I worked with MIP (who is an investor also) and we spoke about the crash that happened the day after the fork and he agreed to run his in valgrind also, and neither of us have yet to have a valgrind crash log. I don't see any valid valgrind from you - please give a link. Btw I never received a reply that I sent you via e-mail. I liked your POG logo much more, that was cool. I asked for your help on github. People who are trying to help are not developers. One need to provide them step by step instructions. Ok, I will reply now. |
|
|
|
What are you going to do about the crashing masternodes? I sent you Valgrind logs as you requested but no response. Investors are losing MN payments as this node crashes daily.
Could you provide a link to where you sent me valgrind logs and there was no reply? Additionally I have a lot of sancs on 2 providers and Im not seeing crashes. I'm an investor too, and I don't see instability. I worked with MIP (who is an investor also) and we spoke about the crash that happened the day after the fork and he agreed to run his in valgrind also, and neither of us have yet to have a valgrind crash log. I don't see any valid valgrind from you - please give a link. Btw I never received a reply that I sent you via e-mail. I liked your POG logo much more, that was cool. |
|
|
|
Rough BiblePay Evolution Timeline
Is this going on the Road Map update? I've heard good things about DASH 0.13.1 (InstantSend default, ChainLocks, separating masternode earnings vs voting, etc) thanks for making this a priority. its a good base to work off of. sounds like a lot of work. i hope you will provide ample time to test. I think it is more important to have a stable working product and have it be late, than untested software making it into production. I think many of us agree, we don't need a repeat of PoG where it seemed like there were mandatory updates every week. Yes, of course it will be on the RoadMap - its a Roadmap change. I'll update the roadmap when we create the wiki about the GSC. Yes, from what I can see Evolution is going to bring many nice features. Yes, respectfully about your "complaints", that is exactly why we are making changes to policies and procedures, so we can have a stable production environment without frequent upgrades. Regarding testing in testnet, it will remain in testnet until everything is tested. You can help us make a complete product this time by ensuring that everyone tests everything on our test list - and add to the list things that we dont think of when its initially posted (send me add-ons and Ill edit the OP of the testnet thread). (On the bright side I'm more confident of the next testnet version than ever, as we not only learned a lot from POG, but breaking rewards into a smart contract should really allow us to debug the entire solution properly and ensure its correct. We can avoid the challenge(s) that POG created in this new model). |
|
|
|
|
Rough BiblePay Evolution Timeline
March 30, 2019 : Release BiblePay-Evolution to Testnet - this allows us to test non-deterministic sanctuaries, send BBP, receive BBP, test proposals and payouts in TestNet (and we will ask people to test this against Prod to ensure Evo runs side-by-side our old nodes)
During this phase, Rob will work on a wiki page outlining the new Generic Smart Contract. This will contain the details of the GSC reward system, campaigns, votable rules and reward points.
Rob will also work on v1.0 of the Generic Smart Contract while our users are testing Evo without POG.
April 7th, 2019: Devs will release the GSC to testnet and ask that we test both sancs and core clients. Test deterministic sanctuaries.
... Fix bugs and re-release Evo patches ...
April 30th, 2019: Go live with Evolution - network wide
We will try our hardest to make this deadline. I will notify everyone as soon as TestNet is ready. We will not have time to release the Wiki until we start testing Evo, as we are working full time on this project.
NOTE: If the PODC retirement vote passes, PODC will be retired at block 107,000 and POG will pay approx 10* more at that time.
Question: What is the Generic Smart Contract for?
Answer: The GSC will allow BiblePay to issue one generic superblock per day, containing the daily mining reward amount (equiv. to PODC currently) as a smart contract.
We will move our "campaigns", and "reward points" to a new design system inside Sanctuaries, and Sancs will assess the point levels per BBP-user and assign points to the campaign(s).
In this way we can vote on GSC changes in the future (without affecting our consensus rules).
We can also create nice new campaigns, such as our Christian Economy features later, (for small % of the daily rewards) etc.
The users/miners who meet the conditions of the GSC are rewarded BBP in exchange for Points rewarded in the campaigns.
This system will replace the current POG reward system, so that we may be more extensible in the future.
It will also allow us to honor Dash's codebase/security model more closely as they have releases, and our devs will merge these changes in, making us a more stable/reliable community.
At this point, we will be known as a true Dash follower, but with our own segregated features that do not break compatibility.
The GSC will also open up more exciting possibilities - such as allowing us to create Orphan contracts for people who want to help us decentralize Compassion (later in the roadmap).
I'll explain all this in detail in the first wiki version.
|
|
|
|
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? I think I can handle this tomorrow by doing a sanctuary pulse test- I can see if we have a common hash over 90 nodes tomorrow and if we do Ill ask them to re-enable if their internal hash matches. But I do ask for help- please keep an eye on the network for any forks while we are in our POG phase, and also, any signs of forks on any open exchange. CoinExchange confirmed they are not on a fork. SX resynced the wallet and I asked them to temporarily disable it. CCEX is disabled also (by us). What I'm aiming for is for this current network to stay synced until we release Evolution (within 60 days). |
|
|
|
exec istithelegal 0cce7c1c9c58d121c7240b583e0ecfc6a3d739b9a4475018cda3e6440a079762

{
"Command": "istithelegal",
"Tithe_Legal": -4,
"Tithe_Legal_Result": "TITHE_DOES_NOT_MEET_COIN_AGE_REQUIREMENTS",
...
} I don't like how tithing works when there is congestion (more than 75 tithes). This is encouraged by the 50 block look back on PoG difficulty. If tithes do not make in to the next confirming block, PoG difficulty will changes and your tithe no longer meets the requirement. 25% of my tithes in the last 205 blocks are "illegal". This affects every tither. Someone that just puts in 1 tithe in will be negatively affected as those that submit 10 or 75 tithes. If your tithe met the requirement at the time you submitted it into the mempool, it should be "legal". It was legal when you tithed so don't change the rules afterwards. Fortunately, I believe all of the issues on the last 40 pages are being handled right now by our devs. Biblepay Evolution does address windows 10, tithe overflows, POG bugs, fork prevention, POBH difficulty, and pretty much everything negative ever discussed here. The great news is its not far away from being ready for testnet. Ill announce a rough timeline soon. |
|
|
|
what do mean "dead"? Not working? Needs to be updated? Please explain. was offline for a short while that I know of, could not get on for a hour or so. Probably one of our anti-bbp members d-dossing it. Maybe its the guy who sells 666 every 15 minutes. |
|
|
|
bbp central showing that we have 487 MN and reward is 604bbp
isnt this too low?
block should be 1m so about 2k bbp
no?
Its more like 4300 bbp per block. On a side note, when sanctuaries crash, the pool miners get to keep the extra reward on a block that is not awarded to a restarted sanctuary. Ive seen a few high rewards on pool.biblepay.org over the last week due to this - of course its split with the participants as usual. |
|
|
|
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. Thanks. |
|
|
|
|
Show Posts
