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

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

Guys, I give up.
I’m stuck in this situation.
I tried everything, reinstalled wallet, changed configuration, changed IP port, updated to the latest version, all the rules of NAT on routers are fixed, if I run a netstat ports are in listen, if I run on external ip telnet on ports 40000 and 41000 the machine reachable.
All this did not help to solve the situation.

Below the output from masternode status

10:11:01
masternode status
10:11:01
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "*.*.*.66:41000",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}

Any suggestion? [/list]

Guys, I give up.
I’m stuck in this situation.
I tried everything, reinstalled wallet, changed configuration, changed IP port, updated to the latest version, all the rules of NAT on routers are fixed, if I run a netstat ports are in listen, if I run on external ip telnet on ports 40000 and 41000 the machine reachable.
All this did not help to solve the situation.

Below the output from masternode status

10:11:01
masternode status
10:11:01
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "*.*.*.66:41000",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}

Any suggestion? [/list]

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.

You didn't post the current mandatory wallet upgrade of 2/8/25 to this thread.

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

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]

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

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": "",
  "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]

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": "",
  "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]

Ahh! Finally I see the problem, thanks for pasting all that.

So you had been doing everything right, your tx was on the mainchain (I see it) and you are synced, and your commands were right, the problem is your collateral address does not have the right amount:

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

Notice that you only sent 450 bbp to that.

The sancs are either:
4 500 001.00    for a Sanc  (IE 4.5MM  or 4,500,001  bbp)
45 000 001.00  for a temple
450 001.00       for an altar

Once you do this over with one of those amounts, then you will see yourself in 'masternodelist' (RPC).

You didn't post the current mandatory wallet upgrade of 2/8/25 to this thread.

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

Its OK, the last prior mandatory was enough for the Sancs, now Im just working in testnet to get fractional fills out.
Once I have a hard fork we will notify again.  (IE Intentional).

Biblepay v023.3 - Mandatory Upgrade for Entire Network @ Height 565718

- Fix memory pool validation


https://github.com/biblepay/biblepay/releases/tag/v023.3-Mandatory

Here is the testnet to help us test the new DOGE-BBP exchange:

https://forum.biblepay.org/index.php?topic=971.0

Reposting for visibility

If we don't keep installing these mandatory updates for a while, what will happen to our balances?

Ahh! Finally I see the problem, thanks for pasting all that.

So you had been doing everything right, your tx was on the mainchain (I see it) and you are synced, and your commands were right, the problem is your collateral address does not have the right amount:

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

Notice that you only sent 450 bbp to that.


The sancs are either:
4 500 001.00    for a Sanc  (IE 4.5MM  or 4,500,001  bbp)
45 000 001.00  for a temple
450 001.00       for an altar

Once you do this over with one of those amounts, then you will see yourself in 'masternodelist' (RPC).

Rob, ...thanks.
Now i'm in another little issue, in my wallet I have in balance field 1 220 756.98 BIBLEPAY ( cut&paste from wallet ) but when i try to send to Altar address the amount of 452 000.000000 RPC response me "the amount exed your balance"
The maximus ammount that i can send is ( I click on wallet "use available balance" ) 142 245.58559888

So now ?
Thanks again
Ale


[/list][/list]

Rob, ...thanks.
Now i'm in another little issue, in my wallet I have in balance field 1 220 756.98 BIBLEPAY ( cut&paste from wallet ) but when i try to send to Altar address the amount of 452 000.000000 RPC response me "the amount exed your balance"
The maximus ammount that i can send is ( I click on wallet "use available balance" ) 142 245.58559888

So now ?
Thanks again
Ale

Solved,
I send BBP in 4 transactions...

And now I will wait...

[/list][/list]

If we don't keep installing these mandatory updates for a while, what will happen to our balances?

The coins that you legitimately bought from exchanges or mined in the past, those are always safe.

When a user decides not to upgrade, you will go on your own personal fork (along with the other sancs who have not upgraded), and will have your own invalid version of the blockchain.

Solved

Great, glad you solved it.  If you ever end up on a fork just do a complete reindex of the wallet and you will catch up.

I will notify Chainz of the new version after this next mandatory (we are working on fractional fills now).

[/list][/list]