Add sentrix chain#8322
Conversation
Per @marcocastignoli's CHANGES_REQUESTED on PR ethereum-lists#8266: - "the explorer is not conform to any standard" Removing the `explorers` field from both eip155-7119 (mainnet) and eip155-7120 (testnet) entries until a standards-conformant explorer deployment lands. A Blockscout deployment is in progress and will be re-added in a follow-up PR once it goes live at the canonical URL. Native SRX uses 8 decimals (sentri unit). EVM-side uses the 18-decimal convention with a 10^10 multiplier applied at the boundary for tooling compatibility — same pattern Polygon/Optimism use. The chain JSON correctly reports decimals=18 for the EVM-facing surface, which is what wallets, RPC clients, and chain-list consumers expect. Testnet faucet (also flagged) is service-up and returns clean error responses (e.g. "Insufficient balance") — the operator action to fund the testnet faucet wallet is tracked separately and does not affect the chain JSON correctness.
scan.sentrixchain.com now exposes EIP-3091 singular routes: /block/<n> /tx/<hash> /address/<addr> /token/<addr> all returning 200 (after locale-prefix redirect chain). Single explorer entry — Sentrix Labs is consolidating to scan only; the parallel Blockscout sidecar at blockscout.sentrixchain.com is being retired.
PNG 512x512 pinned at ipfs://QmTvrKW913yQVjK1PCZ8Kf5D4oJPq1ucnxyepgsFU1poA2
CI prettier check flagged the rpc array as multi-line. Auto-fixed with prettier --write so both Sentrix entries pass the formatting gate.
Switches the IPFS-referenced asset from png-transparent/sentrix-512.png to png-full/sentrix-512.png (same mark, black circle container). Per brand guide, the mark is intended for pure black backgrounds for best contrast — this variant bakes that in for downstream consumers (chainlist, wallets, etc). New CID: QmRpzcXkEYAX4p7j7Qy9AdQdFhFH47WpGZKCohKM2DmYdy Old CID: QmTvrKW913yQVjK1PCZ8Kf5D4oJPq1ucnxyepgsFU1poA2 Note: local gradlew check timed out at 120s (first-time dep resolution); skipped. Schema-correctness verified by hand against tools/schema/chainSchema.json + the Main.kt:checkIcon validator (ipfs:// scheme, png format, 512x512 Int dims).
scan-testnet.sentrixchain.com serves Chain ID 7120 with the testnet network locked at SSR via host-header check (apps/scan/lib/network-server.ts). The prior eip155-7120 entry pointed at scan.sentrixchain.com which is mainnet- locked at SSR, causing the EIP-3091 deeplink ambiguity that PR ethereum-lists#8266 reviewer flagged 2026-05-02. Architecture (post-investigation): - scan.sentrixchain.com → mainnet locked at SSR (chain 7119) - scan-testnet.sentrixchain.com → testnet locked at SSR (chain 7120) - per-network API endpoints (api / testnet-api) confirmed isolated - EIP-3091 routes /block /tx /address /token return 200 on both hosts - client-side cross-network auto-switch already exists, but the canonical chain-list URL should produce SSR-correct data without relying on JS
|
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. |
|
Closing — content already landed on master via #8266 (merged 2026-05-12T08:24). Branch is 16 commits ahead, 0 files changed in diff vs master, so this PR is logically merged via the parallel path. Thanks @marcocastignoli for getting Sentrix into the registry. |
No description provided.