Skip to main content

Set up a Sentry Node

This guide covers a self-hosted mainnet Sentry Node on Core v5.1.3. Use the release for your platform, verify it against the published checksums, and keep backups of the wallet and node configuration. The released Sentry Node uses a BLS operator key. Follow the separate testnet guide to rehearse registration with test funds. Core v5.1.3 release · Testnet guide

Prepare the host and wallet​

Run the Sentry Node on a continuously available host with a reachable public IPv4 address. Allow inbound TCP 8369 for Syscoin peers. Keep Core RPC private and use syscoin-cli locally. Check that Core and the managed NEVM client are following the right network before registering. Use a separate wallet or signing device for the collateral, owner, and voting keys. The node host needs the BLS operator secret to perform its role.

syscoind --version
syscoin-cli getblockchaininfo
syscoin-cli getnevmblockchaininfo
syscoin-cli protx_capabilities

Confirm the correct network and allow initial block download to finish. Check the reported era and requiredCollateralSatoshis. The released mainnet collateral is 100,000 SYS, held in a single unspent output. Reserve an additional spendable balance for the registration fee. Choose a fresh native SegWit single-key address (P2WPKH) for the owner, and another for voting if you want a separate voting key. For new collateral, use a dedicated P2WPKH address in the wallet or signer that will authorize the registration. Keep the payout address separate from the owner and voting addresses. Released signing rules · Wallet registration implementation

Configure the operator​

Generate the key pair through a trusted local Core session. Treat the output as secret. For the current released signing era, use the default basic BLS scheme.

syscoin-cli bls_generate

Keep the returned public value for registration. Place the returned secret in the masternodeblsprivkey setting in the node's protected syscoin.conf. Restrict the configuration to the service account and restart Core. Preserve access to the key for recovery. Configure the node to accept peers at the same public endpoint you will register. A hosted operator can provide its public endpoint and operator public key so the wallet owner can authorize registration. BLS key generation · Core startup configuration

Register the collateral​

Prepare and submit with the wallet holding your registration fee inputs. Sign the message using the collateral wallet or a device that supports Syscoin message signing. Variables below refer to values from your own infrastructure. A script that drives this flow should stop for review before signing and broadcasting.

  1. On the collateral wallet, list compatible outputs and identify the exact txid and index. Make sure its funding transaction is confirmed and this output belongs to your signer.

    syscoin-cli -rpcwallet="$COLLATERAL_WALLET" masternode_outputs
    syscoin-cli gettxout "$COLLATERAL_TXID" "$COLLATERAL_VOUT"
  2. Prepare the transaction. Use the public service IP and port in SERVICE_ENDPOINT. Pass an empty voting address to reuse the owner address. The example uses a zero operator reward share. Set the agreed percentage if a separate operator will receive a share. FEE_ADDRESS must have spendable fee funds in the selected fee wallet outside the collateral output.

    syscoin-cli -rpcwallet="$FEE_WALLET" protx_register_prepare \
    "$COLLATERAL_TXID" "$COLLATERAL_VOUT" "$SERVICE_ENDPOINT" "$OWNER_ADDRESS" \
    "$OPERATOR_PUBLIC_KEY" "$VOTING_ADDRESS" 0 "$PAYOUT_ADDRESS" "$FEE_ADDRESS"
  3. Save the returned tx as PREPARED_TX. Review the collateral address, endpoint, owner and reward destinations against your records. Sign the exact returned signMessage with the key for the returned collateralAddress. If Core holds that key, the wallet command is:

    syscoin-cli -rpcwallet="$COLLATERAL_WALLET" signmessage \
    "$COLLATERAL_ADDRESS" "$SIGN_MESSAGE"
  4. Pass the returned base64 signature as COLLATERAL_SIGNATURE. This step signs the fee inputs and broadcasts the registration. Record the returned registration transaction ID.

    syscoin-cli -rpcwallet="$FEE_WALLET" protx_register_submit \
    "$PREPARED_TX" "$COLLATERAL_SIGNATURE"

Select the correct loaded wallet for each operation and unlock it privately when needed. Keep the registered collateral output unspent while the Sentry Node is in service. Spending it removes the registration from the deterministic list. Collateral checks · Registration and message-signing RPCs

Verify operation​

After registration confirms, verify the on-chain record and the host's local state.

syscoin-cli protx_info "$PROREG_TXID"
syscoin-cli masternode_status
syscoin-cli getchainlocks

Check the registered service endpoint, operator public key, and payout destination. On the host, resolve any service status error before relying on it for quorum participation. For existing nodes, inspect the record before using a service update or making a new registration. protx_update_service changes the service endpoint for an existing registration. Consult help protx_update_service and use a trusted operator session for the signing step. Core RPC reference · Service-update RPC