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 ... 20
61
Earlz, have you had a chance to upgrade your sanc 37.120 yet?  The reason I ask is since its a mandatory I think its preventing chainlocks.
Chainlocks and llmq stopped when I upgraded my 3 sancs (which makes sense) but its supposed to recover within 205 blocks.
However when I look on my 3rd sanc it has one connection to your sanc which might be the problem (and 0 connections to my sanc).

EDIT:
I see you upgraded but not sure about your hash - looks like my sanc sees your sanc with a lower hash, here is my hash:
getblockhash 86417
5cae3b49db8c6ab763ad9d952972389a29a2514e392922a24b29958ffbed5578

EDIT II:
It looks like it worked itself out; I rebooted the sanc that had only one connection and it reconnected to one of my others and chainlocks and llmq continued; and they started to ddos your sanc so it looks like in prod this would resolve itself.

Mornin.

'Yeah i had around 7 hours downtime the other night , isp have some trouble with mobile connections over here.

I ran your getblockhash command on sanc and got :
Code: [Select]
[email protected]:~/biblepay$ ./biblepay-cli getblockhash 86417
5cae3b49db8c6ab763ad9d952972389a29a2514e392922a24b29958ffbed5578
Comparing to yours : getblockhash 86417
5cae3b49db8c6ab763ad9d952972389a29a2514e392922a24b29958ffbed5578

Looks the same to me.

Some other info i get :
Code: [Select]
[email protected]:~/biblepay$ ./biblepay-cli masternode status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "37.120.153.54:40001",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned"
}
[email protected]:~/biblepay$

Code: [Select]
[email protected]:~/biblepay$ ./biblepay-cli -getinfo
{
  "version": 1060104,
  "protocolversion": 70772,
  "walletversion": 61000,
  "balance": 0.00000000,
  "blocks": 86898,
  "timeoffset": 0,
  "connections": 5,
  "proxy": "",
  "difficulty": 2.632266129353999e-05,
  "testnet": true,
  "privatesend_balance": 0.00000000,
  "keypoololdest": 1618251858,
  "keypoolsize": 1000,
  "paytxfee": 0.00000000,
  "relayfee": 0.25000000,
  "warnings": ""
}

Code: [Select]
[email protected]:~/biblepay$ ./biblepay-cli mnsync status
{
  "AssetID": 999,
  "AssetName": "MASTERNODE_SYNC_FINISHED",
  "AssetStartTime": 1620360168,
  "Attempt": 0,
  "IsBlockchainSynced": true,
  "IsSynced": true
}


62
Hello Rob.

I have been busy at work now so i havent been able to do much testing, last time i tried to liquidate a locked stake  it did not work for me, but i will retry this new verison you put out and ofcourse
I see you updated with new testcases.

Quote
QUESTION:

Do any of you have experience in running a Microsoft ASPX based web server and experience in SQL and/or c# programming?  The reason I ask is we are developing a new technology, called the 'biblepay DLL' that allows c# IT organizations (and developers) run a web server that hosts decentralized pages driven by DSQL queries.  Whoever is interested in testing this, I would like to make a wiki to explain how to install it and program it.

Sadly i have no experience of such things.

In the coming days i will do some more testing, exciting times Rob!
Have a good one Brother.

63
** FIVE MORE PAKISTAN WELLS HAVE BEEN COMPLETED! **


I am very pleased to announce that our 5 tube wells in Pakistan (from project https://forum.biblepay.org/index.php?topic=766.msg10785#msg10785) are complete!  Now approximately up to 1000 children in 5 areas can have perpetual water for free!


We numbered them wells #14, 15, 16, 17, and 18!

See project here starting with #14:

https://foundation.biblepay.org/Wells

Praise God for enabling us to facilitate this project for his children!  May God bless us with future revenue to complete more projects soon.
Hello Brother Rob.
Man thats awesome!
Things sure went fast this time.
Been scrolling thru the pictures/videos, something special seeing projects come to life.

Looking forward to future  endeavors.



64
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 
Quote
minimum_bbp_amount commitment_days 0=dry_run/1=real
Should be switched right, like this: highriskbbpstake bbp_amount 1 duration_in_days



65
** Highly Positive for BiblePay **

BiblePay's difficulty for RandomX has been increasing all day, from 10, now to 63.  This is 800% higher than normal!

This is extremely good news, praise God!

Yeah its pretty cool.
I have had some intresting discussions on monero reddit with cpu miners, telling people you can merge mine with biblepay, get some extra profit that you can restake or sell if you want.

Well people i have talked to have been really positive, intrested in what this project is.


66
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.

67
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.

 

68
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.


69
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.


70
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.

71
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.



72
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.

73
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.

74
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.

75
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)

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