Bible Pay

Read 64125 times

  • jaapgvk
  • Hero Member

    • 558


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #60 on: June 18, 2018, 12:55:37 PM »

Hi Jaap,

Oh OK, I see the problem, we dont have the 20bbp requirement spork set up in testnet yet.  So everyone is kind of freeriding right now.

Ill set it up in a couple hours when I look at that filtering of active proposal issue.

Oh, right! That explains is :)


  • orbis
  • Full Member

    • 215


    • 7
    • February 08, 2018, 04:37:14 PM
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #61 on: June 18, 2018, 02:02:05 PM »
Rob, I have compared those translation and I don't know how, but there was many differences to my "update".
I have made new pull request: https://github.com/biblepay/biblepay/pull/26.
Can you please tell me how to get those english phrases from source to SK locale?
Is it enought just to type there new block like this?
Code: [Select]
    <message>
        <source>any text from source code</source>
        <translation>text translation</translation>
    </message>
« Last Edit: June 18, 2018, 02:06:47 PM by orbis »


  • togoshigekata
  • Hero Member

    • 527


    • 31
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #62 on: June 18, 2018, 04:03:49 PM »
I dont think I was in the PODC superblock again

CPID:  c9a2065f******
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1987760

RAC: 32.59
TaskWeight: 100
UTXOWeight: 19

I dont think its auto sending PODC Updates, hmmm, I have a lot of available coins for staking so Id expect to see 100 for utxoweight, and I also dont see any of the podc update transactions in my transactions tab (I forgot how they look exactly, but I believe the look like payments to yourself, which I only have 1 of, and I think thats when I ran exec podcupdate the one time manually)

I only added config options to set up Sanctuary, I dont think config is the issue?:

Code: [Select]
testnet=1
addnode=***
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=***
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=250
externalip=***
masternode=1
masternodeprivkey=***
debug=true
debugmaster=true

BOINC Manager and BiblePay Daemon are both running and fighting for CPU, I wonder if that could be a potential issue?

Maybe I am missing something?

https://www.biblepay-central.org/en/documentations/mining-how-to/
http://wiki.biblepay.org/Distributed_Computing_2
« Last Edit: June 18, 2018, 04:05:57 PM by togoshigekata »


  • jaapgvk
  • Hero Member

    • 558


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #63 on: June 19, 2018, 03:35:01 AM »
I dont think I was in the PODC superblock again

CPID:  c9a2065f******
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1987760

RAC: 32.59
TaskWeight: 100
UTXOWeight: 19

I dont think its auto sending PODC Updates, hmmm, I have a lot of available coins for staking so Id expect to see 100 for utxoweight, and I also dont see any of the podc update transactions in my transactions tab (I forgot how they look exactly, but I believe the look like payments to yourself, which I only have 1 of, and I think thats when I ran exec podcupdate the one time manually)

I only added config options to set up Sanctuary, I dont think config is the issue?:

Code: [Select]
testnet=1
addnode=***
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=***
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=250
externalip=***
masternode=1
masternodeprivkey=***
debug=true
debugmaster=true

BOINC Manager and BiblePay Daemon are both running and fighting for CPU, I wonder if that could be a potential issue?

Maybe I am missing something?

https://www.biblepay-central.org/en/documentations/mining-how-to/
http://wiki.biblepay.org/Distributed_Computing_2

I don't think I was either. Maybe it's because we're running with so few sanctuaries?

Code: [Select]
10:31:14

exec getboincinfo


10:31:16

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 424832,
  "NextSuperblockHeight": 32878,
  "NextSuperblockBudget": 1279917,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 3787.02,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_WCGRAC": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 100,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 409,
  "Total_RAC": 3787.02,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 81224,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 1279917,
  "Superblock Count (One Week)": 165,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "31591,16533",
  "Last Superblock Height": 32779,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 63.46036500804349
}

Code: [Select]
10:30:13

exec getboincinfo


10:30:17

{
  "Command": "getboincinfo",
  "CPID": "8791a036b545f35e9ebd9333922738ac",
  "Address": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "CPIDS": "8791a036b545f35e9ebd9333922738ac;",
  "CPID-Age (hours)": 424832,
  "NextSuperblockHeight": 32878,
  "NextSuperblockBudget": 1279917,
  "8791a036b545f35e9ebd9333922738ac_ADDRESS": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "8791a036b545f35e9ebd9333922738ac_RAC": 176.18,
  "8791a036b545f35e9ebd9333922738ac_TEAM": 15044,
  "8791a036b545f35e9ebd9333922738ac_WCGRAC": 0,
  "8791a036b545f35e9ebd9333922738ac_TaskWeight": 100,
  "8791a036b545f35e9ebd9333922738ac_UTXOWeight": 24,
  "Total_RAC": 176.18,
  "Total Payments (One Day)": 15017,
  "Total Payments (One Week)": 1294933,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 1279917,
  "Superblock Count (One Week)": 165,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "31591,16533",
  "Last Superblock Height": 32779,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 1007.820819631273,
  "Magnitude (One-Week)": 1011.732010747572
}


  • Rob Andrews
  • Administrator

    • 4090


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #64 on: June 19, 2018, 10:45:37 AM »
I dont think I was in the PODC superblock again

CPID:  c9a2065f******
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1987760

RAC: 32.59
TaskWeight: 100
UTXOWeight: 19

I dont think its auto sending PODC Updates, hmmm, I have a lot of available coins for staking so Id expect to see 100 for utxoweight, and I also dont see any of the podc update transactions in my transactions tab (I forgot how they look exactly, but I believe the look like payments to yourself, which I only have 1 of, and I think thats when I ran exec podcupdate the one time manually)

I only added config options to set up Sanctuary, I dont think config is the issue?:

Code: [Select]
testnet=1
addnode=***
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=***
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=250
externalip=***
masternode=1
masternodeprivkey=***
debug=true
debugmaster=true

BOINC Manager and BiblePay Daemon are both running and fighting for CPU, I wonder if that could be a potential issue?

Maybe I am missing something?

https://www.biblepay-central.org/en/documentations/mining-how-to/
http://wiki.biblepay.org/Distributed_Computing_2


I dont think its anything on your end; I found some problems with the testnet sporks.  It didnt have DR mode, WCG was not disabled, RequiredSPR was not set (I set it to 2 just now), the team was empty, etc.  So I just set these, lets regroup in a little bit and see if the next daily superblock is better.

In the mean time, Im working on filtering the active proposals down to unpaid, adding this now.

EDIT: Please ensure you have genproclimit=1 or not set at all, and your mining HPS > 0.  The PODC update is sent from mining thread 0.  Btw, you should have an error in your log if your miner has been running more than 24 hours with "PODCUpdate" in front of it, that should shed light on why its not sending one. 

Also, you can run your 'exec utxoreport cpid' to see exactly which ones it sent.

« Last Edit: June 19, 2018, 10:47:54 AM by Rob A. »


  • jaapgvk
  • Hero Member

    • 558


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #65 on: June 19, 2018, 01:27:19 PM »
I'm having trouble with my Sanctuary (never had it running well this time in testnet). I first had the Sanctuary on my windows wallet, but of course that got a 'watchman expired' error after a while. So I tried my linux wallet.

When I start the wallet I get the following messages:

Quote
"Unable to bind to 0.0.0.0:40001 on this computer. Biblepay Core is probably already running."

"Failed to listen on any port. Use -listen=0 if you want this."

After that the wallet just closes.

The port is open on my router. If I add 'listen=0' to my config, the Sanctuary won't start.

Strange. I deleted the testnet folder (excluding wallet.dat and masternode.conf, but I still get the same error.

Code: [Select]
testnet=1
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=40001
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=***
masternode=1
masternodeprivkey=***


  • Rob Andrews
  • Administrator

    • 4090


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #66 on: June 19, 2018, 02:29:08 PM »
I'm having trouble with my Sanctuary (never had it running well this time in testnet). I first had the Sanctuary on my windows wallet, but of course that got a 'watchman expired' error after a while. So I tried my linux wallet.

When I start the wallet I get the following messages:

After that the wallet just closes.

The port is open on my router. If I add 'listen=0' to my config, the Sanctuary won't start.

Strange. I deleted the testnet folder (excluding wallet.dat and masternode.conf, but I still get the same error.

Code: [Select]
testnet=1
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=40001
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=***
masternode=1
masternodeprivkey=***


The main problem is your rpcport, in 'biblepaytest.conf', the rpcport must never be 40001 (as that is your P2P port in testnet), and it must be a different port number than the rpcport of any running instance (IE prod).  So say for example you were running your rpcport as 35000 on prod, it would have to be different than 40000, 40001, and 35000.  So just make it something lower etc.

Biblepay uses 2 ports in testnet : 40001 (for sharing blocks), and the rpc port (for administering the node).



  • jaapgvk
  • Hero Member

    • 558


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #67 on: June 19, 2018, 03:29:02 PM »

The main problem is your rpcport, in 'biblepaytest.conf', the rpcport must never be 40001 (as that is your P2P port in testnet), and it must be a different port number than the rpcport of any running instance (IE prod).  So say for example you were running your rpcport as 35000 on prod, it would have to be different than 40000, 40001, and 35000.  So just make it something lower etc.

Biblepay uses 2 ports in testnet : 40001 (for sharing blocks), and the rpc port (for administering the node).

Oops  :o Thanks for the explanation. I probably was tired and didn't really think about what I was doing when I put that number there.

Wallet is working like a charm now! Sanctuary started without problems.


  • togoshigekata
  • Hero Member

    • 527


    • 31
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #68 on: June 19, 2018, 06:13:08 PM »
I saw a PODC Update Transaction fire off 10 minutes ago :)
(It doesnt look like I can filter by Type "PODC Update" in the Transactions Tab)

Update: Now I saw a "PODC Payment" transaction, I paid 1,045.4 tBBP
« Last Edit: June 19, 2018, 06:32:14 PM by togoshigekata »


  • Rob Andrews
  • Administrator

    • 4090


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #69 on: June 20, 2018, 12:57:30 PM »
I saw a PODC Update Transaction fire off 10 minutes ago :)
(It doesnt look like I can filter by Type "PODC Update" in the Transactions Tab)

Update: Now I saw a "PODC Payment" transaction, I paid 1,045.4 tBBP

Great!  So things appear to be shaping up.

So I found a bug only affecting the mature_consensus (after go live feature) (I was testing the mature_consensus bullet point) and it needs a little work.  I am going to send this in today for the next testnet version.  Note that this causes the sancs to not come to consensus until all sancs upgrade, so (that is why) the boinc superblocks are not really staking regularly.  Lets try those again after we upgrade.

As far as the cosmetic features like the sort, if you would like to pick the top 5 most important ones and give them to Bhavani that may work.  Im going to be focused on making the pool add tax accountability records for Bloom & cameroon 1, and doing the grand total in the pool by month that Luke requested.  Even after that Ill be focusing on making stratis sync above block 129, so Im looking for Bhavani and others to help on those.

Note that Anton is also jumping in to do more theming.



  • Rob Andrews
  • Administrator

    • 4090


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #70 on: June 21, 2018, 08:47:54 AM »
I just deployed 1.1.3.3.

Please upgrade all testnet sancs so we can test the mature_consensus feature for the daily PODC superblock.

Its OK if non participating sancs are not upgraded; we only need a few that are actually online and synced to make this work.

(I think we had 3 sancs as of yesterday running out of a list of 20 with 17 offline).

(We need 2 for a consensus).



  • jaapgvk
  • Hero Member

    • 558


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #71 on: June 21, 2018, 07:29:11 PM »
I just deployed 1.1.3.3.

Please upgrade all testnet sancs so we can test the mature_consensus feature for the daily PODC superblock.

Its OK if non participating sancs are not upgraded; we only need a few that are actually online and synced to make this work.

(I think we had 3 sancs as of yesterday running out of a list of 20 with 17 offline).

(We need 2 for a consensus).

Just started my 1.1.3.3. Sanctuary. Should be 'ENABLED' in a few hours...


  • togoshigekata
  • Hero Member

    • 527


    • 31
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #72 on: June 21, 2018, 07:49:46 PM »
Upgraded to v1.1.3.3, re-enabling my sanc


  • Rob Andrews
  • Administrator

    • 4090


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #73 on: June 22, 2018, 07:01:47 AM »
Upgraded to v1.1.3.3, re-enabling my sanc

Ok, Im up to 1133 on my two sancs now.

Have you guys been getting paid daily superblock rewards?  I got one while my sanc was off.

So btw, an update on the proposal filter feature:  Its in this version, but as you can see in proposals list, both are still there even though the Groundbreaking one was paid.  I took a look at this in depth, and what it is is that since the supermajority of the sancs went down (Or were not running watchman), they lost the trigger that links the proposal to the trigger to the superblock.  Another words the chain cant see that it was paid.  I was taking a look at this in prod, and I dont think this particular thing can happen with 100+ sancs on line.  So I wrote some debug info for the feature and what I think Ill do is when we deem proposals safe to enable in prod (IE the next leisure release), we can log in on the prod side and test it.  But from what I see from the debug info, it should work in prod as-is and filter paid proposals in prod.



  • jaapgvk
  • Hero Member

    • 558


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #74 on: June 22, 2018, 12:10:53 PM »
Ok, Im up to 1133 on my two sancs now.

Have you guys been getting paid daily superblock rewards?  I got one while my sanc was off.

So btw, an update on the proposal filter feature:  Its in this version, but as you can see in proposals list, both are still there even though the Groundbreaking one was paid.  I took a look at this in depth, and what it is is that since the supermajority of the sancs went down (Or were not running watchman), they lost the trigger that links the proposal to the trigger to the superblock.  Another words the chain cant see that it was paid.  I was taking a look at this in prod, and I dont think this particular thing can happen with 100+ sancs on line.  So I wrote some debug info for the feature and what I think Ill do is when we deem proposals safe to enable in prod (IE the next leisure release), we can log in on the prod side and test it.  But from what I see from the debug info, it should work in prod as-is and filter paid proposals in prod.

I have been getting daily superblock rewards, but looking at my boincinfo it says something strange:

Code: [Select]
18:57:06

exec getboincinfo


18:57:08

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 424912,
  "NextSuperblockHeight": 36244,
  "NextSuperblockBudget": 575962,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 4034.31,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_WCGRAC": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 100,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 8814,
  "Total_RAC": 4034.31,
  "Total Payments (One Day)": 281920,
  "Total Payments (One Week)": 636046,
  "Total Budget (One Day)": 1151924,
  "Total Budget (One Week)": 4991675,
  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,
  "Superblock List": "35650,35551,34264,33472,31591,16533",
  "Last Superblock Height": 36145,
  "Last Superblock Budget": 575962,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 244.7383681562325,
  "Magnitude (One-Week)": 127.4213565586702
}

Code: [Select]
19:00:53

exec getboincinfo


19:00:56

{
  "Command": "getboincinfo",
  "CPID": "8791a036b545f35e9ebd9333922738ac",
  "Address": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "CPIDS": "8791a036b545f35e9ebd9333922738ac;",
  "CPID-Age (hours)": 424913,
  "NextSuperblockHeight": 36244,
  "NextSuperblockBudget": 575962,
  "8791a036b545f35e9ebd9333922738ac_ADDRESS": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "8791a036b545f35e9ebd9333922738ac_RAC": 141.73,
  "8791a036b545f35e9ebd9333922738ac_TEAM": 15044,
  "8791a036b545f35e9ebd9333922738ac_WCGRAC": 0,
  "8791a036b545f35e9ebd9333922738ac_TaskWeight": 100,
  "8791a036b545f35e9ebd9333922738ac_UTXOWeight": 353,
  "Total_RAC": 141.73,
  "Total Payments (One Day)": 25262,
  "Total Payments (One Week)": 1372885,
  "Total Budget (One Day)": 1151924,
  "Total Budget (One Week)": 4991675,
  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,
  "Superblock List": "35650,35551,34264,33472,31591,16533",
  "Last Superblock Height": 36145,
  "Last Superblock Budget": 575962,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 21.93026623284175,
  "Magnitude (One-Week)": 275.0349331637176
}

Both my rigs have been paid in the same daily superblocks it appears, but it says:
"  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,"

The superblock count seems weird. Anyway, PODC-payments seem to be working. Are we still on one minute blocktimes? Because then there should me more like seven 'daily superblocks' each day, right?