Skip to main content

Set up a testnet Sentry Node

Use public testnet to rehearse the released Sentry Node workflow with test funds and independent test keys. Core calls this network test. Its P2P port is 18369, its local Core RPC port is 18370, and the NEVM chain ID is 5700. Released testnet parameters · Core RPC ports

  1. Start Core v5.1.3 with -testnet on the operator host and on any separate Core wallet host. Keep the test operator's settings under [test] in syscoin.conf or use a separate data directory and configuration. Allow inbound TCP 18369 to the operator host and keep its RPC private.
  2. Verify chain is test and initial block download has completed. Use protx_capabilities to confirm the collateral amount and signing era. Generate an independent test BLS operator key and place its secret in the protected test config under masternodeblsprivkey.
  3. Follow the released registration workflow with testnet addresses, testnet fee funds and collateral, and the test host endpoint. Add -testnet before each RPC command and keep -rpcwallet on the wallet calls.
  4. Once the test registration is mined, check the on-chain provider record and the operator's status.
syscoin-cli -testnet getblockchaininfo
syscoin-cli -testnet getnevmblockchaininfo
syscoin-cli -testnet protx_capabilities
syscoin-cli -testnet -rpcwallet="$TEST_COLLATERAL_WALLET" masternode_outputs
syscoin-cli -testnet protx_info "$TEST_PROREG_TXID"
syscoin-cli -testnet masternode_status

The public testnet uses released BLS rules. The PQ candidate’s activation-height overrides apply to isolated development networks. PQ ChainLocks and activation