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

Well the signifigance of Maroon and Gold is 'The blood of Jesus' and the breastplate of righteousness; but the answer to your question is I'm standardizing the CSS so we have less colors all over the place, so I combined the tables yesterday to be one color.

I do like Green but I also need to make sure we have as few colors as possible in the theme.

Ah ok, good to know it does not mean something bad happened.

While I understand the reason for the color by significance now, the Maroon and Gold is much harsher on the eyes (for me, possibly others too), than the green and black.

Ok, I will test this also in a few minutes, but that shouldnt be possible;
Please dont buy any NFTs for the next hour anyone.

Ok.
I received 55,000 bbp on my wallet.
Thanks Rob
Fredo

1000 BBP

Ok.
I received 55,000 bbp on my wallet.
Thanks Rob
Fredo

Hi Fredo,  Sure, but yes, I will explain in full detail when Im done debugging.

So I set my CPK to empty and found we do require the user to have a populated CPK (to buy an NFT) and it must be a valid Prod address:
NFT Buy Error


Sorry, you must populate your 'Christian-Public-Key address', inside your Account Settings (go to Account Edit from the left menu).
You can find this address in your biblepay core home PC wallet in File | Receiving Addresses.
This allows you to transfer ownership of your store bought NFTs to be sent to your home wallet.

So that part is actually working;  I will explain the rest of the issue in detail in 30 mins.

Thanks for your patience.


8100 BBP

Ah ok, good to know it does not mean something bad happened.

While I understand the reason for the color by significance now, the Maroon and Gold is much harsher on the eyes (for me, possibly others too), than the green and black.

I agree, the lime and black is much more consistent for the site; I reverted it back.


8100 BBP

I agree, the lime and black is much more consistent for the site; I reverted it back.

Great! Thank you, it is much nicer to look at now.

Hi Rob, The block 279802 seems to be the point where an issue has appeared. The block on bbp explorer does not match the block shown through my wallet (1.6.2.8 ). All blocks before match, all blocks after do not match.

As an addition to this:

This appears to be serious as it appears there are 2 divergent chains!

Each mining pool is on a different divergent chain.  The foundation pool is on the chain that the bbp explorer is on, but the miningpool.fun pool is on the chain that my wallet (1.6.2.8 ) is on.

As an addition to this:

This appears to be serious as it appears there are 2 divergent chains!

Each mining pool is on a different divergent chain.  The foundation pool is on the chain that the bbp explorer is on, but the miningpool.fun pool is on the chain that my wallet (1.6.2.8 ) is on.

Chainlocks just started a little while back, let me look into this, always something.


8100 BBP

Chainlocks just started a little while back, let me look into this, always something.

Although I see some disturbing figures on one of my sancs that I am now looking into, Im not seeing Fun on a different chain; Their height matches foundation's height and matches my home node height and matches chainz height;  what makes you say Fun is on the wrong chain?  (Also the blocks solved count matches-- if they were on a different chain my pool would get all the blocks).




8100 BBP

Although I see some disturbing figures on one of my sancs that I am now looking into, Im not seeing Fun on a different chain; Their height matches foundation's height and matches my home node height and matches chainz height;  what makes you say Fun is on the wrong chain?  (Also the blocks solved count matches-- if they were on a different chain my pool would get all the blocks).

Because my wallet says Fun got blocks that the explorer says that the Foundation got. Using 279822 as an example:
block explorer 279822 show the foundation pool
My wallet shows the Fun pool (cut for size):

Code: [Select]

19:03:39
getblockhash 279822
19:03:39
dff72c4279cc4edc62f9247946bf5fdcbc7a47abe86b1ce6bcb46fcb06f0e5ba

Code: [Select]

{
  "hash": "dff72c4279cc4edc62f9247946bf5fdcbc7a47abe86b1ce6bcb46fcb06f0e5ba",
  "confirmations": 20,
  "size": 2660,
  "height": 279822,
  "version": 1342177312,
  "versionHex": "50000020",
  "merkleroot": "49566211772f64323aace1d5c6c63b80a4f0c4134cc1b6c4e4acedf0f0c87786",
  "tx": [
    {
      "txid": "a9b06485fe04205e7cf1f4a2ebc8f6bd49ee4ae98f1719a76c61401f07b3ea35",
      "version": 3,
      "type": 5,
      "size": 228,
      "locktime": 0,
      "vin": [
        {
          "coinbase": "030e450404406ce060",
          "sequence": 4294967295
        }
      ],
      "vout": [
        {
          "value": 857.17139665,
          "valueSat": 85717139665,
          "n": 0,
          "scriptPubKey": {
            "asm": "OP_DUP OP_HASH160 e6b9429962942c52702ca99f1a6734166e60b05d OP_EQUALVERIFY OP_CHECKSIG",
            "hex": "76a914e6b9429962942c52702ca99f1a6734166e60b05d88ac",
            "reqSigs": 1,
            "type": "pubkeyhash",
            "addresses": [
              "BRV2xwLJnRsMRMBG6uWyhvwghHFBjKHib7"
            ]
          },
          "message": "<VER>v1.6.2.8-Harvest</VER>"
        },
        {
          "value": 1645.51881254,
          "valueSat": 164551881254,
          "n": 1,
          "scriptPubKey": {
            "asm": "OP_DUP OP_HASH160 921f7a86129adea658fd2de28ea7f2ec248c229e OP_EQUALVERIFY OP_CHECKSIG",
            "hex": "76a914921f7a86129adea658fd2de28ea7f2ec248c229e88ac",
            "reqSigs": 1,
            "type": "pubkeyhash",
            "addresses": [
              "BHmhytrL8fqC7NQEfGGi828WZmcGbqN9mv"
            ]
          },
          "message": ""
        }
      ],

I think that Fun realized and fixed it for a few reasons:
1. They are now showing up on the explorer as mining blocks.
2. A while ago the computer I had on the Fun pool stopped getting work from it and failed over to the foundation pool. It is back on the Foundation pool again.
3. The divergent chain appears to have gone away. Meaning my wallet now shows the same as the explorer. That block I mentioned in my last post (279822) now shows a different hash in my wallet than before. It now matches the explorer.

Code: [Select]

20:19:46
getblockhash 279822
20:19:46
1f54f8930f2335add5b5b673ab50c48b9fe55372031c31ebf19bc8214f6deb4d

2. A while ago the computer I had on the Fun pool stopped getting work from it and failed over to the foundation pool. It is back on the Foundation pool again.

I wish I could edit posts. This should have said "It is back on the Fun pool again now."

I think that Fun realized and fixed it for a few reasons:
1. They are now showing up on the explorer as mining blocks.
2. A while ago the computer I had on the Fun pool stopped getting work from it and failed over to the foundation pool. It is back on the Foundation pool again.
3. The divergent chain appears to have gone away. Meaning my wallet now shows the same as the explorer. That block I mentioned in my last post (279822) now shows a different hash in my wallet than before. It now matches the explorer.

Code: [Select]

20:19:46
getblockhash 279822
20:19:46
1f54f8930f2335add5b5b673ab50c48b9fe55372031c31ebf19bc8214f6deb4d

Yeah, I think you are right;  I think fun was mining on a fork for a few hours (this is based on a discrepancy I found in my graph between 5AM and 8AM).
And apparentely your node was subject to the same fork but it recovered.

On a side note, I was able to pull up the tx that Fun sent to your node while they were on a fork, and it got saved as 'off the main chain' on my node (IE height -1).

I think this has something to do with chainlocks.  Chainlocks 'tried' to start 400 blocks ago but as of last night didnt start yet (this is because of the quorum settings which is normal).
I noticed this morning, I didnt see a chainlock yet at the tip.  Then a couple hours later I saw some chainlocks 5 blocks behind.

Im starting to think that there were not enough participants in the quorum to lock to the tip.
Right now I see all the blocks locked up to tip -1 (getblock blocknumber) look for chainklock:true.

So far all Ive found is one of my servers (server 6) is not synced; so let me resync those nodes now and then I will continue to look at this.

Im making the early assumption that our network shifted over from RX only consensus to RX + Chainlocks this morning and we experienced a 'large hump', but thats all I know so far.


8100 BBP

BiblePay - 1.6.2.9 - Leisure Upgrade

- Fix Buy NFT process flags (on buy side)


** Note:  This is a leisure upgrade.  This code fixes the Buy NFT process.  Therefore, before you buy any NFT, please upgrade first.


8100 BBP

Ok.
I received 55,000 bbp on my wallet.
Thanks Rob
Fredo

Alrighty, going back to this issue, so far this affected Fredo, Pat and Rob (we all tried to buy NFTs).

First of all the explanation:
Although we tested this successfully in TestNet, during the code merges and the rebase, some flags dealing with NFTs (on the buy side) got reverted back to original values.
So now we need a leisure upgrade (thankfully, it does not affect the server side or the exchanges).

Anyway, this makes it impossible to buy an NFT in a version prior to 1629 (the NFT will be paid for and then go back into the marketplace).

As far as these 3 nfts in question, I refunded the users funds in the pool, so now you can buy the NFT again (once you upgrade!).

I have a very important test case also, for whoever buys the next NFT:  Please, once you buy the NFT, check the High-quality URL.  This URL should have the actual deliverable in it.  You can see it in "My NFTs" in the pool.  (Do this on a *new* purchase so we can test end to end in prod).


8100 BBP

*** Amazon Storefront Integration is ready for testing in Alpha on MainNet ***

https://forum.biblepay.org/index.php?topic=779.msg11164#msg11164


8100 BBP