Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 199. (Read 243417 times)

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.

Hopefully before voting of PODC is over

Rob, when will you notify Southexchange to allow BBP ?

Thank you all for supporting BiblePay, and God Bless EVERYONE!

https://github.com/biblepay/biblepay/issues/89 - thanks for your reply there.

Ok, I will reply now. 

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.

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. 

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.

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).

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.

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.

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). 

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.

Probably one of our anti-bbp members d-dossing it.
Maybe its the guy who sells 666 every 15 minutes.

After I quit BBP wallet, I renamed the wallet.dat to something else, then copied a backup wallet.dat just before the unconfirmed date/time. I did a rescan after that to bring the missing tx from that point. I think I got all my txes back w/o the unconfirmed orphans. Thank God DASH built all these Tools Repair options because trying explain command line to everyone when there's a fork or other issue would be a support nightmare.

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.

zapwallets does this. This is not good.


13 yes on Discord they are on 1198 and on correct chain. 0 no.


thanks for reporting it. i set up uptime robot on it to automate the checking. service is free. I set it for 20 minutes. hopefully, its not a web host or ISP daily backup type of thing... we will see.

www.biblepay.org was offline for a short while that I know of, could not get on for a hour or so.