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

[satyakwok]

Hi @marcocastignoli, thanks for the review — pushed a follow-up commit to address both flags:

1. Explorer standard non-conformance (resolved in 07872f8)
Dropped the explorers field from both eip155-7119 (mainnet) and eip155-7120 (testnet) entries. A Blockscout deployment is in progress and will be added in a follow-up PR once it goes live at the canonical evm.sentrixchain.com host (or equivalent). The current internal explorer at scan.sentrixchain.com is a custom Next.js UI that doesn't expose any of the documented standard enum values (etherscan / blockscout / etc.), so removing the field is the correct action until a standards-conformant explorer is live.

2. Testnet faucet error — partially resolved
The faucet service at https://faucet.sentrixchain.com is up. Direct API check shows it returns clean error responses now:

$ curl -s -X POST https://faucet.sentrixchain.com/api/faucet \
    -H 'Content-Type: application/json' \
    --data '{"address":"0x0000000000000000000000000000000000000001","network":"testnet"}'
{"success":false,"error":"Insufficient balance: have 0, need 1000010000"}

The "not configured" error you hit was likely from an earlier deploy state. The remaining Insufficient balance is an operator-side action (fund the testnet faucet wallet from the premine slot) and is tracked internally — it does not affect the chain-list JSON correctness. The faucet field in the testnet JSON is the right URL for downstream tooling to resolve.

3. Decimals = 18 (note for context, no change needed)
Native SRX uses 8 decimals at the protocol level (sentri unit, 1 SRX = 10⁸ sentri). The EVM-facing surface applies the standard 18-decimal convention with a 10¹⁰ multiplier at the boundary — same pattern Polygon and several other dual-stack chains use for tooling compatibility. The chain-list JSON correctly reports decimals: 18 for the EVM surface, which is what wallets, RPC clients, and chain-list consumers expect.

Re-requesting your review. Happy to address any further specifics.

[satyakwok]

@marcocastignoli — re-pinging on this with status updates on both review points:

1. Explorer non-conformance ✅ resolved in 07872f8 — `explorers` field dropped from both `eip155-7119` and `eip155-7120`. The Blockscout deployment is now live at `blockscout.sentrixchain.com` (EIP-3091 conformant) but I'll add it in a separate PR after this lands rather than re-introducing the field here against your request.

2. Testnet faucet ✅ funded. Faucet wallet `0x2ffc302fcd8c0eeab2796b3c1d134f18e8237762` currently holds 10,000,078 tSRX (verified just now via `eth_getBalance` on testnet RPC). The "testnet faucet not configured — contact admin" you saw was a transient state during initial rollout; the wallet was funded shortly after. The faucet UI at `https://faucet.sentrixchain.com\` is serving requests.

I also closed PR #8283 just now — that was a duplicate I opened by accident without checking that this one was still open.

The current diff in this PR is clean against `tools/schema/chainSchema.json` (validated locally), `shortName` `srx` / `srx-testnet` are unique against the live chains.json, `chainId` 7119 / 7120 unrequested elsewhere. Ready for another look whenever you've got a minute, thanks for the original review.

[satyakwok]

Hi @marcocastignoli — addressing the explorer non-conformance you flagged earlier:

scan.sentrixchain.com now serves the EIP-3091 singular routes:

• /block/<blockNumberOrHash> → 200 (via i18n redirect to /en/blocks/...)
• /tx/<txHash> → 200
• /address/<addressHash> → 200
• /token/<tokenContractAddress> → 200

Just pushed an update with the explorers field added to both eip155-7119.json and eip155-7120.json declaring standard: EIP3091.

Verifiable: curl -sI https://scan.sentrixchain.com/block/100 -L → final 200, similarly for /tx/, /address/, /token/.

Re-requesting your review when you have time.

[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