Bible Pay

Read 1989916 times

  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #1605 on: December 14, 2024, 06:53:51 AM »
We will be having a mandatory upgrade in about 10 days (trying to give plenty of notice on this).

The primary driver is to finally seal up the LLMQ (Instantsend) - Quorums code to be fully operational.

A little back story on this.
We always had deterministic masternodes and LLMQs, since Dash released those.  However there is a mix of problems between the version we were on prior to the rebase and where we are today.

At one point, when we had the hybrid (non deterministic Sanc plus LLMQ bolted on), instantsend worked fine.
It was during the period where our sanctuary count decreased and people started to run Investor nodes, where the quorums started to be less reliable.
This caused instant send to revert to non deterministic rules (IE it worked, but it used Dashs legacy code and not LLMQs).
Dash eventually removed that code, which caused our LLMQs to switch between deterministic (IE pure LLMQ instantsend) and LLMQ being off (if a quorum wasnt active at that height).

To remove all the bore of this story, over the last 9 months of releases Ive been trying to ensure these are 100% reliable and always on.

Reason being is, instantsend and chainlocks are actually required for unchained.biblepay.org and our sidechain and for NFTs to work correctly (if you lose instantsend, the experience becomes severely bad for the user, simply because they buy an NFT and it takes 20 mins to lock the tx.  Meaning, they cant see the NFT on the screen for 20 mins.  (The rule prevails that says do not accept a tx in a block until at least 1 block has passed after it was mined).  For us, thats a minimum of 14 mins (7 min block times) which is not acceptable.

So finally, InstantSend is fixed.  Release will be out this weekend.








  • Rob Andrews
  • Administrator

    • 4281


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #1606 on: December 14, 2024, 08:46:56 AM »
Biblepay v0.21.8
Mandatory Upgrade - Cutover Height 555,000



- Make LLMQ quorums ignore investor nodes (more reliable quorums)

Release:
https://github.com/biblepay/biblepay/releases



  • oncoapop
  • Full Member

    • 177


    • 18
    • October 23, 2018, 12:31:17 PM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #1607 on: December 16, 2024, 12:05:25 AM »
Dear Rob,
I managed to recreate my sanc. However, it appears that the controller wallet (Windows Biblepay-qt) displays that my sanc is in INVESTOR mode while the sanc itself shows READY. See attached screenshot. I checked that (at time of posting) almost all of the other sancs also appear to have the same status - INVESTOR.
Is this intended behaviour?
Thank you. Keep up the good work!
Blessings
oncoapop
« Last Edit: December 16, 2024, 12:42:49 AM by oncoapop »


  • lalexcross
  • Jr. Member

    • 29


    • 2
    • April 16, 2018, 04:17:51 AM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #1608 on: December 17, 2024, 05:38:12 AM »
Dear Rob,
I managed to recreate my sanc. However, it appears that the controller wallet (Windows Biblepay-qt) displays that my sanc is in INVESTOR mode while the sanc itself shows READY. See attached screenshot. I checked that (at time of posting) almost all of the other sancs also appear to have the same status - INVESTOR.
Is this intended behaviour?
Thank you. Keep up the good work!
Blessings
oncoapop

Dear oncoapop,
Are you directly connected to public internet or are you behind a NAT by router ?

What is the IP and port configured in your masternode.info because I have always the seame error:

"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "ERROR",
  "stat[/li][/list]
  "us": "Error. Can't detect valid external address. Please consider using the externalip configuration option if problem persists. Make sure to use IPv4 address only."

Thanks for you help
Ale



  • oncoapop
  • Full Member

    • 177


    • 18
    • October 23, 2018, 12:31:17 PM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #1609 on: December 18, 2024, 01:49:08 AM »
    Dear oncoapop,
    Are you directly connected to public internet or are you behind a NAT by router ?

    What is the IP and port configured in your masternode.info because I have always the seame error:

    "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
      "service": "[::]:0",
      "state": "ERROR",
      "stat[/li][/list]
      "us": "Error. Can't detect valid external address. Please consider using the externalip configuration option if problem persists. Make sure to use IPv4 address only."

    Thanks for you help
    Ale
    Dear Ale,
    Thanks for your question. I have them both behind NAT and also in a datacenter.

    This is the one behind NAT.
    $ cli masternode status
    {
      "outpoint": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193-0",
      "service": "108.180.46.33:41000",
      "proTxHash": "f64ce28c46d989035dc00e48fd5c2906050d20ad471b9ef7188d3fc32e3365a5",
      "type": "Regular",
      "collateralHash": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193",
      "collateralIndex": 0,
      "dmnState": {
        "version": 2,
        "service": "108.180.46.33:41000",
        "registeredHeight": 551815,
        "lastPaidHeight": 552264,
        "consecutivePayments": 0,
        "PoSePenalty": 0,
        "PoSeRevivedHeight": -1,
        "PoSeBanHeight": -1,
        "revocationReason": 0,
        "ownerAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
        "votingAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
        "payoutAddress": "BKcbU8zYxfHGfaytRowYQLkyVA1U2BDYx4",
        "pubKeyOperator": "a8aba6cd5915acb888c5b7c689808f015b1c417d7fa9edbf3042a1ee1168ba17446cfdb1f0b5492fcaf6924629d0081c"
      },
      "state": "READY",
      "status": "Ready"
    }
    To make this work, as an example, I needed to go to my router IP 108.180.46.33 (get this from whatsmyip.com) and map 41000 to an internal port 41000 in this case, on my internal server 192.168.1.16 (get this from ifconfig)

    Add this to your biblepay.conf

    externalip=108.180.46.33:41000
    masternodeaddr=192.168.1.16:41000
    port=41000
    maxconnections=128
    masternodeblsprivkey=......132b9d4ef47f91bdc7a692820e.....

    Blessings
    oncoapop


    • Rob Andrews
    • Administrator

      • 4281


      • 97
      • June 05, 2017, 08:09:04 PM
      • Patmos, Island Of
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1610 on: December 19, 2024, 01:51:24 PM »
    Dear Ale,
    Thanks for your question. I have them both behind NAT and also in a datacenter.

    This is the one behind NAT.
    $ cli masternode status
    {
      "outpoint": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193-0",
      "service": "108.180.46.33:41000",
      "proTxHash": "f64ce28c46d989035dc00e48fd5c2906050d20ad471b9ef7188d3fc32e3365a5",
      "type": "Regular",
      "collateralHash": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193",
      "collateralIndex": 0,
      "dmnState": {
        "version": 2,
        "service": "108.180.46.33:41000",
        "registeredHeight": 551815,
        "lastPaidHeight": 552264,
        "consecutivePayments": 0,
        "PoSePenalty": 0,
        "PoSeRevivedHeight": -1,
        "PoSeBanHeight": -1,
        "revocationReason": 0,
        "ownerAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
        "votingAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
        "payoutAddress": "BKcbU8zYxfHGfaytRowYQLkyVA1U2BDYx4",
        "pubKeyOperator": "a8aba6cd5915acb888c5b7c689808f015b1c417d7fa9edbf3042a1ee1168ba17446cfdb1f0b5492fcaf6924629d0081c"
      },
      "state": "READY",
      "status": "Ready"
    }
    To make this work, as an example, I needed to go to my router IP 108.180.46.33 (get this from whatsmyip.com) and map 41000 to an internal port 41000 in this case, on my internal server 192.168.1.16 (get this from ifconfig)

    Add this to your biblepay.conf

    externalip=108.180.46.33:41000
    masternodeaddr=192.168.1.16:41000
    port=41000
    maxconnections=128
    masternodeblsprivkey=......132b9d4ef47f91bdc7a692820e.....

    Blessings
    oncoapop

    Hi Oncoapop,

    I believe you have everything set up correctly, because I can telnet to your port 41000 from my house, and as you show above you have the masternode status returning successfully.

    The issue is within our code, we have specific requirements for non-investors:
    if (nPort == 40000 || (nPort >= 10000 && nPort <= 10100))
        fPortPassed=true;

    The public port has to either be 40000 (Prod), or 10000-10100 in Prod.

    If its not in our docs, I will add a todo to put that in asap.
    Sorry for the inconvenience.

    Once you recreate your sanc on one of those ports, it should switch to non investor.

    On a side note, it is possible to edit your deterministic.conf and masternode.conf (both entries) with the new port number and do an 'exec upgradesanc sancNN' and that should also change your port number on chain.

    Good luck,
    Rob


    • oncoapop
    • Full Member

      • 177


      • 18
      • October 23, 2018, 12:31:17 PM
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1611 on: December 20, 2024, 02:35:19 AM »
    Dear Rob,

    Thank you for that tip!

    I changed my port using the command "protx update_service <protx_hash> "<ip:new_port>" <operator_privkey>" as the proposed "exec upgradesanc sancNN" command gave the error "bad-protx-dup-key (code -1)" and chatGPT gave me the solution (which I shared!)

    Thank you - my updated sanc appears to be ONLY ENABLED SANCTUARY on the BBP Blockchain at the moment! Time to update my other sancs...

    Blessings
    Oncoapop






    Hi Oncoapop,

    I believe you have everything set up correctly, because I can telnet to your port 41000 from my house, and as you show above you have the masternode status returning successfully.

    The issue is within our code, we have specific requirements for non-investors:
    if (nPort == 40000 || (nPort >= 10000 && nPort <= 10100))
        fPortPassed=true;

    The public port has to either be 40000 (Prod), or 10000-10100 in Prod.

    If its not in our docs, I will add a todo to put that in asap.
    Sorry for the inconvenience.

    Once you recreate your sanc on one of those ports, it should switch to non investor.

    On a side note, it is possible to edit your deterministic.conf and masternode.conf (both entries) with the new port number and do an 'exec upgradesanc sancNN' and that should also change your port number on chain.

    Good luck,
    Rob


    • Rob Andrews
    • Administrator

      • 4281


      • 97
      • June 05, 2017, 08:09:04 PM
      • Patmos, Island Of
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1612 on: December 20, 2024, 01:20:34 PM »
    Dear Rob,

    Thank you for that tip!

    I changed my port using the command "protx update_service <protx_hash> "<ip:new_port>" <operator_privkey>" as the proposed "exec upgradesanc sancNN" command gave the error "bad-protx-dup-key (code -1)" and chatGPT gave me the solution (which I shared!)

    Thank you - my updated sanc appears to be ONLY ENABLED SANCTUARY on the BBP Blockchain at the moment! Time to update my other sancs...

    Blessings
    Oncoapop

    Hi Oncoapop,

    I do not see the same sanctuary view as you do.  On my end 50% of the regular sancs are up and 90% of the temples are up.

    Please confirm that you have updated your sancs to the latest version?  V0.21.8 - Hamans Hanging II.  And your home node?


    10:54:02
    getblockhash 552842


    10:54:02
    0000013a9221fdd81e13939ffb22b2e7bc1ebb53ab6b8dc24ddd0bc77f588e1f


    I do believe there is a problem on bololex and chainz however, probably due to the Sancs agreeing on the latest quorum rules.
    I asked Chainz to reindex, and I sent the upgrade to bololex.

    Can you please try stopping your sanc wallet, delete all files but wallet.dat and reindex from scratch? (This is different than a -reindex=1, I call it an erase chain).

    I did confirm on two of my sancs, after an erasechain, I do agree with the hash above (IE nothing changed on my end before or after the erasechain, but it confirms the hash is correct as I agree on all my nodes, which is more than 6).

    Note that 'revivesanctuary' should work, if you were synced.  The problem with protx update is it does not update the deterministic.conf file.

    Have a good one,
    Rob


    • oncoapop
    • Full Member

      • 177


      • 18
      • October 23, 2018, 12:31:17 PM
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1613 on: December 23, 2024, 01:26:00 AM »
    Hi Oncoapop,

    I do not see the same sanctuary view as you do.  On my end 50% of the regular sancs are up and 90% of the temples are up.

    Please confirm that you have updated your sancs to the latest version?  V0.21.8 - Hamans Hanging II.  And your home node?


    10:54:02
    getblockhash 552842


    10:54:02
    0000013a9221fdd81e13939ffb22b2e7bc1ebb53ab6b8dc24ddd0bc77f588e1f


    I do believe there is a problem on bololex and chainz however, probably due to the Sancs agreeing on the latest quorum rules.
    I asked Chainz to reindex, and I sent the upgrade to bololex.

    Can you please try stopping your sanc wallet, delete all files but wallet.dat and reindex from scratch? (This is different than a -reindex=1, I call it an erase chain).

    I did confirm on two of my sancs, after an erasechain, I do agree with the hash above (IE nothing changed on my end before or after the erasechain, but it confirms the hash is correct as I agree on all my nodes, which is more than 6).

    Note that 'revivesanctuary' should work, if you were synced.  The problem with protx update is it does not update the deterministic.conf file.

    Have a good one,
    Rob
    Dear Rob,

    Thank you. All my wallets have the same hash. One of my sancs on port 40000 appears to be READY, is on the "masternodelist status" list as ENABLED but appears on the wallet as INVESTOR. All the rest are ENABLED.

    How do I use the "revivesanctuary" command to revive it?  Ah, it is exec revivesanc sancname.

    Blessings
    oncoapop



    « Last Edit: December 23, 2024, 01:27:34 AM by oncoapop »


    • Rob Andrews
    • Administrator

      • 4281


      • 97
      • June 05, 2017, 08:09:04 PM
      • Patmos, Island Of
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1614 on: December 23, 2024, 06:11:41 AM »
    Just an update:
    Chainz did upgrade their wallet and they are back up again:
    https://chainz.cryptoid.info/bbp/

    Their hash and height does agree with all my nodes (and their historical height to the one I posted a couple posts back).
    Oncoapop just let me know if yours does not agree with Chainz now or if there is a new issue.

    Does anyone want to test the new BBPRDP feature?  Its ready for release.
    This allows you to RDP to your home PC from a remote PC (using the BBP network as the conduit).  It is similar to GoToMyPC.com, except as a BBP service.

    PS I renotified Bololex to upgrade.

    PSII: Great news, we must be doing something right.  If you do an instantsend of 7 transactions in a row, (you can do this by
    sendtoaddress youraddress 1000) * 7, check out how 100% lock using IS now.  Also chainlocks are locking.  So we finally have a fully functional rebase and working wallet with sidechain capability.  There is a lot of other great news as well in the ecosystem, but I will finish the roadmap doc first.




    « Last Edit: December 23, 2024, 06:15:28 AM by Rob Andrews »


    • oncoapop
    • Full Member

      • 177


      • 18
      • October 23, 2018, 12:31:17 PM
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1615 on: December 25, 2024, 12:49:02 AM »
    Just an update:
    Chainz did upgrade their wallet and they are back up again:
    https://chainz.cryptoid.info/bbp/

    Their hash and height does agree with all my nodes (and their historical height to the one I posted a couple posts back).
    Oncoapop just let me know if yours does not agree with Chainz now or if there is a new issue.

    Does anyone want to test the new BBPRDP feature?  Its ready for release.
    This allows you to RDP to your home PC from a remote PC (using the BBP network as the conduit).  It is similar to GoToMyPC.com, except as a BBP service.

    PS I renotified Bololex to upgrade.

    PSII: Great news, we must be doing something right.  If you do an instantsend of 7 transactions in a row, (you can do this by
    sendtoaddress youraddress 1000) * 7, check out how 100% lock using IS now.  Also chainlocks are locking.  So we finally have a fully functional rebase and working wallet with sidechain capability.  There is a lot of other great news as well in the ecosystem, but I will finish the roadmap doc first.

    One sanc is still not in the ENABLED State although local command `masternode status` shows READY and the hash checks out...

    Anyway, that's for later.

    Wishing Rob and everyone at Biblepay a very Happy and Blessed Christmas!

    Blessings
    oncoapop


    • Rob Andrews
    • Administrator

      • 4281


      • 97
      • June 05, 2017, 08:09:04 PM
      • Patmos, Island Of
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1616 on: December 25, 2024, 09:01:28 AM »
    One sanc is still not in the ENABLED State although local command `masternode status` shows READY and the hash checks out...

    Anyway, that's for later.

    Wishing Rob and everyone at Biblepay a very Happy and Blessed Christmas!

    Blessings
    oncoapop


    Ok, I attached a screenshot of your sancs.
    I see that all are good except the one running on 40000.
    The issue on that one is when I telnet to it from my house it does not answer, hence the reason it stayed as investor.

    You have a Merry Christmas also.

    And please let me know if you are interested in testing the RDP feature.
    This network underlay based on OpenZiti network technology is decentralized, thats why Im excited to integrate it into biblepay.
    « Last Edit: December 25, 2024, 09:03:51 AM by Rob Andrews »


    • Rob Andrews
    • Administrator

      • 4281


      • 97
      • June 05, 2017, 08:09:04 PM
      • Patmos, Island Of
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1617 on: December 25, 2024, 10:20:19 AM »
    Since it is Christmas, and Merry Christmas to everyone as we celebrate Jesus Birth!

    Lets talk about Biblepay, where we are and where we can go in 2025-2026.  I am actively writing the roadmap backing doc so we will have more details very soon also but in the mean time lets discuss RDP, sidechains, gospel features, social media, and the move to be 100% decentralized in one year.

    First RDP.  The use case is this:  Some people have dynamic IPs, some are behind firewalls and some do not want to configure their network to allow traffic in on certain ports that would allow RDP (IE the ability for you to remote into your PC and control it, or into your work machine, or into your server and control it).

    This is where the BBP network comes in.  Using OpenZiti technology we can create a BiblePay mesh network that will allow you to remote in to your PC even without opening the extenal port 3389, and without having a public IP.  And what is exciting is this is decentralized.

    Before discussing the RDP tech, lets talk about how the software runs.  We have something called BBP Extensions, that can be launched from the wallet.  This is a list of BiblePay programs that can run on your machine, and as they are enhanced, the extensions automatically upgrade themselves.  So when you launch BBP Extensions, you really see a list of programs that we wrote that do specific functions and as releases occur they upgrade themselves.

    One of the programs is BBPRDP.

    In this case when you launch BBPRDP, the program will create a BBP keypair, one that designates the machines public network address (the BBP pubkey).  The private key is used to generate the public key and to store cold wallet funds for the service (currently the service is free, but we can do a pay-as-you-go plan in the future if this takes off, IE a certain amount say $5 a month or depending on the bytes sent over the BBP network, per month for use).

    You can then create a virtual network between two BBP addresses (you must own them both).  The bytes sent and received are encrypted, so there is no way for anyone on the network to see or decrypt those bytes (those are using the bbp account connected to the ziti overlay, which is private to you).

    The machine guid and public and private key are stored on your own machine.  The connection records are stored on our sidechain (so that the remote host can see and accept connections created by you).  Once the network conduit is started, those bytes are encrypted and sent through one volunteer sanctuary (one of the temples) and delivered to your private network.

    The latest release, Hamans-Hanging 0.21.9 now has BBPExtensions v1.26 in it.
    Note this was just released today.  In order to use this software, please re-download the windows wallet from www.biblepay.org | Wallet.
    Once you launch it you can then click "BBP Extensions" from the left menu.

    Wiki Guide:
    https://wiki.biblepay.org/RDP

    « Last Edit: December 25, 2024, 10:24:35 AM by Rob Andrews »


    • Rob Andrews
    • Administrator

      • 4281


      • 97
      • June 05, 2017, 08:09:04 PM
      • Patmos, Island Of
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1618 on: December 25, 2024, 11:39:00 AM »
    On the side chain and document storage and decentralized database:
    We still have a conduit to store all of our BBP documents (IE prophecy videos, images of Foundation activity such as childrens letters and wells, images of NFTs, and all of the user stored documents) on STORJ, which works.  We have a working sanctuary feature, where we can charge a rental fee for documents that are stored on the BBP chain as metadata (which points to the Storj bytes that store the image or doc), can be billed to the user monthly automatically.  All that works.
    NFTs are decentralized now.  Yes, the marketplace needs re-released on unchained, but it works again (working on that release currently) which allows you to edit your Native BBP NFTs and mark them as marketable, etc.

    A story about CockroachDB and PerconaDB.
    CockroachDB was "close".  We almost used cockroachdb to be our decentralized database to store BBP sidechain data.  However in the end, the problem with cockroachdb was it could be made to be fragile by nefarious Temples.  I went through a set of steps that could take it down and put it in a corrupt state by manipulating my timestamps and once a new temple comes on and syncs, if there is a minority of temples (IE their algorithm does not work like bitcoin supermajority rules), the whole cluster comes down.  That in itself is not a problem, however rebuilding the cluster is just too much work for an amateur (the user would need to be at the shell for hours to get the node back up).  I finally gave up on cockroachdb (and percona previously).  I decided we have to have our own decentralized db that is fault tolerant for even dummies (IE it just self heals under all conditions).  So we do have BBPDB 1.0 now and it is running on one Sanc, and now we need this whole release cycle so that unchained honors BBPDB, and all of our data (think Orphan  expenses, fundraising revenue, sidechain metadata, User records, everything that lives in Cockroach) is being migrated to BBPDB.  This BBPDB is 100% decentralized!  Note that I will not even be required after this is fully deployed in 2025!  So that is exciting for our future as well.

    Regarding social media, I feel like social.biblepay.org was excellent and we are actually missing something.
    Some of the features I would like BBP to thrive on is:
    - An enhanced user friendly prayer room that is "fun" to use.  I think our current attempts at this were "drab".
    - A social media system that is chain based.
    - A Prophecy room where we can take modern day prophets, like Amanda Grace, Julie Green, Elijah Streams prophets, etc, and make rooms for them.  We can sync their open source content to our prophet rooms.  We can add new prophecies in real time.
    - A "salvation Dashboard".  This allows you to keep track of salvations of your freinds, that you are working on.  Think current Status.  History of entries.

    A cryptocurrency index that is an investment vehicle for BBP that is "your keys your money".
    This is novel, because all of our old attempts at this were not really decentralized.
    We need to have volunteer market makers, one for each small upcoming and established crypto (my list is :  XRP, XLM, DOGE, BBP, BTC) as an example, and these market makers will be paid to "make a market" to run an AMM that will auto exchange XLM-BTC for example, but in a decentralized way.  What is the purpose.  If we had 4 market makers fro the above example (BBP not included), here is how this works:
    New User A comes in and wants to buy $500 of the BBP CryptoIndex. (BBPCI).
    When the trade is placed, 4 of the market makers execute $100 each of the above tickers and each of those result in the user receiving $100 of the native currency inside the *home wallet* private key.  Lets say you have a private key called "CPK".  The home wallet will derive private keys for these 5 currencies without the key material ever leaving your machine.  We can do that with a BBP extension.

    So what this means in effect, a church comes in and buys $1000 of the index, and in their home wallet, they now 5 cryptos equally weighted (with $200 being in BBP) held in their own *private key* that never left the wallet.  This is totally decentralized.  I really feel we can make this market making happen by offering sanctuaries a reward to be a market maker.  It can look something like this:
    Lets say you run sanctuary #1 and want to be an XRP market maker. The requirement is you deposit $1000 of XRP in your sanctuary private key and $1000 of BBP in your sanctuary private key.  Whenever a customer buys the index, you receive a market making fee of say 1% (or whatever the free market dictates to make this happen).  If they Bought BBP, you now have $100 more of BBP and $100 less of XRP, but you have $10 more of BBP as the reward for market making.  Something like that.  The algorithm in the BBP wallet would automatically AMM the trade so you dont have to actually do anything except replenish your balances when they get low.  Say XRP draws down to $100, then you need to sell BBP on the exchange and buy XRP on the exhchage to get these back to $1000 so our index stays in business. 

    From the user standpoint they get a decentralized index that offers crypto exposure into the future, legally without us needing to be a hedge fund.  So its useful to churches and our users.  Who have Fiat to protect, they can invest in the BBP index.  And its useful for people who want one click crypto exposure and we do the rest.  They just come in once every 90 days and buy $5k more.  And their balance is safe because its "their key their money", its stored in their home wallet and the key never leaves the machine.

    « Last Edit: December 25, 2024, 11:45:01 AM by Rob Andrews »


    • oncoapop
    • Full Member

      • 177


      • 18
      • October 23, 2018, 12:31:17 PM
      more
    Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
    « Reply #1619 on: December 29, 2024, 12:22:28 AM »
    Ahh, I didnt realize that, thanks.  I did see that they installed some type of auto trading bot (AMM) on bololex, (similar to the way SX used to work). 
    Maybe it is good for volume in the long run as people want to liquidate things.

    I hope they are going to stay in business.

    So on the bright side since Trump won, this will be a very good time for Crypto.
    All, keep praying that a Christian exchange owner steps up and lists us on a large exchange, for more volume.


    In the mean time Ill start putting the roadmap together.
    With the goal of outlining all of our ideas and where they are in a succinct way.

    It appears (at least for me) that https://bololex.com/ is completely down! Apparently, it has been previously flagged as inactive since Sep https://www.cryptowisser.com/exchange/bololex-exchange/

    There is no way to access any part of it. If anyone is in contact with their staff, please provide some update as if I am not wrong that appears to be BBP only exchange. Thank you.

    Blessings
    Oncoapop

    « Last Edit: December 29, 2024, 12:25:54 AM by oncoapop »