Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - earlzmoade

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 ... 21
91
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.


92
Mornin folks.

Quote
1.6.1.3-Leisure Upgrade

- Ensure Virtual Gift card is created successfully while being embedded into the rendered text.
- Encrypt Hi-Qual URL of each NFT.


Alright this version fixes the 'invalid data' error, please try again.

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.


93
Evenin Brother Rob.

For sure i will do some testing tomorrow morning.
ill do some bbp-only stake tomorrow then do your test scenario there with the notepad and all.

Yeah the NFT encryption there for the high quality urls sounds like a good plan.

talk to you later.

94
Quote
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.

Okay so first went for a dry run,

ran command:
Code: [Select]
highriskstake min_bbp_amount foreign_currency_address foreign_currency_amount commitment_duration_in_days 0
looked good so then ran command:
Code: [Select]
highriskstake min_bbp_amount foreign_currency_address foreign_currency_amount commitment_duration_in_days 1
Wallet used was Ledger live with nano s for foreign currency.

Looks good to me Rob, first i did a dryrun but without bankroll and i saw over 9M console wanted to spend so i did a
Code: [Select]
bankroll 1 6100000and it took that amount instead.

Dryrun output:

Code: [Select]
12:01:04
highriskstake 6000000  0x95Dc21040641BfEC3a9CC641047F154bc0bf10D0 1.0093154 90 0


12:01:05
{
  "BBP UTXO": "bfcb4630d9e75ecec8fe34770e4ee489d12b1dd56c3ba2c2664a365fca221b38-11",
  "BBP Address": "yhFqES1X7kY4nSxnLgieZTE3ytCBL3yWrx",
  "BBP Amount": 6100000.001,
  "Foreign Symbol": "ETH",
  "Foreign Amount": 1.0093154,
  "Foreign UTXO": "6716ec6325d1e29c77c129666692e9d053fb795551d2a9f3c951b6c2f445f60b",
  "Foreign Ordinal": 0,
  "Foreign Value USD": 2134.680150815593,
  "BBP Value USD": 4924.473033761291,
  "DWU": 507.4626865671642,
  "!WARNING!": "When you promise to lock for 90 days for a high yield reward,  you hereby AGREE that you may be PENALIZED by 200% of the TOTAL reward if you spend your UTXO early.   If you do not fulfill your obligation, your original UTXO will have burn fees deducted from it.   EXAMPLE:  You have a 100,000 BBP coin.  You lock it for 90 days for a 60% DWU.  On the 15th day you try to spend the coin (breaking your obligation).   You will be penalized 60%*2=120% of your original UTXO, which is MORE THAN THE ORIGINAL VALUE.  Due to our 90% cap, we will charge you a 90% BURN FEE to spend the coin.  (If you do not agree please use our conservative staking feature.)  Thank you for using BIBLEPAY.  ",
  "Foreign Address": "0x95Dc21040641BfEC3a9CC641047F154bc0bf10D0",
  "Pin": 93154,
  "pin_valid": true,
  "Error": "",
  "Dry Run Mode": true
}

Then i ran it live for testnet:

Code: [Select]
12:05:32
highriskstake 6000000  0x95Dc21040641BfEC3a9CC641047F154bc0bf10D0 1.0093154 90 1


12:05:34
{
  "BBP UTXO": "bfcb4630d9e75ecec8fe34770e4ee489d12b1dd56c3ba2c2664a365fca221b38-11",
  "BBP Address": "yhFqES1X7kY4nSxnLgieZTE3ytCBL3yWrx",
  "BBP Amount": 6100000.001,
  "Foreign Symbol": "ETH",
  "Foreign Amount": 1.0093154,
  "Foreign UTXO": "6716ec6325d1e29c77c129666692e9d053fb795551d2a9f3c951b6c2f445f60b",
  "Foreign Ordinal": 0,
  "Foreign Value USD": 2134.680150815593,
  "BBP Value USD": 4924.473033761291,
  "DWU": 507.4626865671642,
  "!WARNING!": "When you promise to lock for 90 days for a high yield reward,  you hereby AGREE that you may be PENALIZED by 200% of the TOTAL reward if you spend your UTXO early.   If you do not fulfill your obligation, your original UTXO will have burn fees deducted from it.   EXAMPLE:  You have a 100,000 BBP coin.  You lock it for 90 days for a 60% DWU.  On the 15th day you try to spend the coin (breaking your obligation).   You will be penalized 60%*2=120% of your original UTXO, which is MORE THAN THE ORIGINAL VALUE.  Due to our 90% cap, we will charge you a 90% BURN FEE to spend the coin.  (If you do not agree please use our conservative staking feature.)  Thank you for using BIBLEPAY.  ",
  "Foreign Address": "0x95Dc21040641BfEC3a9CC641047F154bc0bf10D0",
  "Pin": 93154,
  "pin_valid": true,
  "Error": "",
  "Foreign Ticker": "ETH",
  "UTXO Value": 5416.352621472399,
  "Results": "The UTXO Stake Contract was created successfully.  Thank you for using BIBLEPAY. ",
  "TXID": "41cf648c82b51b8c7538f90c829574378cad82b62ad2a38a715fc11ab813bfe0"
}


Looks ok to me.



95
1.6.1.2c-Leisure Upgrade

- Add Christmas, Easter and Kittens Greeting cards.  Make the greeting card fields customizable by the user.  Theoretically fix the crash during 'acceptgift', and the UI balance refresh.



Ok, so now we have 3 types of Greeting cards.
Will you guys please create a couple new ones and paste here, and I will try a new import, and respond with a card back to you.

Ill be sure to add CSV card generation in the next few weeks.

Mornin.
So i did the normal routine menue misc , send greeting card, populated the fields. Then when i click send i get up this new window saying : Mail delivery result: Invalid Adress Data.
First i thought maybe i put in wrong adress, so i tested Another then yet Another but changed from christmas to easter one.
Also i noticed that the transactions goes  thru. Atleast i can see them in the transactions details.


Im sending with some transaction details below and some log information.

log:
Code: [Select]
UnlockGift::VecSz 303
UnlockGift1::AmtGift 10347.153700 for yMYadWmegDUzwQnHpGRcFpoEcT3JGBpc1J
UnlockGift1::AmtGift 61425.153700 for ydXRG5gwcx3518UeF372omZBEhmgpNxLpdkeypool reserve 119
2021-04-20 07:55:22 keypool keep 119
2021-04-20 07:56:12 CalculateAPM::Result==1.000000::LastHeight 80585 Price 0.010000000000, Current Price 0.010000000000
We already have this key 7198BishopAve.
UnlockGift::VecSz 300
UnlockGift1::AmtGift 10347.153700 for yMYadWmegDUzwQnHpGRcFpoEcT3JGBpc1J
UnlockGift1::AmtGift 61425.153700 for ydXRG5gwcx3518UeF372omZBEhmgpNxLpd
UnlockGift1::AmtGift 24744.153700 for yegvdSDZt5cxihZgRCt9gVvWmhgGrsX5mJ
UnlockGift1::AmtAddrGift 24744.153700 for yegvdSDZt5cxihZgRCt9gVvWmhgGrsX5mJ
UnlockGift::Unlocking 24744.153700 for yegvdSDZt5cxihZgRCt9gVvWmhgGrsX5mJkeypool added 1 keys (0 internal), size=1000 (0 internal)
2021-04-20 07:56:32 init message: Loading wallet... (111.79 %)
2021-04-20 07:56:32 keypool reserve 120
2021-04-20 07:56:32 keypool keep 120
2021-04-20 07:57:16 CalculateAPM::Result==1.000000::LastHeight 80585 Price 0.010000000000, Current Price 0.010000000000
UnlockGift::VecSz 298
UnlockGift1::AmtGift 24744.153700 for yegvdSDZt5cxihZgRCt9gVvWmhgGrsX5mJ
UnlockGift1::AmtGift 10347.153700 for yMYadWmegDUzwQnHpGRcFpoEcT3JGBpc1J
UnlockGift1::AmtGift 61425.153700 for ydXRG5gwcx3518UeF372omZBEhmgpNxLpd
UnlockGift1::AmtGift 24744.153700 for yegvdSDZt5cxihZgRCt9gVvWmhgGrsX5mJkeypool added 1 keys (0 internal), size=1000 (0 internal)
2021-04-20 07:58:08 init message: Loading wallet... (111.89 %)
2021-04-20 07:58:08 keypool reserve 121
2021-04-20 07:58:08 keypool keep 121

Transaction details first 1:

Code: [Select]
Status: 2 confirmations, locked via ChainLocks
Date: 2021-04-20 09:55
Total debit: -24 744.15370000 tBBP
Total credit: 24 744.15370000 tBBP
Transaction fee: -0.18675000 tBBP
Net amount: -0.18675000 tBBP
Transaction ID: 75b14b57b4c85086143d601d9f9e55c106d86b04cfb25f0364fbcecd7e9b7d0c
Output index: 0
Transaction total size: 745 bytes

Height: 80742
Difficulty: 0.00
Time: 04-20-2021 08:05:03
Subsidy: 7611.3509

Second :

Code: [Select]
Status: 2 confirmations, locked via ChainLocks
Date: 2021-04-20 09:56
Total debit: -24 744.15370000 tBBP
Total credit: 24 744.15370000 tBBP
Transaction fee: -0.14975000 tBBP
Net amount: -0.14975000 tBBP
Transaction ID: d394b89d16f4e13003f918d5b95f3b4e85b6456be926ca3ea33cbf49ca6f78ce
Output index: 0
Transaction total size: 598 bytes

Height: 80742
Difficulty: 0.00
Time: 04-20-2021 08:05:03
Subsidy: 7611.3509

Third:

Code: [Select]
Status: 2 confirmations, locked via ChainLocks
Date: 2021-04-20 09:58
Total debit: -24 744.15370000 tBBP
Total credit: 24 744.15370000 tBBP
Transaction fee: -0.14125000 tBBP
Net amount: -0.14125000 tBBP
Transaction ID: 1c90d4e5d9d2acefd2c1750f8055a31333f18491e2723547e15cc83e3724a4b8
Output index: 0
Transaction total size: 565 bytes

Height: 80742
Difficulty: 0.00
Time: 04-20-2021 08:05:03
Subsidy: 7611.3509

Ofcourse this on Windows 10.

Well i will leave this as is for now  and im gonna try out the staking feature.

96
Mornin.

Aye  will try this time with the quotes still there and see what happends.

Opened console window and ran :
Code: [Select]
10:26:53
acceptgift  "1009 Swiss Cheese Ave."


10:27:23
{
  "Address": "ydXRG5gwcx3518UeF372omZBEhmgpNxLpd",
  "Note": "Your wallet will now rescan to reflect the gift balance!"
}

Wallet did not crash this time , but i didnt receive any funds either.
Should i try a rescan blockchain files?

Update:
Pretty strange, i rebooted qt-wallet  and now i see the missing transaction. Also its dated from yesterday , well i send with transaction details for you.

Code: [Select]
Status: 273 confirmations
Date: 2021-04-18 15:54
From: unknown
To: ydXRG5gwcx3518UeF372omZBEhmgpNxLpd (own address, label: 1009SwissCheeseAve.)
Credit: 42 847.00000001 tBBP
Net amount: +42 847.00000001 tBBP
Transaction ID: 0553b0da464d07ee273189449554e318d07094efaff3fa25585f317bde470511
Output index: 1
Transaction total size: 972 bytes

Height: 80140
Difficulty: 0.00
Time: 04-18-2021 13:54:55
Subsidy: 7611.1169

Debit: -18 578.15369999 tBBP
Credit: 61 425.15370000 tBBP
To: ydXRG5gwcx3518UeF372omZBEhmgpNxLpd 61425.0000 BIBLEPAY


Anyways im thinking im gonna try do one of these high return long utxo stake that i saw you wrote about earlier, i will keep you posted on that aswell.

97
Evenin Brother Rob.

Yeah the giftcard is a pretty sweet feature, like you say, potentially more usecases.
I like it alot.

On to the test case:

So i wrote in terminal :
Code: [Select]
acceptgift 1009 Swiss Cheese Ave.
it worked, got up a new window saying something like "rescanning"  , then disaster followed. My biblepay-qt wallet crashed so i restarted qt wallet  and i dont see any new funds in my accout, so i figure it was probably crash Before rescan complete and all. 

Here is information from debug.log

Code: [Select]
UnlockGift::VecSz 129
UnlockGift1::AmtGift 10347.153700 for yMYadWmegDUzwQnHpGRcFpoEcT3JGBpc1J
AcquireWallets::GetWallets size=1, acquired=1RescanFromTime: Rescanning last 80203 blocks
2021-04-18 18:38:05 CalculateAPM::Result==1.000000::LastHeight 80175 Price 0.010000000000, Current Price 0.010000000000Windows Exception: EXCEPTION_ACCESS_VIOLATION
No debug information available for stacktrace. You should add debug information and then run:
biblepay-qt.exe -printcrashinfo=cfbgsytmmvigc6kdojqxg2cjnztg6aiab5rgsytmmvygc6jnof2c4zlymuwvo2lomrxxo4zaiv4ggzlqoruw63r2ebcvqq2fkbkest2ol5augq2fknjv6vsjj5gecvcjj5hbbjh35yaaaaaaadp2b2aaaaaaaagz3jeaaaaaaaacawcmaaaaaaaa5opucaiaaaaabf2ljqaaaaaaabwk4qibaaaaaagrbl7aaaaaaaapu576aaaaaaaadu5egaiaaaaaammgimaqaaaaabg2hgqbaaaaaac3yjmacaaaaaab2xcbaaaaaaaacjlecaaaaaaaa252laaqaaaaaaaa====
2021-04-18 18:38:53

Btw my tnet sanctuary  is offline because my VPN provider are doing something on my dedicated ip again, lets hope they get it together and fix my connection issues once and for all.

98
Mornin.

Yeah i see what you ment about bouyout price was not populated, checked NFTs>edit and yeah i said 0   on buyout price so seems i missed that one.
Should now be updated.
Code: [Select]
Status: 1 confirmations, locked via ChainLocks
Date: 2021-04-18 10:45
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -100.00000000 tBBP
Transaction fee: -0.31500000 tBBP
Net amount: -100.31500000 tBBP
Transaction ID: 648941b866bf6e5ab1542ea2ac40d74b18ea4d3516921b2024033dce48dac3c3
Output index: 0
Transaction total size: 1260 bytes

Height: 80065
Difficulty: 0.00
Time: 04-18-2021 08:45:15
Subsidy: 7611.1882

Debit: -637.49818176 tBBP
Credit: 537.18318176 tBBP
To: yi5c1NGPCVSDogzGzWyQ5TZe8B1ewU9BHE 537.0000 BIBLEPAY

Lookin at the NFT Browser i discovered something intresting.
I changed the buyout price to 1125 tBBP  but i see now when look at the NFT browser that there already was a bid for 2222 tBBP  , perhaps could add like Warning popup in NFT edits "Warning: You are trying to set lower buyout price then current highbid etc etc" 

Just a idea i had.

Ok let me update BBP core wallet  and send you a new postcard.

As Before Went into  core wallet top menue>Misc.>Send Greeting Card

Populated the fields and link  below:
https://dmprint.s3-us-west-2.amazonaws.com/assets/177b033bfdcc1a8704e2748911e16cf243caeeeb2cb50d45542a903967724b49.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210418%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210418T090138Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=7537e5b4bd99f47ac1ed4eca0a4f6452592434a44674e320afa2dbfdf7cbf5f7

Transaction details below:
Code: [Select]
Status: 2 confirmations, locked via ChainLocks
Date: 2021-04-18 11:01
Total debit: -18 578.15369999 tBBP
Total credit: 18 578.15369999 tBBP
Transaction fee: -0.13825000 tBBP
Net amount: -0.13825000 tBBP
Transaction ID: cedf9ad0991f8a69f8d19cd44c1ce78a15510b4ce326159f3b71e87488ca297e
Output index: 0
Transaction total size: 552 bytes

Height: 80069
Difficulty: 0.00
Time: 04-18-2021 09:02:34
Subsidy: 7611.0114

Debit: -7605.38215503 tBBP
Debit: -4552.43905000 tBBP
Debit: -7605.35265503 tBBP
Credit: 1184.88191007 tBBP
To: yZg81G9f45xyuVwgS4PthuZ2QQBZZDmEAC 1184.0000 BIBLEPAY
Credit: 18 578.15369999 tBBP
To: yZp18xG7c4jjndmSRDDLuN8DJGMupihXAR 18578.0000 BIBLEPAY

Transaction:
CTransaction(hash=cedf9ad099, ver=2, type=0, vin.size=3, vout.size=2, nLockTime=80067, vExtraPayload.size=0)
    CTxIn(COutPoint(002466087a7a97992fec2122301f8e0b56a81f8c5d88c6cf0c124bd7bbb89347, 1), scriptSig=483045022100daae6890512b, nSequence=4294967294)
    CTxIn(COutPoint(5f43649cc1b3eb16542d4144cfcedb8d92d576ef79fd0b8167c2ffe418d84eee, 1), scriptSig=47304402200bb2d41899b6c3, nSequence=4294967294)
    CTxIn(COutPoint(750dd8e8f671d97509c38605876dd46e0dbd78aefa6887d439802959949db5ff, 1), scriptSig=4830450221009bd288411c9b, nSequence=4294967294)
    CTxOut(nValue=1184.88191007, scriptPubKey=76a9149282a3eefb0ca37b55cacd4f)
    CTxOut(nValue=18578.15369999, scriptPubKey=76a91494003c46b5ad9a89f6f73b6e)

99
Evenin Brother Rob.

I just used imgur because was just first hosting site i could think of,  im back home from workshop so i cant check statuses but i was sure i edited the winter deer ones to have buyout price aswell.

Cant say for certain i might have missed that one. But i believe i edited Pats p1, p2, p3  best prayer for depression  to have buyout aswell.
Ill check tomorrow morning and get back to you.

100
Quote
Test case for Christmas Card:

First read this:
https://wiki.biblepay.org/Direct_Mail_Delivery

1.  From the command line, save your home address information using the "Setup Environment" instructions (exec setmyaddress).
2.  Create a card with "exec testmail" with dry run set to 0 and biblepay gift card amount set to 0.
3.  Verify you receive the "PDF" link. 
4.  Open the link in a browser and verify all the info in the From, all the info in the To, and the extra paragraph added in step 2.


Separate test case for BiblePay gift cards:

1.  Re-do another dry run for a new Christmas card, but set the USD amount to be above 0 (IE 5.00 for example).
2.  Verify the wallet sent out the correct amount of BBP by comparing it to the actual gift card and our value.
3.  Note the passphrase that biblepay core included in the Proof PDF. 
4.  For this test, lets not unlock the passphrase for yourself, lets do one to each other.  Can one of you paste your passphrase in testnet and Ill try to claim it?
Then I will do a test too and send you my passphrase and see if you can open it.

EDIT: To get to the biblepay rpc console, click Tools | Console.  Then you can enter these advanced commands from there.


Okay, warming up with the gift card test case.
In core wallet top menue, navigated to : Misc>Send Greeting Card
Then i populated the fields and set out test christmas card, link below:

https://dmprint.s3-us-west-2.amazonaws.com/assets/6a608a92468b6c5e2ba26176eb8990a6778301b8193f7f1a2effabade549af61.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210417%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210417T180930Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=4353bde2cf5cf2f7548c8b682033d16e1e388015e3c98541854802563452ba38

Heres transaction details:
Code: [Select]
Status: 17 confirmations, locked via ChainLocks
Date: 2021-04-17 20:09
Total debit: 0.00000000 tBBP
Total credit: 0.00000000 tBBP
Transaction fee: -0.06425000 tBBP
Net amount: -0.06425000 tBBP
Transaction ID: 61e3d66e7764e0a9e34a7ec3bd6732b00281d90d9788f78092e8f83ea73017c4
Output index: 0
Transaction total size: 256 bytes

Height: 79856
Difficulty: 0.00
Time: 04-17-2021 18:16:13
Subsidy: 7806.1137

Debit: -15 000.00000000 tBBP
Credit: 4652.78205000 tBBP
To: yWxHrHhJE5bNyk5y8quCErNrxcsH7Gf7Jx 4652.0000 BIBLEPAY
Credit: 10 347.15370000 tBBP
To: yMYadWmegDUzwQnHpGRcFpoEcT3JGBpc1J 10347.0000 BIBLEPAY

Went smooth as far as i can tell.

Next test case i figure i do the NFTs one :

Quote
NFT (Non Fungible Tokens) Test cases:

NFT Add:
- Create a brand new NFT by going to "NFTs | NFT Add".  Fill in the fields.  For the type be sure to select digital good.  For the URL, choose the final URL of the product-good-service you are selling a copy of (or the original of).  Side Note we will need to address copyright laws - most likely with a process to blacklist non-verified owners or plagiarizers etc.  Also on another side note, I would like to add a 'private encrypted URL' that can be deciphered when the item is purchased - this would be useful for us to render a low quality version of a product and/or a demo URL (for binaries), but when purchased, the user receives the high-quality asset URL.  Save the new NFT.  (We hash the NFT by its distinct URL so no two can exist that are the same).
- After a few blocks verify you can see the NFT in the NFT list (NFTs | List NFTs).
Also, verify you can see the NFT in the marketplace:
Goods:
https://foundation.biblepay.org/NFTBrowse

- Edit the NFT.  Verify you can change the marketable status, and the minimum offer price.
- View the NFT in the marketplace.  Verify you can see it.
- Buy the NFT in the marketplace.  Verify you receive the NFT in your NFT list.  For this test, buy one that you did NOT create, and let us buy one that you created so we can cross check the buy operation from each other.

Let us know if we have any serious considerations to fix, etc.

EDIT:  I think one way we can establish the 'private encrypted URL for a high-quality deliverable' is to add the HQ URL (or final deliverable URL) field to NFT create, and what we can do is RSA-encrypt it with the public key of the marketplace.  This means that the marketplace can decrypt the HQ url for the buyer upon a buy.  Yet, all other BBP users cannot decrypt it.

Quote
Btw, could everyone who created NFTs also Edit them and populate the "Buy it now" price?  It is a new field.

I edited the old NFTs  so they all now have buy-it now price set.
Also created a new one that has all of them set.
Can also say that i deleted 1 nft and i dont see it in the list anymore so.

101
Gooday.

Yeah i see the sanctuary list on the home qt wallet , your 3 plus mine, no problems.
Quote
Thats great you could buy the depression; I have it where it doesnt actually debit your pool balance for the buy yet; but it does do a real purchase using the tBBP funds from the pool.

Aha yeah then thers no problem i suppose.

Quote
Does Pats NFTs show up in your Owned NFT list now?  If so you can edit them to make them remarketable if you want (IE to resale them to us) so we see them again.

Yeah  i see all my nfts in the NFTs>List My NFTs i also checked in the terminal/Console : listnfts 1 1   and i see them there aswell.

Aye will edit and enable them in the Marketplace again.

Heres the magnet link for the picture, but i suppose you need a torrent program for the p2p sharing from me to you.

Code: [Select]
magnet:?xt=urn:btih:cl4bsk54ys2hyihfp2k5s7ksusj357n3&dn=winterland.Deer.jpg&xl=3128938&fc=1
its just a normal jpg picture but just figure would be cool to see if it worked to create a magnet link in the nfts section.
I believe Ubuntu has Transmission as standard torrent p2p program and its lightweight and no stupid ads in it either.





102
NFT (Non Fungible Tokens) Test cases:

NFT Add:
- Create a brand new NFT by going to "NFTs | NFT Add".  Fill in the fields.  For the type be sure to select digital good.  For the URL, choose the final URL of the product-good-service you are selling a copy of (or the original of).  Side Note we will need to address copyright laws - most likely with a process to blacklist non-verified owners or plagiarizers etc.  Also on another side note, I would like to add a 'private encrypted URL' that can be deciphered when the item is purchased - this would be useful for us to render a low quality version of a product and/or a demo URL (for binaries), but when purchased, the user receives the high-quality asset URL.  Save the new NFT.  (We hash the NFT by its distinct URL so no two can exist that are the same).
- After a few blocks verify you can see the NFT in the NFT list (NFTs | List NFTs).
Also, verify you can see the NFT in the marketplace:
Goods:
https://foundation.biblepay.org/NFTBrowse

- Edit the NFT.  Verify you can change the marketable status, and the minimum offer price.
- View the NFT in the marketplace.  Verify you can see it.
- Buy the NFT in the marketplace.  Verify you receive the NFT in your NFT list.  For this test, buy one that you did NOT create, and let us buy one that you created so we can cross check the buy operation from each other.

Let us know if we have any serious considerations to fix, etc.

EDIT:  I think one way we can establish the 'private encrypted URL for a high-quality deliverable' is to add the HQ URL (or final deliverable URL) field to NFT create, and what we can do is RSA-encrypt it with the public key of the marketplace.  This means that the marketplace can decrypt the HQ url for the buyer upon a buy.  Yet, all other BBP users cannot decrypt it.

Quote
- Edit the NFT.  Verify you can change the marketable status, and the minimum offer price.
I created a NFT yesterday and bought it myself and i saw in transactions it was success.
Code: [Select]
Status: 210 confirmations, locked via ChainLocks
Date: 2021-04-16 21:30
From: unknown
To: yhFqES1X7kY4nSxnLgieZTE3ytCBL3yWrx (own address, label: CHRISTIAN-PUBLIC-KEY)
Credit: 15 000.00000000 tBBP
Net amount: +15 000.00000000 tBBP
Transaction ID: e3f2dd502a9640d8ad3cfbf1480f5afbc97303c8ba6c1be4189a905e010fb3bf
Output index: 1
Transaction total size: 1519 bytes

Today i edited same nft , it worked, confirmation window and all and it should be up in Marketplace again. All this was on windows 10, core wallet version 1.6.0.9.
Also i bought Pats  p1,p2,p3 about depression, but i dont think i "payed" anything for them..Atleast i dont see any transactions in core wallet for them.

103
1.6.1.0-Leisure Upgrade for testnet

- Coin Control: Display gift icon when it is a gift
- Auto unlock the gift if they 'acceptgift', lock gifts on wallet boot by default (this prevents gifts from being spent by the giver).  Add gift key to givers wallet so they can recall the gift if it is never redeemed.




Hi Guys--

Can we please try a new gift card for each of you?

This new release shows a "locked gift icon" in coin control once you create the gift.  It stays locked so that you dont spend it and it dissapears if the recipient redeems it.

Ill explain the rest when I redeem one of yours.

Thanks.

I noticed download windows link for testnet  still 1.6.0.9

For sure will try and send a new gift card once i have new version installed.
btw Rob, if i want to check the status of the masternode to for example see if block height same as the other masternodes in testnet, any useful commands  that i could use?

currently i have diffrent commands i have tried out  for various diffrent outputs
like: ./biblepay-cli masternode status , ./biblepay-cli -getinfo , ./mnsync status


104
Quote
I have a question though on the Honey Creek delivery.  When I type
14:13:46
acceptgift "21 Honey Creek Street"


14:13:46
{
  "Address": "yhYFfPdVaxDTCyuzWboHvm8BBb2GNwg4bd",
  "Note": "Your wallet will now rescan to reflect the gift balance!",
  "Accept": null
}

I see an address of yhYFf*.  The one you pasted above I think might be for the Older test; did the Honey Creek transaction send to the above address?  if you want can you paste that destination transaction for the Honey creek card?

Ill word on locking in the mean time.

Evenin.

I Think that adress is for the honey crek card, hmm let me post the gsc transmission.

Code: [Select]
Status: 23 confirmations, locked via ChainLocks
Date: 2021-04-16 20:05
Total debit: 0.00000000 tBBP
Total credit: 0.00000000 tBBP
Transaction fee: -0.10100000 tBBP
Net amount: -0.10100000 tBBP
Transaction ID: 0ab27651d5d33b005c6bb1e973acb0f21bbefebfc78829b3649902efcf842702
Output index: 0
Transaction total size: 404 bytes

Height: 79509
Difficulty: 0.00
Time: 04-16-2021 18:05:56
Subsidy: 7806.1504

Debit: -6289.66688210 tBBP
Debit: -1196.97674000 tBBP
Credit: 1138.95068176 tBBP
To: ybwXJMQUEdMsQ9WKdTcQuepaYBT2d9EmAP 1138.0000 BIBLEPAY
Credit: 6347.59194034 tBBP
To: yhYFfPdVaxDTCyuzWboHvm8BBb2GNwg4bd 6347.0000 BIBLEPAY

Transaction:
CTransaction(hash=0ab27651d5, ver=2, type=0, vin.size=2, vout.size=2, nLockTime=79508, vExtraPayload.size=0)
    CTxIn(COutPoint(82cc96d985d0a880fc4378814d829b6db4548372e55c3267df3c302381d75faa, 0), scriptSig=483045022100d40d8a6ebca7, nSequence=4294967294)
    CTxIn(COutPoint(fdfd52c494f18874770b63c1988b7ea38297fb55161f2a7e01d4d24b43b45e1c, 0), scriptSig=4830450221008197bd4dd381, nSequence=4294967294)
    CTxOut(nValue=1138.95068176, scriptPubKey=76a914ab5c93a70693bf06fdf99aba)
    CTxOut(nValue=6347.59194034, scriptPubKey=76a914e8c6b604fa142b5d2ca7f76a)

105
1.6.0.9-Leisure Upgrade for TestNet

- Greeting Card:  Make Proof link bigger and pink
- Sanitize virtual gift card passphrases
- UTXO:  Add UTXO type (High risk or Conservative), Modify listutxostakes to actually be JSON
- Raise BBP block fees from dust levels to small levels (they were at dust in testnet, should be more like 1 bbp per 1K of size now - similar to prod) but providing an incentive for our miners as subsidies decrease over time
- Add tier2 payment for non POOS sancs (not active yet).  This gives tier2 a 250bbp reward to run a sanc that does not sponsor an orphan, simply for network stability.
- Recaption Duffs to Pence (This gives a name to our microcoins)
- Add better verbiage when unlocking a high-yield stake
- Modify coin control to include a nice 3 facet icon for: 1) A normal coin that is Locked/Unlocked is a normal Lock, 2) A conservative UTXO that is locked has a hard-disk plate on it in Red (or white if locked), 3) A high-yield UTXO that is locked has a chain on it and is red, a high-yield UTXO that is FULFILLED turns into a Holy Spirit Dove, a high yield Unlocked/Fulfilled turns to a Green dove.  This signifies : If it is High Yield and NOT fulfilled, it has the Chain on the lock meaning you dont want to touch it.  If it is high yield and fulfilled, it has the Dove.

Sweet.

Alright so i redid the send greeting card, i noticed the bigger text for the verification link and the diffrent colour ofcourse.  Here is link to new card i set up :  https://dmprint.s3-us-west-2.amazonaws.com/assets/353a83ae62054ded19864e9614812b3f30ff00cb04b21c64b963d5df88c0a6ec.pdf?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2GKFO2GYKMXXMHQ%2F20210416%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20210416T180544Z&X-Amz-SignedHeaders=host&X-Amz-Expires=518400&X-Amz-Signature=ebf577ed70b2e4b6214d72c08aeb3fc3553bd45cc1212d57f078dc3e37388b49


I noticed that the last christmas card were debited twice if im not mistaken.
Hmm ill send with the information if you can make something out of it.

Code: [Select]
Status: 58 confirmations, locked via ChainLocks
Date: 2021-04-16 16:15
To: yYkEWzAaADwjMQeaZ2etUGxg9PJ2nagfi3
Debit: -9322.42856796 tBBP
Transaction fee: -0.32486000 tBBP
Net amount: -9322.75342796 tBBP
Transaction ID: facf769977558ae2ccd08217b8c7108bf27b7790e951da9a52c815717125e8d9
Output index: 1
Transaction total size: 32374 bytes

Height: 79454
Difficulty: 0.00
Time: 04-16-2021 14:18:54
Subsidy: 7806.3743

Then the second:

Code: [Select]
Status: 57 confirmations, locked via ChainLocks
Date: 2021-04-16 16:19
To: ygefa1gXn8KEhfq6dNYMH7cC7CL1EvV6c2
Debit: -9322.42856796 tBBP
Transaction fee: -0.00336000 tBBP
Net amount: -9322.43192796 tBBP
Transaction ID: 82cc96d985d0a880fc4378814d829b6db4548372e55c3267df3c302381d75faa
Output index: 1
Transaction total size: 335 bytes

Height: 79455
Difficulty: 0.00
Time: 04-16-2021 14:23:15
Subsidy: 7806.0528

I think i will see if i can do the NFT case scenario that you wrote earlier.

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 ... 21