Bible Pay

Read 596820 times

  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Also, is the drop in fractional sanc rewards here to stay, or just a temporary drop? Thanks, and may God bless you all,
twinkle

1000 BBP

The Fractional Sanc ROI (I see its -10% right now, and just a month ago it was 78%), so that is dynamically calculated over the last moving 7 day average.
So its based on actual revenue (from running a sanc) minus actual expenses (of sponsoring an orphan).
So yeah it can easily turn positive again as soon as our market price goes about 20% higher (I guess thats .80 satoshi or so).

The nice thing about it even though its negative is you are still sponsoring an orphan for an 80% discount right now if you have a position....


7800 BBP


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
**** FRAUD/SCAM ALERT - TOKOK EXCHANGE ****


All, it has become apparent that Tokok has gone from 'reputable' to 'non-reputable' (and possibly a SCAM).

I'm sorry to report that this exchange refused to upgrade during our last mandatory upgrade (March 2021), and we have been trying to contact them over and over and they refuse to reply or upgrade.

More recently I've been monitoring the list of coins that are now in maintenance in TOKOK, and the list is growing signifigantly higher.
At this point I am starting to conclude that the owners of TOKOK are rug pulling the assets.

So please do not send BBP or any crypto over to TOKOK.  If you have funds at TOKOK I recommend withdrawing them (if they are non biblepay).  BBP is in maintenance so you can't withdraw actual bbp.

As far as a plan, I appeal to you to come together with me and pray for a resolution.  If we pray for TOKOK, a psalm like prayer, it could be good for them in the end if they repent and change their ways.  I also appeal to God with a resolution that they stop advertising false volume figures.  So in general you can pray for a positive resolution for the TOKOK debacle,  fair weights and measures in this space, and for the salvation of their owner(s).





*** USE CAUTION WITH DEFI (Decentralized Finance) ***



- Use extreme caution when investing in the DEFI space
- I recommend only sending BBP you can afford to lose until this space matures
- Start small and work up to a bigger number only if you feel comfortable
- Rug pulls exist in this space, where the owner of the contracts can pull the entire pools funds and run with all of it
- Use caution when exchanging your BBP to wrapped tokens, ensure the process works consistently many many times




7800 BBP
« Last Edit: June 15, 2021, 09:08:40 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Thanks to whoever donated 5MM to the Foundation on 6-9!

As always, we will use this in the most efficient manner possible.
For example to dig a new water well, etc.

We will always be transparent with our expenses and community projects (and everything else).



7800 BBP
« Last Edit: June 17, 2021, 09:25:21 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
*** All whales have been Paid (Dynamic Whale Stake Reconciliation - Final) ***


If you were owed a DWS balance in the future, your DWS payment has just been sent and you have been paid in full (height 277277).  Also, if there was any discrepancy between what you should have received in total (since inception) that was included in this payment.

Whale Stake Reconciliation Report:
Code: [Select]

19:47:29

whalestakefinalreport


19:47:43

{
  "Total DWS Quantity": 2060,
  "B5Bs3sxaw1VYNCdDRmzCDZDZT92mFmQSi3 burned": 250000,
  "B5Bs3sxaw1VYNCdDRmzCDZDZT92mFmQSi3 owed": 250522.3054,
  "B5Bs3sxaw1VYNCdDRmzCDZDZT92mFmQSi3 paid": 250522.3054,
  "B5Bs3sxaw1VYNCdDRmzCDZDZT92mFmQSi3 stake-count": 2,
  "B5Bs3sxaw1VYNCdDRmzCDZDZT92mFmQSi3 payment-count": 2,
  "B5Bs3sxaw1VYNCdDRmzCDZDZT92mFmQSi3 net owed": 0,
  "B5CxZ5A8M4Fbp56xZHZtcQRyyunKGZAr14 burned": 4000000,
  "B5CxZ5A8M4Fbp56xZHZtcQRyyunKGZAr14 owed": 4953886.6108,
  "B5CxZ5A8M4Fbp56xZHZtcQRyyunKGZAr14 paid": 1014489.1527,
  "B5CxZ5A8M4Fbp56xZHZtcQRyyunKGZAr14 stake-count": 4,
  "B5CxZ5A8M4Fbp56xZHZtcQRyyunKGZAr14 payment-count": 1,
  "B5CxZ5A8M4Fbp56xZHZtcQRyyunKGZAr14 net owed": 3939397.4581,x
  "B5Hc3HVfhWpNoK7NYhaip4idKDxDAqAPPN burned": 100000,
  "B5Hc3HVfhWpNoK7NYhaip4idKDxDAqAPPN owed": 101475.1527,
  "B5Hc3HVfhWpNoK7NYhaip4idKDxDAqAPPN paid": 101475.1527,
  "B5Hc3HVfhWpNoK7NYhaip4idKDxDAqAPPN stake-count": 1,
  "B5Hc3HVfhWpNoK7NYhaip4idKDxDAqAPPN payment-count": 1,
  "B5Hc3HVfhWpNoK7NYhaip4idKDxDAqAPPN net owed": 0,
  "B65pLo4i5wirnkq7kB5nwrVfU3ho6WtdUq burned": 973000,
  "B65pLo4i5wirnkq7kB5nwrVfU3ho6WtdUq owed": 975358.1377999998,
  "B65pLo4i5wirnkq7kB5nwrVfU3ho6WtdUq paid": 1075651.4378,
  "B65pLo4i5wirnkq7kB5nwrVfU3ho6WtdUq stake-count": 14,
  "B65pLo4i5wirnkq7kB5nwrVfU3ho6WtdUq payment-count": 16,
  "B65pLo4i5wirnkq7kB5nwrVfU3ho6WtdUq net owed": -100293.2999999999,
  "B67D4N9V2WHvY5GfgQjKwJhKLd6hZ1dRRD burned": 1000000,
  "B67D4N9V2WHvY5GfgQjKwJhKLd6hZ1dRRD owed": 1349383.1527,
  "B67D4N9V2WHvY5GfgQjKwJhKLd6hZ1dRRD paid": 1349383.1527,
  "B67D4N9V2WHvY5GfgQjKwJhKLd6hZ1dRRD stake-count": 1,
  "B67D4N9V2WHvY5GfgQjKwJhKLd6hZ1dRRD payment-count": 1,
  "B67D4N9V2WHvY5GfgQjKwJhKLd6hZ1dRRD net owed": 0,
  "B6Sguc8sudT3YZZgY4CLBFzaNpBBMAgEth burned": 1100000,
  "B6Sguc8sudT3YZZgY4CLBFzaNpBBMAgEth owed": 1434811.3054,
  "B6Sguc8sudT3YZZgY4CLBFzaNpBBMAgEth paid": 1434811.3054,
  "B6Sguc8sudT3YZZgY4CLBFzaNpBBMAgEth stake-count": 2,
  "B6Sguc8sudT3YZZgY4CLBFzaNpBBMAgEth payment-count": 2,
  "B6Sguc8sudT3YZZgY4CLBFzaNpBBMAgEth net owed": 0,
  "B6hM2heXgySePwGbsobXjQjQYDNTVksZGo burned": 3000000,
  "B6hM2heXgySePwGbsobXjQjQYDNTVksZGo owed": 3038172.4581,
  "B6hM2heXgySePwGbsobXjQjQYDNTVksZGo paid": 3038172.4581,
  "B6hM2heXgySePwGbsobXjQjQYDNTVksZGo stake-count": 3,
  "B6hM2heXgySePwGbsobXjQjQYDNTVksZGo payment-count": 3,
  "B6hM2heXgySePwGbsobXjQjQYDNTVksZGo net owed": 0,
  "B72qJt2JP5iEuX5XMF9qjNDLZHRhgFZVwK burned": 1000000,
  "B72qJt2JP5iEuX5XMF9qjNDLZHRhgFZVwK owed": 1150697.3054,
  "B72qJt2JP5iEuX5XMF9qjNDLZHRhgFZVwK paid": 1150697.3054,
  "B72qJt2JP5iEuX5XMF9qjNDLZHRhgFZVwK stake-count": 2,
  "B72qJt2JP5iEuX5XMF9qjNDLZHRhgFZVwK payment-count": 2,
  "B72qJt2JP5iEuX5XMF9qjNDLZHRhgFZVwK net owed": 0,
  "B76TkLSoZ5RCCLCgUJj6iajb4j6Ceo9Xdv burned": 17410000,
  "B76TkLSoZ5RCCLCgUJj6iajb4j6Ceo9Xdv owed": 22407741.90129999,
  "B76TkLSoZ5RCCLCgUJj6iajb4j6Ceo9Xdv paid": 14939386.0451,
  "B76TkLSoZ5RCCLCgUJj6iajb4j6Ceo9Xdv stake-count": 19,
  "B76TkLSoZ5RCCLCgUJj6iajb4j6Ceo9Xdv payment-count": 14,
  "B76TkLSoZ5RCCLCgUJj6iajb4j6Ceo9Xdv net owed": 7468355.856199997,x
  "B7AuLcF2yYgPzhtPJXdwR8EjNLz4C7GLyH burned": 50132597,
  "B7AuLcF2yYgPzhtPJXdwR8EjNLz4C7GLyH owed": 50763256.53629997,
  "B7AuLcF2yYgPzhtPJXdwR8EjNLz4C7GLyH paid": 50770064.61089997,
  "B7AuLcF2yYgPzhtPJXdwR8EjNLz4C7GLyH stake-count": 69,
  "B7AuLcF2yYgPzhtPJXdwR8EjNLz4C7GLyH payment-count": 70,
  "B7AuLcF2yYgPzhtPJXdwR8EjNLz4C7GLyH net owed": -6808.074599996209,
  "B7gYGopY6JmPsFSRB4wSxxadRMZ6NLL3yb burned": 6900000,
  "B7gYGopY6JmPsFSRB4wSxxadRMZ6NLL3yb owed": 6993424.536300012,
  "B7gYGopY6JmPsFSRB4wSxxadRMZ6NLL3yb paid": 7298585.683600013,
  "B7gYGopY6JmPsFSRB4wSxxadRMZ6NLL3yb stake-count": 69,
  "B7gYGopY6JmPsFSRB4wSxxadRMZ6NLL3yb payment-count": 73,
  "B7gYGopY6JmPsFSRB4wSxxadRMZ6NLL3yb net owed": -305161.1473000012,
  "B8WPDgxr5eNcqVXMXStAXurMphhsYyJiLd burned": 500000,
  "B8WPDgxr5eNcqVXMXStAXurMphhsYyJiLd owed": 523204.3054,
  "B8WPDgxr5eNcqVXMXStAXurMphhsYyJiLd paid": 523204.3054,
  "B8WPDgxr5eNcqVXMXStAXurMphhsYyJiLd stake-count": 2,
  "B8WPDgxr5eNcqVXMXStAXurMphhsYyJiLd payment-count": 2,
  "B8WPDgxr5eNcqVXMXStAXurMphhsYyJiLd net owed": 0,
  "B8mTjd78HkLBXDw31cCSs57XMQ24C6DTNK burned": 173000,
  "B8mTjd78HkLBXDw31cCSs57XMQ24C6DTNK owed": 176204.1527,
  "B8mTjd78HkLBXDw31cCSs57XMQ24C6DTNK paid": 176204.1527,
  "B8mTjd78HkLBXDw31cCSs57XMQ24C6DTNK stake-count": 1,
  "B8mTjd78HkLBXDw31cCSs57XMQ24C6DTNK payment-count": 1,
  "B8mTjd78HkLBXDw31cCSs57XMQ24C6DTNK net owed": 0,
  "B9LKjFjjSitSbHcPHKiHaRmU7nRcbQfHYA burned": 3000000,
  "B9LKjFjjSitSbHcPHKiHaRmU7nRcbQfHYA owed": 3038559.4581,
  "B9LKjFjjSitSbHcPHKiHaRmU7nRcbQfHYA paid": 3038559.4581,
  "B9LKjFjjSitSbHcPHKiHaRmU7nRcbQfHYA stake-count": 3,
  "B9LKjFjjSitSbHcPHKiHaRmU7nRcbQfHYA payment-count": 3,
  "B9LKjFjjSitSbHcPHKiHaRmU7nRcbQfHYA net owed": 0,
  "B9Mfu8vfQdnxpreUCEz2cyegX7j4cF4jV2 burned": 2004,
  "B9Mfu8vfQdnxpreUCEz2cyegX7j4cF4jV2 owed": 2061.4581,
  "B9Mfu8vfQdnxpreUCEz2cyegX7j4cF4jV2 paid": 2061.4581,
  "B9Mfu8vfQdnxpreUCEz2cyegX7j4cF4jV2 stake-count": 3,
  "B9Mfu8vfQdnxpreUCEz2cyegX7j4cF4jV2 payment-count": 3,
  "B9Mfu8vfQdnxpreUCEz2cyegX7j4cF4jV2 net owed": 0,
  "BAV71kHZepvKLBuAkCkYsGE4ior9SVGkdv burned": 20000,
  "BAV71kHZepvKLBuAkCkYsGE4ior9SVGkdv owed": 20791.1527,
  "BAV71kHZepvKLBuAkCkYsGE4ior9SVGkdv paid": 20791.1527,
  "BAV71kHZepvKLBuAkCkYsGE4ior9SVGkdv stake-count": 1,
  "BAV71kHZepvKLBuAkCkYsGE4ior9SVGkdv payment-count": 1,
  "BAV71kHZepvKLBuAkCkYsGE4ior9SVGkdv net owed": 0,
  "BAbnRdkyeyW9JC6j3BQrNr6osodsqdT9hW burned": 35000,
  "BAbnRdkyeyW9JC6j3BQrNr6osodsqdT9hW owed": 35108.1527,
  "BAbnRdkyeyW9JC6j3BQrNr6osodsqdT9hW paid": 35108.1527,
  "BAbnRdkyeyW9JC6j3BQrNr6osodsqdT9hW stake-count": 1,
  "BAbnRdkyeyW9JC6j3BQrNr6osodsqdT9hW payment-count": 1,
  "BAbnRdkyeyW9JC6j3BQrNr6osodsqdT9hW net owed": 0,
  "BAj9eAeV6dwBwikb4ccgkoptjQKgCeK9jB burned": 3000,
  "BAj9eAeV6dwBwikb4ccgkoptjQKgCeK9jB owed": 3010.1527,
  "BAj9eAeV6dwBwikb4ccgkoptjQKgCeK9jB paid": 3010.1527,
  "BAj9eAeV6dwBwikb4ccgkoptjQKgCeK9jB stake-count": 1,
  "BAj9eAeV6dwBwikb4ccgkoptjQKgCeK9jB payment-count": 1,
  "BAj9eAeV6dwBwikb4ccgkoptjQKgCeK9jB net owed": 0,
  "BAzYQgrU4akmjz9BrvNMjfgLxrQPNSxDxb burned": 10000,
  "BAzYQgrU4akmjz9BrvNMjfgLxrQPNSxDxb owed": 10032.1527,
  "BAzYQgrU4akmjz9BrvNMjfgLxrQPNSxDxb paid": 10032.1527,
  "BAzYQgrU4akmjz9BrvNMjfgLxrQPNSxDxb stake-count": 1,
  "BAzYQgrU4akmjz9BrvNMjfgLxrQPNSxDxb payment-count": 1,
  "BAzYQgrU4akmjz9BrvNMjfgLxrQPNSxDxb net owed": 0,
  "BB2H8K3d4SPL6te3LUiu637tKycAHJzAMo burned": 1000000,
  "BB2H8K3d4SPL6te3LUiu637tKycAHJzAMo owed": 1375585.1527,
  "BB2H8K3d4SPL6te3LUiu637tKycAHJzAMo paid": 1375585.1527,
  "BB2H8K3d4SPL6te3LUiu637tKycAHJzAMo stake-count": 1,
  "BB2H8K3d4SPL6te3LUiu637tKycAHJzAMo payment-count": 1,
  "BB2H8K3d4SPL6te3LUiu637tKycAHJzAMo net owed": 0,
  "BBPmp88ueiAjhMnx3EXgxfpDJzG9PFXDjj burned": 50000,
  "BBPmp88ueiAjhMnx3EXgxfpDJzG9PFXDjj owed": 50104.1527,
  "BBPmp88ueiAjhMnx3EXgxfpDJzG9PFXDjj paid": 100208.3027,
  "BBPmp88ueiAjhMnx3EXgxfpDJzG9PFXDjj stake-count": 1,
  "BBPmp88ueiAjhMnx3EXgxfpDJzG9PFXDjj payment-count": 2,
  "BBPmp88ueiAjhMnx3EXgxfpDJzG9PFXDjj net owed": -50104.15,
  "BCQRwo7G3LqUURdJoKrH1SSBVPh7S26B2q burned": 85733,
  "BCQRwo7G3LqUURdJoKrH1SSBVPh7S26B2q owed": 95357.52700000003,
  "BCQRwo7G3LqUURdJoKrH1SSBVPh7S26B2q paid": 95357.527,
  "BCQRwo7G3LqUURdJoKrH1SSBVPh7S26B2q stake-count": 10,
  "BCQRwo7G3LqUURdJoKrH1SSBVPh7S26B2q payment-count": 10,
  "BCQRwo7G3LqUURdJoKrH1SSBVPh7S26B2q net owed": 2.91038304567337e-011,
  "BCRTHVznu1kRyf6VdyShaUPrPNXXyQ3Koa burned": 1000000,
  "BCRTHVznu1kRyf6VdyShaUPrPNXXyQ3Koa owed": 1433999.1527,
  "BCRTHVznu1kRyf6VdyShaUPrPNXXyQ3Koa paid": 0,
  "BCRTHVznu1kRyf6VdyShaUPrPNXXyQ3Koa stake-count": 1,
  "BCRTHVznu1kRyf6VdyShaUPrPNXXyQ3Koa payment-count": 0,
  "BCRTHVznu1kRyf6VdyShaUPrPNXXyQ3Koa net owed": 1433999.1527,x
  "BCoF7usTkQLxggdKrTqDDWnsRVMWBNvcfG burned": 610000,
  "BCoF7usTkQLxggdKrTqDDWnsRVMWBNvcfG owed": 813618.3054,
  "BCoF7usTkQLxggdKrTqDDWnsRVMWBNvcfG paid": 0,
  "BCoF7usTkQLxggdKrTqDDWnsRVMWBNvcfG stake-count": 2,
  "BCoF7usTkQLxggdKrTqDDWnsRVMWBNvcfG payment-count": 0,
  "BCoF7usTkQLxggdKrTqDDWnsRVMWBNvcfG net owed": 813618.3054,x
  "BCps2L7D5tWY3rRsSFDRtNcCX9UxtwzAUs burned": 230000,
  "BCps2L7D5tWY3rRsSFDRtNcCX9UxtwzAUs owed": 234171.527,
  "BCps2L7D5tWY3rRsSFDRtNcCX9UxtwzAUs paid": 208277.3743,
  "BCps2L7D5tWY3rRsSFDRtNcCX9UxtwzAUs stake-count": 10,
  "BCps2L7D5tWY3rRsSFDRtNcCX9UxtwzAUs payment-count": 9,
  "BCps2L7D5tWY3rRsSFDRtNcCX9UxtwzAUs net owed": 25894.15270000001,x
  "BDwoudPjXciK94pxA3bztGbEnT3sfC9UK6 burned": 10000,
  "BDwoudPjXciK94pxA3bztGbEnT3sfC9UK6 owed": 10095.1527,
  "BDwoudPjXciK94pxA3bztGbEnT3sfC9UK6 paid": 10095.1527,
  "BDwoudPjXciK94pxA3bztGbEnT3sfC9UK6 stake-count": 1,
  "BDwoudPjXciK94pxA3bztGbEnT3sfC9UK6 payment-count": 1,
  "BDwoudPjXciK94pxA3bztGbEnT3sfC9UK6 net owed": 0,
  "BENwgjhYYHpJVSVqheX3BdctEtjQCXYwsB burned": 100,
  "BENwgjhYYHpJVSVqheX3BdctEtjQCXYwsB owed": 100.1527,
  "BENwgjhYYHpJVSVqheX3BdctEtjQCXYwsB paid": 115.4227,
  "BENwgjhYYHpJVSVqheX3BdctEtjQCXYwsB stake-count": 1,
  "BENwgjhYYHpJVSVqheX3BdctEtjQCXYwsB payment-count": 2,
  "BENwgjhYYHpJVSVqheX3BdctEtjQCXYwsB net owed": -15.27,
  "BEnG96E4bTH9JDXhnDUFMnZ6k1XCnMXq8o burned": 100,
  "BEnG96E4bTH9JDXhnDUFMnZ6k1XCnMXq8o owed": 100.1527,
  "BEnG96E4bTH9JDXhnDUFMnZ6k1XCnMXq8o paid": 100.1527,
  "BEnG96E4bTH9JDXhnDUFMnZ6k1XCnMXq8o stake-count": 1,
  "BEnG96E4bTH9JDXhnDUFMnZ6k1XCnMXq8o payment-count": 1,
  "BEnG96E4bTH9JDXhnDUFMnZ6k1XCnMXq8o net owed": 0,
  "BF16ULUzvFbw7ukzhunvxoqqx4SEKFon15 burned": 1010000,
  "BF16ULUzvFbw7ukzhunvxoqqx4SEKFon15 owed": 1375440.3054,
  "BF16ULUzvFbw7ukzhunvxoqqx4SEKFon15 paid": 11341.1527,
  "BF16ULUzvFbw7ukzhunvxoqqx4SEKFon15 stake-count": 2,
  "BF16ULUzvFbw7ukzhunvxoqqx4SEKFon15 payment-count": 1,
  "BF16ULUzvFbw7ukzhunvxoqqx4SEKFon15 net owed": 1364099.1527,x
  "BFQVf7KbTAGfZFaPiHSwU4qAUd5Cwmy4CU burned": 400100,
  "BFQVf7KbTAGfZFaPiHSwU4qAUd5Cwmy4CU owed": 518960.4580999999,
  "BFQVf7KbTAGfZFaPiHSwU4qAUd5Cwmy4CU paid": 100.1527,
  "BFQVf7KbTAGfZFaPiHSwU4qAUd5Cwmy4CU stake-count": 3,
  "BFQVf7KbTAGfZFaPiHSwU4qAUd5Cwmy4CU payment-count": 1,
  "BFQVf7KbTAGfZFaPiHSwU4qAUd5Cwmy4CU net owed": 518860.3054,x
  "BGXPtbhygDwXMUeZLf7DioHpkGE6fqNtzy burned": 1000000,
  "BGXPtbhygDwXMUeZLf7DioHpkGE6fqNtzy owed": 1409599.1527,
  "BGXPtbhygDwXMUeZLf7DioHpkGE6fqNtzy paid": 1409599.1527,
  "BGXPtbhygDwXMUeZLf7DioHpkGE6fqNtzy stake-count": 1,
  "BGXPtbhygDwXMUeZLf7DioHpkGE6fqNtzy payment-count": 1,
  "BGXPtbhygDwXMUeZLf7DioHpkGE6fqNtzy net owed": 0,
  "BGXZXBdBQKdX4rDZrnzxBR5ojyo1FgyRHa burned": 1000000,
  "BGXZXBdBQKdX4rDZrnzxBR5ojyo1FgyRHa owed": 1433999.1527,
  "BGXZXBdBQKdX4rDZrnzxBR5ojyo1FgyRHa paid": 0,
  "BGXZXBdBQKdX4rDZrnzxBR5ojyo1FgyRHa stake-count": 1,
  "BGXZXBdBQKdX4rDZrnzxBR5ojyo1FgyRHa payment-count": 0,
  "BGXZXBdBQKdX4rDZrnzxBR5ojyo1FgyRHa net owed": 1433999.1527,x
  "BGbXQ3X87AYuXAjTS5uTocf9iiXCCfb7cB burned": 1000000,
  "BGbXQ3X87AYuXAjTS5uTocf9iiXCCfb7cB owed": 1063073.1527,
  "BGbXQ3X87AYuXAjTS5uTocf9iiXCCfb7cB paid": 1063073.1527,
  "BGbXQ3X87AYuXAjTS5uTocf9iiXCCfb7cB stake-count": 1,
  "BGbXQ3X87AYuXAjTS5uTocf9iiXCCfb7cB payment-count": 1,
  "BGbXQ3X87AYuXAjTS5uTocf9iiXCCfb7cB net owed": 0,
  "BGcsQpSpxfK5QctJvWrp7dAJjPAt2Uq8XE burned": 1000000,
  "BGcsQpSpxfK5QctJvWrp7dAJjPAt2Uq8XE owed": 1394499.1527,
  "BGcsQpSpxfK5QctJvWrp7dAJjPAt2Uq8XE paid": 1394499.1527,
  "BGcsQpSpxfK5QctJvWrp7dAJjPAt2Uq8XE stake-count": 1,
  "BGcsQpSpxfK5QctJvWrp7dAJjPAt2Uq8XE payment-count": 1,
  "BGcsQpSpxfK5QctJvWrp7dAJjPAt2Uq8XE net owed": 0,
  "BGz1NwRvia3hzCqp4LurrHZAnJqc6BaaxA burned": 184588,
  "BGz1NwRvia3hzCqp4LurrHZAnJqc6BaaxA owed": 197302.527,
  "BGz1NwRvia3hzCqp4LurrHZAnJqc6BaaxA paid": 197302.527,
  "BGz1NwRvia3hzCqp4LurrHZAnJqc6BaaxA stake-count": 10,
  "BGz1NwRvia3hzCqp4LurrHZAnJqc6BaaxA payment-count": 10,
  "BGz1NwRvia3hzCqp4LurrHZAnJqc6BaaxA net owed": 0,
  "BJNekzwfcVyxRPQeJRbYYYdWKxbfPAsoqd burned": 1000000,
  "BJNekzwfcVyxRPQeJRbYYYdWKxbfPAsoqd owed": 1414099.1527,
  "BJNekzwfcVyxRPQeJRbYYYdWKxbfPAsoqd paid": 0,
  "BJNekzwfcVyxRPQeJRbYYYdWKxbfPAsoqd stake-count": 1,
  "BJNekzwfcVyxRPQeJRbYYYdWKxbfPAsoqd payment-count": 0,
  "BJNekzwfcVyxRPQeJRbYYYdWKxbfPAsoqd net owed": 1414099.1527,x
  "BJgCwqKR24pLDTC8biLC3rjkmiMsanbdWa burned": 230676,
  "BJgCwqKR24pLDTC8biLC3rjkmiMsanbdWa owed": 249054.8955000049,
  "BJgCwqKR24pLDTC8biLC3rjkmiMsanbdWa paid": 190146.3956000035,
  "BJgCwqKR24pLDTC8biLC3rjkmiMsanbdWa stake-count": 1165,
  "BJgCwqKR24pLDTC8biLC3rjkmiMsanbdWa payment-count": 953,
  "BJgCwqKR24pLDTC8biLC3rjkmiMsanbdWa net owed": 58908.49990000142,x
  "BJxfXErViKkpgDMaqzQNyATMJjEVd7VFck burned": 24200,
  "BJxfXErViKkpgDMaqzQNyATMJjEVd7VFck owed": 26409.06889999999,
  "BJxfXErViKkpgDMaqzQNyATMJjEVd7VFck paid": 26409.0689,
  "BJxfXErViKkpgDMaqzQNyATMJjEVd7VFck stake-count": 7,
  "BJxfXErViKkpgDMaqzQNyATMJjEVd7VFck payment-count": 7,
  "BJxfXErViKkpgDMaqzQNyATMJjEVd7VFck net owed": -3.637978807091713e-012,
  "BLBjptmhNbKcrXaWDDYm6fEQnTwnDuceT1 burned": 500000,
  "BLBjptmhNbKcrXaWDDYm6fEQnTwnDuceT1 owed": 651700.1527,
  "BLBjptmhNbKcrXaWDDYm6fEQnTwnDuceT1 paid": 651700.1527,
  "BLBjptmhNbKcrXaWDDYm6fEQnTwnDuceT1 stake-count": 1,
  "BLBjptmhNbKcrXaWDDYm6fEQnTwnDuceT1 payment-count": 1,
  "BLBjptmhNbKcrXaWDDYm6fEQnTwnDuceT1 net owed": 0,
  "BLENRYgVPwzfsrJoJNbvC537qMHsCVyeFU burned": 34492175.1,
  "BLENRYgVPwzfsrJoJNbvC537qMHsCVyeFU owed": 36211175.33329993,
  "BLENRYgVPwzfsrJoJNbvC537qMHsCVyeFU paid": 36923295.17979997,
  "BLENRYgVPwzfsrJoJNbvC537qMHsCVyeFU stake-count": 179,
  "BLENRYgVPwzfsrJoJNbvC537qMHsCVyeFU payment-count": 186,
  "BLENRYgVPwzfsrJoJNbvC537qMHsCVyeFU net owed": -712119.8465000391,
  "BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip burned": 100000,
  "BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip owed": 105633.1527,
  "BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip paid": 211266.3027,
  "BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip stake-count": 1,
  "BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip payment-count": 2,
  "BLpAqYhjuxJAfTC9yJBUxzUyNfDFfiduip net owed": -105633.15,
  "BLt1htJPLeQx62ufQ9xmRR5zsnSLbhNEWX burned": 1757973,
  "BLt1htJPLeQx62ufQ9xmRR5zsnSLbhNEWX owed": 1780235.9851,
  "BLt1htJPLeQx62ufQ9xmRR5zsnSLbhNEWX paid": 1781634.7724,
  "BLt1htJPLeQx62ufQ9xmRR5zsnSLbhNEWX stake-count": 13,
  "BLt1htJPLeQx62ufQ9xmRR5zsnSLbhNEWX payment-count": 13,
  "BLt1htJPLeQx62ufQ9xmRR5zsnSLbhNEWX net owed": -1398.787299999967,
  "BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U burned": 4100000,
  "BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U owed": 4504786.0689,
  "BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U paid": 5001586.0662,
  "BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U stake-count": 7,
  "BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U payment-count": 7,
  "BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U net owed": -496799.9972999999,
  "BMDb6Z4mmKmmKXDAhBCPW5XXpEqzT1Q1PV burned": 88000,
  "BMDb6Z4mmKmmKXDAhBCPW5XXpEqzT1Q1PV owed": 88258.97020000007,
  "BMDb6Z4mmKmmKXDAhBCPW5XXpEqzT1Q1PV paid": 88359.72020000003,
  "BMDb6Z4mmKmmKXDAhBCPW5XXpEqzT1Q1PV stake-count": 26,
  "BMDb6Z4mmKmmKXDAhBCPW5XXpEqzT1Q1PV payment-count": 30,
  "BMDb6Z4mmKmmKXDAhBCPW5XXpEqzT1Q1PV net owed": -100.7499999999563,
  "BMFexP5awPZRLr5eD5W9oXEQ4paE3eVuaj burned": 1000000,
  "BMFexP5awPZRLr5eD5W9oXEQ4paE3eVuaj owed": 1399723.1527,
  "BMFexP5awPZRLr5eD5W9oXEQ4paE3eVuaj paid": 0,
  "BMFexP5awPZRLr5eD5W9oXEQ4paE3eVuaj stake-count": 1,
  "BMFexP5awPZRLr5eD5W9oXEQ4paE3eVuaj payment-count": 0,
  "BMFexP5awPZRLr5eD5W9oXEQ4paE3eVuaj net owed": 1399723.1527,x
  "BN1wgJYBL2VUCaCP3TYE6nHB9PNwFA2Gz8 burned": 167809794,
  "BN1wgJYBL2VUCaCP3TYE6nHB9PNwFA2Gz8 owed": 170008438.6927008,
  "BN1wgJYBL2VUCaCP3TYE6nHB9PNwFA2Gz8 paid": 146771912.7071005,
  "BN1wgJYBL2VUCaCP3TYE6nHB9PNwFA2Gz8 stake-count": 201,
  "BN1wgJYBL2VUCaCP3TYE6nHB9PNwFA2Gz8 payment-count": 187,
  "BN1wgJYBL2VUCaCP3TYE6nHB9PNwFA2Gz8 net owed": 23236525.98560032,x
  "BNaUGAyKSSzo7DYTz5UYwxbzDJBXMWJgV3 burned": 11102158,
  "BNaUGAyKSSzo7DYTz5UYwxbzDJBXMWJgV3 owed": 11264143.7486,
  "BNaUGAyKSSzo7DYTz5UYwxbzDJBXMWJgV3 paid": 12709961.3886,
  "BNaUGAyKSSzo7DYTz5UYwxbzDJBXMWJgV3 stake-count": 18,
  "BNaUGAyKSSzo7DYTz5UYwxbzDJBXMWJgV3 payment-count": 24,
  "BNaUGAyKSSzo7DYTz5UYwxbzDJBXMWJgV3 net owed": -1445817.639999995,
  "BNz6GSdpjGHDb3JxzE45pKxbwdi1GWTqSs burned": 300000,
  "BNz6GSdpjGHDb3JxzE45pKxbwdi1GWTqSs owed": 300942.4581,
  "BNz6GSdpjGHDb3JxzE45pKxbwdi1GWTqSs paid": 300942.4581,
  "BNz6GSdpjGHDb3JxzE45pKxbwdi1GWTqSs stake-count": 3,
  "BNz6GSdpjGHDb3JxzE45pKxbwdi1GWTqSs payment-count": 3,
  "BNz6GSdpjGHDb3JxzE45pKxbwdi1GWTqSs net owed": 0,
  "BPChFuc6wFRUEjDHaX4sZyHdqUeXj7QRgQ burned": 2009621,
  "BPChFuc6wFRUEjDHaX4sZyHdqUeXj7QRgQ owed": 2034550.4581,
  "BPChFuc6wFRUEjDHaX4sZyHdqUeXj7QRgQ paid": 2034550.4581,
  "BPChFuc6wFRUEjDHaX4sZyHdqUeXj7QRgQ stake-count": 3,
  "BPChFuc6wFRUEjDHaX4sZyHdqUeXj7QRgQ payment-count": 3,
  "BPChFuc6wFRUEjDHaX4sZyHdqUeXj7QRgQ net owed": 0,
  "BPHr5ooeyin5gE4EvRaGLurmG2jaumUzjp burned": 6310000,
  "BPHr5ooeyin5gE4EvRaGLurmG2jaumUzjp owed": 6378392.527000001,
  "BPHr5ooeyin5gE4EvRaGLurmG2jaumUzjp paid": 6378291.696999999,
  "BPHr5ooeyin5gE4EvRaGLurmG2jaumUzjp stake-count": 10,
  "BPHr5ooeyin5gE4EvRaGLurmG2jaumUzjp payment-count": 11,
  "BPHr5ooeyin5gE4EvRaGLurmG2jaumUzjp net owed": 100.8300000019372,x
  "BPwCkuAy7p9bDeuus19GhpBEmGa14t9TnA burned": 1000000,
  "BPwCkuAy7p9bDeuus19GhpBEmGa14t9TnA owed": 1421999.1527,
  "BPwCkuAy7p9bDeuus19GhpBEmGa14t9TnA paid": 0,
  "BPwCkuAy7p9bDeuus19GhpBEmGa14t9TnA stake-count": 1,
  "BPwCkuAy7p9bDeuus19GhpBEmGa14t9TnA payment-count": 0,
  "BPwCkuAy7p9bDeuus19GhpBEmGa14t9TnA net owed": 1421999.1527,x
  "BPzegTQtqKfyF9ii3PMSekU87hMKckiEci burned": 450000,
  "BPzegTQtqKfyF9ii3PMSekU87hMKckiEci owed": 457110.7635,
  "BPzegTQtqKfyF9ii3PMSekU87hMKckiEci paid": 457110.7635,
  "BPzegTQtqKfyF9ii3PMSekU87hMKckiEci stake-count": 5,
  "BPzegTQtqKfyF9ii3PMSekU87hMKckiEci payment-count": 5,
  "BPzegTQtqKfyF9ii3PMSekU87hMKckiEci net owed": 0,
  "BQKpAthM8pyYWpZfEvWRvQ7pZrecV3qZZw burned": 1500000,
  "BQKpAthM8pyYWpZfEvWRvQ7pZrecV3qZZw owed": 1525510.4581,
  "BQKpAthM8pyYWpZfEvWRvQ7pZrecV3qZZw paid": 1525510.4581,
  "BQKpAthM8pyYWpZfEvWRvQ7pZrecV3qZZw stake-count": 3,
  "BQKpAthM8pyYWpZfEvWRvQ7pZrecV3qZZw payment-count": 3,
  "BQKpAthM8pyYWpZfEvWRvQ7pZrecV3qZZw net owed": 0,
  "BQLmLFZreTaAcNgnnzfb3w2JyNyiZjgeNb burned": 1000,
  "BQLmLFZreTaAcNgnnzfb3w2JyNyiZjgeNb owed": 1044.1527,
  "BQLmLFZreTaAcNgnnzfb3w2JyNyiZjgeNb paid": 1044.1527,
  "BQLmLFZreTaAcNgnnzfb3w2JyNyiZjgeNb stake-count": 1,
  "BQLmLFZreTaAcNgnnzfb3w2JyNyiZjgeNb payment-count": 1,
  "BQLmLFZreTaAcNgnnzfb3w2JyNyiZjgeNb net owed": 0,
  "BQXj5kV9LVUZGF4ipFCRmkzBbZu366grJt burned": 109326430.11,
  "BQXj5kV9LVUZGF4ipFCRmkzBbZu366grJt owed": 135027537.3091004,
  "BQXj5kV9LVUZGF4ipFCRmkzBbZu366grJt paid": 97169983.15190017,
  "BQXj5kV9LVUZGF4ipFCRmkzBbZu366grJt stake-count": 133,
  "BQXj5kV9LVUZGF4ipFCRmkzBbZu366grJt payment-count": 100,
  "BQXj5kV9LVUZGF4ipFCRmkzBbZu366grJt net owed": 37857554.15720028,x
  "BRtbY3jJ32Zs4ZzfqXXqrbNh5oyyV8jZfL burned": 27339000,
  "BRtbY3jJ32Zs4ZzfqXXqrbNh5oyyV8jZfL owed": 40718387.42829999,
  "BRtbY3jJ32Zs4ZzfqXXqrbNh5oyyV8jZfL paid": 17705626.6797,
  "BRtbY3jJ32Zs4ZzfqXXqrbNh5oyyV8jZfL stake-count": 29,
  "BRtbY3jJ32Zs4ZzfqXXqrbNh5oyyV8jZfL payment-count": 11,
  "BRtbY3jJ32Zs4ZzfqXXqrbNh5oyyV8jZfL net owed": 23012760.74859999,x
  "BSZ9Ag8qpEp893nnmawFzw59c1CKBt8xjR burned": 125000,
  "BSZ9Ag8qpEp893nnmawFzw59c1CKBt8xjR owed": 130619.3054,
  "BSZ9Ag8qpEp893nnmawFzw59c1CKBt8xjR paid": 101690.1527,
  "BSZ9Ag8qpEp893nnmawFzw59c1CKBt8xjR stake-count": 2,
  "BSZ9Ag8qpEp893nnmawFzw59c1CKBt8xjR payment-count": 1,
  "BSZ9Ag8qpEp893nnmawFzw59c1CKBt8xjR net owed": 28929.15270000001,x
  "BTbgCzc3YogmVvBkH6SoN9iJ3G31oxy14M burned": 160100,
  "BTbgCzc3YogmVvBkH6SoN9iJ3G31oxy14M owed": 163420.6108,
  "BTbgCzc3YogmVvBkH6SoN9iJ3G31oxy14M paid": 163420.6108,
  "BTbgCzc3YogmVvBkH6SoN9iJ3G31oxy14M stake-count": 4,
  "BTbgCzc3YogmVvBkH6SoN9iJ3G31oxy14M payment-count": 4,
  "BTbgCzc3YogmVvBkH6SoN9iJ3G31oxy14M net owed": 0,
  "Grand Owed": 524496878.5620123,
  "Grand Paid": 422292306.3070009
}



Note, if you have a negative balance you can keep it as a gift from BiblePay.


DWS has been replaced with UTXO staking. 
In our next mandatory upgrade, we have Trust Wallet integration that will make UTXO staking very easy (it will work from the UI), and we now support 10 coins! 
We are also releasing the Biblepay Cryptocurrency Index, which is an index that tracks these 10 coins.




7800 BBP


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
BiblePay Core Wallet
1.6.2.4 - Mandatory Upgrade for Entire Network at height 278014


- https://github.com/biblepay/biblepay/blob/master/changelog.md (See changes from 1.6.0.1 - 1.6.2.4)
- New Montserrat font (smooth font for non windows OS), new CSS background
- LLMQ Instant Send + ChainLocks
- BiblePay Portfolio Builder (Retirement Accounts) with Ten major cryptocurrency staking options in "Misc | Portfolio Builder" including Stellar and Ripple!
   b.  Add Ripple and Stellar support for UTXO staking (v1.0), and modify getpin for this also
   c.   Add Trust Wallet Integration (Allows the user to use ONE trusted mobile wallet for all of their crypto, including our 10 currencies and earn UTXO rewards on the portfolio)
   d.  Add the BiblePay Cryptocurrency Index - this is an index of 10 major currencies.  To view it, click Misc | Portfolio Builder.
- Block Subsidy changes:  Increased Portfolio Builder emissions and Less for Sanctuaries : Sanctuaries (20%), monthly budget (5%),  UTXO (50%), RANDOMX (25%), with a calling for New Users
  b. Enhance listutxostakes to actually be JSON
- NFT 1.0 (Non-Fungible Tokens) and NFT marketplace.  Dedicated marketplace for Orphans and for Digital Goods
   b. Add NFT Auctions (Buy It Now Amount and Reserve Price)
- Referral Codes 1.0 (allows user to generatereferralcode, listattachedreferralcodes, checkreferralcode, claimreferralcode).  This type is used for viral PR.
  b. Note: referralrewards bonuses decay over 2 years similar to RAC (this keeps our emissions schedule perfectly aligned and phases out viral rewards over time).
- BiblePay Greeting Cards and phrase protected virtual gift cards - to use click Misc | Greeting Cards
   b.  Add Christmas, Easter and Kittens Greeting cards.  Make the greeting card fields customizable by the user.
   c.  Add CSV Greeting Card generate process
- BBP Transaction Fees have increased to small levels from dust levels (should be about 1 bbp per 1K of size now)
- Added Tier2 payment for non POOS sancs. This gives tier2 a 250bbp reward to run a sanc that does not sponsor an orphan, simply for network stability and voting rights
- Recaption Duffs to Pence (This gives a name to our microcoins) (Purely in honor of the archaic currency).
- Coin Control: Display gift icon when it is a gift from a gift card
  b. Auto unlock the gift if they run 'acceptgift', secondly, lock gifts on wallet boot by default (this prevents gifts from being spent by the giver).
  c.  Add gift key to givers wallet so they can recall the gift if it is never redeemed.
- Add Alpha Invoicing and Payments and Statements v1.0 (This is mostly integrated but still disabled and in alpha).
- Unchained feature: Add DSQL to server side (this supports an insert and a read) in alpha.  This feature is still in Alpha (see our unchained project: https://unchained.biblepay.org/).
   b. Add rest pushtx, getaddressutxo. This is also for unchained, allowing a decentralized client to relay a tx, allowing a c# consumer to query utxos, and query DSQL data.
- Add rpc getvalue command - Allows you to convert from BBP to USD
- Remove Randomx calls on MAC making it an SPV client (this allows us to notarize the mac software)
  b. Update build instructions for mac cross compiling
- Add erasechain UI (to wallet tools)



1.  All sanctuaries need to be re-created (because we have transitioned to DM blocks, and our old sancs were created inside non-dm blocks).
    a.  You must re-create your sanctuary as a deterministic sanc.  Please see this guide:
         https://wiki.biblepay.org/EasySanc
    b.  Please contact cameroon-one with your new public key (copy the orphan bio from the Sanctuaries UI page and send to cameroon) so that your bio can be updated.
2.  All leaderboard UTXOs need to be re-created as Portfolio Builder positions.  Note that we now monitor Cryptocurrency Addresses (in contrast to individual utxos).
    a.   We still use pins.  Since the leaderboard is empty, I will explain how to jumpstart some position easily and then you can move to the more elaborate positions later.
    b.   To easily create a BBP position, simply click Misc | Portfolio Builder.  Select BBP from the Coin Ticker dropdown.  Populate an Amount.  Click Send.  BBP will allocate that much into your position (which is equivalent to our old easybbpstake command).  Then you will be in the leaderboard.
3.  When you upgrade, if you are running QT, you will need to click Tools | Erase Chain and restart (this will start with a clean chain).  If you are running a full node, start with -erasechain=1.
     The reason why is we have added the timestampindex and the addressindex as a default option to our chain which consumes two more database index positions therefore a rescan is required.  The address index is Required for all sanctuaries.  (If you do not erase the chain you will go out of sync).
4.  Both pools need to upgrade immediately (these DM blocks are not backwards compatible).  Foundation.biblepay.org has upgraded already and fun has been notified.
XMRig miners are not affected as the miner will seamlessly mine through the mandatory upgrade.
5.  Note to self compiled nodes:  You will need to cd depends, and rebuild the dependencies, rerun autogen.sh and rebuild.  (We have a new set of dependencies in this branch).  Follow Build Biblepay for more information:  https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt





Guides:

NFTs:
https://wiki.biblepay.org/NFT

NFT Marketplace:
http://foundation.biblepay.org/NFTBrowse

NFT Orphan Sponsorship Area:
http://foundation.biblepay.org/NFTOrphans

Direct Mail Delivery and Greeting Cards:
https://wiki.biblepay.org/Direct_Mail_Delivery

Greeting Cards:
https://wiki.biblepay.org/Greeting_Cards

Creating a DM Sanc from Scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

Upgrading a Sanctuary to Deterministic Mode:
https://wiki.biblepay.org/EasySanc

Referral Codes for creating Viral PR and Referral Gift Codes:
https://wiki.biblepay.org/Referrals

Portfolio Builder:
https://wiki.biblepay.org/Portfolio_Builder




Press Release #1:

https://foundation.biblepay.org/Press/PressRelease1624.htm





7800 BBP
« Last Edit: June 23, 2021, 07:49:39 AM by Rob Andrews »


  • Budinga
  • Jr. Member

    • 27


    • 3
    • January 28, 2020, 02:21:29 AM
    more
BiblePay Core Wallet
1.6.2.4 - Mandatory Upgrade for Entire Network at height 278014


- https://github.com/biblepay/biblepay/blob/master/changelog.md (See changes from 1.6.0.1 - 1.6.2.4)
- New Montserrat font (smooth font for non windows OS), new CSS background
- LLMQ Instant Send + ChainLocks
- BiblePay Portfolio Builder (Retirement Accounts) with Ten major cryptocurrency staking options in "Misc | Portfolio Builder" including Stellar and Ripple!
   b.  Add Ripple and Stellar support for UTXO staking (v1.0), and modify getpin for this also
   c.   Add Trust Wallet Integration (Allows the user to use ONE trusted mobile wallet for all of their crypto, including our 10 currencies and earn UTXO rewards on the portfolio)
   d.  Add the BiblePay Cryptocurrency Index - this is an index of 10 major currencies.  To view it, click Misc | Portfolio Builder.
- Block Subsidy changes:  Increased Portfolio Builder emissions and Less for Sanctuaries : Sanctuaries (20%), monthly budget (5%),  UTXO (50%), RANDOMX (25%), with a calling for New Users
  b. Enhance listutxostakes to actually be JSON
- NFT 1.0 (Non-Fungible Tokens) and NFT marketplace.  Dedicated marketplace for Orphans and for Digital Goods
   b. Add NFT Auctions (Buy It Now Amount and Reserve Price)
- Referral Codes 1.0 (allows user to generatereferralcode, listattachedreferralcodes, checkreferralcode, claimreferralcode).  This type is used for viral PR.
  b. Note: referralrewards bonuses decay over 2 years similar to RAC (this keeps our emissions schedule perfectly aligned and phases out viral rewards over time).
- BiblePay Greeting Cards and phrase protected virtual gift cards - to use click Misc | Greeting Cards
   b.  Add Christmas, Easter and Kittens Greeting cards.  Make the greeting card fields customizable by the user.
   c.  Add CSV Greeting Card generate process
- BBP Transaction Fees have increased to small levels from dust levels (should be about 1 bbp per 1K of size now)
- Added Tier2 payment for non POOS sancs. This gives tier2 a 250bbp reward to run a sanc that does not sponsor an orphan, simply for network stability and voting rights
- Recaption Duffs to Pence (This gives a name to our microcoins) (Purely in honor of the archaic currency).
- Coin Control: Display gift icon when it is a gift from a gift card
  b. Auto unlock the gift if they run 'acceptgift', secondly, lock gifts on wallet boot by default (this prevents gifts from being spent by the giver).
  c.  Add gift key to givers wallet so they can recall the gift if it is never redeemed.
- Add Alpha Invoicing and Payments and Statements v1.0 (This is mostly integrated but still disabled and in alpha).
- Unchained feature: Add DSQL to server side (this supports an insert and a read) in alpha.  This feature is still in Alpha (see our unchained project: https://unchained.biblepay.org/).
   b. Add rest pushtx, getaddressutxo. This is also for unchained, allowing a decentralized client to relay a tx, allowing a c# consumer to query utxos, and query DSQL data.
- Add rpc getvalue command - Allows you to convert from BBP to USD
- Remove Randomx calls on MAC making it an SPV client (this allows us to notarize the mac software)
  b. Update build instructions for mac cross compiling
- Add erasechain UI (to wallet tools)



1.  All sanctuaries need to be re-created (because we have transitioned to DM blocks, and our old sancs were created inside non-dm blocks).
    a.  You must re-create your sanctuary as a deterministic sanc.  Please see this guide:
         https://wiki.biblepay.org/EasySanc
    b.  Please contact cameroon-one with your new public key (copy the orphan bio from the Sanctuaries UI page and send to cameroon) so that your bio can be updated.
2.  All leaderboard UTXOs need to be re-created as Portfolio Builder positions.  Note that we now monitor Cryptocurrency Addresses (in contrast to individual utxos).
    a.   We still use pins.  Since the leaderboard is empty, I will explain how to jumpstart some position easily and then you can move to the more elaborate positions later.
    b.   To easily create a BBP position, simply click Misc | Portfolio Builder.  Select BBP from the Coin Ticker dropdown.  Populate an Amount.  Click Send.  BBP will allocate that much into your position (which is equivalent to our old easybbpstake command).  Then you will be in the leaderboard.
3.  When you upgrade, if you are running QT, you will need to click Tools | Erase Chain and restart (this will start with a clean chain).  If you are running a full node, start with -erasechain=1.
     The reason why is we have added the timestampindex and the addressindex as a default option to our chain which consumes two more database index positions therefore a rescan is required.  The address index is Required for all sanctuaries.  (If you do not erase the chain you will go out of sync).
4.  Both pools need to upgrade immediately (these DM blocks are not backwards compatible).  Foundation.biblepay.org has upgraded already and fun has been notified.
XMRig miners are not affected as the miner will seamlessly mine through the mandatory upgrade.
5.  Note to self compiled nodes:  You will need to cd depends, and rebuild the dependencies, rerun autogen.sh and rebuild.  (We have a new set of dependencies in this branch).  Follow Build Biblepay for more information:  https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt





Guides:

NFTs:
https://wiki.biblepay.org/NFT

NFT Marketplace:
http://foundation.biblepay.org/NFTBrowse

NFT Orphan Sponsorship Area:
http://foundation.biblepay.org/NFTOrphans

Direct Mail Delivery and Greeting Cards:
https://wiki.biblepay.org/Direct_Mail_Delivery

Greeting Cards:
https://wiki.biblepay.org/Greeting_Cards

Creating a DM Sanc from Scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

Upgrading a Sanctuary to Deterministic Mode:
https://wiki.biblepay.org/EasySanc

Referral Codes for creating Viral PR and Referral Gift Codes:
https://wiki.biblepay.org/Referrals

Portfolio Builder:
https://wiki.biblepay.org/Portfolio_Builder




Press Release:
This will be discussed shortly.

Loving the new THEME oh and of course the features :).

Thanks Rob, for the great work and effort you put in to this coin.

1000 BBP


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Thank you for being here, Mr. Budinga.


7800 BBP


  • Budinga
  • Jr. Member

    • 27


    • 3
    • January 28, 2020, 02:21:29 AM
    more
Thank you for being here, Mr. Budinga.

You are most welcome my friend.

1000 BBP


  • sntjo2847
  • Jr. Member

    • 46


    • 3
    • May 21, 2021, 02:55:13 PM
    more
BiblePay Core Wallet
1.6.2.4 - Mandatory Upgrade for Entire Network at height 278014


Hi Rob,

These seem like a lot of really useful upgrades. Thank you for all the hard work you have put into it!

May I ask though why this upgrade needed to be done in such a rushed manner? World breaking changes should have more time given to upgrade unless there is a very good reason why it has to be done right away. It seems like this could have been set to a block height that was more than 1 day away. I am not able to check the forum every single day.

Also, there is no build posted on github. And no email was sent out about the mandatory rush upgrade.

Blessings,
Jo


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Hi Rob,

These seem like a lot of really useful upgrades. Thank you for all the hard work you have put into it!

May I ask though why this upgrade needed to be done in such a rushed manner? World breaking changes should have more time given to upgrade unless there is a very good reason why it has to be done right away. It seems like this could have been set to a block height that was more than 1 day away. I am not able to check the forum every single day.

Also, there is no build posted on github. And no email was sent out about the mandatory rush upgrade.

Blessings,
Jo
1) Thank you Jo!
2) It had to be done in a rushed manner this time because the very first block of the new client had to be deterministic (that is, a DM block), and our old sancs were not compatible with those blocks.  That means that there was a very short time limit available to upgrade our sancs and make the daily GSC block (and we made it) - those happen every 205 blocks!.  So in this release I had our 3 exchanges put us in maintenance, and then the moment we were in maintenance I started the upgrade process.  One other unique issue with this upgrade is our biblepay-classic client (running in both pools) would *not* allow the miners to mine any DM block due to a classic branch constraint - they are not backward compatible.  So we also had a pool deadline also.  That led to the decision that it had to be done this way.
3) Note that you did not really lose any revenue, because xmrig miners were able to transition through the height and continue earning (even if your biblepay client went out of sync)-- as the pool keeps your share of work in the database.  Also, since the leaderboard is empty you have plenty of space to create portfolio positions now  (we only have 5 people in there right now).
4) I did tweet this out to every forum user and I posted it on bitcointalk also.  Its possible those emails are lagging however (unless you are not subscribed).
5) I think this is a one-time unique situation.  We always strive for a 7 day notice during upgrades, and will in the future.  We are on the new codebase now, so things are back to normal!
6) The github was updated (see build biblepay)  https://github.com/biblepay/biblepay; The code was checked in, but you are referring to the mandatory release in the releases list; I deliberately did not check that record in yet because I needed to know everything worked out -- and it appears everything worked.  That will be checked in either tonight or tomorrow.






7800 BBP
« Last Edit: June 24, 2021, 08:03:30 AM by Rob Andrews »


  • sntjo2847
  • Jr. Member

    • 46


    • 3
    • May 21, 2021, 02:55:13 PM
    more
Hi Rob,

2) That would seem like a reason it had to be on a DM block, which could have been set to a DM block 1 week away, which would allow everyone to update in the meantime. I may be missing something though.
3) Thank you, I realized that after the wallet finished updating. The blockchain explorer is apparently not updated, so it was not showing there.
4) Where would I see such messages? I did not see any message, and there are none in the My Messages tab. I am subscribed to the update emails.
5) Glad to hear such a short upgrade time window is not the norm. I think though that the more stable blockchains normally have longer than 1 week though.
6) I would suggest that if there is a mandatory upgrade it should be posted to github immediately. If it needs another update due to an issue, it can be updated.

Is there a guide to the trust wallet integration? It is not clear how to set it up. I found Portfolio Builder, which mentions Trust wallet integration, but then says you can use any wallet, which is how it was before the update.

Regarding the press release: I think it is a great idea to have a press release. However, the website/wiki should be updated before it is released in order for it to be effective. That way new users are not turned away by confusing/conflicting information. As it stands now, the press release points you to the post about the update, which does not explain how it works. The website does not have the information either, and still points to DWS which was disabled a while ago. And PODC, which was disabled even further ago. I know I spent many hours trying to get PODC working only to discover it was disabled.

I hope my comments / suggestions are not taken the wrong way. I like BiblePay and think you have spent a lot of time improving it. I am especially looking forward to the wallet integration. I want BiblePay to be successful and think that the new user experience is currently a significant hinderance.

Blessings,
Jo


  • MIP
  • Sr. Member

    • 368


    • 47
    • February 13, 2018, 11:55:52 AM
    more
Thank you Rob for the hard work. I published notes in Telegram, Discord, Twitter and LinkedIn

Users are asking about when the SouthXchange wallet is going back online.

On my side, I added some entries in the investment portfolio section and it works nicely!

I hope these exciting new features catch the attention of many new users.


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Hi Rob,

2) That would seem like a reason it had to be on a DM block, which could have been set to a DM block 1 week away, which would allow everyone to update in the meantime. I may be missing something though.
3) Thank you, I realized that after the wallet finished updating. The blockchain explorer is apparently not updated, so it was not showing there.
4) Where would I see such messages? I did not see any message, and there are none in the My Messages tab. I am subscribed to the update emails.
5) Glad to hear such a short upgrade time window is not the norm. I think though that the more stable blockchains normally have longer than 1 week though.
6) I would suggest that if there is a mandatory upgrade it should be posted to github immediately. If it needs another update due to an issue, it can be updated.

Is there a guide to the trust wallet integration? It is not clear how to set it up. I found Portfolio Builder, which mentions Trust wallet integration, but then says you can use any wallet, which is how it was before the update.

Regarding the press release: I think it is a great idea to have a press release. However, the website/wiki should be updated before it is released in order for it to be effective. That way new users are not turned away by confusing/conflicting information. As it stands now, the press release points you to the post about the update, which does not explain how it works. The website does not have the information either, and still points to DWS which was disabled a while ago. And PODC, which was disabled even further ago. I know I spent many hours trying to get PODC working only to discover it was disabled.

I hope my comments / suggestions are not taken the wrong way. I like BiblePay and think you have spent a lot of time improving it. I am especially looking forward to the wallet integration. I want BiblePay to be successful and think that the new user experience is currently a significant hinderance.

Blessings,
Jo

Hi Jo--

On #2, the problem with that method is you are making the assumption that if everyone is ready to upgrade in the future block, that everything will go well on that particular day.  I chose to start the upgrade as soon as we were in maintenance, in case we needed another emergency update in between.  Without causing any arguments over this, the real deal killer was that our classic chain was already in dip3 mode, and no new pool blocks could be mined in the pool unless they were upgraded FIRST.  That set an extraordinary problem ahead of us meaning we had to upgrade both pools first in order to mine, and in order to mine new clients already had to be running (as users).  So no, dash would not have had this problem because they were not in dip3 mode when they upgraded. 

On #3, I had to wait for my internal green light before releasing the Mandatory notice for BX's and exchanges.  Its going out right now.

On #4, there are two ways.  First be sure you have Notify clicked on this thread.  Our foundation.biblepay.org will Tweet you an upgrade notice if you are subscribed here.  The other way is triggered *after* the mandatory is checked in to github.  So I recommend both until we start our social media platform.

On #5,  I agree with you here, but to clarify my position, I was referring to exchange minimums.  Basically we should give a 30 day upgrade notice to our users in general, but a 10 day exchange minimum to our partners.  We do have a history of doing this, but we were not organized well this quarter.  I like to set a very accurate date in testnet as we close on our testing (and we did, but again I didnt KNOW that our pools would cause an emergency honestly until it became an emergency).  I think what we should do is add a phase at the end of testing to start to notify everyone that the upgrade is *coming* in only 21 more days .. etc.. We can definitely do a better job in that area;  thank you for the suggestion.

On #6, Yes, we always will in all normal circumstances.  In this case it was not possible.  A mandatory upgrade in github triggers our partners to upgrade and we did not want that in phase #1.






7800 BBP
« Last Edit: June 24, 2021, 10:09:17 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 4147


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Thank you Rob for the hard work. I published notes in Telegram, Discord, Twitter and LinkedIn

Users are asking about when the SouthXchange wallet is going back online.

On my side, I added some entries in the investment portfolio section and it works nicely!

I hope these exciting new features catch the attention of many new users.

Thanks.

As far as SX,  we will be releasing the github release later today and then our block explorers and SX will be notified to upgrade; I would tell them ~48 more hours.



7800 BBP


  • sntjo2847
  • Jr. Member

    • 46


    • 3
    • May 21, 2021, 02:55:13 PM
    more
Hi Rob,

Ah ok, that explains it. Thank you.

I put a notice at the top of the wiki PODC, PODC Setup, DWS pages about them being disabled so it does not cause confusion for new users. And the UTXO Mining page about Portfolio Builder. The Main wiki page needs updated with new Block reward, remove exchanges that are not recommended, etc. I do not have access to update it. Same with pages on the website.

Blessings,
Jo

Hi Jo--

On #2, the problem with that method is you are making the assumption that if everyone is ready to upgrade in the future block, that everything will go well on that particular day.  I chose to start the upgrade as soon as we were in maintenance, in case we needed another emergency update in between.  Without causing any arguments over this, the real deal killer was that our classic chain was already in dip3 mode, and no new pool blocks could be mined in the pool unless they were upgraded FIRST.  That set an extraordinary problem ahead of us meaning we had to upgrade both pools first in order to mine, and in order to mine new clients already had to be running (as users).  So no, dash would not have had this problem because they were not in dip3 mode when they upgraded. 

Ill be back..