Bible Pay

Read 7591 times

  • sunk818
  • Sr. Member

    • 319


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #225 on: November 24, 2019, 10:45:55 AM »
did we need something in our biblepay.conf to send out wcg tx regularly?


  • capo
  • Newbie

    • 44


    • 2
    • March 11, 2018, 07:02:14 AM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #226 on: November 24, 2019, 01:44:16 PM »
sorry guys, i dont have time now, i'm redesigning house so whole day without pc ... :D
but i think i'm on some fork now... downloaded new version and did reindex, will see tomorrow...


  • 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 #227 on: November 24, 2019, 09:51:47 PM »
BiblePay - TestNet
1.4.8.1 - Mandatory Upgrade for TestNet


- Update private send denominations
- Ensure exec bankroll spends coins with depth > 0
- Release dash 0.14.0.4 :  https://blog.dash.org/product-update-november-22-2019-1dc02575ce58

** This is the windows release only. **


  • togoshigekata
  • Sr. Member

    • 482


    • 25
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #228 on: November 25, 2019, 12:21:24 PM »
I'm still having same issue with mixing, cant find random masternode

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1170

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1040

How does vecMasternodesUsed variable work?

Code: [Select]
int nCountEnabled = mnList.GetValidMNsCount();
int nCountNotExcluded = nCountEnabled - vecMasternodesUsed.size();

LogPrintf("CPrivateSendClientManager::%s -- %d enabled masternodes, %d masternodes to choose from\n", __func__, nCountEnabled, nCountNotExcluded);


  • orbis
  • Full Member

    • 203


    • 6
    • February 08, 2018, 04:37:14 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #229 on: November 25, 2019, 01:46:07 PM »
Hi all,
I was out for a moment, but it looks, that it's all working good for me.
What is needed to test? Some special scenarios? (but except MN)
It looks that taking tBBP to WCG only from CPK address is working for me good.
But I don't know if it's instantsend working good.
When I sent tBBP to myself, it everytime needs 6 block to confirm.
BTW. It'


  • orbis
  • Full Member

    • 203


    • 6
    • February 08, 2018, 04:37:14 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #230 on: November 25, 2019, 01:51:35 PM »
BTW: It's possible to put Smart-Contract reward on main screen recent tx?


  • 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 #231 on: November 25, 2019, 03:35:31 PM »
I'm still having same issue with mixing, cant find random masternode

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1170

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1040

How does vecMasternodesUsed variable work?

Code: [Select]
int nCountEnabled = mnList.GetValidMNsCount();
int nCountNotExcluded = nCountEnabled - vecMasternodesUsed.size();

LogPrintf("CPrivateSendClientManager::%s -- %d enabled masternodes, %d masternodes to choose from\n", __func__, nCountEnabled, nCountNotExcluded);

We first need to verify every sanctuary upgraded to the new version, then we can re-try private send mixing.

I recommend trying the mixing from a new wallet (so we dont intermingle the new external purse and PODC testing with this).



  • 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 #232 on: November 25, 2019, 04:19:06 PM »
Hi all,
I was out for a moment, but it looks, that it's all working good for me.
What is needed to test? Some special scenarios? (but except MN)
It looks that taking tBBP to WCG only from CPK address is working for me good.
But I don't know if it's instantsend working good.
When I sent tBBP to myself, it everytime needs 6 block to confirm.
BTW. It'

We need to verify the sancs have upgraded before we re-test IX.

These sancs who are running a lower protocol version will refuse to handle the IX request.

You can also help by verifying that we covered the other test cases in post #2.  I think you can safely skip by Kairos for now, as Kairos is about to go online in testnet with Andys side, so dont test that and also dont test Cameroon 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 #233 on: November 25, 2019, 04:21:12 PM »
Will we have InstantSend default or ChainLocks in the recent merges?

Yes, now InstantSend autolocks is on by default, and also, chainlocks is on permanently now (in testnet).

But all sancs need to be on the highest protoversion first, and I see one of my sancs failed to upgrade.

Lets re-test hashes once we all do that, lets post here if your sanc is running 1.4.8.1.


  • 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 #234 on: November 25, 2019, 04:21:54 PM »
did we need something in our biblepay.conf to send out wcg tx regularly?

No, nothing.  If you type 'exec rac' it should reveal the height in which the daily tx goes out (automatically).

PODC_Height:


  • 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 #235 on: November 25, 2019, 04:25:09 PM »
sorry guys, i dont have time now, i'm redesigning house so whole day without pc ... :D
but i think i'm on some fork now... downloaded new version and did reindex, will see tomorrow...

We seem to get a fork at the GSC height after every mandatory upgrade.

I have a hypothesis for this:  When I put it out it usually takes 12 hours for MIP to compile it, and then maybe about 24 hours longer for the sancs to upgrade.
During that span, if we miss the "common voting" on the GSC contract, this causes the POW miners to mine a POW block in place of the gsc.

Other miners probably mine their own view of a block with the GSC voted in - hard to say which side of the network wins.

Then we all resync and end up on the chain with the most work.
I am still thinking about this dirtyblockindex; not sure if its doing more harm than good for us.  It is the reason we need to resync when our node has one bad block in the chain.

Ill talk to MIP about this logic.



  • 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 #236 on: November 25, 2019, 04:54:55 PM »
We seem to get a fork at the GSC height after every mandatory upgrade.

I have a hypothesis for this:  When I put it out it usually takes 12 hours for MIP to compile it, and then maybe about 24 hours longer for the sancs to upgrade.
During that span, if we miss the "common voting" on the GSC contract, this causes the POW miners to mine a POW block in place of the gsc.

Other miners probably mine their own view of a block with the GSC voted in - hard to say which side of the network wins.

Then we all resync and end up on the chain with the most work.
I am still thinking about this dirtyblockindex; not sure if its doing more harm than good for us.  It is the reason we need to resync when our node has one bad block in the chain.

Ill talk to MIP about this logic.


So as we get a little more complicated our checklist is increasing.

In my case, I was able to overcome the fork by doing this:

rm instantsend.dat
restart client
exec reassesschains


The problem was the instantsend transmissions done between mandatory upgrades were memorized as IX locks.

Now my 3 sancs are syncing to the same height.




  • 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 #237 on: November 25, 2019, 08:31:34 PM »
Ok, my 3 sancs are on 1.4.8.1 now;  if we can get a confirmation that Oncoapops are on 1.4.8.1 then I think we can test IX and PS.



  • oncoapop
  • Full Member

    • 116


    • 12
    • October 23, 2018, 12:31:17 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #238 on: November 25, 2019, 10:08:49 PM »
Ok, my 3 sancs are on 1.4.8.1 now;  if we can get a confirmation that Oncoapops are on 1.4.8.1 then I think we can test IX and PS.

My 3 sancs are on 1.4.8.1
As you previously observed, my sancs are all running Linux and it does take time for the linux binaries to be available for download. My machines are also not powerful ones so they take an age to compile them from source. With all these said, mine are now current.

Is there a command to see which version the sancs are running without logging into the sancs themselves? Like version report for sancs?


  • 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 #239 on: November 26, 2019, 09:19:08 AM »
My 3 sancs are on 1.4.8.1
As you previously observed, my sancs are all running Linux and it does take time for the linux binaries to be available for download. My machines are also not powerful ones so they take an age to compile them from source. With all these said, mine are now current.

Is there a command to see which version the sancs are running without logging into the sancs themselves? Like version report for sancs?

Unfortunately, Dash took out the masternode version in the deterministic branch, so now we have no way to tell what version they are running.

I tried to put it back in 'masternodelist all', but it is actually missing everywhere in the code.

10-4 on the upgrade speed; Im pretty much in the same boat with my QT sancs, because I self compile and it puts a strain on this small hosting companies server.