Bible Pay

Recent Posts

Pages: 1 2 3 4 5 6 [7] 8 9 10
61
I see the two 500K proposals won in the last superblock (getgovernanceinfo:last superblock height).  I see the 1Mil (dog mascot) didnt get paid, so it appears this one worked also.

62
I guess the next step is to see if one can create a DIP3 masternode on the mainnet but I am unable to help with that as I do not have the required collateral...

Yes, the collateral is going up to 4,500,001, so its quite a risky thing to tie up 3* the amount currently LOL.
Well this is actually a very critical issue and relies on something that isn't readily apparent in the code that sort of drives our decision to do this a certain way.
The new Dash non-financial transactions require the pro-reg-tx payload to be stored in a certain way that starts storing data in the prod chain in an extended place, that I really don't want to be intermingled with biblepay-classic nodes.  Another words, we must ensure the dip15 cutover is on a height well after our mandatory upgrade height to evo - we will have to phase Evo in at a certain height, and run legacy sancs first:
For example:
Height 135,000 - Cutover to Evolution - convert sancs from 1.55m to 4.5MM
Height 145,000 - Upgrade to Deterministic sancs (between 135K-145K)
Height 145,001 - Mandatory upgrade to deterministic non-financial txes (dip15 is enabled)
Its a shame that we have to do this in two steps, but its really the only way I can see doing this - if we go directly to deterministic sancs, we would break the biblepay classic nodes (as the extra non-financial data would not be parseable).

But yes, we will talk more about this soon, and I will act as a sacrificial lamb with one of my sancs and create it in Prod through evo as a 4.5MM and ensure it starts. 
I think we will need to organize this endeavor in a way where we ask our Prod sancs to upgrade 7 days before the mandatory cutover height (IE before the exchanges even upgrade), because moving to evo requires all sancs to re-organize into a 4.5MM farm.
(If we asked them to upgrade after the height prod would have no sancs at the cutover height).  We also have to take into consideration the monthly budget height.
It would be good to frame this upgrade right after either May 30ths block, or June 30th's block.
At that point Sancs in prod would download Evo, upgrade to 4.5 MM in classic mode, then around the 7th, the mandatory height passes, the exchanges upgrade and then we have a certain buffer (say 25 more days) to upgrade to deterministic.




63
I guess the next step is to see if one can create a DIP3 masternode on the mainnet but I am unable to help with that as I do not have the required collateral...
64
~/biblepay-evolution/src/qt/biblepay-qt loads ok but perhaps to be expected crashed when you try to view leaderboard and proposals.
65
Interesting, I managed to send funds (BBP not tBBP) from my wallet on the mainnet to the wallet running EVO!

~/biblepay-evolution/src/biblepay-cli getinfo
{
  "version": 1040207,
  "protocolversion": 70732,
  "walletversion": 61000,
  "balance": 100.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 117804,
  "timeoffset": 0,
  "connections": 11,
  "proxy": "",
  "difficulty": 9338.691900918453,
  "testnet": false,
  "keypoololdest": 1557217142,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}

~/biblepay-evolution/src/biblepay-cli listtransactions
  {
    "account": "",
    "address": "BC2RsquwDER8sCKcMmDCy9rgKSusWLZpGn",
    "category": "receive",
    "amount": 100.00000000,
    "label": "",
    "vout": 1,
    "confirmations": 2,
    "instantlock": false,
    "blockhash": "49d1f7e4d26f8547da3ae9c25a40232080706293a95859f2e0c0770aa05d5270",
    "blockindex": 1,
    "blocktime": 1557225899,
    "txid": "29f1b61e84d4f6eae1ef9eb49b8ef3f9f49366576b3eeb57282e2e7367f9c917",
    "walletconflicts": [
    ],
    "time": 1557225892,
    "timereceived": 1557225892
  }

66
Oh btw, I did test Evo against prod last month, and also tested Pool mining (in prod mode).

If anyone feels up for it, please sync in prod, and verify you can sync to the top in prod.
Then configure the miner to be pointed at a pool, and ensure pool mining is working.
Note:  It would be very helpful if someone could test Purepool.  I only tested mining in evo in prod against pool.biblepay.org (successfully).

$ ~/biblepay-evolution/src/biblepay-cli getblockcount
117799

$ ~/biblepay-evolution/src/biblepay-cli getblockhash 117799
1a038e93b4046038444f7a98abd546aa2a7a8580ade7771224a73685b79314b5

I don't know what exactly is required but here is the output of getmininginfo of EVO on the main chain pointed to purepool.

{
  "blocks": 117798,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 10211.68938254838,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 14937188254.95241,
  "hashps": 28.84073865488929,
  "minerstarttime": "05-07-2019 10:24:22",
  "hashcounter": 4865,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "gsc_errors": "",
  "poolmining": true,
  "pool_url": "https://pool.purepool.org",
  "required_abn_weight": 0
}


The progress can be followed here http://www.purepool.org/main/miner/BD9gmJ5vmPJtDewo9NyqUT7fJQgV39AW7R
67
Oh btw, I did test Evo against prod last month, and also tested Pool mining (in prod mode).

If anyone feels up for it, please sync in prod, and verify you can sync to the top in prod.
Then configure the miner to be pointed at a pool, and ensure pool mining is working.
Note:  It would be very helpful if someone could test Purepool.  I only tested mining in evo in prod against pool.biblepay.org (successfully).

68
Next we need to ensure the payment amounts are correct for : POBH, monthly superblocks, daily superblocks and the qt effect on it.


After this it appears the entire wishlist has been fulfilled.  Let me know if anyone has any questions or concerns for this next version of BiblePay.

I believe we have tested almost all of the pieces successfully!


On a side note, I hope people have noticed the chained bible verses are now consecutive and the txlist double click shows these also.

69
Church Tithing/Mobile-wallet staking:
MIP is working on it.  If we don't get it finished by the end of June we will push it back to September.  On a side note, BBP has a PO Box (actually we have a physical address po box) now, and MIP is working on a relationship with Apple so he can also release BiblePay for iPhone.

ChainLocks:
This is most likely the only feature in this guide that won't make it in time for an end of June release.  This is only because Dash is still testing it and MIP and I would like to see it promoted to Dash-Prod before we release it in BiblePay. 



70
I'm starting to review this page:
https://wiki.biblepay.org/Nutrition_Information
To see what we forgot to test, and I wanted to mention something about soft forks and stable-prod features in Evo:

We did test the stable-prod feature a couple of releases back successfully.

At the time, we were not rewarding for diary entries and QT was around 30% and climbing.

I added two business logic changes to the server side and we had a leisure, and did not specifically mention it, but what happened was the current GSCs with existing votes were downvoted automatically and the new GSC (because of the 2% contract change in that GSC superblock) was upvoted, meaning this feature was tested successfully (we had a leisure upgrade for sancs, no hard consensus change release) and we succeeded in emitting a GSC.  So this is really great and very useful in the future as I can see a lot of possible releases in mid quarter updates with useful things between exchange mandatory upgrades.



Pages: 1 2 3 4 5 6 [7] 8 9 10