June 2021 Release - Harvest - TestNet Thread

Hi Rob,

Gift card working,...

The problem with the AWS link was when you bought it and but it back into the marketplace, it was  changed from https://videohelp12.s3-us-west-2.amazonaws.com/Best+Prayer+for+Depression.mp4 to
https://videohelp12.s3-us-west-2.amazonaws.com/BestPrayerforDepression.mp4

The plus separating BestPrayerforDepression.mp4 were not there and this caused the problem. I have put it pack in the marketplace.

Mornin folks.

Ok lets try some greeting cards.
Top menue in QT-wallet  Misc.>Send Greeting Card populated the fields and clicked send. Confirmation window popped up with link and said OK.

Verification link for christmas gift card:

Code: [Select]

https://dmprint.s3-us-west-2.amazonaws.com/assets/0cb77405af661d2bb032e10cf9b3e64f2cc9f3f083adac092f8d0e21655f97ee.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210421%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210421T070653Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=4deb94482135027f29e93aebabda09834f39d42dabf3465cfdf148b9fb4ea710
Verificaton for easter gift card:

Code: [Select]

https://dmprint.s3-us-west-2.amazonaws.com/assets/0c8340923aa657529ee0933d20bd0762d4617646c61ee7f890938ea1cc760092.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210421%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210421T071115Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=dc0ec13058e77c44be1aed709c66f972ad4a5de7c46709e007c446d4e45d79aa
Verification for kittens card:

Code: [Select]

https://dmprint.s3-us-west-2.amazonaws.com/assets/9ea657bdb5811f8ca99537048f4b86a1ccbaf26ab288ea541ff8fc0ef14c4243.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210421%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210421T071425Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=8f6c852ae87ee7d76447a02ff80dcd7b40efb0efe4aeef742e2ccdb11fb236f7
So far creating the diffrent cards i encountered no problems, the earlier release i received error but this released seems you fixed it Rob, looking good man.

Gmorning Bro Earlz,

Sweet, thanks for the cards--

So I was able to open all three in my browser, then, I cashed in each of them, and they all seem to have worked.
I have the extra funds now visible in my wallet and it didnt crash and it rescanned and updated the UI properly.

Let me send you one back first (please let Earlz cash this one in, I will send a different one to Pat):

Code: [Select]

https://dmprint.s3-us-west-2.amazonaws.com/assets/0a07fb4384831aca43b11f995e6f835495e8934da0499afbe573bdb1cb06bafd.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210421%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210421T170720Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=9247e24013f045e766d7296a18a2becc669878e5cbfc5c7972598d7c65dfd0ee


Lets hope your system updates with this one this time and hopefully we can move past that bug now!

Optionally remember you can go into coin control after you receive this, and see if the gift is visible and unlocked.  There should be a gift icon on gifts.  On a side note, we also label the address book with the street address it was received from.  If people use this for things other than addresses, we label it with the phrase used.  (IE the email address, or phrase).

Have a good day--
Rob

Heres an Easter Card for Pat:

Code: [Select]


https://dmprint.s3-us-west-2.amazonaws.com/assets/193c6e7a019bf212d3a2a44674d9cbe73807086caaf300e5e6490e2e983a4cb0.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210421%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210421T171252Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=b6c94dfb59f5ecda4088fc752be8f00edbf0c89036328fab8402a7a25abc6225


Pat, to cash it in please type acceptgift then the code in quotes, and see if you can see it in the tx-list and plz see if your balance increased and if its visible in coin control.  I dont know if I told you how to enable coin control.  Settings | Options | Check Enable Coin Control Features.   Then, to get to coin control you click Send Money | Coin Control.  From there you can see your individual coins, UTXO stakes and gifts as individual coins in the wallet.

Hi Rob,

Gift card working,...

The problem with the AWS link was when you bought it and but it back into the marketplace, it was  changed from https://videohelp12.s3-us-west-2.amazonaws.com/Best+Prayer+for+Depression.mp4 to
https://videohelp12.s3-us-west-2.amazonaws.com/BestPrayerforDepression.mp4

The plus separating BestPrayerforDepression.mp4 were not there and this caused the problem. I have put it pack in the marketplace.

Hi Pat,

Ok that is good to know that somehow I am stripping out +'s on repastes.  Ill have to look at how that is happening.

I was asking cause some people have strange security models for AWS files (especially after learning that a hacker downloaded my rapture video 3million times and charged me over $2,500 for it).  So watch out on your hosted files too if they are public.  Thats one of the things Im trying to solve in our next hosted solution, automatic protection.

Looks like the gift worked...

11:14:06
acceptgift "90000 Maple Way"


11:14:12
{
  "Address": "yTPvyLu1kmPGRgWJ5aq7H9GH2DBr161jdu",
  "importprivkey": null,
  "Your wallet will now rescan to reflect the gift balance!": true
}

Evenin.

Indeed just like for Pat it worked just fine for me aswell.
The rescan worked well no errors or anything.

The transaction details i didnt see strait away, but then i did just reboot of core wallet and i saw the transaction there in the tx list no problemas.


I Think tomorrow morning i will try and liquidate one of the long term tBBP stake that i did today , will be intresting to see the penalty for it.

Looks like the gift worked...

11:14:06
acceptgift "90000 Maple Way"


11:14:12
{
  "Address": "yTPvyLu1kmPGRgWJ5aq7H9GH2DBr161jdu",
  "importprivkey": null,
  "Your wallet will now rescan to reflect the gift balance!": true
}

Good, but just to double check, were you able to see the tx in the txlist and that your balance increased?

Also, will you please look into the coin-control part also:
https://forum.biblepay.org/index.php?topic=762.msg10749#msg10749

Thanks Pat.

Yes Rob,

I see that the balance increased...and the Coin Select....Amount Fee...After Fee...etc

Yes Rob,

I see that the balance increased...and the Coin Select....Amount Fee...After Fee...etc

Thats good; and in List mode you can see an icon of a gift (looks like a present) etc.  This is the screen that will show your UTXO stake status for each stake also.

Today I got the greeting card system ready for both dry run and real mode.  Another words when we are ready to turn it on in prod, we should theoretically be able to send a real gift card to a home address and it will charge the correct fee.  (Those code changes can wait til our next test release though-- I tested them locally and it worked).

Im going to review the orphan NFTs next and invite cameroon one in.

We still need to test referrals and high yield stakes.

Chainlocks and LLMQs appear to be working fine.
Btw, Earlz I think your sanc is down could you do the exec revivesanc sancname and see if it goes back to 700?

Hello Rob.

Yeah i will get the sanc up again asap. I have open support ticket at torguard, lets see how fast they fix it for me.  If they have to change my dedicated ip then well worst case i have to make new sanctuary i suppose.
Should go easier now when i kinda know procedure so to say.

I tried to send a highriskstake to my normal test wallet adress but i received 2 diffrent popup errors from it, i will redo highriskstake and see if i can  liquidate early.

 

Hello Rob.

Yeah i will get the sanc up again asap. I have open support ticket at torguard, lets see how fast they fix it for me.  If they have to change my dedicated ip then well worst case i have to make new sanctuary i suppose.
Should go easier now when i kinda know procedure so to say.

I tried to send a highriskstake to my normal test wallet adress but i received 2 diffrent popup errors from it, i will redo highriskstake and see if i can  liquidate early.

Hi Earlz,

Btw, just so you know, when you type our 'exec revivesanc sancname' command we not only send the proreg update_service command (to unpose ban a sanc) but we also send the params that allow the change of IP and/or port (similar to if you changed hosts).  So to accomplish that all you have to do is edit your deterministic.conf first, change the ip or port, then run the revivesanc.  That should change the IP *and* unpose all at the same time.  Ive moved a few of my sancs in prod this way to preserve the POOS orphan public key BIO.

10-4 on the highriskstake, let me know if the amount was roughly correct.  I think we should cap the penalty at 50% in the next release to create a propensity for people to 'get out early' and not give us a black eye, etc.  It also provides some revenue for the high risk pool.  Im sort of leaning against the super long duration stakes, I think maybe we should leave the curve at 2 years for now.  The reason why is I made a time-of-money chart,and I feel if we offer the super long term stakes we risk spending too much on interest expenses which might make us look like we have slightly less integrity.  We can revisit those super long ones later after we see the effects of referral codes and highrisk stakes in prod (maybe under a different design for example).

I need to add the CPK, nickname, and portfolio size to the 'listattachedreferralcodes' rpc also so we can see who we attached to.  This will provide more transparency so people can audit the entire system etc and know that we arent wasting more than a few percent on referral code emissions etc.  And also that no one is getting a disproportionate size of referral code revenue.

Hi Earlz,

Btw, just so you know, when you type our 'exec revivesanc sancname' command we not only send the proreg update_service command (to unpose ban a sanc) but we also send the params that allow the change of IP and/or port (similar to if you changed hosts).  So to accomplish that all you have to do is edit your deterministic.conf first, change the ip or port, then run the revivesanc.  That should change the IP *and* unpose all at the same time.  Ive moved a few of my sancs in prod this way to preserve the POOS orphan public key BIO.

10-4 on the highriskstake, let me know if the amount was roughly correct.  I think we should cap the penalty at 50% in the next release to create a propensity for people to 'get out early' and not give us a black eye, etc.  It also provides some revenue for the high risk pool.  Im sort of leaning against the super long duration stakes, I think maybe we should leave the curve at 2 years for now.  The reason why is I made a time-of-money chart,and I feel if we offer the super long term stakes we risk spending too much on interest expenses which might make us look like we have slightly less integrity.  We can revisit those super long ones later after we see the effects of referral codes and highrisk stakes in prod (maybe under a different design for example).

I need to add the CPK, nickname, and portfolio size to the 'listattachedreferralcodes' rpc also so we can see who we attached to.  This will provide more transparency so people can audit the entire system etc and know that we arent wasting more than a few percent on referral code emissions etc.  And also that no one is getting a disproportionate size of referral code revenue.

Cheers Rob.
Thats some sweet information.
Yeah im thinking if i keep having trouble with this particular IP  then i will ask them to change to some other static ip.
Anyways i revived the sanctuary and it looks like it was a success , also booted up the VM with the sanc and it looks fine over there.

Alright let me see if i can get some highriskstaking done.

Hello Rob.

I ran this command in console/terminal :

Code: [Select]

20:57:36
highriskbbpstake


20:57:36
You must specify highriskbbpstake minimum_bbp_amount commitment_days 0=dry_run/1=real (code -1)

I noticed 

minimum_bbp_amount commitment_days 0=dry_run/1=real

Should be switched right, like this: highriskbbpstake bbp_amount 1 duration_in_days

Hello Rob.

I ran this command in console/terminal :

Code: [Select]

20:57:36
highriskbbpstake


20:57:36
You must specify highriskbbpstake minimum_bbp_amount commitment_days 0=dry_run/1=real (code -1)

I noticed  Should be switched right, like this: highriskbbpstake bbp_amount 1 duration_in_days

Hey bro,

Good catch; Yeah I noticed that myself yesterday and fixed the code; will get it out soon!

Got a nice (imho) thing coming that God led us to:  Invoices and Statement and Payments!

Trying to get that in so we can do some testing on these things also.