June 2021 Release - Harvest - TestNet Thread

Hi Rob,

Send another Christmas Card, where do I see the proof link ??

The UI just gives me the Successfully created Mail Delivery ID...

btw: The NFT's that I created can not be seen in the List my NFT's, they do show in the forum NFT marketplace....

btw: My Testnet says Syncing Headers 99.3% looks like it is not fully synced

Hi Pat,

First on the syncing.  I wouldnt mind if you could try a couple things before resorting to erase index.  Because in testnet we really need to know the underlying problem (if we rebuild we will lose the potential root cause).  However I see all 3 of my sancs are in sync and my home client in sync so there is a good chance your 99.3% message is just what you get during the first 5 mins of boot (when its loading governance data).  First we need to check to see if you are actually out of sync.  Plz run this command:

getblockhash 79088


31f092b81ca0cc1429cc19c7de9ce4372da1bb4fd9eefe007993fb2a5ff95b5a

See if it matches?  If it does its probably just you have to wait longer for your masternode data - or maybe you have no connections?  See if you have peer connections?  (Tools | Debug Console | Peers - look for other peers).

So on the link, when you make the card, it pops up an anchor link on the message box that can be clicked or right clicked.  If you click it, it takes you to the card and from there you can copy it.  Or you can copy the link by right clicking and click copy URL.

We also provide the link on the bottom of the page so if you already hit enter, you can copy it from there. 

Let me know if you are in sync and if you arent, this would be a good log for you to send me (you can send me debug.log from %appdata%\biblepaytest\testnet3) to my email but only if your node is actually out of sync.

EDIT:  Btw we had a mandatory upgrade to 1.6.0.7, so plz ensure your version is 1607 also?  That would also cause you to go out of sync.


EDIT II:  On the NFTs, Ok yes I do see your nfts in the marketplace, but they are not in your NFT list -- OK, let me try to reproduce that on my end, thanks....

Im making an orphan NFT now.

Hello Pat.

If you are still stuck at the "syncing headers part" you could try in the core wallet : Tools>wallet repair>rebuild index.

Hi Earlz!  On your sanc I see it went back to revived (700) yesterday but it crept up to (721) again.  Im just trying to ensure we have perfect llmqs in testnet could you see if it was off or a bad connection or went out of sync or anything at all?  Im hoping it was just off for a while...

I sent Pat my last hash you can check your sanc with the same one too?

Hi Rob,

- Cannot see the NFTs in the list

Hi Pat, regarding this one:
First I checked my 3 that I created (the new ones) and I can see them so lets try to drill down into this to figure this out.
(I click on NFTs | List My NFTs - and I see just my 3 in the grid...  Yours are still empty correct?):

Could you please try:
listnfts 1 1

This should show you all the nfts and the first 3 or so should be yours, and I see they look fine (I see both URLs and they are not deleted and I see your CPK).
So to know if they are Yours, we compare the CPK (Christian-public-key) with your cpk.

Could you please take note of your cpk address, then click File | Receiving addresses, and tell me if your "Christian-Public-Keypair"has not been altered, and is it still labeled?  I dont know but maybe you erased your wallet and went to a new key possibly (compare the addresses)?

Thanks!

Hi Earlz!  On your sanc I see it went back to revived (700) yesterday but it crept up to (721) again.  Im just trying to ensure we have perfect llmqs in testnet could you see if it was off or a bad connection or went out of sync or anything at all?  Im hoping it was just off for a while...

I sent Pat my last hash you can check your sanc with the same one too?

Howdy.

Yeah i believe its my internet connection. Im running over 4G network and normally its stable enough run mining rigs and what not. But ever so often i need to reboot this ZTE 4G router that i have.

Today i also shut off masternode so i could update to v 1.6.0.8
i ran the getblockhash command in terminal and got:

Code: [Select]

getblockhash 79088
31f092b81ca0cc1429cc19c7de9ce4372da1bb4fd9eefe007993fb2a5ff95b5a

comparing to the one you posted: 31f092b81ca0cc1429cc19c7de9ce4372da1bb4fd9eefe007993fb2a5ff95b5a

It looks the same to me as the one you posted.

I suppose i could setup a sanctuary on a real VPS provider by the end of the month, alteast uptime then should be 100%

Just FYI, I see the links on the greeting card generate page are pretty small and in QT they default to dark blue, so on the next version I force it to be 150% bigger in Pink, and it will say "REVIEW PROOF HERE" etc..  We will wait til next feature release though for this as its cosmetic only.

Howdy.

Yeah i believe its my internet connection. Im running over 4G network and normally its stable enough run mining rigs and what not. But ever so often i need to reboot this ZTE 4G router that i have.

Today i also shut off masternode so i could update to v 1.6.0.8
i ran the getblockhash command in terminal and got:

Code: [Select]

getblockhash 79088
31f092b81ca0cc1429cc19c7de9ce4372da1bb4fd9eefe007993fb2a5ff95b5a

comparing to the one you posted: 31f092b81ca0cc1429cc19c7de9ce4372da1bb4fd9eefe007993fb2a5ff95b5a

It looks the same to me as the one you posted.

I suppose i could setup a sanctuary on a real VM provider by the end of the month, alteast uptime then should be 100%

Hi Earlz,

Well thats actually pretty good then we may not need a new sanc later, because this simulates real conditions of going in and out.  Theoretically, every time your sanc makes a good chainlock call, the 721 should decrease by itself back toward 700.  So if the sanc continues to get paid and running, its fine.

Let me know if you can do a greeting card virtual gift generate too so I can try to cash one in.

Im going to make test cases for "referrals" and "high risk stakes" also.

I added an orphan NFT:

http://foundation.biblepay.org/NFTOrphans

If anyone wants to sponsor her go ahead:

But we need 2 more features I have in todo list for orphans:  We need to make it so a person cannot re-sell an orphan once they 'sponsor one'  - so basically they Sponsor Now, that establishes the 'buy date' in the chain, the orphan is Good for that many days (IE 90 from that date) and at the end of the term the orphan automatically deletes herself, etc, but they may not re-sell the orphan.

But if you try now you should at least have her in your NFTs list.

Also on the digital goods you can see we now have Auctions 1.0 (ability to accept Offers) and Buy-it-now:
http://foundation.biblepay.org/NFTBrowse

I entered a few Offers on some.

The way it currently works is the only way an offer is accepted is if the owner sees the offer and Edits the NFT reserve price to be a little lower, then a new offer hits higher than that and that person gets the nft.  (We dont currently continually monitor old bidders and escrow their funds and allow a purchase to go through although, I think we should do that soon.

An example of that is John Bids 1000 for NFT1, it is below the reserve.  Later the Owner lowers the Reserve to 999.  At that very second the foundation could "remember" the bidder that bid 1000, and immediately take it and complete the sale.  Thats the feature we dont have yet that we can add soon)..

First we need to test a high risk stake as compared to a regular conservative stake.

The old conservative stake for BBP alone is the one where you type:
easybbpstake 1000000 1
(For example to stake 1MM)

Now we have this High risk staking, where we lock up your coins for the duration You specify (from 31 days to 365 days currently).
Please read this page about High-risk including the End FAQ:
https://wiki.biblepay.org/UTXO_Mining

Then go ahead and create a high risk stake with "highriskbbpstake" command.
If you are savvy and have some extra foreign coins you can also run a "highriskstake" hybrid stake as well.

Ill explain how we can report on the listutxostakes in a little while.  Right now we have a field called "elapsed" vs. "commitment".  The commitment is the number of days you locked up your stake for (IE 365 equals one year).  If you have a commitment of 365, and 7 days has elapsed since you staked the high risk stake, listutxostakes says :  e7/365 (this means elapsed 7, out of 365 days committed).  Note in testnet, we tweaked the clock to be 24* faster so we can test faster.  So days fly by 24* faster here (for utxostakes).

Why is this all relevant?  We need to test brute unlocking of the high risk stake to make sure the penalty is correct.  You can try to unlock and spend one of your high risk stakes early.  You should be penalized between ~30-99% (depending on market conditions) according to the wiki guide.  You will receive a warning in the UI detailing the network fees.

Let me know if you guys have any questions on all this.

In the mean time I will modify listutxostakes to have a better 'utxotype' column and cleaner elapsed etc, its kind of hard to know the difference between all your stakes right now.

Btw, you can double click on your position in the leaderboard and see the % of high risk stakes you have etc.

EDIT:  Id also like us to stake at least 50MM tBBP in test, because Id like to see the DWU drop down below 99% so we can see the differences in the next version which will have fields for high risk DWU vs conservative etc (so we are not hitting the cap).  Please create extra big stakes.

We also need to test referral codes.  Please read this first:
https://wiki.biblepay.org/Referrals

I have created a referral code for my portfolio:
f7fb2bc74e818e4f84d28c7ad89f1ba129de4c55f9c779f89961debad931b6ad

Go ahead and attach it to your portfolios; and share your referral codes with me and I will attach yours and then we can run reports.

Hi Rob,

Spent a lot of time figuring out why Windows 10 was so unstable regarding the Testnet installation, and after much searching and installing on another old Window 7 machine .....

The main problem was the Ext on the file names, corrected this problem and now back on track.

In the process I wiped out my Testnet wallet info, could you please send tBBP to:

CPK: ybQiJDpeboUbDQBNZUofFidcj1wgTsXfys

Hi Rob,

Spent a lot of time figuring out why Windows 10 was so unstable regarding the Testnet installation, and after much searching and installing on another old Window 7 machine .....

The main problem was the Ext on the file names, corrected this problem and now back on track.

In the process I wiped out my Testnet wallet info, could you please send tBBP to:

CPK: ybQiJDpeboUbDQBNZUofFidcj1wgTsXfys

Hi Pat,

Ok, I sent 10MM. 
Just so you know yeah the old NFTs are 'owned' by that old wallet but I think what you can do (this would be a great test for us anyway) is you can try to buy those NFTs with your new testnet wallet and see if you re-own them, then change the price a little and see if they update in the marketplace.

Yeah, thats another reason I havent gone to windows 10 yet.  I hear there is some spyware that needs disabled, and, there is a default 'mirror' for app storage that sort of makes everything confusing -- Im sure if you ask another win10 user here what the fix is they can explain.  Im still on 7 myself.

Just so you know when you move to prod, if you have a serious amount of BBP, and for best practices its good to backup your 'wallet.dat' file.  If you lose everything you can move it back and the CPK, NFTs, and BBP will be there.

Rob,

I bought one of the NFT's and it was a success...

It does not show up in the Testnet list of NFT's, and it is gone from the marketplace..

I did back up my real BBP from the core wallet...

Rob,

Tried to send a Card and got this error message...

Rob,

Sorry, the NFT I bought does show up the the List my NFT's, but it has nor appeared in the marketplace yet

The NFT I bought and added different price shows up in the marketplace..