Messages

1

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 28, 2025, 06:25:20 AM »

Same here guys ! From Italy

2

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: March 27, 2025, 11:02:24 AM »

Hi Lalex,

Theres something wrong.
1) When I do the getrawtransaction 03b8c0e70ca3b21dfc72bf4fe46a7294016d542db95b4ad20bb18e7794cdee19 1
I can see that you sent 450,001.99 to the address in vout1.  It has to be exactly 450001 though, for it to work.
2) Once you have the TXID and ordinal, then you go on to the further steps - in order - placing the fields in the masternode.conf, and calling the exec upgradesanc name_of_entry, and, during that step you should clearly see if it accepted the collateral.
In this case you should have an error on the screen (bad collateral).
Once you have an error, you have to start over and make new collateral (you cant make collateral after the fact out of order) etc.

Good luck man.

[/list][/list]

Thanks Rob I will start from fresh !

So restart 
Ale

3

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: March 26, 2025, 12:45:49 PM »

Hi Lalex,
Thank you for your patience.

On this one you are close but it is a similar problem to last time.
Btw, I hid your private bls sanc key.  (Its just for control of the sanc, not the collateral so no biggie).

So the issue is still that you did not send the right collateral to the collateral address.
As I posted last week, it should be 450001 (not 450 bbp).

See your chainz balance you sent here:
https://chainz.cryptoid.info/bbp/tx.dws?ec3e3f040b87aa37ed761b2446c49bda2c78f1517577e2e7bfe344270c580f67.htm

You can also go with Sanc, 4500001 or temple  45000001 alternatively but altar is 450001.

[/list][/list]

Thanks for your answer Rob.

Please check below

https://chainz.cryptoid.info/bbp/tx.dws?1826911.htm ( 03b8c0e70ca3b21dfc72bf4fe46a7294016d542db95b4ad20bb18e7794cdee19 )

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

God bless you.

Alex.

4

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: March 19, 2025, 03:58:27 AM »

I dont see any new sanctuary registrations in the list (we usually at least see one that is pending with a wrong IP) so we need to find out what happened a step earlier.

Can you paste your collateral output TXID and your Sanc proTXID so I can look at the collateral?  If you lost them you can get them from the bottom of deterministic.conf.  If you dont have that you can start over and log each step of the way in notepad, and then provide it.
Technically though if you are adding an entry to %appdata%\biblepay\masternode.conf and doing a registersanc, you should have that entry appended in the deterministic.conf file.  If you dont thats a problem in itself -- let me know.

[/list][/list]

10:52:44
exec upgradesanc AltareSanto 0


10:52:45
{
  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary AltareSanto with IP 93.55.252.66:40000 with TXID ec3e3f040b87aa37ed761b2446c49bda2c78f1517577e2e7bfe344270c580f67",
  "bls_public_key": "a83847615495e2ce6fea600466db17b50438ca6f2c196b9af78f561f0670e339bbf357c773e824965742831566c87386",
  "bls_private_key": "0x0",
  "pro_reg_txid": "0300010001c6ab7042f3546ef8ffce32163b58366180776341ee99c345c8871d50a5d236cb0100000000feffffff016cd2f505000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000670f580c2744e3bfe7e2777551f1782cda9bc446241b76ed37aa870b043f3eec0000000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0ea83847615495e2ce6fea600466db17b50438ca6f2c196b9af78f561f0670e339bbf357c773e824965742831566c87386a0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588acb6503e98ae1229dae9b0aac0c018b1e0786833736244da2a30d11092bc759af300",
  "pro_reg_collateral_address": "BHn32VamZjQKE3iAtNWeN3LoDDsNQAr8yM",
  "pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|a72aa3b28ae2b9edcbd6e0da95ed5c1f3be00fd2fe87c8a08718e8aba4353dc3",
  "pro_reg_signature": "HzFe/j5vh/ipci/3vAGCodadqvgh+XaVSO5wNLVkul5hA1wheBL1yC2+IwqjxIMr1/sDMQHR8xMJA5uXiSL8hWk=",
  "sent_txid": ""
}

5

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: March 13, 2025, 04:10:35 AM »

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, stil in same issue


10:40:23
masternode status


10:40:23
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "93.55.250.*:40000",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}

Thanks in advance...

6

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: February 19, 2025, 05:04:44 AM »

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]

7

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: February 18, 2025, 09:18:19 AM »

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]

8

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: February 12, 2025, 04:45:30 AM »

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]

9

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: February 11, 2025, 09:48:18 AM »

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

10

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: February 11, 2025, 04:32:45 AM »

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]

11

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: February 06, 2025, 03:26:34 AM »

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]

12

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: December 17, 2024, 05:38:12 AM »

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

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

13

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: November 27, 2024, 07:35:24 AM »

No, thats cool, I dont mind going into more detail where need be.  We also do have some wiki guides on some of these concepts and when one is discovered that is really necessary to document we do make an end-to-end tutorial as a wiki.

First of the reason there are 3 flavors of Sancs now is because some people cant afford 4.55MM bbp for a sanctuary; so now we offer one flavor of sanc for 455,001 bbp and also a Temple for 45MM bbp.  They each have really the same reward (IE the altar pays 10%, the Sanc 100% and the Temple 1000%).

With a sanc you get a bigger reward because its doing the randomx mining in the pool, and you end up with the entire block reward every time your deterministic sanctuary is scheduled for payment. 

If you are an investor you will get 50% of the reward, but an active hosted sanc on a VM, you get 100%.

I would suggest to go back to the release where we ask you to create a deterministic sanctuary, and simply ask questions on any area that is confusing and I can try to help.
Most of this documentation was already established dash; so any terminology on the basics, you can get that from googling that term and Dash Masternode.

Weve simply enhanced and extended those Masternodes to become deterministic sancs with different sizes, and we ported the block miner into the sanc.  And we added the 50% active/passive rules.

Here is the guide to set up a sanc:
https://wiki.biblepay.org/Create_Sanctuary

Just let me know what you need help with.  If you simply want to set up one without renting an actual VM (IE as a passive investor) you just follow the guide, but you point it to your own IP address.

Substitute the 4,500,001 with 450001 to create an altar.

14

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: November 14, 2024, 03:58:00 AM »

Hey Rob,

So when you issue the command upgradesanc, usually, its not actually a "crash" (crash means that the wallet either threw an unhandled exception and ended the program), but instead was sitting there with no RPC response, right?
Yes, but 3 minutes it's not enough.
After al lot of time, hrs, still "hang" and need to be killed.
 
"Masternode command at Italian time"

10:44:48
masternode status

10:44:48
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}


Now, the question is:
How many time need the ProTx to appear on the chain ?

Thanks

15

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: November 07, 2024, 04:09:01 AM »

Rob, brother.

The wallet is crashed during the "exec upgradesanc AltareSanto 1" command.

Now the situation is changed to this.


11:02:52
exec upgradesanc AltareSanto 0


11:02:52
{
  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary AltareSanto with IP *.*.*.66:40000 with TXID 13cb0827e303d05604481be19dab67ae401357a9c2fe48b15936cb48e03d29c6",
  "bls_public_key": "b82a0249b0323c05f89448b9246b63ac2d3c91bec2431e8596581b664ea95484382c46c718c70a92c1016c089c838f2b",
  "bls_private_key": "61a3a78031ebf958832fb960ded4160f353d64a16591e286a41a2713713133b8",
  "pro_reg_txid": "0300010001df2ed6b028f35f75f28d21cb82bd415901acef3edcad869ea90f126bf1920f2a0100000000feffffff016c661903000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000c6293de048cb3659b148fec2a9571340ae67ab9de11b480456d003e32708cb130100000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0eb82a0249b0323c05f89448b9246b63ac2d3c91bec2431e8596581b664ea95484382c46c718c70a92c1016c089c838f2ba0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588ac0db6b50e182f58cc86674b55a713e6304e94b86bd611f00da54793759a5072eb00",
  "pro_reg_collateral_address": "BKcqLFDfZZUJWyaivmZR3WRMVdFCv1p6Qy",
  "pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|d8a79a5a10e600c12ee6c759e86772df3a3233de8326a72c7930d4eecc11c80b",
  "pro_reg_signature": "IGBCLghtakvYladlI8To5LJiBqeZ1z7A5FjssRSB1756C5BEH4QY+TGVwD2Y7cphWE5k7vSepP5Xz4aKxdlDV0E=",
  "sent_txid": ""
}

The IP add is masked by me


11:04:22
exec upgradesanc AltareSanto 1


11:04:22
bad-protx-collateral-01 (code -1)


The transaction message from wallet appear




11:05:44
masternode status


11:05:44
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "ERROR",
  "status": "Error. Can't detect valid external address. Please consider using the externalip configuration option if problem persists. Make sure to use IPv4 address only."
}


Is this a bug or something like it ?

Thanks
Ale