Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - oncoapop

Pages: [1] 2 3 4 5 6 7 8 ... 12
1
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


2
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

3
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




4
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

5
    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

    6
    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

    7
    SX BBP Wallet is up and synced and my withdrawal was successful!
    Thank you!
    Blessings
    oncoapop

    Yeah, I DMed all 3 of my contacts at SX on discord, and left them a support message also but did not get a reply.
    https://discord.com/channels/665836598767910913/948553815844610078

    Ill keep checking on them over the period as well as Cameroon One still needs to liquidate one superblock.

    8
    Thank you for the heads up!
    Is there a way to get them to restart their BBP wallet so I can withdraw my BBP instead of selling it and crashing the price further...

    Cheers
    oncoapop

    Happy new Years, Loyal BiblePay enthusiasts!

    Note that unfortunately, SouthXChange is going out of business:

    Please withdraw your coins.

    I think our main exchange will be Bololex now:
    https://bololex.com/trading/?symbol=BBP-USDT

    I just tested a withdraw on bololex, and it worked, so we appear to be good!

    Good luck and God bless you.

    9
    Thank you for that. Looks okay.

    The temple appears to be receiving 16,830 bbp for when it is ENABLED but if for some reason they are out of sync, their payment is not halved but appears to be only 841 bbp (ie half a sanctuary's). Is this expected and correct behaviour?

    Since the temple is the only BBP wallet running on the server, we have no way of knowing when it is out of sync, At least if there were 10 sancs as a temple, I could calculate the consensus and reset the lagging sancs. The only that we know a temple may be lagging if it fails to receive the full payment amount.

    Thank you for looking into this.

    Blessings
    oncoapop


    BiblePay - 0.17.4.8 - Mandatory Upgrade for Entire Network


    - Added checkpoint @ 440K
    - Filter out misbehaving sanc peers in LLMQ for one duration
    - Prevent division by zero in LLMQ class
    - Require Sancs to be on protoversion >= 70790
    - Enable ReviveSanctuaries batch job for Altars and Sancs but not Temples
    - Edit release name to be 'Latter Rain'


    Github Release:

    https://github.com/biblepay/biblepay/releases/tag/0.17.4.8

    10
    Active Discussions / Re: Nov 2023 - Latter Rain Release
    « on: September 21, 2023, 12:01:10 AM »
    Dear Rob,

    Oncoapop reporting :

    getblockhash 192206
    021ad04526fd5f76ec03a3cdfb5bd26fbc6d84695c2aac95c3ab1df431f388a4
     
    getnewaddress
    yRBCwJyobxyjXmjFm1qiCWirxiKsTHsmrk

    getblockcount
    192628

    testnet wallet.dat backed up

    Blessings
    Oncoapop




    11
    The Linux binaries in biblepay-lin64.zip appear to only have  BiblePay.BMSD


     
    BiblePay 0.17.4.2
    Mandatory Upgrade for Sanctuaries and Home Controller Wallets


    - Add more robust POSE ban for investors (keep our quorums intact) and keep investor payments at 50%
    - Add Investor pose status to masternodelist UI and masternodelist rpc command
    - Added exec versionreport so we can see the % that have upgraded

    ** Note: On your self compiled sanctuary, you can simply type "git pull origin master && make -j4" to upgrade.  Then stop and restart all instances.

    12
    Thank you, Rob. Perfect timing: I am going to try to resync using blocks.zip since the chain on 2/10 of my sancs on the temple has been halted >12 hours.

    Output of `getblockcount` for each sanc
    1.   444333
    2.   444333
    3.   444333
    4.   444086 <---
    5.   444333
    6.   444333
    7.   444333
    8.   444333
    9.   444159 <---
    10.   444333

    Mode(s) of the dataset: 444333

    Sancs 4 and 9 are halted since 7:36 this morning. Time now 20:45

    However, the 2 sancs in question report being ok:

    Sanc 4
    {
      "AssetID": 999,
      "AssetName": "MASTERNODE_SYNC_FINISHED",
      "AssetStartTime": 1693214535,
      "Attempt": 0,
      "IsBlockchainSynced": true,
      "IsSynced": true
    }
    and     
        "PoSePenalty": 0,
        "PoSeBanHeight": -1,
        "revocationReason": 0,

    Sanc 9
    {
      "AssetID": 999,
      "AssetName": "MASTERNODE_SYNC_FINISHED",
      "AssetStartTime": 1693213491,
      "Attempt": 0,
      "IsBlockchainSynced": true,
      "IsSynced": true
    }
    and
        "PoSePenalty": 0,
        "PoSeBanHeight": -1,
        "revocationReason": 0,

    I only checked as you previously mentioned a similar issue. I don't remember any of my sancs going out of sync with each other previously, but I did not have this many sancs before and certainly not all on one VPS.

    Furthermore, Sanc 4 mined blocks at 00:35 and 12:16 (the former maybe it was in sync but the later, I recorded that it was AFTER it was halted and lagged by at least 50 block at 7:35) and Sanc 9 mined blocks at 07:34 and 18:35 (I am sure that both times, Sanc 9 was out of sync as I recorded it was lagging at least by 50 blocks at 08:16).

    Is there any mechanism to ensure sancs in a temple are in sync with one another? I caught this as I have a script (attached) to find the mode (most common ie consensus) height of the sancs in the temple and then flag any that deviate from this by at least 50 blocks.

    Blessings,
    oncoapop




    Sanctuary Block Sync feature


    If you have the need to sync BBP blocks fast, you can download the chain from https://biblepay.org/blocks.zip.

    (Useful if you have more than one sanc for example, and you want to spawn multiple copies of the chain to data directories).

    13
    Active Discussions / Re: March 2023 - Red Sea Release
    « on: August 19, 2023, 11:15:31 PM »
    Firstly are you on MainNet or TestNet? If MainNet which version? Biblepay Core version v0.17.3.8-Red-Sea?

    I'm facing a problem the balance doesn't change from -1.00 no matter how many times refreshed.

    14
    Active Discussions / Re: March 2023 - Red Sea Release
    « on: August 17, 2023, 10:13:19 PM »
    Sent 1,000 BP. If you like to test, my BBP phone number is 12065310541.

    B7o95DhHoPW9rTuBWAeFTKxAJzesvEXWbA

    15
    Active Discussions / Re: March 2023 - Red Sea Release
    « on: August 13, 2023, 10:59:16 PM »
    Do you need real BBP or tBBP? How much do you need to test?
    Kindly send me your BBP address.

    Blessings
    oncoapop

    Can I get few bbp for sms test?

    Pages: [1] 2 3 4 5 6 7 8 ... 12