Bible Pay

Read 7598 times

  • sunk818
  • Sr. Member

    • 319


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #195 on: November 18, 2019, 08:42:22 PM »
I don't know how I ended up on a fork? But have half a dozen peers.


  • MIP
  • Developer

    • 237


    • 27
    • February 13, 2018, 11:55:52 AM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #196 on: November 19, 2019, 03:01:35 AM »
Does anyone have an IP to use in addnode for this testnet? seems the one I had from past test is no longer valid.
Thanks.


  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #197 on: November 19, 2019, 08:58:10 AM »
Some Dynamic Whale Stake took but not all.



Ok, so you mean 'I tried to send out multiple whale stakes from the rpc in succession, and they returned from the console successfully, but were not picked up by any of the other nodes - and - the status of the transaciton when I double click is Offline'.  Ok, this usually happens when the coins are locked by the prior transaction and the wallet prevents the next successive transaction against double spending those.  To find out if this is the exact cause copy the transactionID to the clipboard (after double clicking the transaction on the gui row).

Then do a 'cat debug.log | grep txid'.  It should say something like attempt to spend locked (or already spent) coins.  This is primarily a new feature in the .14 branch because Dash tries to autolock coins now for free instantsends. 

You can then recover by restarting with -zapwallettxes=1 and they will dissapear.

This is not really related to sending DWS's.

I maintain that we bubble the DWS error to the console now.

On DWS, we should wait until we see "In memory pool - broadcast through N nodes" before sending another one.



  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #198 on: November 19, 2019, 09:01:26 AM »
I don't know how I ended up on a fork? But have half a dozen peers.

Check your log to see if you rejected the last superblock?  You can do this by getting the height of it (exec health, go to last block height) and analyze very close to that height and see if block rejects started to happen at that point.  If not find the exact height your rejects started.  That usually is one of the superblock heights.  If it is it means the node version you were running was probably running the old rules.  (Or, the node had gobject propagation issues).  You can also type 'gobject count' and make sure your gobject count is roughly what the other nodes are; and exec health should have the same number of votes as the other nodes.

Looking at the infrastructure now I dont see a fork.  All the sancs made it and my node is still in sync.

One nice thing about LLMQs is when a fork occurs, they start pose-banning each other very quickly (cause they cant hold the quorum), so technically the deterministic sancs should be a benefit to us in the next version.


« Last Edit: November 19, 2019, 09:05:41 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #199 on: November 19, 2019, 10:27:44 AM »
Does anyone have an IP to use in addnode for this testnet? seems the one I had from past test is no longer valid.
Thanks.

We had our primary DNS server->node for testnet running on the wrong port.

Fixed.  Now we have two running on the right port.



  • sunk818
  • Sr. Member

    • 319


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #200 on: November 19, 2019, 11:02:07 AM »
one of my test wallet was stuck on block before superblock. other one was fine.


  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #201 on: November 19, 2019, 02:31:35 PM »
I voted for the Kanye West proposal:

gobject list all proposals

Let me know if you receive the funds.



  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #202 on: November 19, 2019, 07:15:39 PM »
** SPORK_19 : CHAINLOCKS HAS BEEN ENABLED FOR BIBLEPAY TESTNET ! **


- Now that we have 7 running sancs in testnet (we need a minimum of 3), theoretically we will keep the chainlocks LLMQ quorum.
- Chainlocks theoretically makes it almost impossible to perform a 51% attack on BBP.  This is because the chain will no longer be allowed to "roll-back" for reorgs.  Because, each sanctuary will be assessing the chain block by block.
- Additionally, biblepay should have higher security.  This is because not only do we have POW security, but sanctuary security.  An example here would be someone trying to alter the business logic in a fraudulent client.  The sanctuary quorum will already have each official block memorized that has been seen.
- Therefore, we now benefit by not only proof-of-work (strongest decentralized hashes provide security) but we also benefit from a form of proof-of-stake (because you must have capital to control N # of sancs).  This gives us a much higher total level of decentralized security than POW or POS alone.
- Because of this, BiblePay's GSCs just became stronger.  In addition, we can do "cool" things now, such as save energy, or provide subsidies for future items such as letter writing that simply were almost impossible or dangerous without chainlocks.
- Exchange Security:  Theoretically, with instant send autolocks and chainlocks, our exchange security just rose by a magnitude.  We will technically not need to have more than 7 block confirmations, since rollback risk is almost eliminated with chainlocks.
- What happens instead of reorgs now:  One strange side effect of chainlocks is the POSE ban sanc effect.  Theoretically what will happen in place of a fork is :  Sanctuaries will POSE ban each other and many small chains will exist.  This should not happen in prod, because of the massive number of sanctuaries (any number > 10 or so will keep the main chain rolling forward).  However in testnet, if we take down 75% of the sancs, we should see the chain split into multiple small and useless forks (meaning that they will be harmless).  This is in contrast to two big forks in pure POW mode.  Why is this?  This is because the chainlocks rules dictate that when a quorum cannot be maintained, the network will keep trying.  This prevents reorgs, and keeps everyone on a harmless "segment".





  • sunk818
  • Sr. Member

    • 319


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #203 on: November 19, 2019, 08:44:54 PM »

2019-11-20 02:28:28 UpdateTip: new best=609dd6f5a03962ad5313f4f7a9a1ffc945a0ae8d4e4578f3ae972ccab3e3cebd height=17211 version=0x20000001 log2_work=45.77639859 tx=26702 date='2019-11-20 02:28:18' progress=0.249753 cache=0.1MiB(448txo)
2019-11-20 02:28:28 {PNB}: ACC  {PNB}: ACC  ERROR: AcceptBlockHeader: prev block f449b1b97feddb3869fc604682355eefb80d35186d853bf678ff49daee7feecb conflicts with chainlock



  • sunk818
  • Sr. Member

    • 319


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #204 on: November 20, 2019, 07:50:55 AM »
2019-11-20 02:28:28 UpdateTip: new best=609dd6f5a03962ad5313f4f7a9a1ffc945a0ae8d4e4578f3ae972ccab3e3cebd height=17211 version=0x20000001 log2_work=45.77639859 tx=26702 date='2019-11-20 02:28:18' progress=0.249753 cache=0.1MiB(448txo)
2019-11-20 02:28:28 {PNB}: ACC  {PNB}: ACC  ERROR: AcceptBlockHeader: prev block f449b1b97feddb3869fc604682355eefb80d35186d853bf678ff49daee7feecb conflicts with chainlock


Seems to be okay now, I quit the testnet wallet and tried again and both are on 17308:
"hash": "0975df866939ada03b79d06fc5a087178b3f89931105ec5aaa02cd57345b8a78",


  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #205 on: November 20, 2019, 01:25:33 PM »

Seems to be okay now, I quit the testnet wallet and tried again and both are on 17308:
"hash": "0975df866939ada03b79d06fc5a087178b3f89931105ec5aaa02cd57345b8a78",

I grepped my dev log and don't see any chainlock errors, and it looks like our quorum is holding up from the sanc perspective so far.  No sancs are POSE banning each other.



  • togoshigekata
  • Sr. Member

    • 482


    • 25
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #206 on: November 20, 2019, 03:01:17 PM »
I voted for the Kanye West proposal:

gobject list all proposals

Let me know if you receive the funds.

I do not believe I got the funds for this proposal, looks like superblock passed recently,
I believe the proposal had 4-5 yes votes and 0 no votes,
I do still see the proposal in the proposals tab, hmmm



  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #207 on: November 20, 2019, 03:06:50 PM »
BiblePay - TestNet
1.4.7.7 - Mandatory Upgrade for TestNet

- Add mandatory (prod) cutover height 166,000 for PODC 2.0
- Increase deflation to 20.04% after PODC2.0 cutover height, and, enable DWS.  Ensure we have a spending cap in prod for each DWS day.  Add anti-fork DWS rules.  Ensure burn payments never exceed the cap (decrease them if this happens).
- Fix instantsend lock behavior
- Fix privatesend mixing denominations and mixing behavior
- Remove QT
- (MIP): Merge in all Dash prod changes from July up to the current date

** Windows is ready, the rest are compiling **

Please note:  All sancs and the entire network must upgrade as this includes all the Dash changes up to the current date and a consensus change.



  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #208 on: November 20, 2019, 03:09:48 PM »
I do not believe I got the funds for this proposal, looks like superblock passed recently,
I believe the proposal had 4-5 yes votes and 0 no votes,
I do still see the proposal in the proposals tab, hmmm

I took a look at it this morning when the monthly budget was about to pass, and I believe what happened is the proposal was entered a couple blocks after the late-duration cut off - this is the cut off where its too late to create a trigger for payment.
So I copied the proposal into a new one, and now we know its at the beginning of the cycle again; lets see if this one pays.

Part of the challenge in testnet is the cycle is 4* per month instead of 1, so Im confident if it picks it up this time it was just the late-duration cut off issue.
(Especially since we had 7 sancs running at that time).

Lets defintely follow this through though.  I did test a few proposals in this branch a while back (back when we had 3 sancs) and they all paid, so I don't "believe" we have a payment issue with watchman but nevertheless lets watch it.



  • Rob Andrews
  • Administrator

    • 2262


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #209 on: November 20, 2019, 07:01:06 PM »
I do not believe I got the funds for this proposal, looks like superblock passed recently,
I believe the proposal had 4-5 yes votes and 0 no votes,
I do still see the proposal in the proposals tab, hmmm

Togo, will you please test the Private Send mixing in testnet to ensure denominations are now correct, and mixing is faster and correct?