Bible Pay

Recent Posts

Pages: [1] 2 3 4 5 6 7 8 ... 10
1
      Verify that you are in the masternodelist, even if it is the wrong IP, you should be in the list
I'm not in the list
The machine is reachable from outside network by telnet on por 41000 and the demon is in listen

15:36:04
getnetworkinfo


15:36:04
{
  "version": 2209,
  "buildversion": "v0.22.9 Great-Awakening",
  "subversion": "/BiblePay Core:0.22.9/",
  "protocolversion": 70784,
  "localservices": "0000000000000c05",
  "localservicesnames": [
    "NETWORK",
    "BLOOM",
    "NETWORK_LIMITED",
    "HEADERS_COMPRESSED"
  ],
  "localrelay": true,
  "timeoffset": 1,
  "networkactive": true,
  "connections": 10,
  "inboundconnections": 0,
  "outboundconnections": 10,
  "mnconnections": 4,
  "inboundmnconnections": 0,
  "outboundmnconnections": 4,
  "socketevents": "select",
  "networks": [
    {
      "name": "ipv4",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "ipv6",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "onion",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "i2p",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    }
  ],
  "relayfee": 0.00000700,
  "incrementalfee": 0.00000700,
  "localaddresses": [
    {
      "address": "*.*.*.66",
      "port": 40000,
      "score": 4
    }
  ],
  "warnings": ""
}


Netstat command from windows shell/cmd

TCP    192.168.68.208:40000   verunix:56860          ESTABLISHED
TCP    192.168.68.208:40000   ip109:45890            ESTABLISHED
TCP    192.168.68.208:40000   vmi2331614:40804       ESTABLISHED
TCP    192.168.68.208:40000   seven:51086            ESTABLISHED
TCP    192.168.68.208:40000   seven:53327            ESTABLISHED
TCP    192.168.68.208:40000   vmi690434:45594        ESTABLISHED
TCP    192.168.68.208:40000   108.180.46.33:44924    ESTABLISHED
TCP    192.168.68.208:40000   108.180.46.33:58966    ESTABLISHED
TCP    192.168.68.208:40000   vmi2331596:56606       ESTABLISHED
TCP    192.168.68.208:40000   vmi2331597:36226       ESTABLISHED
TCP    192.168.68.208:40000   174-47-79-220:62306    TIME_WAIT
TCP    192.168.68.208:40000   vmi674906:58334        ESTABLISHED



11:44:35
exec upgradesanc AltareSanto 0


11:44:35
{
  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary AltareSanto with IP 93.55.252.66:40000 with TXID ec3e3f040b87aa37ed761b2446c49bda2c78f1517577e2e7bfe344270c580f67",
  "bls_public_key": "8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5",
  "bls_private_key": "01bc22c2b16bbc52e1705844935a79b6068342fccb942adb00e972d8063b36ac",
  "pro_reg_txid": "0300010001609e5ce9b57500890998887c7c6a050994e4c9ca104ac28336f3c8a5f22b1aa80000000000feffffff016cd2f505000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000670f580c2744e3bfe7e2777551f1782cda9bc446241b76ed37aa870b043f3eec0000000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0e8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5a0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588acd33796ed5126898ff5b10412b40b5f14a0c8f07889575fdeefa55abe12a2f8b900",
  "pro_reg_collateral_address": "BHn32VamZjQKE3iAtNWeN3LoDDsNQAr8yM",
  "pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|c36781721e1a114bf020f549e286da08375d473c77edbec707fbbf37b8d83061",
  "pro_reg_signature": "H9q/GPzVkA02knhPSv9EZb0T/nUcQF8vP5E/63qqmXOUVg9vIOnDuWTaEHocal2zc9qrlF56sZ3vY110Z2ouaXE=",
  "sent_txid": ""
}

11:44:35
exec upgradesanc AltareSanto 0


11:44:35
{
  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary AltareSanto with IP 93.55.252.66:40000 with TXID ec3e3f040b87aa37ed761b2446c49bda2c78f1517577e2e7bfe344270c580f67",
  "bls_public_key": "8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5",
  "bls_private_key": "01bc22c2b16bbc52e1705844935a79b6068342fccb942adb00e972d8063b36ac",
  "pro_reg_txid": "0300010001609e5ce9b57500890998887c7c6a050994e4c9ca104ac28336f3c8a5f22b1aa80000000000feffffff016cd2f505000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000670f580c2744e3bfe7e2777551f1782cda9bc446241b76ed37aa870b043f3eec0000000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0e8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5a0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588acd33796ed5126898ff5b10412b40b5f14a0c8f07889575fdeefa55abe12a2f8b900",
  "pro_reg_collateral_address": "BHn32VamZjQKE3iAtNWeN3LoDDsNQAr8yM",
  "pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|c36781721e1a114bf020f549e286da08375d473c77edbec707fbbf37b8d83061",
  "pro_reg_signature": "H9q/GPzVkA02knhPSv9EZb0T/nUcQF8vP5E/63qqmXOUVg9vIOnDuWTaEHocal2zc9qrlF56sZ3vY110Z2ouaXE=",
  "sent_txid": ""
}
[/list][/list]
2
    Rob,
    My wallet is uncrypted. can be this the problem ?
    [/list]

    Rob,
    My wallet is uncrypted. can be this the problem ?
    [/list]

    Verify that you are in the masternodelist, even if it is the wrong IP, you should be in the list
    I'm not in the list
    The machine is reachable from outside network by telnet on por 41000 and the demon is in listen

    15:36:04
    getnetworkinfo


    15:36:04
    {
      "version": 2209,
      "buildversion": "v0.22.9 Great-Awakening",
      "subversion": "/BiblePay Core:0.22.9/",
      "protocolversion": 70784,
      "localservices": "0000000000000c05",
      "localservicesnames": [
        "NETWORK",
        "BLOOM",
        "NETWORK_LIMITED",
        "HEADERS_COMPRESSED"
      ],
      "localrelay": true,
      "timeoffset": 1,
      "networkactive": true,
      "connections": 10,
      "inboundconnections": 0,
      "outboundconnections": 10,
      "mnconnections": 4,
      "inboundmnconnections": 0,
      "outboundmnconnections": 4,
      "socketevents": "select",
      "networks": [
        {
          "name": "ipv4",
          "limited": false,
          "reachable": true,
          "proxy": "",
          "proxy_randomize_credentials": false
        },
        {
          "name": "ipv6",
          "limited": false,
          "reachable": true,
          "proxy": "",
          "proxy_randomize_credentials": false
        },
        {
          "name": "onion",
          "limited": true,
          "reachable": false,
          "proxy": "",
          "proxy_randomize_credentials": false
        },
        {
          "name": "i2p",
          "limited": true,
          "reachable": false,
          "proxy": "",
          "proxy_randomize_credentials": false
        }
      ],
      "relayfee": 0.00000700,
      "incrementalfee": 0.00000700,
      "localaddresses": [
        {
          "address": "*.*.*.66",
          "port": 40000,
          "score": 4
        }
      ],
      "warnings": ""
    }


    Netstat command from windows shell/cmd

    TCP    192.168.68.208:40000   verunix:56860          ESTABLISHED
    TCP    192.168.68.208:40000   ip109:45890            ESTABLISHED
    TCP    192.168.68.208:40000   vmi2331614:40804       ESTABLISHED
    TCP    192.168.68.208:40000   seven:51086            ESTABLISHED
    TCP    192.168.68.208:40000   seven:53327            ESTABLISHED
    TCP    192.168.68.208:40000   vmi690434:45594        ESTABLISHED
    TCP    192.168.68.208:40000   108.180.46.33:44924    ESTABLISHED
    TCP    192.168.68.208:40000   108.180.46.33:58966    ESTABLISHED
    TCP    192.168.68.208:40000   vmi2331596:56606       ESTABLISHED
    TCP    192.168.68.208:40000   vmi2331597:36226       ESTABLISHED
    TCP    192.168.68.208:40000   174-47-79-220:62306    TIME_WAIT
    TCP    192.168.68.208:40000   vmi674906:58334        ESTABLISHED




    3
      Sorry to hear you are having issues creating a new sanc.  I am sure it works as last month I created a few more (to ensure our LLMQ was working good etc).

      The Sanc IP is public and announced all over the place (its in the masternode list) so it should not really have to be concealed.
      If you dont want to reveal it I would try this from another machine on a network outside your LAN, like a work machine:
      telnet sancip port
      And see if it answers; if you do want to reveal it I can telnet from my house and tell you if it answers.

      Im not sure if you are saying the problem is that you are not being entered into sanc list, or if you are in the list and are not being paid 100%.
      Even a faulty setup should get you in the list and get you 50% payments (IE investor type payments).

      Im not saying to be happy with that just looking for more info.

      Definitely do a getnetworkstatus on each machine, and verify they are on the latest software version, and a getblockhash, verify they match chainz.
      Verify the TXID that sent the 'exec upgradesanc' command is in the chain more than 6 deep.
      Verify that you are in the masternodelist, even if it is the wrong IP, you should be in the list.
      Then you can do an additional 'exec upgradesanc sancname' and that will fix the ip.

      I always do that after I create a sanc, and after a few blocks pass as generally I have a new sanc with the wrong ip, then the exec upgradesanc fixes the ip.
    Rob,
    My wallet is uncrypted. can be this the problem ?
    [/list]
    4
    Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE
    « Last post by Budinga on February 11, 2025, 01:59:01 AM »

    Ahhh,  great to see that solved it, Praise God!

    Yes, good idea, notice I left an area available for metrics.  I also left a little line in between the Bid and Ask where we can put in the current Midpoint (IE the current price).

    - Add some volume, price and metrics to the top right and mid pane
    - Implement Fractional fills would be sweet

    So now ive managed to sell some bbp and if i do
    exec getassetbalance DOGE

    I have a balance i dont seem to be able to buy back now, it says my balance is 0.
    5
    Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE
    « Last post by AIDS_SKRILLEX on February 10, 2025, 10:15:17 PM »
    exec getdogebalance works every time now

    the exchange is populated

    i attempted to buy all open sell orders and was able to but my exec getassetbalance DOGE only was deducted from twice... i still have over 6 but spent more than that... i have all the bbp

    https://chainz.cryptoid.info/bbp/address.dws?BG39CtdNTZHRt2tcQ83Qqdkv6EE2Q3Xm8v.htm

    https://chainz.cryptoid.info/bbp/block.dws?564829.htm

    idk what im looking at
    6
    Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE
    « Last post by talisman on February 10, 2025, 04:26:00 PM »
    Hi again Rob !

    Here are the two TRADING-ASSET-DOGE addresses I see in my wallet:

    B98GozkCagidcdFMY2zyKf7k3ioud2DgZz
    BM9NqJq4JEDcGuEa1oR3vcpKgLPaoeDgzz

    7
    Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE
    « Last post by Rob Andrews on February 10, 2025, 03:33:32 PM »
    Hi Guys!

    Sorry, late in the game - hectic these days. I just downloaded 0.22.9 and here is what I have seen so far:

    - Exchange showed up fine, populated.
    - TRADING-PUBLIC-KEY and TRADING-ASSET-DOGE all there without hassle, cool. For some reason I have 2 addresses labelled TRADING-ASSET-DOGE, don't know if that is normal.
    - I transferred some BBP to my TRADING-PUBLIC-KEY
    - Checked the board: SELL @ 0.00002939 and BUY @ 0.00002700
    - Placed a SELL order for 1000 BBP @ 0.00002900, showed up fine (received warning that min order size is 1000 BBP when tried with lower amount)
    - Placed another SELL order for 1000 BBP @ 0.00002700 (where the best BUY was at) : My order just got listed without execution. I understand the book only executes matching orders; so was not surprised to see my order not get executed. Still, kind of awkward to see SELL @ 0.00002700 and BUY @ 0.00002700 on the book :)
    - Placed another SELL order for 14777 BBP @ 0.00002700 (to match a standing BUY order on the book) : executed fine, and the BUY order was deleted from the book.
    - Cancelled my non-matching SELL order @ 0.00002700 : deleted from the book, good.
    - Attempted to mess the book buy placing a non-matching SELL order @ 0.00002600 under the price of the best BUY order @ 0.00002700 : OMG it is listed :)

    I think we need to be able to prevent that from happening, until exact matching requirement is lifted.

    I will keep playing around and let you know if I come across other glitches. But, all in all, it is WONDERFUL to see this capability in the wallet. Thanks a lot Rob !

    Ahh, thanks for testing and the compliments, sweet!
    Notice that I did take into consideration the ability to list another ticker in the future.  Most of the plumbing is there.

    I havent dug in to your details too far yet: but notice that when you place an order that matches another order and both are your own (IE the flags are M and M) there is an area of the code where it either cancels both automatically, or ignores them (cant remember which one it is) because it results in an unfillable atomic tx, so that may explain that one exception above.  But yeah everything else should be the "real deal". 

    I am going to work on fractional fills soon as that would be exciting to get in there.

    Glad we did it, as it provides some value to BBP (rather than just another clone coin); plus Bololex has not come back. 

    So im just reading through your message Talisman and on the two addresses for TRADING-ASSET-DOGE, can you paste the pubkeys?  I just want to see if they both end in DGZZ.  That is weird, because we check to see if you have one before we mine a new one.   It should be OK though as when the wallet goes to spend a colored coin, it searches all the DGZZ addresses for it (IE the same type of coin that is being spent in the trading room).  Need to make it so it lists the pubkey on the 'getassetbalance doge' output as well (TODO).

    Very cool on the test results, they seem OK.  Now I will get on to fractional fills soon.  When fractional fills work, there will no longer be crosses in the order book.


    8
    Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE
    « Last post by Rob Andrews on February 10, 2025, 03:30:35 PM »
    Looks like it has now been solved. Maybe just a suggestion maybe have the amount of BBP and Doge available for trade on the exchange page.


    Ahhh,  great to see that solved it, Praise God!

    Yes, good idea, notice I left an area available for metrics.  I also left a little line in between the Bid and Ask where we can put in the current Midpoint (IE the current price).

    - Add some volume, price and metrics to the top right and mid pane
    - Implement Fractional fills would be sweet

    9
    Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE
    « Last post by talisman on February 10, 2025, 02:16:55 PM »
    Hi Guys!

    Sorry, late in the game - hectic these days. I just downloaded 0.22.9 and here is what I have seen so far:

    - Exchange showed up fine, populated.
    - TRADING-PUBLIC-KEY and TRADING-ASSET-DOGE all there without hassle, cool. For some reason I have 2 addresses labelled TRADING-ASSET-DOGE, don't know if that is normal.
    - I transferred some BBP to my TRADING-PUBLIC-KEY
    - Checked the board: SELL @ 0.00002939 and BUY @ 0.00002700
    - Placed a SELL order for 1000 BBP @ 0.00002900, showed up fine (received warning that min order size is 1000 BBP when tried with lower amount)
    - Placed another SELL order for 1000 BBP @ 0.00002700 (where the best BUY was at) : My order just got listed without execution. I understand the book only executes matching orders; so was not surprised to see my order not get executed. Still, kind of awkward to see SELL @ 0.00002700 and BUY @ 0.00002700 on the book :)
    - Placed another SELL order for 14777 BBP @ 0.00002700 (to match a standing BUY order on the book) : executed fine, and the BUY order was deleted from the book.
    - Cancelled my non-matching SELL order @ 0.00002700 : deleted from the book, good.
    - Attempted to mess the book buy placing a non-matching SELL order @ 0.00002600 under the price of the best BUY order @ 0.00002700 : OMG it is listed :)

    I think we need to be able to prevent that from happening, until exact matching requirement is lifted.

    I will keep playing around and let you know if I come across other glitches. But, all in all, it is WONDERFUL to see this capability in the wallet. Thanks a lot Rob !

     
    10
    Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE
    « Last post by Budinga on February 10, 2025, 04:49:19 AM »
    BIBLEPAY 0.22.9 - Mandatory Upgrade

    - Add stability to exchange RPC functions.

    https://github.com/biblepay/biblepay/releases/tag/v022.9-Mandatory


    All, please upgrade to the latest version (available on the github link above).
    Now theoretically all of the commands should be stable.
    Aids, can you please check your 'getdogebalance' is stable 7 times in a row during a retest?
    And now, Prof Budinga, you can try checking the Exchange room stays populated.
    Note that anyone who has an encrypted wallet, you do have to unlock the wallet for the exchange to function.
    There is still a 2minute delay after booting the wallet (for the exchange to populate); once that expires it repopulates as you move the mouse over the grids.

    Looks like it has now been solved. Maybe just a suggestion maybe have the amount of BBP and Doge available for trade on the exchange page.
    Pages: [1] 2 3 4 5 6 7 8 ... 10