BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

Totally, no sweat at all! I saw that thing pop up with the Bible verse too, it is actually really neat, and definitely adds to the overall feel and user interface offered. I am going to be composing the last edition of this letter (email, actually) that I will send to some companies, but I want to make it as official as possible. I will post my rough idea of it before I send it to the companies, and I was thinking that it might look a bit better if: a: I don't sign it personally, but rather as "Team BiblePay" or something like that, and b: if it is sent from a reputable looking business related address. So, maybe I send it from the inbuilt BBP email in PC wallet or through my account here? That should work, right? I honestly have not tried out the PC wallet email address yet, but just want to make sure that we send the right impression with this letter, so I will definitely not rush the process at all.
Thanks again for your help,
May God bless you,
twinkle

Well the biblepaycore smtp sender does not actually support sending into the internet yet-- it can only either A) Receive pop3 from other biblepaycore addresses, or B) Send SMTP to other core wallet users.  So yeah you would have to send it from your personal e-mail address.  We have a Tweet-from-pool feature where we send it to the 1,500 pool e-mail addresses but thats pretty limited to our current user base.  I can give you some free credits in the pool if you ever need to use that feature (to tweet something out).


8000 BBP

Alright, I will definitely keep that in mind, I will probably have an answer within a few days or so, but thanks for your feedback on the emailing, I was definitely not sure about its capabilities, so your response definitely cleared up some things.
Have a great rest of your day, and may God bless you all!
twinkle
1000 BBP

Hi Talisman,

I believe the issue you are running into is probably something very simple disguised by a confusing error message.

First ensure that the wallet is unlocked, and that your unspent coins are between 1000 and 10MM bbp each.  If they arent, try the 'bankroll 10 100000' for example, just to ensure thats not the problem.

Im leaning towards the wallet being locked.  It should be that simple; technically we auto-allocate the amount from PM now not requiring the bankroll.
If it does not work, please check the debug.log for a strange error message and let us know.


8000 BBP

Hi Rob!

It was indeed the wallet lock preventing the submission. Once I unlocked, Portfolio Builder did its job smoothly.

I like the new look and features available. Thanks and kudos for the great job!
1300 BBP

I had no problems creating a BBP only stake.  Thanks for the referral reward, Rob!

Now I'm trying to create a BTC stake, but when I paste the BTC address I copied from Trust Wallet, bc1q08tkcyac8dzwm5wzxacy898g2fu69nsj2kf7fc, Portfolio Builder says "Address invalid." when I click on either "Submit" or "Query UTXO."  Why isn't this working for me?

I had no problems creating a BBP only stake.  Thanks for the referral reward, Rob!

Now I'm trying to create a BTC stake, but when I paste the BTC address I copied from Trust Wallet, bc1q08tkcyac8dzwm5wzxacy898g2fu69nsj2kf7fc, Portfolio Builder says "Address invalid." when I click on either "Submit" or "Query UTXO."  Why isn't this working for me?

My guess is that it is because it is because that is a Bech32 format address, which I think is not as widely supported. That is in contrast to P2SH or the (legacy) P2PKH, which are 34 characters long. Bech32 is longer, and there is more than one option for length.

I just checked and it looks like the code checks for the BTC address to be 34 characters long, and gives an Address Invalid error message if it is not.

To add to this:
It looks like the api provider BiblePay uses (blockchair) supports Bech32 format addresses just like the other addresses. So theoretically it should fix it by changing the length check in rpcpog ValidateAddress3.
Notes:
Bech32 address is variable in length, so it should not be checked against a static number. Instead it should be checked against min/max length, as well as starting with the correct prefix.
Note that it appears that LTC also supports Bech32. These have a different prefix than bitcoin Bech32 prefixes.

BiblePay - 1.6.2.8 - Leisure Upgrade


- Fix the supply figure in 'gettxoutsetinfo' rpc call (it was doubled in error).
- Machine language fix for arm64 compatibility
- Correct the DWU% calculation in Portfolio Builder to be accurate (and the drill in the leaderboard) and increase font size.
- Correct the global transaction fee calculation to be accurate (IE lower than 100 bbp, ~IE 1-5 bbp for small txs)
- Add support for BTC/Bech32 (42 character) addresses
- Chainz, our block explorer, has upgraded!  https://chainz.cryptoid.info/bbp/


8000 BBP

I had no problems creating a BBP only stake.  Thanks for the referral reward, Rob!

Now I'm trying to create a BTC stake, but when I paste the BTC address I copied from Trust Wallet, bc1q08tkcyac8dzwm5wzxacy898g2fu69nsj2kf7fc, Portfolio Builder says "Address invalid." when I click on either "Submit" or "Query UTXO."  Why isn't this working for me?

Yeah, it was due to our address length check on BTC; I have added the 42 char (bech32) support to 1.6.2.8 - please see latest release above.

Please try now!


8000 BBP

Yeah, it was due to our address length check on BTC; I have added the 42 char (bech32) support to 1.6.2.8 - please see latest release above.

Please try now!


8000 BBP

It seems to be accepting the address now, though now it doesn't seem to be working because I didn't have enough BTC to put a '0' between the PIN and the rest of the amount.  I think I'll be converting it to something else, which means I'll have to spend even more on network fees to send my BTC to an exchange.  I'm certainly never going to use BTC to buy coffee or pizza.

It seems to be accepting the address now, though now it doesn't seem to be working because I didn't have enough BTC to put a '0' between the PIN and the rest of the amount.  I think I'll be converting it to something else, which means I'll have to spend even more on network fees to send my BTC to an exchange.  I'm certainly never going to use BTC to buy coffee or pizza.

Yeah, I hear you, I was going through the same thing in TestNet when I wanted to test BTC.  If you add three zeroes before your pin, (IE .00012345) it gets it down to about $20 at the end, but nevertheless thats a lot of money to make an 'adjustment'.   (Same goes for ethereum, as far as network fees).

DOGE is turning out to be very valuable for those type of things.

Of course Stellar only costs .01 to make an adjustment.


8000 BBP

Congratulations to whoever bought an NFT!  Someone bought someone elses NFT, the one with the clock, for 55K.

At least we are starting to see a use case for these!

Todd is in the process of creating a few Orphan NFTs for us, he's got the mac client working.


8000 BBP

Yeah, I hear you, I was going through the same thing in TestNet when I wanted to test BTC.  If you add three zeroes before your pin, (IE .00012345) it gets it down to about $20 at the end, but nevertheless thats a lot of money to make an 'adjustment'.   (Same goes for ethereum, as far as network fees).

DOGE is turning out to be very valuable for those type of things.

Of course Stellar only costs .01 to make an adjustment.


8000 BBP

Since 8 decimal places seems to be standard, if you put in 3 zeroes before the PIN, it seems that you need to stake over 0.010 of whatever currency for the PIN to be recognized, which is a significant amount for BTC (or perhaps simply stake the PIN itself with 2 or 3 zeroes before it, which gives very little flexibility.)

Since 8 decimal places seems to be standard, if you put in 3 zeroes before the PIN, it seems that you need to stake over 0.010 of whatever currency for the PIN to be recognized, which is a significant amount for BTC (or perhaps simply stake the PIN itself with 2 or 3 zeroes before it, which gives very little flexibility.)

I have an opposing view that what we've done is bent over backwards to provide a high level of flexibility for the user to stake currencies that are not even related to biblepay and earn rewards, for very little fees.

It's a one time adjustment, and the transaction charges are something inherently high in bitcoin and ethereum, not on our end.


8000 BBP

Congratulations to whoever bought an NFT!  Someone bought someone elses NFT, the one with the clock, for 55K.

At least we are starting to see a use case for these!

Todd is in the process of creating a few Orphan NFTs for us, he's got the mac client working.


8000 BBP

Hello Rob,
I was the one who bought the NFT "When the World Stool Still" but I had not entered the CPK address on my account and the NFT went back for sale. 
I'm waiting to see if the 55,000 bbp returns to my wallet to be able to redeem it ...
1000 BBP

I have an opposing view that what we've done is bent over backwards to provide a high level of flexibility for the user to stake currencies that are not even related to biblepay and earn rewards, for very little fees.

It's a one time adjustment, and the transaction charges are something inherently high in bitcoin and ethereum, not on our end.


8000 BBP

I didn't mean this as a criticism of BiblePay.  Using a 5 digit PIN is a reasonable security measure to prevent possible abuse, while allowing the user to keep the foreign cryptocurrency themselves.  It had occurred to me that an extremely limited way around the minimum 1 million SAT stake for BTC might be, if the PIN is, say, 12345, would be to stake exactly 0.00012345 or 0.0012345 BTC.  It might be helpful if the documentation noted the high minimum value for a BTC stake, and the high BTC and ETH fees.
1000 BBP