Bible Pay

TestNet => Active Discussions => Topic started by: Rob Andrews on July 19, 2020, 07:02:25 PM

Title: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 19, 2020, 07:02:25 PM
September 2020 Release


Welcome to the Biblepay September 2020 Testnet Testing thread for POOS!


In this thread we will be testing:

- POOS (Proof of Orphan Sponsorship):
     Verify the Sanctuary Owner may Sponsor a Cameroon-One Orphan (by associating this Orphan with the Sanctuary public key)
     Verify the legacy POSE ban system still POSE bans a node for lack of service
     Verify the POOS ban system will increase the ban for non-paid orphan accounts
     Verify the POOS ban system will decrease the ban once the orphan is paid for
     Verify the sanctuary cannot revive itself unless they pay the amount owed first

- Coin-Age voting:
     Verify you can vote from the Proposals UI by right clicking a proposal and voting with coin-age
     Verify you can increase the default (configurable) coin-age percentage using the biblepaytest.conf key value
     Verify the voted tally shows the correct coin-age and distinct sum of users who voted
     Verify we can vote with coin age from the RPC

- ChainLocks and DIP0008:
     Verify that testnet LLMQ quorums are forming, and advancing
     Verify testnet LLMQ locked IX transactions occur automatically, and quickly (IE test autolocks)
     Verify chainlocks locks the block (getblock hash, verify when entire block is IX locked, then it is also chainlocked)

- APM (Automatic Price Mooning)
     Verify the subsidy is 7 if an APM decrease event occurs day-over-day
     Verify the subsidy is normal if the price is unchanged, or if the APM increase event occurs day-over-day

- DWS (Dynamic Whale Staking)
     Verify the 'dws' and 'dwsquote' commands work as dedicated commands.


Additional Testing for BiblePay Unchained - added on August 6th:
First, read this guide:
https://wiki.biblepay.org/Using_Unchained


- BIPFS (Biblepay IPFS)
     Test exec bipfs_file (Upload a file into unchained).  Once the file is uploaded, verify the price, the duration, the density, and that you can navigate to the URL.
          (Verify both large and small files).
     Test exec bipfs_folder (Upload a folder into unchained).  Verify the price, duration, density, and a few URLs from the upload.
     Test uploading an encrypted file, retrieving the encrypted file (with exec bipfs_get), and re-opening the encrypted file.  Test it with a bad password also.
     Test exec bipfs_get (Download a file).
     Verify the sidechain sync height (Info Sidechain Sync Blocks).
     Verify bipfs_list (the uploaded file is now in the sidechain).

- BIPFS C# Client
     Test file upload and folder upload in the c# client.  Verify the file density, duration, and URL result, and download the asset from the URL.
     Verify the charge amount and the TXID was charged to the payment source (via API-KEY method).
   
- DWS UI
     Verify you can make a DWS burn from Send Coins Entry (these burns are always 90 days).  Verify the Quote works.


- Verify Monthly Budget changes:
     Verify as of block 55720, the sanctuary payout is 8.75% higher and the monthly governance budget is 8.75% lower












NOTE:
Most likely you will need to recreate your sanctuary, unless you see your sanctuary is POSE banned.  In that case you can revive the sanctuary with 'exec revivesanc'.


Starting Version:    1.5.1.7+


(Please ensure your version is greater than this, otherwise your testnet branch will not sync. 

We are at block  ____52500_____ as of July 21st, 2020).

BlockHash:
getblock 52500   "hash": "12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1"



Testnet Download Links:


Ready:
     Windows 64-bit:      https://biblepay.org/biblepayevo64develop.exe
     MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg
     Linux 64 bits II (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip


To self compile:
https://github.com/biblepay/biblepay/blob/develop/BuildBiblePay.txt





CONFIGURING FOR TESTNET:


Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepay



Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepay/testnet3 folder.


NOTE: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

__________________________________________________________________________________________________________________________________________________________________________________________



Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 21, 2020, 08:41:50 PM
Ok, this version is ready for testnet.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: oncoapop on July 22, 2020, 12:33:56 PM
Ok, this version is ready for testnet.

Hi Rob. Sorry for the absence. I have synced my sancs but unable to revive them
error code: -2
error message:
Safe mode: Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade.

Even though they are all on the correct blockhash
cli getblockhash 52500
12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 01:27:41 PM
Hi Rob. Sorry for the absence. I have synced my sancs but unable to revive them
error code: -2
error message:
Safe mode: Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade.

Even though they are all on the correct blockhash
cli getblockhash 52500
12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1

Hi bro-
Good to have a helper here in testnet make this release a success.
To make this easier on us, I have 4 sancs going also.

Also, in testnet, we have a quorum of 5 with 2 or more signers required (for llmq) so we should be able to test everything positively, including chainlocks.

So first you appear to be close to set up properly since you have the right hash.

Lets get rid of the safemode warning first.  Please restart the wallet, then look at any peers in the peers list that have a height of less than 52500 and ban them, then your safe mode should go away.

Let me know why you cant revive a sanc - you should get an error message.

If its code -25, that means 'unpaid POOS'.  If its 25, let me know what the sanctuary public key is for the sanc you try to revive - you can find it by double clicking on the sanc.

In testnet Im temporarily acting as cameroon-one.  Of course in prod, they will completely take over because in prod we will use their domain name.  In testnet we use foundation.biblepay.org for POOS.


Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 01:56:43 PM
Hi bro-
Good to have a helper here in testnet make this release a success.
To make this easier on us, I have 4 sancs going also.

Also, in testnet, we have a quorum of 5 with 2 or more signers required (for llmq) so we should be able to test everything positively, including chainlocks.

So first you appear to be close to set up properly since you have the right hash.

Lets get rid of the safemode warning first.  Please restart the wallet, then look at any peers in the peers list that have a height of less than 52500 and ban them, then your safe mode should go away.

Let me know why you cant revive a sanc - you should get an error message.

If its code -25, that means 'unpaid POOS'.  If its 25, let me know what the sanctuary public key is for the sanc you try to revive - you can find it by double clicking on the sanc.

In testnet Im temporarily acting as cameroon-one.  Of course in prod, they will completely take over because in prod we will use their domain name.  In testnet we use foundation.biblepay.org for POOS.


I made biographies for the 6 sancs that are POOS banned in testnet.

So please try to revive now.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 01:57:51 PM

I made biographies for the 6 sancs that are POOS banned in testnet.

So please try to revive now.


Also guys if you could please test at least one wallet per distinct test user from the biblepay-QT wallet, so we can test the main GUI features, thanks.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: oncoapop on July 22, 2020, 02:25:03 PM

I made biographies for the 6 sancs that are POOS banned in testnet.

So please try to revive now.

Sancs are synced and revived. There are 7 enabled sancs on testnet now.
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 03:40:07 PM
Sancs are synced and revived. There are 7 enabled sancs on testnet now.

Ok great, lets start by pretending you paid for the first month and just fell behind on payments to cameroon-one.

Please give me a couple sanctuary public keys so I can put your bios in non-payment mode.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 03:43:07 PM
Sancs are synced and revived. There are 7 enabled sancs on testnet now.

Another test we can start doing - coin-age voting.
In coin-age voting, we let the average user, not the sanctuary, place a vote on a proposal.  This lets us see the total-coin-age voted, and the total distinct user votes.

For example, lets say 5 regular users voted FOR a proposal, and each had 1 mil in coin age.  The total would be +5 FOR, 0 Against, and +5 MM coin-age in the "FOR" bracket.

To vote, please right click the proposal from your regular wallet (NOT from the sanctuary).


I entered a proposal called Bikers For Jesus.  Please go ahead and vote as a regular user and then check it after 3 blocks to see if the two totals incremented?


Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 03:47:12 PM
In testnet we have LLMQ autolocks turned on (this allows 10 second confirmations) and we have LLMQ Chainlocks on.

Lets test autolocks - please send a tithe to the foundation (just click Donate to Foundation), but ensure Instant Send is off.
See if the little Key appears within 10 seconds after you send it in the tx list.

Then after its in a block you can type 'getrawtransaction txid 1' and just see if both the chainlock and the Instant Send autolock is true?

This is going to allow us to then test chainlocks (as we do NOT have this feature turned on in prod, due to a probblem with dip008 in prod).  This will be great once we confirm this works 100%, as then we can turn on faster tx and more secure Chainlocks in prod.  Our prod environment has an LLMQ issue because of dip008 which we need to iron out here in testnet for September.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: oncoapop on July 22, 2020, 04:02:20 PM
Ok great, lets start by pretending you paid for the first month and just fell behind on payments to cameroon-one.

Please give me a couple sanctuary public keys so I can put your bios in non-payment mode.

My 3 that are enabled
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.108.63:40002
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.116.179:19998
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 45.62.240.90:19998
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 04:20:42 PM
My 3 that are enabled
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.108.63:40002
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.116.179:19998
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 45.62.240.90:19998

Ok, I made your 89c* sanc and your 07ba* sanc as if you didnt pay, so now you should see the POOS level increase.
Btw, you can see your sanctuary POOS level in the QT wallet - in the Sanctuaries UI.

You should then start receiving only 1 bbp for those two sancs.

EDIT:  I just made the biblepayd (non-qt non-gui wallet) also show the POOS level in 'masternodelist full' - this will be in the next release, but its not a high priority to get it out yet (until we find a bug, etc).

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 22, 2020, 09:42:57 PM
1.5.1.8-Mandatory Upgrade for TestNet

- Add POOS ban level to masternodelist full
- Fix bug in APM calculation
- Add APM narrative banner to the overview page
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: oncoapop on July 24, 2020, 02:47:43 PM
Ok, I made your 89c* sanc and your 07ba* sanc as if you didnt pay, so now you should see the POOS level increase.
Btw, you can see your sanctuary POOS level in the QT wallet - in the Sanctuaries UI.

You should then start receiving only 1 bbp for those two sancs.

EDIT:  I just made the biblepayd (non-qt non-gui wallet) also show the POOS level in 'masternodelist full' - this will be in the next release, but its not a high priority to get it out yet (until we find a bug, etc).

1. "613535d6ea651c5b5c3c224ab782409da6a873b8c10dda3216c6da9a6098f7de-1": "       POSE_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595486691  52832 45.62.240.90:19998",
Result of update: (initially updated, tried again and this is the second result. Sanc
  "service": "45.62.240.90:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned")
error code: -26
error message:
18: protx-dup


2.   "7392277be75eac0b90f2faea5a023565d1b408ecc045a17074d49bc227532a60-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595467363  52785 104.167.116.179:19998",
Result of update:
error code: -25
error message:

3.  "900c710e527cd634ca2c0e3d30d8f0a9983f0b8a5b93964adb1b8a7f5902b034-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595468292  52786 104.167.108.63:40002",
Result of update:
error code: -25
error message:

Note the error messages on the sanc themselves
BiblePay Core RPC client version 1.5.1.8
> sanc status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned"
}

Don't know reason for ban - mandatory upgrade (POSE) or POOS when queried from sanc itself.
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 25, 2020, 01:48:38 PM
1. "613535d6ea651c5b5c3c224ab782409da6a873b8c10dda3216c6da9a6098f7de-1": "       POSE_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595486691  52832 45.62.240.90:19998",
Result of update: (initially updated, tried again and this is the second result. Sanc
  "service": "45.62.240.90:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned")
error code: -26
error message:
18: protx-dup


2.   "7392277be75eac0b90f2faea5a023565d1b408ecc045a17074d49bc227532a60-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595467363  52785 104.167.116.179:19998",
Result of update:
error code: -25
error message:

3.  "900c710e527cd634ca2c0e3d30d8f0a9983f0b8a5b93964adb1b8a7f5902b034-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595468292  52786 104.167.108.63:40002",
Result of update:
error code: -25
error message:

Note the error messages on the sanc themselves
BiblePay Core RPC client version 1.5.1.8
> sanc status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned"
}

Don't know reason for ban - mandatory upgrade (POSE) or POOS when queried from sanc itself.

Note that any time we have a mandatory upgrade, all sancs that are part of the current quorum will end up getting POSE banned.  This also happens if all of us have our miners shut off.  Yesterday for example I had a power outage here and no one was mining for about 4 hours, so we had a lot of members of the quorum get pose banned. 

Today, I have a single thread miner running on one of the sancs - so theroetically none of us that are at the 0 ban level should increase.  Im going to be watching that.

I see your sancs:  104.167.116.179, and 108.63 are both POOS banned.  The way you can tell if you are POOS, or POSE, or both is:  700=POOS, 100=POSE, 800 = BOTH.
I see your two POOS banned sancs are both POOS+POSE banned (thats good) because they didnt pay their theoretical orphanage bill.

Ill set 104.167.108.63 as PAID now: OK 63 is paid.  Please revive it now.

Thats good you got the code -25 earlier, when trying to revive the POOS banned sancs.  Thats correct, people cant revive them unless the bill is paid first (this keeps people from slipping in and out and getting half paid by sending 15 revivals per month and tricking us).

Yes, I see you revived 45.62.240.90 earlier.  Good.  The "protx-dup' just means you sent a duplicate revival tx before the network fully processed the other one.  That doesnt hurt anything.  I think it takes about 2-3 confirms for us to all see the revival occur.

So far this test case (for cameroon one orphan-banning vs revival) has passed for me and for you.

Let me know if you have problems testing the test cases I posted in the OP post.

I dont know if you run the QT wallet or not.

On a side note, do you like the idea of POOS?  Didnt see any comments about it in the POOS thread.  How do you feel about sanc owners paying for an orphan?



Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: oncoapop on July 27, 2020, 04:08:02 PM
Note that any time we have a mandatory upgrade, all sancs that are part of the current quorum will end up getting POSE banned.  This also happens if all of us have our miners shut off.  Yesterday for example I had a power outage here and no one was mining for about 4 hours, so we had a lot of members of the quorum get pose banned. 

Today, I have a single thread miner running on one of the sancs - so theroetically none of us that are at the 0 ban level should increase.  Im going to be watching that.

I see your sancs:  104.167.116.179, and 108.63 are both POOS banned.  The way you can tell if you are POOS, or POSE, or both is:  700=POOS, 100=POSE, 800 = BOTH.
I see your two POOS banned sancs are both POOS+POSE banned (thats good) because they didnt pay their theoretical orphanage bill.

Ill set 104.167.108.63 as PAID now: OK 63 is paid.  Please revive it now.

Thats good you got the code -25 earlier, when trying to revive the POOS banned sancs.  Thats correct, people cant revive them unless the bill is paid first (this keeps people from slipping in and out and getting half paid by sending 15 revivals per month and tricking us).

Yes, I see you revived 45.62.240.90 earlier.  Good.  The "protx-dup' just means you sent a duplicate revival tx before the network fully processed the other one.  That doesnt hurt anything.  I think it takes about 2-3 confirms for us to all see the revival occur.

So far this test case (for cameroon one orphan-banning vs revival) has passed for me and for you.

Let me know if you have problems testing the test cases I posted in the OP post.

I dont know if you run the QT wallet or not.

On a side note, do you like the idea of POOS?  Didnt see any comments about it in the POOS thread.  How do you feel about sanc owners paying for an orphan?

1. Thank you.  104.167.108.63 has been revived.

2. 104.167.116.179
still  error code: -25

3. Just a quick reflection on the POOS.
a. It does place an extra burden on the sanc owners. They need to keep their servers running 24/7 or else get PoSE banned and also keep up Orphan payment or else get POOS banned.
b. Secondly, I presume that that orphan payments will be fixed in USD? Unless there are specific channels set up, frequently small payments in other than USD usually incur transaction fees which can add up. I personally support charities abroad and that is often a real problem.
 

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 27, 2020, 09:03:55 PM
1. Thank you.  104.167.108.63 has been revived.

2. 104.167.116.179
still  error code: -25

3. Just a quick reflection on the POOS.
a. It does place an extra burden on the sanc owners. They need to keep their servers running 24/7 or else get PoSE banned and also keep up Orphan payment or else get POOS banned.
b. Secondly, I presume that that orphan payments will be fixed in USD? Unless there are specific channels set up, frequently small payments in other than USD usually incur transaction fees which can add up. I personally support charities abroad and that is often a real problem.

On 108.63, good, it seems that works as expected then.
On 116.179, good, that is because (as per my original message about marking two of your sancs as unpaid) this one is still set as unpaid.  I just went ahead and set it to paid, so please revive it when you get a chance and see if payments start back up.

On POOS, thanks for the advice:
The payments for POOS are set at $40 USD per month, but are accepted in Paypal, BBP, BTC, XRP, so afaik paypal-intl does not charge any fees  -  so you are only on the hook for intl conversion rate risk.
However remember, in our world, you will be compensated for all of the child sponsorship in BBP Sanc rewards, since our sanc count will drop from 251 to 50 or so - therefore theoretically a sanc owner will receive a much higher reward per month after this starts. 

I'll take a look at the OP post and post some of the test case results.




Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 27, 2020, 09:10:37 PM
Test Case:

- APM (Automatic Price Mooning)
     Verify the subsidy is 7 if an APM decrease event occurs day-over-day
     Verify the subsidy is normal if the price is unchanged, or if the APM increase event occurs day-over-day


1.  Verified that when the price stayed stagnant or dropped day-over-day (this was 7-25-2020), the subsidy did drop from 4283 to 3 bbp.  PASS
2.  Verified that when the price increased (7-26-2020), the subsidy rose from 3 bbp back to 4283.  PASS
3.  Verified the contract contains the price change signal (1,2,3) and the bbp price in satoshi: PASS
4.  Verified the UI contains the relevant info (Current Price, Last Price, Last Superblock Height, Current superblock height, next APM signal) : PASS
5.  Verify the chain can sync from 0 after a price rise and price drop (verify we did not break any business logic) :  I Just resynced to 53769 :  PASS
6.  Verify Getgovernanceinfo does not lower the block subsidy during times of low payments:  PASS
7.  Verify the daily GSC superblock is not lower due to the lowered coinbase subsidy : PASS

Overall test results for APM:  PASS



Test Case:

- DWS (Dynamic Whale Staking)
     Verify the 'dws' and 'dwsquote' commands work as dedicated commands.

1.  Tested 'dwsquote' from RPC:  PASS
2.  Tested 'dws' from RPC:  PASS



ChainLocks and DIP0008:
     Verify that testnet LLMQ quorums are forming, and advancing
     Verify testnet LLMQ locked IX transactions occur automatically, and quickly (IE test autolocks)
     Verify chainlocks locks the block (getblock hash, verify when entire block is IX locked, then it is also chainlocked)


1.  Monitor 'quorum list', and verify 'quorum info 100 quorumid' contains a constantly new quorum of 3-7 sancs with block height fresher than 205 blocks : PASS
2.  Verify LLMQ autolocks, LLMQ IX, and Chainlocks sporks are ON:  PASS
3.  Verify a non-instantsend tx to the foundation in testnet is sent as an autolock : PASS
3b.  Verify the tx is autoconfirmed within 10 seconds: PASS
4.  Verify each new block is automatically locking every tx in the block: PASS
5.  Verify chainlocks is actually locking each block (getblock 53770, chainlock: true): PASS
6.  Verify that when we break the quorum, autolocks turn off:  PASS
(I broke the quorum by turning off all the miners for 4 hours)
7.  Verify POSE banned sancs in quorums have failed signatures : PASS  (quorum info 100 quorumid, look for pose banned sanc, look for bad sig: PASS)
8.  Verify our good sanctuaries will now vote to remove sancs who fail to sign llmqs (in testnet our min vote count is 2 sancs that have the power to boot out a fraudulent sanc, and in this same way we will
ensure this works in prod - this keeps the quorums running even if we have perpetrators acting as a sanc and trying to break the quorums): PASS



Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on July 29, 2020, 08:28:18 PM
Just reminding everyone:  No one has tested coin-age-voting yet.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 06, 2020, 09:08:28 AM
BiblePay TestNet - September 2020
1.5.1.9-Mandatory Upgrade for TestNet

- Add DWS (Dynamic Whale Stake) from the Send Coins UI (via checkbox)
- Add BiblePay Unchained (BIPFS Upload, Download, Encrypted, File and Folder support), Sidechain, and sidechain sync, and UI for sidechain block count
- Add exec bipfs_list, bipfs_folder, bipfs_file
- Modify Sanc payout to be 8.75% higher and monthly governance to be 8.75% lower
- Ensure our gsc contract contains the APM price (this means sancs will vote in unison for the correct price)

** I will be updating the required test cases in the OP Post Today - I will clearly delineate pre1.5.1.8 test cases from 1.5.1.9 with a horiz. rule so we know what additional test cases to test **

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 06, 2020, 09:25:17 AM
Please see this important information on how to use Unchained in testnet:

https://wiki.biblepay.org/Using_Unchained


Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 06, 2020, 09:33:06 AM
Todd from Cameroon-One has gotten involved in testnet also. 
We have moved the testnet POOS domain to the cameroon-one domain as of Aug 6th.
We will test POOS overall status (system up, system down), a new orphan, the POOS level, and an orphan in non-payment.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 06, 2020, 04:47:39 PM
Test results for Coin-Age voting:

Voted with coin age voting For the proposal from the QT wallet - verified that the distinct vote count increased and the distinct coin-age increased: PASS
Voted against the proposal - verified the "No" vote increased and the distinct "NO" coin-age increased: PASS
Verify the Proposals UI independent columns are correct in the datagrid: PASS

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: sunk818 on August 15, 2020, 09:24:57 AM
is the mac binary out of date? i downloaded it and it seems to show 1.5.0.5?
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 15, 2020, 10:51:39 AM
is the mac binary out of date? i downloaded it and it seems to show 1.5.0.5?

I'll reach out to MIP now and see if he will build it.  He said he has been too busy for anything over the last couple months.
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: MIP on August 15, 2020, 02:45:20 PM
I'll reach out to MIP now and see if he will build it.  He said he has been too busy for anything over the last couple months.

Thanks Rob for reaching. This weekend I am out in the high mountains and have very limited bandwidth so I don't think I will be able to upload the binaries (and in Mac it is required twice, once for notarising the DMG at Apple, and another one to biblepay.org FTP site).

On monday morning I will be back to a civilised place and I will be able to get it ready.
Sorry for the delay and the inconveniences..
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 15, 2020, 07:03:16 PM
Thanks Rob for reaching. This weekend I am out in the high mountains and have very limited bandwidth so I don't think I will be able to upload the binaries (and in Mac it is required twice, once for notarising the DMG at Apple, and another one to biblepay.org FTP site).

On monday morning I will be back to a civilised place and I will be able to get it ready.
Sorry for the delay and the inconveniences..

That sounds great!

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: orbis on August 16, 2020, 04:46:27 PM
Hi all,
sorry for not be here for a longer time, but I have busy time at home and work :) :(
But I'm still keeping an eye on BBP :)
Today I have try to read, what will be changed in next mandatory and I'm little bit confused.
Rob, can you please try to explain me what and will be changed?
As I read it, I get that there will be POOS, but I have few question.
POOS will be here instead of PODC, so it won't be necceccary use PC power to take rewards?
What is the lowest possible donation to POOS? Or it still 38$?
I'm asking, because my payment for my VPSs is 12/month and that is maximum what I'm possible to invest monthly. Does it mean, that I won't be able to mine?
How will be POOS connected to sanctuary? Will it be necceccary to donate for sanctuary rewards too?
How will be the rewards (payouts) changed?
Will be the coin name changed (BBP to DAI)?

Once again, I'm sorry, that I didn't helped in testnet this time.
Thanks.
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 16, 2020, 07:30:58 PM
Hi all,
sorry for not be here for a longer time, but I have busy time at home and work :) :(
But I'm still keeping an eye on BBP :)
Today I have try to read, what will be changed in next mandatory and I'm little bit confused.
Rob, can you please try to explain me what and will be changed?
As I read it, I get that there will be POOS, but I have few question.
POOS will be here instead of PODC, so it won't be necceccary use PC power to take rewards?
What is the lowest possible donation to POOS? Or it still 38$?
I'm asking, because my payment for my VPSs is 12/month and that is maximum what I'm possible to invest monthly. Does it mean, that I won't be able to mine?
How will be POOS connected to sanctuary? Will it be necceccary to donate for sanctuary rewards too?
How will be the rewards (payouts) changed?
Will be the coin name changed (BBP to DAI)?

Once again, I'm sorry, that I didn't helped in testnet this time.
Thanks.

Hi Orbis, its nice to see you have been hanging around!  No problem--

So, we are not retiring PODC, so you can still receive PODC and RandomX rewards.

POOS simply requires all the existing sanctuaries to re-lock their capital, and sponsor a Cameroon-One orphan for $40 a month in order to receive sanctuary rewards.  (Otherwise they get POOS banned in the sanctuary list).

You still have to keep the machine sending GSC stakes for PODC though daily (but of course for POOS, you dont need to power up your home PC, but you need to have a dedicated sanc running instead).

As far as POOS being connected to a sanc, take a look at the QT testnet sanc list.  Cameroon one will make a bio for each sanctuary.  If it exists, the sanc gets paid.  If it does not exist, the sanc starts getting banned, etc.  Cameroon will EDIT the bio if the user falls behind in payments.

Sancs pay a dynamic reward (depending on how many exist) so I believe that completely answers that question, but let me know.

I added a blurb in the DAC (coin-name) discussion thread that I think we should wait and put that decision off for 6 months.  At this point I personally lean a little tiny bit more to BiblePay again, based on our existing reputation we have built up.  The votes for it were really mostly neutral.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: sunk818 on August 16, 2020, 08:49:22 PM
Is creating a sanctuary harder since moving to newer DASH code?
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 17, 2020, 08:43:35 AM
Is creating a sanctuary harder since moving to newer DASH code?

Yeah, it is relatively complicated.  Its still a page full of archaic commands and requires a guide to do it.  I personally recommend creating the sanctuary the old way (send 4,500,001 to your address, copy the txid vin and add an entry to the masternode.conf file, and then just upgrade the sanc to deterministic using this command - all you need is the sanctuary nickname):
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

The primary reason I recommend this method is that BIBLEPAY (our niche feature) stores your BLS key info in the deterministic.conf file (thats one of our files). 
This allows you to revive the sanc later using our commands.

Otherwise, if we were entrirely dash, I would recommend the DASH way, but since we have advanced features - I found it extremely useful to be able to access that key and also run the 'exec revivesanc' command any time we get POSE banned.



Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: orbis on August 17, 2020, 01:52:49 PM
Hi Orbis, its nice to see you have been hanging around!  No problem--

So, we are not retiring PODC, so you can still receive PODC and RandomX rewards.

POOS simply requires all the existing sanctuaries to re-lock their capital, and sponsor a Cameroon-One orphan for $40 a month in order to receive sanctuary rewards.  (Otherwise they get POOS banned in the sanctuary list).

You still have to keep the machine sending GSC stakes for PODC though daily (but of course for POOS, you dont need to power up your home PC, but you need to have a dedicated sanc running instead).

As far as POOS being connected to a sanc, take a look at the QT testnet sanc list.  Cameroon one will make a bio for each sanctuary.  If it exists, the sanc gets paid.  If it does not exist, the sanc starts getting banned, etc.  Cameroon will EDIT the bio if the user falls behind in payments.

Sancs pay a dynamic reward (depending on how many exist) so I believe that completely answers that question, but let me know.

I added a blurb in the DAC (coin-name) discussion thread that I think we should wait and put that decision off for 6 months.  At this point I personally lean a little tiny bit more to BiblePay again, based on our existing reputation we have built up.  The votes for it were really mostly neutral.

Thanks for answers.
I was asking about retiring PODC, because I read POOS wiki and there is written, that it's neccessary to retire PODC to be effective.
Maybe in 2-3 months I'll be lowering down my VPS, so my income from PODC won't be so interresting as now :)

As I understand it correctly, what look worse to me is POOS on MN. I was hardly try to get enough BBP for my next MN (even with thanks to your fractional sanc :)), but now it looks, that I won't be able to maintain even one sanc, so my BBP will be laying down on my wallet and not earning anymore :(
Now my sanc gives me around 100k BBP which is around 10-12 and I think it won't be profitable even with lower number of sancs.  $40 a month is too much for me. Sorry. But it will be better to others :)

I'll try to check testnet before mandatory to take a look on changes.

Have a nice day to all :)
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 17, 2020, 03:41:22 PM
Thanks for answers.
I was asking about retiring PODC, because I read POOS wiki and there is written, that it's neccessary to retire PODC to be effective.
Maybe in 2-3 months I'll be lowering down my VPS, so my income from PODC won't be so interresting as now :)

As I understand it correctly, what look worse to me is POOS on MN. I was hardly try to get enough BBP for my next MN (even with thanks to your fractional sanc :)), but now it looks, that I won't be able to maintain even one sanc, so my BBP will be laying down on my wallet and not earning anymore :(
Now my sanc gives me around 100k BBP which is around 10-12 and I think it won't be profitable even with lower number of sancs.  $40 a month is too much for me. Sorry. But it will be better to others :)

I'll try to check testnet before mandatory to take a look on changes.

Have a nice day to all :)

Hi Orbis,
Can you please paste the link where we said PODC must be retired in POOS?  Maybe we originally discussed it but for now, afaik, PODC will stay along with RX.

On the sanc income, if we only have 25 sancs, the BBP earnings should be much higher, but we just have to wait it out to see the actual figs.

On the testnet testing, we have a mandatory upgrade coming in about 2 hours so please hang on for the latest version,
Thanks,
Rob
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: orbis on August 17, 2020, 03:51:47 PM
Here:
https://wiki.biblepay.org/Proof_Of_Orphan_Sponsorship

Quote
The concept has the following cons:
PODC would need to be eliminated to raise the POOS budget.
More administrative burden for each sanctuary owner (approving mining permits monthly).
Stringent verification requirements to prevent fraud.
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 17, 2020, 04:39:56 PM
Here:
https://wiki.biblepay.org/Proof_Of_Orphan_Sponsorship

Oh ok, no wonder both you and I were confused.

I wrote that way back when I knew very little about what we would become, and, I think that concept had more to do with creating a domain that sponsors orphans etc.
IE before we even had a partner (cameroon-one) to help us establish the relationship between orphan bios and sanc, etc.

The thread for POOS is here:
https://forum.biblepay.org/index.php?topic=569.0

To cut down confusion, I changed the name of that old POOS wiki to proof of retirement and moved it.

Thanks.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 17, 2020, 05:41:54 PM
1.5.2.1b-Mandatory Upgrade for TestNet

- Add DashStake (dashstake, dashstakequote), autolocking of BBP collateral held in stakes, Dash Reward icons in QT UI
- Add right-click Copy UTXO action to coin control
- Fix DIP008 for Prod release, and, set new LLMQs params for PROD release
- Add show exchange button to QT
- (Fix cosmetic display bug in dashstakequote in 1.5.2.1b)

MIP will be building the MAC release soon.
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 17, 2020, 06:55:09 PM
Here is my first stab at the Dash Stake user guide:

https://wiki.biblepay.org/Dash_Stake

Needs a lot more user friendliness and explanation about USDBBP-USDDASH ROI still.  Will try to improve it over the next 20 days.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: MIP on August 18, 2020, 03:24:08 AM
1.5.2.1b-Mandatory Upgrade for TestNet

- Add DashStake (dashstake, dashstakequote), autolocking of BBP collateral held in stakes, Dash Reward icons in QT UI
- Add right-click Copy UTXO action to coin control
- Fix DIP008 for Prod release, and, set new LLMQs params for PROD release
- Add show exchange button to QT
- (Fix cosmetic display bug in dashstakequote in 1.5.2.1b)

MIP will be building the MAC release soon.

MacOS release ready
https://biblepay.org/biblepaycore-evo-testnet.dmg
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: sunk818 on August 18, 2020, 09:51:31 AM
Any good peers I can connect to?
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 18, 2020, 11:01:04 AM
Any good peers I can connect to?

testnet1.biblepay.org:40001 answers and is compiled in the wallet.  Please check your clock and timezone also, and ensure version is 1.5.2.1+.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: sunk818 on August 20, 2020, 10:52:28 AM
I had to add the peer manually.


addnode testnet1.biblepay.org:40001 add
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: sunk818 on August 20, 2020, 11:17:50 AM
Can't get to 100%. I erased the chain data and left just wallet.dat . I've gotten to the same place twice.



2020-08-20 16:11:51 {PNB}: ACC  {PNB}: ACC  UpdateTip: new best=108870ace145be01d3881c59832e404d816ec4d39997e09a8d5c136dbee9b52f height=51850 version=0x50000000 log2_work=48.51148818 tx=86585 date='2020-07-17 19:17:20' progress=0.747391 cache=0.5MiB(2408txo) evodb_cache=0.0MiB
2020-08-20 16:11:51 UpdateTip: new best=4a87ae0853795a71eea3a2bbeb79e3eb75dfd428c982ebaef3d2544789987692 height=51851 version=0x50000000 log2_work=48.51148818 tx=86587 date='2020-07-17 19:29:20' progress=0.747442 cache=0.5MiB(2410txo) evodb_cache=0.0MiB
2020-08-20 16:11:51 CFinalCommitment::VerifySizes -- invalid signers.size=70
2020-08-20 16:11:51 ERROR: ConnectBlock(DASH): ProcessSpecialTxsInBlock for block 7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4 failed with bad-qc-invalid-null (code 16)
2020-08-20 16:11:51 Misbehaving: 107.191.44.254:40001 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2020-08-20 16:11:51 InvalidChainFound: invalid block=7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4  height=51852  log2_work=48.51148818  date=2020-07-17 19:30:45
2020-08-20 16:11:51 InvalidChainFound:  current best=4a87ae0853795a71eea3a2bbeb79e3eb75dfd428c982ebaef3d2544789987692  height=51851  log2_work=48.51148818  date=2020-07-17 19:29:20
2020-08-20 16:11:51 ERROR: ConnectTip(): ConnectBlock 7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4 failed with bad-qc-invalid-null (code 16)
2020-08-20 16:11:51 InvalidChainFound: invalid block=7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4  height=51852  log2_work=48.51148818  date=2020-07-17 19:30:45
2020-08-20 16:11:51 InvalidChainFound:  current best=4a87ae0853795a71eea3a2bbeb79e3eb75dfd428c982ebaef3d2544789987692  height=51851  log2_work=48.51148818  date=2020-07-17 19:29:20
2020-08-20 16:11:51 {PNB}: ACC  {PNB}: ACC 

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 20, 2020, 12:53:49 PM
Can't get to 100%. I erased the chain data and left just wallet.dat . I've gotten to the same place twice.



2020-08-20 16:11:51 {PNB}: ACC  {PNB}: ACC  UpdateTip: new best=108870ace145be01d3881c59832e404d816ec4d39997e09a8d5c136dbee9b52f height=51850 version=0x50000000 log2_work=48.51148818 tx=86585 date='2020-07-17 19:17:20' progress=0.747391 cache=0.5MiB(2408txo) evodb_cache=0.0MiB
2020-08-20 16:11:51 UpdateTip: new best=4a87ae0853795a71eea3a2bbeb79e3eb75dfd428c982ebaef3d2544789987692 height=51851 version=0x50000000 log2_work=48.51148818 tx=86587 date='2020-07-17 19:29:20' progress=0.747442 cache=0.5MiB(2410txo) evodb_cache=0.0MiB
2020-08-20 16:11:51 CFinalCommitment::VerifySizes -- invalid signers.size=70
2020-08-20 16:11:51 ERROR: ConnectBlock(DASH): ProcessSpecialTxsInBlock for block 7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4 failed with bad-qc-invalid-null (code 16)
2020-08-20 16:11:51 Misbehaving: 107.191.44.254:40001 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2020-08-20 16:11:51 InvalidChainFound: invalid block=7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4  height=51852  log2_work=48.51148818  date=2020-07-17 19:30:45
2020-08-20 16:11:51 InvalidChainFound:  current best=4a87ae0853795a71eea3a2bbeb79e3eb75dfd428c982ebaef3d2544789987692  height=51851  log2_work=48.51148818  date=2020-07-17 19:29:20
2020-08-20 16:11:51 ERROR: ConnectTip(): ConnectBlock 7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4 failed with bad-qc-invalid-null (code 16)
2020-08-20 16:11:51 InvalidChainFound: invalid block=7bb375978c124c058c1f3bf897452d02b4f81ba54b515a080199ca4a39a47bc4  height=51852  log2_work=48.51148818  date=2020-07-17 19:30:45
2020-08-20 16:11:51 InvalidChainFound:  current best=4a87ae0853795a71eea3a2bbeb79e3eb75dfd428c982ebaef3d2544789987692  height=51851  log2_work=48.51148818  date=2020-07-17 19:29:20
2020-08-20 16:11:51 {PNB}: ACC  {PNB}: ACC

Just out of curiosity can you please check if your download of mac was from today?
I found the 1.5.2.1 release was bad and we re-released today with a couple changes.

Once you reinstall, please sync from zero, as llmqs have changed since our last testnet session(s).

Thanks,
Rob
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: orbis on August 20, 2020, 03:25:13 PM
Hi.
So, I've tried to run testnet BBP and I have problem to connect.
I have 1521, but don't know if it's 1521b, or not. I've downloaded it few hours back from first post of this thread.
I'm stucked on block 51851.
I've tried clean install, blockchain delete, ... but nothing worked. Still stucked.
Any idea?
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 20, 2020, 03:44:51 PM
Hi.
So, I've tried to run testnet BBP and I have problem to connect.
I have 1521, but don't know if it's 1521b, or not. I've downloaded it few hours back from first post of this thread.
I'm stucked on block 51851.
I've tried clean install, blockchain delete, ... but nothing worked. Still stucked.
Any idea?

Hi Orbis, is this windows version?

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 20, 2020, 03:50:26 PM
Hi.
So, I've tried to run testnet BBP and I have problem to connect.
I have 1521, but don't know if it's 1521b, or not. I've downloaded it few hours back from first post of this thread.
I'm stucked on block 51851.
I've tried clean install, blockchain delete, ... but nothing worked. Still stucked.
Any idea?
Sorry, I forgot to deploy it.

Please try downloading now.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: orbis on August 20, 2020, 05:04:18 PM
Hi Orbis, is this windows version?
yes. W10 64bit.
And BTW, it installed in same directory as proper BBP and my BBP standard wallet is in new version...
Is that problem?
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: Rob Andrews on August 20, 2020, 05:25:23 PM
yes. W10 64bit.
And BTW, it installed in same directory as proper BBP and my BBP standard wallet is in new version...
Is that problem?

Normally, it would be, but Ill explain why not.
A) The location of the install directory is set by you.  So what I usually do is install testnet builds in my program files\testnet directory (for the EXE) on windows then I run them with the -conf=biblepaytest.conf when I test them, just to ensure my binary never gets mixed with the current prod binary.  Then you can test on your home windows box without a problem.
B) You have to normally be careful not to run a testnet version against your prod wallet (and your prod blockchain files).  As testnet versions contain new params and stuff and could corrupt them.  So thats why I always start the testnet version pointing to a different -conf file switch.
C) In the case of today however, this version passed test and is being released to prod so its OK if you ran it against your prod files - as it will be in prod in a few days anyway. 
D) I still recommend overwriting your Prod version with the version that will be announced on the forum thread tomorrow, because, that version has an extra spork in it for APM.  Your testnet only works for a certain # of days in prod etc.

But feel free to do any more testing if you want, but I didnt have a lot of responses over the last 75 days so I had to unit test all of it in order to get it out today.

I want to get it out because we have some things that need to get started in prod (POOS etc).

What I mean is testing is still valuable for BIPFS, etc.

Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: sunk818 on August 21, 2020, 11:43:57 AM
Just out of curiosity can you please check if your download of mac was from today?
I found the 1.5.2.1 release was bad and we re-released today with a couple changes.

Once you reinstall, please sync from zero, as llmqs have changed since our last testnet session(s).

Thanks,
Rob


Okay, I'll try DMG again. I think I remember why you said new builds sometimes have the same version number as before.
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: orbis on August 21, 2020, 03:23:35 PM
Normally, it would be, but Ill explain why not.
A) The location of the install directory is set by you.  So what I usually do is install testnet builds in my program files\testnet directory (for the EXE) on windows then I run them with the -conf=biblepaytest.conf when I test them, just to ensure my binary never gets mixed with the current prod binary.  Then you can test on your home windows box without a problem.

Problem was, that previous testnets used "c:\Program Files (x86)\" and prod "c:\Program Files\"...
Now I don't see this change and testnet was installed in classic prod "c:\Program Files\" :)
Next time I'll take a better look on that and install it in different folder again :)
BTW: Today I was get over that stucked block, so I'm synced in testnet
Title: Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020
Post by: sunk818 on August 22, 2020, 11:40:29 PM
macOS DMG is still on 1.5.2.1 - I seem to be forked. Will wait for a new build.