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
- Start Core v5.1.3 with
-testneton the operator host and on any separate Core wallet host. Keep the test operator's settings under[test]insyscoin.confor use a separate data directory and configuration. Allow inbound TCP 18369 to the operator host and keep its RPC private. - Verify
chainistestand initial block download has completed. Useprotx_capabilitiesto confirm the collateral amount and signing era. Generate an independent test BLS operator key and place its secret in the protected test config undermasternodeblsprivkey. - Follow the released registration workflow with testnet addresses, testnet fee funds and collateral, and the test host endpoint. Add
-testnetbefore each RPC command and keep-rpcwalleton the wallet calls. - 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