Skip to content

Add Sentrix Chain (chainId 7119)#36652

Closed
satyakwok wants to merge 1 commit into
trustwallet:masterfrom
satyakwok:add-sentrix-chain
Closed

Add Sentrix Chain (chainId 7119)#36652
satyakwok wants to merge 1 commit into
trustwallet:masterfrom
satyakwok:add-sentrix-chain

Conversation

@satyakwok
Copy link
Copy Markdown

Adds Sentrix Chain to blockchains/sentrix/ per the standard format used by Base, Aurora, and other EVM-compatible L1s.

Chain identity

Production status

  • Mainnet block height: ~1.7M+ live
  • Consensus: Voyager BFT (Tendermint-style, single-block finality)
  • Execution: revm 38, EVM-compatible (Solidity 0.8.x, Cancun-enabled)
  • Latest release: v2.2.10 with cosign keyless signatures + SLSA L3 build provenance — https://github.com/sentrix-labs/sentrix/releases/tag/v2.2.10
  • Working cross-chain bridge to Ethereum via Hyperlane: github.com/sentrix-labs/sentrix-bridge

Files added

  • blockchains/sentrix/info/info.json — chain metadata
  • blockchains/sentrix/info/logo.png — 256×256 PNG, from official brand-kit

Related listings

Sentrix is a Rust-implemented EVM-compatible Layer 1, mainnet h=1.7M+
live, signed releases (cosign + SLSA L3), live cross-chain bridge to
Ethereum via Hyperlane.

Native asset: SRX, 18 decimals.
Chain ID: 7119.
RPC: https://rpc.sentrixchain.com
Explorer: https://scan.sentrixchain.com (EIP-3091 compliant)
Source: github.com/sentrix-labs/sentrix (BUSL-1.1)
Chainlist: pending merge at ethereum-lists/chains#8266
@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot Bot commented May 12, 2026

No token files found. If you try to add/modify a token, check the name and location of your files! Logo file must be named exactly 'logo.png'. If you are not adding a token, ignore this message.

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot Bot commented May 12, 2026

Hi! In order to compensate for the efforts of processing PRs, we kindly ask for a contribution.
💀 As there is no refund, before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
See also the PR Fee FAQ.

Please pay 500 TWT to the BEP20 (Binance Smartchain) address 0x97f96Ac4170e92f4BAaba1A7b88679eC592F7004.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet

TWT Acquiring:

Notes:

  • New tokens without significant usage are rejected, see criteria mentioned above.
  • One PR should be for a single project; PR's with more than 10 logos will be rejected.
  • Payment evaluation happens automatically, but with a few minutes delay. When payment is detected, an Accept Review is automatically placed on the PR, which is a condition for merge.
  • Evaluating the PR is done manually, and it is merged only if all conditions are satisfied.
    There will be a fee to process this request. None of it goes to the developers.
    Before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
    If you are paying TWT for the submission, this will be burned automatically. There will be no refunds.

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot Bot commented May 13, 2026

@satyakwok, kind reminder: please pay fee: 500 TWT to the address 0x97f96Ac4170e92f4BAaba1A7b88679eC592F7004.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet
See the Pull Request Fee FAQ.

2 similar comments
@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot Bot commented May 13, 2026

@satyakwok, kind reminder: please pay fee: 500 TWT to the address 0x97f96Ac4170e92f4BAaba1A7b88679eC592F7004.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet
See the Pull Request Fee FAQ.

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot Bot commented May 14, 2026

@satyakwok, kind reminder: please pay fee: 500 TWT to the address 0x97f96Ac4170e92f4BAaba1A7b88679eC592F7004.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet
See the Pull Request Fee FAQ.

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot Bot commented May 14, 2026

This PR is being closed due to inactivity. If you wish to continue, please have us reopen the PR before sending your payment, or just create a new one.
Do NOT send payments for closed PR, as the fee may by lost!

@merge-fee-bot merge-fee-bot Bot closed this May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant