Bible Pay

Read 93578 times

  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
./biblepay-cli getinfo

"errors": "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."

Im seeing this on both of my testnet sanctuaries

Lets see if there are any errors in the log, and what block # and hash are you on?


  • togoshigekata
  • Sr. Member

    • 431


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
both on block: #11978

I think we lost our testnet explorer,
I can spin up another vultr and set one up, I assume we need one still?

cd ~/.biblepaycore
cd testnet3/
tail debug.log

2018-02-18 22:04:45 Misbehaving: 38.21.22.209:4643 (0 -> 14)
2018-02-18 22:07:39 Misbehaving: 195.201.30.231:42166 (0 -> 14)
2018-02-18 22:07:48 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:09:50 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:12:45 Misbehaving: 95.91.244.91:57302 (0 -> 14)
2018-02-18 22:13:01 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:13:01 Misbehaving: 47.189.53.97:54037 (0 -> 12)
2018-02-18 22:14:27 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:14:27 Misbehaving: 47.189.53.97:54070 (0 -> 12)
2018-02-18 22:14:48 Misbehaving: 38.21.22.209:4808 (0 -> 14)


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
both on block: #11978

I think we lost our testnet explorer,
I can spin up another vultr and set one up, I assume we need one still?

cd ~/.biblepaycore
cd testnet3/
tail debug.log


I get the same error.

2018-02-19 03:34:15 Misbehaving: 94.130.53.103:35416 (0 -> 14)
2018-02-19 03:37:20 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-19 03:38:04 Misbehaving: 195.201.30.231:34442 (0 -> 14)
2018-02-19 03:40:09 Misbehaving: 38.21.22.209:12281 (0 -> 14)
2018-02-19 03:44:50 Misbehaving: 91.219.3.153:53440 (0 -> 14)
2018-02-19 03:48:22 Misbehaving: 195.201.30.231:38404 (0 -> 14)
2018-02-19 03:48:56 Misbehaving: 94.130.53.103:35844 (0 -> 14)
2018-02-19 03:50:13 Misbehaving: 38.21.22.209:12452 (0 -> 14)
2018-02-19 03:54:26 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-19 03:55:37 Misbehaving: 91.219.3.153:53568 (0 -> 14)
2018-02-18 22:04:45 Misbehaving: 38.21.22.209:4643 (0 -> 14)
2018-02-18 22:07:39 Misbehaving: 195.201.30.231:42166 (0 -> 14)
2018-02-18 22:07:48 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:09:50 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:12:45 Misbehaving: 95.91.244.91:57302 (0 -> 14)
2018-02-18 22:13:01 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:13:01 Misbehaving: 47.189.53.97:54037 (0 -> 12)
2018-02-18 22:14:27 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:14:27 Misbehaving: 47.189.53.97:54070 (0 -> 12)
2018-02-18 22:14:48 Misbehaving: 38.21.22.209:4808 (0 -> 14)


  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
I get the same error.


I also got the same error yesterday, and only on my masternode, not on my normal miner. But I messed something up with my masternode, now I re-installed it and everything seems fine again :)

Also, the windows wallet now also seems to mine with 1% of it's original HPS if you use one tread, so that's nice.

And the things you said about PODC are still crunching in my head Rob. Might take a little while to take it all in.


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Hi Guys! Good Morning!

So unfortunately yesterday we had a Chinese New Year celebration that I had to attend so most of the evening was hogged.  Sorry.

Anyway, I did start looking at the issues last night that all 3 of you reported.  And I believe I see the problem, but its very boring and quite complicated to explain.  I'm thinking its best for us to roll the blockchain back to around block 2000 just for safety (Ill explain why) - this is in Testnet only of course.

So I remember we made an adjustment somewhere between block 2000 & 8000 with a core difficulty parameter which changed the max superblock (getsuperblockbudget N) by an amount that ends up "looking" like a masternode payment, and through all this syncing, we never marked the prior blocks as dirty (you dont encounter that until you reindex), and I had a rule in the code for testnet to "ällow" those (thats called grandfathering in by height).  So now that I see it was a parameter change, that makes me feel a little uneasy (about keeping the current chain) as I want a pristine test result so we have no surprises later - we need to isolate any issues with PODC alone so we can hit all the notes before March 15th.  Anyway the next thing we definitely ran into is between block 8000 and 10000 we had people lagging to upgrade, creating blocks on the wrong client version, and I see a couple old bad superblock amounts (apparently based on the old params). 

So in this new version Im going to enforce the testnet block version and the testnet App version.

Im testing now in testnet alone, once I feel this baby is syncing Ill release it.

I believe the only nuisance we have to go through is setting up some of our hot sancs again.  In my case I just send 500K hot to myself and it recovers... Not sure if you all tried that...

I should be done with this within an hour....

So in summary, please stop testing 1092 and wait and upgrade 1093 system wide.



  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.



  • jaapgvk
  • Hero Member

    • 617


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.

Nice work! Upgrading now...

I'll just have to see where I was as block 2000 and get my sanctuary up and running again.


  • togoshigekata
  • Sr. Member

    • 431


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.

Also remember that the blocks and chainstate folders and *.dat files are in testnet3 folder since we are in testnet

How to Update and Clean Wallets
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/



  • togoshigekata
  • Sr. Member

    • 431


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
I updated my 2 testnet machines, theyre both on block 922, is that correct?
block numbers keep going up, so I guess some are mining
my balances are empty,

Should I start mining?
Also do we need a testnet explorer?

Ill set up both my sanctuaries later today


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
I updated my 2 testnet machines, theyre both on block 922, is that correct?
block numbers keep going up, so I guess some are mining
my balances are empty,

Should I start mining?
Also do we need a testnet explorer?

Ill set up both my sanctuaries later today

Yes sure you can start mining, here is the blockhash:


getblockhash 950

c2e419d2e90547325f9c133f9b19986626a0cfbcf172f505564cc41436584884


So I have 1000 magnitude right now as I am the Sole cpid.  Ive solved 4 superblocks so far and verified the amounts emitted match the expected creation amounts - so far so good.

The reason why the blocks are clicking by so fast is I have the CPID check shut off until block 10000.




  • togoshigekata
  • Sr. Member

    • 431


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Ok I am on the correct chain, awesome,
setting both machines to mine with 1 thread

then Ill re-do the CPID burn,
and then set up the sancturaires


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
So Ive been thinking of ideas for raising the integrity of PODC, and here is one I came up with that at least feels promising but its in its infancy still.
Just to be clear I dont propose we stop PODC testing and implement this; I would rather finish testing this version as a unit and ensure it works with no bad superblock amounts - and as we enter the CPID phase no bad syncing before we add anything else to PODC.

Also keep in mind, that I know there might be better ideas that come to mind, but this idea comes from what *can* be done technologically that is reasonable, that allows miners on PCs tablets and Phones to execute the idea, in contrast to ideas that might fathomably be possible but would either be too hard to implement or would potentially not work on that Carribean cell phone.

So here it is:
I was thinking of preventing SQL tampering and increasing PODC integrity.  Possibly this way:
We make the controller wallet monitor your devices, those would be considered:  CPIDHASH-MACHINEHASH devices, in laymans terms that means your CPID as a Researcher Plus your first PC for example is that machine hash of your first device, it would iterate through the list of your devices and gather your Rosetta tasks that you are to be crunching.  It would be specifically interested in the starttime of the taskid, and would create a list of tasks that are unanounced to the network.  We would then take one UTXO (thats an unspent coin), and broadcast the cpidhash-machinehash-taskhash-taskid-utxo to the network, and allow biblepay to track the starttime of the tasks.  Then instead of rewarding you with RAC in the superblock we reward you with coin*age*rac, for each individual completed task that was provably started at a specific timestamp.

In this way, we can say that my machine asserts via signed CPID for this message that I own this task and I started it at Y unix timestamp.  Other nodes would verify this timestamp to see if you really started the task at that time.  (Boinc has that info live). 

Then in addition when the task is completed, you receive coin*age * RAC , meaning that there will now be a relationship between your machine, its task, its owner cpid, and the coins spent, and the corresponding public key of the owners wallet.

This would give a level of integrity that would be hard to crack because if SQL tampering is to occur, lets say at gunpoint most likely the perpetrator would be updating many records at once, affecting hundreds of tasks timestamps.  These boinc tasks fortunately are create before they are given out to researchers so if they do a mass update it would hose those records *after* our network said they were started (which would show tampering).  Or, if they update many as validated at once, our report would detect timestamp altering (because now we are tracking info in real time).

Then we could add a report to the core wallet to show this info daily and have it so we can export the RPC report to Excel. Maybe we make our wallet export excel reports to the drive from the controller wallet.

Another way to look at this is, at the very least it brings PODC up and past the trust level of POS, because some communities already trust POS coin consensus, this way PODC would have not only cancer research in real time, but proof-of-utxo-spending as well, tying spent coins to RAC.

The small devices would still work, but this would require a controller wallet running to know when the small device starts hashing.

Thinking about this a little deeper,  that might be a big boon for biblepay.  This would mean to get paid you need to keep your controller wallet running so it can send messages that your devices are starting tasks.  Thats a plus for our security , as that means our networking full node count is higher and the POW-heat side would not be virtually zero.  So this is actually a reasonable and positive requirement....

Lets think about this.



  • togoshigekata
  • Sr. Member

    • 431


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.

Also remember that the blocks and chainstate folders and *.dat files are in testnet3 folder since we are in testnet

How to Update and Clean Wallets
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

To re-associate your BOINC CPID:
http://wiki.biblepay.org/Distributed_Computing_2#PART_C._Link_BOINC_Account_to_BiblePay


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.



Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.


Windows has been deployed!    1.0.9.3:

https://www.biblepay.org


  • T-Mike
  • Administrator

    • 398


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Rob, how did you send the tBBP to yourself, Before I updated, it gave me that peers warning message when I tried to look up my addresses.