Bible Pay

Read 1879846 times

  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
DUDE THIS IS INSANE. This Amazon integration is literally something that I think no other cryptocurrency has at the moment. Man, I am so pumped. This really does sound like a fantastic time to do a lot of the reaching out to companies. I have been really busy with college lately, so that has been keeping me from working on the email and emailing list too much. But, I am going to re-double my efforts. This really does seem like this has to make the currency so much more appealing and useful to everyone. I just looked it up, and the only way I could find online for people to be able to spend their crypto was to first convert it into fiat or gift cards, and THEN spend it. This really does streamline the process so much! Really nice work, let's keep it up!
May God bless you all, and may all glory go to Him alone from this project,
twinkle

1000 BBP
Thank you Twinkle for the compliments!  This keeps me excited for our future, praise God!



8200 BBP


  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
One quick Q I had for it, though. Rob, are you having to order all of this yourself after we "buy" it on the store page? Or, is there some sort of system by which it can actually convert the spent BBP to fiat and then spend it on the item immediately through Amazon? I am just wondering about how this sort of thing could scale in the future.
Thanks, and may God bless you all!
twinkle

1000 BBP
No, I think it can scale fine because its actually completely automated.  My API has very low latency (it places an order in a couple seconds of computer time completely by itself), and the integration with BBP and the exchange for USD is all automatic.  I have to do a little bit of work every so often when I move a batch of crypto from the pool or something but that can be automated later once the process is entirely established.  I think this could be sustainable even with relatively large growth.  Our price might sink, but as long as we gain new users it might rise more that it sinks due to picking up more investors.


WOW THIS IS SO CLEAN! I just added a product to the store, and it IMMEDIATELY went up. Insane. So, just to be clear, what would happen if I tried to add a product that was not prime? I will definitely help with getting as many products on here as I can!
May God bless you all,

Thanks!  I am happy that any product in the whole $300 billion store can be added in a couple seconds and purchased with free shipping.

On our conference call today, Pat & I and MIP were also talking about how nice it would be if we could get it working in India, so the unbanked can buy groceries with it. 

8200 BBP
« Last Edit: July 04, 2021, 05:04:22 PM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
To whomever bought my NFT I had listed the other day in the store, I just finished donating all of the funds from that to a global Christian missions outreach. I honestly don't have a very good way of verifying this without giving away a lot of personal info, so there will have to be some trust with this process. I just took the rate of BBP, converted it to USD, and then tithed it to this mission trip program.
May God bless you all, and your loved ones,
twinkle

Thats so awesome of you man, God bless you!



8200 BBP


  • alee67
  • Jr. Member

    • 16


    • 2
    • May 25, 2020, 05:29:56 AM
    more
I tried creating a DOGE stake; I sent an amount of DOGE from Trust Wallet to itself ending with the PIN over 4 hours ago.  It doesn't show up at all in the leaderboard, and 'listutxostakes 0' says that I have 0 DOGE staked.  In Portfolio Builder, when I click on 'Query UTXO', it shows the change received from the transaction, which went to the same address, 'DNrVShF3dp1gj6KaPGfR6ADdhU4WQEE3yX', and that amount doesn't end in the PIN, of course.  The PIN for the DOGE address ends in '0'.  Could it be that the trailing zero in the amount staked is getting dropped, so the PIN isn't being recognized?

1000 BBP


  • sntjo2847
  • Jr. Member

    • 46


    • 3
    • May 21, 2021, 02:55:13 PM
    more
So for one, I take security very seriously, and couldnt possibly imagine having RandomX + Chainlocks in our community and ending up with a sidechain, so I've been vehemently trying to find the root cause of this and I believe I found the root cause and it should be fixed now. 
Basically the first part of the explanation is correct; we were transitioning over to chainlocks and the chainlocks started successfully, I can see this because yesterday morning we didnt have blocks locked at the tip and now we have hundreds of blocks locked and we are locked to the tip, so that part is good, the delay was due to normal quorum formation (which takes 2 days from my experience in testnet) and it took about 2 days in prod.

Now the second part of the issue, how we were jittering in and out of the go live and having a side chain form for a few hours (which, to my knowledge is the Only side chain we ever had since randomx started) - I honestly dont remember any sidechain even forming while on randomx because its a very expensive algorithm and it clearly keeps our consensus.

So what I found when debugging my server #6 which has multiple sancs on it was all the instances of BBP went down at the same time (during that height range of the sidechain), and fortunately I was able to find the problem in the debug logs on the server and this leads to a Fix.....  The problem is in our memorize prayers function believe it or not.  Its hard to fathom how that could cause a problem like this; but here is how.  We serialize the prayers based on a filename location that works for Single nodes only.  When more than one node instance on a sanctuary tries to write to that file at the same time it can crash the node (and that can cause database corruption because its an immediate non flushed berkeley db exit). 

So the fix is now checked in, I have upgraded my sancs.  The fix is working (cause I can see the prayers file has a distinct name now per server instance etc) and they are not clashing anymore. 

Now we need to let everything run for a week and monitor chainlocks and instantsend and see if chainlocks keeps us on one main chain for long periods of time, and my feeling is that we are going to be successful this time; I think we have fixed our bugs and we have a solid chain to build on. 
Thank you for spending the time to dig into this, identify the issue, and fix it! And thank you for the detailed explanation too, I appreciate it!


  • sntjo2847
  • Jr. Member

    • 46


    • 3
    • May 21, 2021, 02:55:13 PM
    more
I have a question about APM(Automatic Price Mooning)

What parts of the block reward are subject to this? It is clear that sanctuaries and randomx mining are subject to APM. Are portfolio builder rewards and the 5% monthly budget subject to it? Are they reduced by the same %?


  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I have a question about APM(Automatic Price Mooning)

What parts of the block reward are subject to this? It is clear that sanctuaries and randomx mining are subject to APM. Are portfolio builder rewards and the 5% monthly budget subject to it? Are they reduced by the same %?

Only the coinbase is reduced (the sanc reward, plus the mining reward).  The monthly budget is not affected and the daily UTXO rewards are not affected.
We deliberately did that of course to be able to have a budget (when we have enough marketcap to actually have a budget again). 
In order to pull that off we had to tweak the budget estimator to use a non-apm subsidy estimate.



8200 BBP


  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I tried creating a DOGE stake; I sent an amount of DOGE from Trust Wallet to itself ending with the PIN over 4 hours ago.  It doesn't show up at all in the leaderboard, and 'listutxostakes 0' says that I have 0 DOGE staked.  In Portfolio Builder, when I click on 'Query UTXO', it shows the change received from the transaction, which went to the same address, 'DNrVShF3dp1gj6KaPGfR6ADdhU4WQEE3yX', and that amount doesn't end in the PIN, of course.  The PIN for the DOGE address ends in '0'.  Could it be that the trailing zero in the amount staked is getting dropped, so the PIN isn't being recognized?
Hi Alee,

So I think you might be experiencing a transaction deduction issue from the provider you sent it from.  When I reproduce with your DOGE address I see the pin is supposed to be 75720 (its ok this is publicaly calculable) and the amount sent to the address is 1.58372072 leading me to believe a fee was deducted first.

If you are sending to trustwallet from binance or from SX, on SX you have to pay the fee yourself, and on binance you have to take out your calculator and add the fee on first.  Bottom line is the address has to receive '75720' for it to count (in the suffix).  On binance I add the fee on with my calculator for example...




8200 BBP


  • sntjo2847
  • Jr. Member

    • 46


    • 3
    • May 21, 2021, 02:55:13 PM
    more
Only the coinbase is reduced (the sanc reward, plus the mining reward).  The monthly budget is not affected and the daily UTXO rewards are not affected.
We deliberately did that of course to be able to have a budget (when we have enough marketcap to actually have a budget again). 
In order to pull that off we had to tweak the budget estimator to use a non-apm subsidy estimate.
Ok, thank you for the information. That is what I thought was happening from reading the code, but there is a lot of code and I am not very familiar with the biblepay code.

I hope you do not mind all the questions. I have another one:
Is the recent increase in average block time intentional? Illustration:
The last 1000 blocks (279163 - 280162) took 5 days, 23 hours, 18 minutes (8598 minutes) for an average block time of 8.598 minutes/block.
At an average of 7 min block or 24 hour * 60 min / 205 ~= 7.024 min/block there should have been 1224 blocks in that amount of time.
Which means we "lost" 224 blocks - more than a whole day.

Please note that if it is intentional, I am guessing it is due to a previous over-emission of blocks or bbp. I am curious though.


  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
** Orphan NFTs are now Available **


I am very pleased to announce the new Orphan NFTs that are finally available from Cameroon One!

http://foundation.biblepay.org/NFTOrphans

You can also click on NFT Orphans from the "Orphans" left menu in the pool...

So we had 4 orphans created by Cameroon-One (with 90 day durations), and two are already sponsored!

Praise God!

To sponsor one just send BBP to your pool account.  Also you can actually buy nfts or sponsor orphans from the core wallet with the 'buynft' rpc command if you want to stay anonymous...

We didnt forget about anonymous centric users - you can also create anonymous UTXO retirement accounts in portfolio builder by leaving your nickname as N/A...

On another side note, we have Orphan NFTs on Biblepay-TV in testnet!  See the Biblepay-TV testnet thread for more information.



8200 BBP


  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Ok, thank you for the information. That is what I thought was happening from reading the code, but there is a lot of code and I am not very familiar with the biblepay code.

I hope you do not mind all the questions. I have another one:
Is the recent increase in average block time intentional? Illustration:
The last 1000 blocks (279163 - 280162) took 5 days, 23 hours, 18 minutes (8598 minutes) for an average block time of 8.598 minutes/block.
At an average of 7 min block or 24 hour * 60 min / 205 ~= 7.024 min/block there should have been 1224 blocks in that amount of time.
Which means we "lost" 224 blocks - more than a whole day.

Please note that if it is intentional, I am guessing it is due to a previous over-emission of blocks or bbp. I am curious though.

Well first of all, no I don't mind any questions as long as they don't attract hackers to some public conversation that would hurt us, but this is obviously fine;

Next let me clarify on our 7 minute block target, on the point where you asked if it was intentional that we were emitting slow; This is not intentional in any way.

Let me expound that bitcoin, is off by something like a Year on their masterclock; this is entirely normal when the chain goes through periods that are increasing in difficulty (I think in the last quarter, in our case, generally, our randomx miners doubled their mining efforts in the Fun pool- we went from a diff of 1 to a diff of 7-8 and back to 3 or so), so I think we had an increasing diff and that slowed the block rate down a little; so we are actually much less volatile than bitcoin in general since genesis;

But to your point, I am extremely concerned with fair weight and measures in biblepay (proverbs 16:11), so much that we have a dedicated masterclock command (from the rpc, you can type 'exec masterclock' and see the metric and suggestions) that gives us the guide to whether we should speed up the masterclock-- and we actually have sped it up.  When we went from POBH to RX, we had a period of slow emissions, and we sped it up from 420 seconds to 370 seconds, in accordance with the estimated adjustment in the masterclock output; so its actually running at a 13%+ tweak in speed right now to catch us up... Another words it will probably speed up naturally over the next quarter without doing anything; what we do is we can speed it up even more if we dont eventually see 6 min blocks by next quarter, for example.

This is not based on our emission target though.  Our emission target was definitely too high up to 2020 due to overspending on DWS; but we reacted vehemently with APM and that actually corrected the emission problem completely (which just finished actually); but if you type 'gettxoutsetinfo' you will see this is complete, we made up for that, thank God, and we are right on schedule now.  Our emissions perfectly match the schedule and should hit the exact number roughly in Dec this year..  Our only problem now is praying to God to remove our sell wall on SX.. I think that is our biggest hole to climb out of.  Other than that, we have no debt to anyone, and fair weights and measures here (a fair mining algorithm with double compensation and no electricity costs etc), and Im committed to speeding up the master clock over time to reach the exact block count since genesis etc.




8200 BBP


  • alee67
  • Jr. Member

    • 16


    • 2
    • May 25, 2020, 05:29:56 AM
    more
Hi Alee,

So I think you might be experiencing a transaction deduction issue from the provider you sent it from.  When I reproduce with your DOGE address I see the pin is supposed to be 75720 (its ok this is publicaly calculable) and the amount sent to the address is 1.58372072 leading me to believe a fee was deducted first.

If you are sending to trustwallet from binance or from SX, on SX you have to pay the fee yourself, and on binance you have to take out your calculator and add the fee on first.  Bottom line is the address has to receive '75720' for it to count (in the suffix).  On binance I add the fee on with my calculator for example...




8200 BBP

That was the change, worth about $0.40.  I sent the stake from my Trust Wallet address back to my Trust Wallet address, so both outputs went to the same address.  This is the transaction:

https://blockchair.com/dogecoin/transaction/bc157112f04f5e2f9d64d7a3a2d8ea706dfb501516a600a930aa3e5509b4c700?from=trustwallet

1000 BBP


  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
That was the change, worth about $0.40.  I sent the stake from my Trust Wallet address back to my Trust Wallet address, so both outputs went to the same address.  This is the transaction:

https://blockchair.com/dogecoin/transaction/bc157112f04f5e2f9d64d7a3a2d8ea706dfb501516a600a930aa3e5509b4c700?from=trustwallet
Bottom line is, your DOGE address, DNr*, has an unspent output from TXID bc157112f04f5e2f9d64d7a3a2d8ea706dfb501516a600a930aa3e5509b4c700 for 1.58372072 and not for
1.5875720 like we require.

Here is the current UTXO:
https://api.blockchair.com/dogecoin/dashboards/address/DNrVShF3dp1gj6KaPGfR6ADdhU4WQEE3yX

Our users need to adjust the utxos to end in the correct pin suffix - or they do not count.

I've sent DOGE from binance and from coinbase to trustwallet, and yes you do have control over what you send to your address if you check further into the fees. 

If you are wondering why they are not additive, for security purposes, we do not allow non matching UTXOs to be additive.  Each pin matched UTXO counts and is additive.




8200 BBP
« Last Edit: July 05, 2021, 01:33:30 PM by Rob Andrews »


  • sntjo2847
  • Jr. Member

    • 46


    • 3
    • May 21, 2021, 02:55:13 PM
    more
Well first of all, no I don't mind any questions as long as they don't attract hackers to some public conversation that would hurt us, but this is obviously fine;

Next let me clarify on our 7 minute block target, on the point where you asked if it was intentional that we were emitting slow; This is not intentional in any way.

Let me expound that bitcoin, is off by something like a Year on their masterclock; this is entirely normal when the chain goes through periods that are increasing in difficulty (I think in the last quarter, in our case, generally, our randomx miners doubled their mining efforts in the Fun pool- we went from a diff of 1 to a diff of 7-8 and back to 3 or so), so I think we had an increasing diff and that slowed the block rate down a little; so we are actually much less volatile than bitcoin in general since genesis;

But to your point, I am extremely concerned with fair weight and measures in biblepay (proverbs 16:11), so much that we have a dedicated masterclock command (from the rpc, you can type 'exec masterclock' and see the metric and suggestions) that gives us the guide to whether we should speed up the masterclock-- and we actually have sped it up.  When we went from POBH to RX, we had a period of slow emissions, and we sped it up from 420 seconds to 370 seconds, in accordance with the estimated adjustment in the masterclock output; so its actually running at a 13%+ tweak in speed right now to catch us up... Another words it will probably speed up naturally over the next quarter without doing anything; what we do is we can speed it up even more if we dont eventually see 6 min blocks by next quarter, for example.

This is not based on our emission target though.  Our emission target was definitely too high up to 2020 due to overspending on DWS; but we reacted vehemently with APM and that actually corrected the emission problem completely (which just finished actually); but if you type 'gettxoutsetinfo' you will see this is complete, we made up for that, thank God, and we are right on schedule now.  Our emissions perfectly match the schedule and should hit the exact number roughly in Dec this year..  Our only problem now is praying to God to remove our sell wall on SX.. I think that is our biggest hole to climb out of.  Other than that, we have no debt to anyone, and fair weights and measures here (a fair mining algorithm with double compensation and no electricity costs etc), and Im committed to speeding up the master clock over time to reach the exact block count since genesis etc.




8200 BBP
Yeah, if I had a question that I thought might do something like that I would send a PM or maybe an email, not post here.

Thank you once again for a clear detailed explanation. It definitely cleared things up for me!

In regards to the sell wall, is a lot of that from all the Sanctuaries that shutdown recently? At 4.2 million each, that is a lot of BBP. I noticed that there were quite a few less since the mandatory update.


  • alee67
  • Jr. Member

    • 16


    • 2
    • May 25, 2020, 05:29:56 AM
    more
Bottom line is, your DOGE address, DNr*, has an unspent output from TXID bc157112f04f5e2f9d64d7a3a2d8ea706dfb501516a600a930aa3e5509b4c700 for 1.58372072 and not for
1.5875720 like we require.

Here is the current UTXO:
https://api.blockchair.com/dogecoin/dashboards/address/DNrVShF3dp1gj6KaPGfR6ADdhU4WQEE3yX

Our users need to adjust the utxos to end in the correct pin suffix - or they do not count.

I've sent DOGE from binance and from coinbase to trustwallet, and yes you do have control over what you send to your address if you check further into the fees. 

If you are wondering why they are not additive, for security purposes, we do not allow non matching UTXOs to be additive.  Each pin matched UTXO counts and is additive.

It's the other UTXO output from the transaction to the same address, for 402.0007572(0) DOGE, that's supposed to be the stake: https://blockchair.com/dogecoin/transaction/bc157112f04f5e2f9d64d7a3a2d8ea706dfb501516a600a930aa3e5509b4c700?from=trustwallet.  The smaller amount was the change.

1000 BBP