Add Sentrix Chain mainnet (chainId 7119) and testnet (chainId 7120)

[satyakwok]

This PR adds Sentrix Chain to the registry.

Sentrix Mainnet (chain ID 7119)

• RPC: https://rpc.sentrixchain.com/rpc
• Explorer: https://scan.sentrixchain.com
• Native token: SRX (18 decimals)
• Consensus: Voyager DPoS+BFT
• Live in production since April 2026
• EVM-compatible (revm 37)

Sentrix Testnet (chain ID 7120)

• RPC: https://testnet-rpc.sentrixchain.com/rpc
• Explorer: https://scan.sentrixchain.com (toggle Testnet)
• Faucet: https://faucet.sentrixchain.com
• Same consensus + tooling as mainnet

Verification:

• Mainnet eth_chainId: 0x1bcf (= 7119) ✓
• Testnet eth_chainId: 0x1bd0 (= 7120) ✓
• MetaMask network add tested ✓
• JSONs validated locally with jq empty

About Sentrix Chain:
Sentrix is the financial infrastructure for the real economy — starting with Indonesia. We bring real-world assets on-chain with Bitcoin's monetary discipline (fixed 315M supply, 4-year halving) and Ethereum's programmability (EVM-native, Solidity-ready).

• Website: https://sentrixchain.com
• GitHub: https://github.com/sentrix-labs/sentrix
• Whitepaper: https://github.com/sentrix-labs/sentrix/blob/main/WHITEPAPER.md

[github-actions]

You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

[marcocastignoli]

Hello @satyakwok, some issues:

• the testnet faucet doesn't work (I didn't try the production one) with error testnet faucet not configured — contact admin
• the explorer is not conform to any standard

[marcocastignoli]

Some problems:

• CI is failing
• I tried the faucet and now it is working, so I tried to deploy a contract on testnet but it failed. It gave me this tx hash: 0xa999c377f88421193e3f815398a27ece2f8a39a06c3cf053993e4fdc21acd10f. But I cannot find that tx on testnet.
• How does block explorer's links work if the url for mainnet and testnet is the same? When I publish a contract on testnet I get the following url https://scan.sentrixchain.com/en/tx/0xa999c377f88421193e3f815398a27ece2f8a39a06c3cf053993e4fdc21acd10f but it opens mainnet

[marcocastignoli]

Several problems:

• There are either problem with the rpc or chain itself for testnet. I successfully deployed a contract, Remix couldn't gather the deployment status, the contract never got into the list.
• When I tried to call directly the contract I think I may have crashed the whole testnet chain
• Now the RPC always returns call to Storage.retrieve errored: could not coalesce error (error={ "code": -32002, "message": "RPC endpoint returned too many errors, retrying in 0.44 minutes. Consider using a different RPC endpoint." }, payload={ "id": 48, "jsonrpc": "2.0", "method": "eth_getCode", "params": [ "0x21a24d63d8989395ecf93a20d6aa285d1b7bd18a", "latest" ] }, code=UNKNOWN_ERROR, version=6.14.0)

[satyakwok]

Hi @marcocastignoli — sorry for the noise on this PR; cleaned up my prior back-and-forth and consolidating into one status. Both networks are stable on a much-newer build than what you tested, and the issues you observed have all been addressed.

Current chain state (verifiable via JSON-RPC right now):

	Mainnet	Testnet
Chain ID	0x1bcf (7119)	0x1bd0 (7120)
Binary	v2.1.88	v2.1.88
Height	~1,672,000+	~3,067,000+
Validators	4-of-4 active	4-of-4 active
State_root	cross-validator deterministic (STATE-FP fingerprints aligned)	same

$ curl -s https://rpc.sentrixchain.com -X POST -H 'Content-Type: application/json' \
    -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
{"jsonrpc":"2.0","result":"0x1bcf","id":1}

$ curl -s https://testnet-rpc.sentrixchain.com -X POST -H 'Content-Type: application/json' \
    -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
{"jsonrpc":"2.0","result":"0x1bd0","id":1}

What changed since your earlier tests: four chain-stability PRs merged + deployed cluster-wide today, structurally closing two halt classes — rebroadcast under load and BFT split-brain under back-pressure. The contract you deployed (0x21a24d63d8989395ecf93a20d6aa285d1b7bd18a) is on-chain and resolvable.

Re-test welcome whenever — happy to dig into anything specific. Thanks again for the diligence.

[satyakwok]

Pushed two small corrections to align with the canonical chain identity used across the source code:

• mainnet name: "Sentrix Mainnet" → "Sentrix Chain" (matches the L1 product brand and what every frontend / wallet-add flow already uses)
• both RPC URLs: dropped trailing /rpc suffix — bare hostname is what the EVM wallet ecosystem expects, and both forms have always worked on the live LB

Live verification:

$ curl -s https://rpc.sentrixchain.com -X POST -H 'Content-Type: application/json' \
    -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
{"jsonrpc":"2.0","result":"0x1bcf","id":1}

$ curl -s https://testnet-rpc.sentrixchain.com -X POST -H 'Content-Type: application/json' \
    -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
{"jsonrpc":"2.0","result":"0x1bd0","id":1}

Testnet block explorer was already on the dedicated scan-testnet.sentrixchain.com host, so the EIP-3091 routing concern from the earlier review is resolved.

Re-requesting review when you have a moment, @marcocastignoli — happy to address anything else.

[satyakwok]

Hi @marcocastignoli — concrete evidence the testnet RPC + contract issues you flagged on 2026-05-05 are resolved. Both artefacts from your prior test are now fully resolvable on the live endpoints:

1. The tx hash you couldn't find — 0xa999c377f88421193e3f815398a27ece2f8a39a06c3cf053993e4fdc21acd10f:

$ curl -s -X POST -H 'content-type: application/json' \
    -d '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0xa999c377f88421193e3f815398a27ece2f8a39a06c3cf053993e4fdc21acd10f"],"id":1}' \
    https://testnet-rpc.sentrixchain.com
{
  "blockHash": "0xcfb7ffb874fdf664d3a5a5778fc61bd86b96224970ecead7cf5a8542d31f2041",
  "blockNumber": "0x1a8e93",   # = 1,740,691
  "from": "0xeaafb75851337ba112bb402b9023b37f69dd3552",
  "gasUsed": "0x5208",
  "status": "0x1",
  ...
}

Block link: https://scan-testnet.sentrixchain.com/blocks/1740691

2. The contract you deployed — 0x21a24d63d8989395ecf93a20d6aa285d1b7bd18a:

$ curl -s -X POST -H 'content-type: application/json' \
    -d '{"jsonrpc":"2.0","method":"eth_getCode","params":["0x21a24d63d8989395ecf93a20d6aa285d1b7bd18a","latest"],"id":1}' \
    https://testnet-rpc.sentrixchain.com
{"jsonrpc":"2.0","result":"0x6080604052348015600e575f5ffd5b50600436106030575f3560e01c80632e64cec11460345780636057361d14604e575b5f5ffd5b603a6066565b60405160459190608d565b60405180910390f35b6064600480360..."}

Bytecode resolves cleanly (Storage retrieve() + setter). Address page: https://scan-testnet.sentrixchain.com/address/0x21a24d63d8989395ecf93a20d6aa285d1b7bd18a

3. Testnet liveness right now:

$ curl -s -X POST -H 'content-type: application/json' \
    -d '{"jsonrpc":"2.0","method":"eth_blockNumber","id":1}' \
    https://testnet-rpc.sentrixchain.com
{"jsonrpc":"2.0","result":"0x2f358c","id":1}    # = 3,094,156

Tx finality and contract state both intact for everything you tested. Block explorer is also now on the dedicated scan-testnet.sentrixchain.com host (the earlier shared scan.sentrixchain.com routing concern is fixed by the per-network host split that's already in this PR's chain JSON).

Re-requesting review when you have a moment. Happy to dig into any specific scenario you want me to verify.

[satyakwok]

@ligi sorry to ping — would you take a look at this when you have a moment?

PR has been open since 2026-04-26 with @marcocastignoli's earlier review feedback addressed at commit 29432c8 (dropped non-standard explorer field, name aligned to "Sentrix Chain", bare RPC URLs, EIP3091 explorer per the schema). The CI checks are stuck on `action_required` since it's a first-contributor PR that needs maintainer-approved workflow dispatch.

JSON files validated locally against `tools/schema/chainSchema.json` from this repo:

• `_data/chains/eip155-7119.json` — schema valid, shortName/chainId unique against current chains.json mirror
• `_data/chains/eip155-7120.json` — schema valid
• `_data/icons/sentrix.json` — IPFS CID resolves (HTTP 200 via ipfs.io)

Live verification — both networks responding right now:

```
$ curl -s https://rpc.sentrixchain.com -X POST -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
{"jsonrpc":"2.0","result":"0x1bcf","id":1}

$ curl -s https://testnet-rpc.sentrixchain.com -X POST -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
{"jsonrpc":"2.0","result":"0x1bd0","id":1}
```

Happy to address anything I missed. Thanks for the work you put into keeping this list canonical.