Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
5a01efe
skills: The evmonly-loadtest tool adds a new --storage-dir flag to co…
seidroid[bot] Nov 18, 2026
05d26b7
skills: The EVM-only JSON-RPC surface now supports eth_getBalance, re…
seidroid[bot] Nov 18, 2026
b313260
skills: The CLI command `seid tx evm register-cw-pointer` and the `Ms…
seidroid[bot] Nov 18, 2026
8d26e7d
skills: EVM pointer contracts and their CLI commands/governance propo…
seidroid[bot] Nov 18, 2026
5e81430
skills: CHANGELOG references a new JSON output option for the seidb e…
seidroid[bot] Nov 18, 2026
d3cd241
skills: The `seid tx evm deploy-wsei` CLI command and its WSEI contra…
seidroid[bot] Nov 18, 2026
3646908
skills: Adds a new `eth_getCode` JSON-RPC endpoint to the EVM-only RP…
seidroid[bot] Nov 19, 2026
5c3a784
skills: Adds eth_feeHistory and eth_gasPrice JSON-RPC methods to the …
seidroid[bot] Nov 19, 2026
2da15e7
skills: This CHANGELOG update introduces numerous developer-facing ch…
seidroid[bot] Nov 19, 2026
de66afa
skills: The oracle module is fully removed behind the v6.8 upgrade—it…
seidroid[bot] Nov 19, 2026
4b8801e
skills: Adds a new EVM-only JSON-RPC WebSocket listener with a config…
seidroid[bot] Nov 19, 2026
2dbf0a6
skills: The deprecated UpgradedConsensusState query/precompile method…
seidroid[bot] Nov 19, 2026
4afd9cc
skills: Adds two new EVM JSON-RPC methods, eth_getBlockTransactionCou…
seidroid[bot] Nov 19, 2026
92bf18f
skills: Adds two new EVM JSON-RPC methods, eth_getTransactionByBlockN…
seidroid[bot] Nov 19, 2026
c1ab246
skills: The staking precompile's redelegations query now enforces sup…
seidroid[bot] Nov 19, 2026
b1ee871
skills: Adds support for the eth_getStorageAt JSON-RPC method to the …
seidroid[bot] Nov 19, 2026
3452cd9
skills: Adds a new EVM JSON-RPC endpoint eth_getBlockReceipts that re…
seidroid[bot] Nov 19, 2026
dd7f4d4
skills: The EVM-only JSON-RPC now supports historical state queries: …
seidroid[bot] Nov 20, 2026
ee7117d
skills: The Docker image now builds and ships the seidb tool binary a…
seidroid[bot] Nov 20, 2026
469a5f2
skills: The Cosmos gRPC and gRPC-Web servers (and the Rosetta API ser…
seidroid[bot] Nov 20, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
425 changes: 425 additions & 0 deletions skill/references/cli/evmonly-rpc.md

Large diffs are not rendered by default.

15 changes: 13 additions & 2 deletions skill/references/cli/seid-cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -177,6 +177,11 @@ Supported types:

Note: `pointee` does not support `CW1155` or `ERC1155`.


### Oracle Module Removed

The oracle module has been removed behind the v6.8 upgrade ([sei-chain#4319](https://github.com/sei-protocol/sei-chain/pull/4319)): its CLI commands, store, protobuf schema, REST/gRPC endpoints, and CosmWasm query route are gone. `seid q oracle ...` now returns `unknown command "oracle"`, and store queries against the deleted store return `no such store: oracle`. Only the oracle `Msg` types remain decodable so historical blocks still trace; oracle transactions submitted after the upgrade are rejected before any fee is charged. The `oracle` module no longer appears in any tooling module list (`dump_app_state_for_height.sh`, `seidb` `AllModules`, iaviewer helpers).

### Transaction Lookup

```bash
Expand Down Expand Up @@ -234,6 +239,10 @@ seid tx evm call-precompile <precompile-name> <method> [args...]

Available precompile names: `distribution`, `json`, `p256`, `staking`. See [EVM Precompiles](https://docs.sei.io/evm/precompiles) for method signatures.



> **No built-in WSEI deploy command.** The `seid tx evm deploy-wsei` subcommand (with flags `--from`, `--gas-fee-cap`, `--gas-limit`, `--evm-rpc`, `--nonce`) has been removed, along with its embedded WSEI (Wrapped Sei) contract artifacts. There is no `seid` command to deploy a Wrapped Sei ERC20 contract. To deploy a Wrapped Sei contract, compile and deploy your own bytecode via `seid tx evm deploy <path-to-binary> --from <name>` or external EVM tooling.

## Node Start (`seid start`)

### `--freeze-height`
Expand All @@ -250,7 +259,6 @@ seid start --freeze-height <uint64>
Constraints:
- Must not exceed `MaxInt64`.
- Cannot be combined with `--halt-height`/`halt-height` or `--halt-time`/`halt-time`.
- Cannot be combined with grpc-only mode (`--grpc-only`).
- State sync is disabled under freeze mode and falls back to block sync.
- Full nodes only: not supported in validator or seed mode, or with Autobahn.
- The target height must not be below the chain's initial height, and the application, block store, and state store must not have reached it yet — otherwise the node refuses to start.
Expand Down Expand Up @@ -314,6 +322,9 @@ For writes: sign first, then submit via `eth_sendRawTransaction`. Prefer a walle

`seidb` is the SeiDB maintenance/analysis tool (built from `sei-db/tools/cmd/seidb`). Use it for inspecting on-disk state stores — not for chain queries. The commands below cover FlatKV analysis and hash-log inspection. As of v6.7.0 the fourth FlatKV bucket is named `misc` (it was `legacy` in v6.6).


> **Shipped in the Docker image.** The official Docker image now builds and ships `seidb` at `/usr/bin/seidb` alongside `/usr/bin/seid`, so container users already have it and do not need a separate build (sei-chain Dockerfile). `seidb` is pure Go — it builds with `CGO_ENABLED=0` and does not link libwasmvm. Outside the container, build it from source with `CGO_ENABLED=0 go build -o seidb ./sei-db/tools/cmd/seidb`.

### dump-flatkv

Iterates a FlatKV store and dumps every physical `(key, value)` pair into per-bucket files, one file per bucket, formatted to match `dump-iavl` so the same diff tooling works on both.
Expand Down Expand Up @@ -416,7 +427,7 @@ seidb evm-logical-digest --backend flatkv|memiavl|composite --db-dir <dir> --hei
| `--list-limit` | | Inspect mode: maximum pairs to print with `--list`; `<=0` means unlimited | `1000` |
| `--details` | | Inspect list mode: include backend-specific version metadata | `false` |
| `--find-hash` | | 32-byte hex per-entry hash to hunt for; every entry whose `sha256(len(key)||key||len(val)||val)` matches is printed as `FOUND-HASH` | — |
| `--json` | | Emit the digest or inspect report as one JSON object on stdout (narration goes to stderr), for scheduled digest checks | `false` |
| `--json` | | Emit the digest or inspect report as one JSON object on stdout (narration goes to stderr), for scheduled digest checks (sei-chain#4255) | `false` |

Notes:
- The per-bucket accumulator is an order-independent XOR of `sha256(len(key)||key||len(val)||val)`, so it does not matter that flatkv iterates in pebble global order while memiavl is scanned by leaf index.
Expand Down
6 changes: 6 additions & 0 deletions skill/references/contracts/common-errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,12 @@ STAKING.delegate{value: 1 ether}(validatorAddr);
**Cause**: Calling a precompile from a contract without `payable` when the precompile requires value.
**Fix**: Ensure the calling function is `payable` and forwards `msg.value`.



### `pointer precompile is retired; EVM pointer creation is disabled`
**Cause**: EVM pointer creation has been retired. The pointer precompile at `0x…100b` stays registered so its `addNativePointer`, `addCW20Pointer`, `addCW721Pointer`, and `addCW1155Pointer` selectors still decode, but every call now reverts with this reason. The removed `seid tx evm register-evm-pointer`, `seid tx evm call-precompile pointer addNativePointer`, `seid tx evm add-cw-erc20-pointer`, and the pointer governance proposals (`AddERCNativePointer`/`AddERCNativePointerProposalV2`, `AddERCCW20/721/1155Pointer`, `AddCWERC20/721/1155Pointer`) all fail the same way — proposals now return `ErrPointerProposalDeprecated`.
**Fix**: None — there is no retry, flag, or workaround that re-enables creation. Do not attempt to create a new pointer of any kind. Pointers registered before the retirement remain live and readable: their registry entries, versions, and `seid query evm pointer`-equivalent lookups (via the pointerview precompile at `0x…100A`) are unchanged, and their deployed ERC20/721/1155 contracts keep working. Only creation of new pointers is disabled.

### `JSON precompile: path not found`
**Cause**: `extractAs*` function given a JSON path that doesn't exist in the input.
**Fix**: Validate JSON structure before passing to precompile. Use try/catch.
Expand Down
35 changes: 35 additions & 0 deletions skill/references/contracts/performance-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,41 @@ Source: https://github.com/sei-protocol/sei-chain/tree/main/loadtest

You don't need to fork it. Build your own loadtest in TypeScript with viem (above) — same shape, easier to iterate.



### evmonly-loadtest

`giga/evmonly/cmd/evmonly-loadtest` is a standalone binary that feeds synthetic blocks to the EVM-only executor through the disk-backed Giga state and receipt stores (no Cosmos SDK state, mempool, or RPC).

Build it:

```bash
make build-evmonly-loadtest
```

This writes `./build/evmonly-loadtest`. `go run ./giga/evmonly/cmd/evmonly-loadtest` is equivalent when you don't want a binary.

Run a bounded prebuilt test:

```bash
./build/evmonly-loadtest --blocks=1000 --txs-per-block=1000
```

**`--storage-dir`** sets the GigaStorageManager home directory:

- Empty (default) → a temporary directory is used and removed on exit.
- A set path is created if missing and is **kept** after the run.

```bash
./build/evmonly-loadtest \
--blocks=1000 \
--txs-per-block=1000 \
--storage-dir=/tmp/evmonly-storage
```

Note: a second run against an already-populated `--storage-dir` will fail at genesis commit — point each kept run at a fresh (empty or non-existent) directory.


## Common bottlenecks discovered by load testing

| Symptom | Likely cause | Fix |
Expand Down
10 changes: 6 additions & 4 deletions skill/references/contracts/tokens.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,11 +97,13 @@ USDC on Sei is a native ERC20 — no pointer or bridging step needed.

| Legacy | Recommended |
|---|---|
| CW20 token | ERC20 token + optional pointer |
| CW721 NFT | ERC721 NFT + optional pointer |
| Native denom | Native denom + ERC20 pointer (TokenFactory) |
| CW20 token | ERC20 token |
| CW721 NFT | ERC721 NFT |
| Native denom | Native denom (TokenFactory) |

For existing CW20/CW721 tokens: register an ERC20/ERC721 pointer to make them accessible in EVM wallets while migrating. See [pointers/overview.md](../pointers/overview.md).
> **EVM pointer creation is disabled.** The pointer precompile is retired, and transactions that previously created pointers now revert with `pointer precompile is retired; EVM pointer creation is disabled`. The CLI commands and governance proposals that registered pointers have been removed (`seid tx evm register-evm-pointer`, `seid tx evm call-precompile pointer addNativePointer`, `seid query evm pointer`, `seid tx evm add-cw-erc20-pointer`, and the `AddERC*/AddCW*Pointer` proposal types).

For existing CW20/CW721 tokens there is **no longer any way to create a new pointer** to make them accessible in EVM wallets — new tokens should be deployed natively as ERC20/ERC721. Only pointers registered before the retirement remain live and readable.

## Native Denoms

Expand Down
2 changes: 1 addition & 1 deletion skill/references/ecosystem/integration-defi.md
Original file line number Diff line number Diff line change
Expand Up @@ -240,7 +240,7 @@ Pointer addresses are deterministic from the underlying CW20 denom. See [pointer

## Sei-specific notes

- **WSEI** (wrapped SEI) plays the role of WETH. Verify the canonical WSEI address via [docs.sei.io ecosystem contracts](https://docs.sei.io/evm/ecosystem-contracts).
- **WSEI** (wrapped SEI) plays the role of WETH. It is an already-deployed ecosystem contract — verify the canonical WSEI address via [docs.sei.io ecosystem contracts](https://docs.sei.io/evm/ecosystem-contracts). There is no CLI deployment path for it: the `seid tx evm deploy-wsei` subcommand and its bundled WSEI contract artifacts have been removed. To get WSEI, call `deposit()` (or send SEI) on the already-deployed WSEI contract — do not attempt to deploy your own.
- **Native SEI** uses 18 decimals (not 6 like Cosmos-side `usei` micro-denom — that's a Cosmos-side concept; EVM sees 18 decimals).
- **Atomic batching**: account abstraction (see [contracts/account-abstraction.md](../contracts/account-abstraction.md)) lets users do approve+swap in one user op without a separate approval tx.
- **Liquidation latency**: 400ms blocks make liquidation MEV competitive; bots can react within 1-2 blocks.
94 changes: 92 additions & 2 deletions skill/references/ecosystem/node-operations.md
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,29 @@ ss-keep-recent = 100000 # Keep last 100k blocks
ss-prune-interval = 600
```


---

## Receipt-store reward percentiles (`receipt-store.rs-reward-percentiles`)

Controls the per-block gas-weighted reward percentiles computed and stored alongside each block's receipts. These are what the EVM-only (giga) RPC server's `eth_feeHistory` reward rows and `eth_gasPrice` congestion escalation read from.

```toml
[receipt-store]
# Gas-weighted eth_feeHistory reward percentiles stored per block.
# Applies ONLY when rs-backend = "littidx".
# Each entry must be in [0, 100], with no duplicates.
# An empty list ([]) defaults to [0, 10, 20, 25, 30, 50, 75, 90, 100].
rs-reward-percentiles = []
```

- **littidx backend only.** The pebble backend does not group receipts by block and records no block stats; `eth_feeHistory`/`eth_gasPrice` callers fall back to recomputing from receipts.
- **Validation (startup fails if violated):** each entry must be within `[0, 100]`, there must be no duplicates, and the list must be 100 entries or fewer.
- **Empty default:** an empty list (`[]`) applies the built-in default `[0, 10, 20, 25, 30, 50, 75, 90, 100]`.
- **Read through the AppOptions/viper key** `receipt-store.rs-reward-percentiles`. Settable via a comma- or whitespace-separated environment-variable string (e.g. `0,50,100`) in addition to a TOML float array.
- A requested `eth_feeHistory` percentile not covered by the stored set is recomputed from that block's receipts rather than approximated.


---

## SeiDB storage, RocksDB, and Giga
Expand All @@ -181,6 +204,51 @@ SeiDB has two layers: **State Commit (SC)** — a memiavl Merkle tree that holds
The migration is staged: `migrate_evm` drains EVM data in the background and settles at `evm_migrated`; later modes migrate the remaining modules.
- **Giga Executor** (`[giga_executor] enabled`) is a *separate* feature — an evmone-based EVM interpreter for throughput. Don't conflate it with Giga Storage.


### `seidb` CLI from the Docker image

The official Docker image now builds and ships the `seidb` tool binary at `/usr/bin/seidb` alongside `seid` ([sei-chain#4323 build change](https://github.com/sei-protocol/sei-chain)). Container users no longer need to build it separately — run it directly:

```bash
docker run --rm -v $HOME/.sei:/root/.sei <sei-image> seidb --help
```

- `seidb` is pure Go — it is built with `CGO_ENABLED=0` and does not link `libwasmvm`, so it runs standalone in the container.
- Use it for SeiDB State Store / State Commit inspection and maintenance tasks against the node's data directory (mount `$HOME/.sei` into the container).
- Note the post-v6.8 tooling change: `oracle` has been removed from the seidb `AllModules` list, so module-iterating subcommands no longer include it.



---

## `[giga]` app.toml section

A `[giga]` section in `app.toml` is honored on the Autobahn node ([sei-chain#4323](https://github.com/sei-protocol/sei-chain/pull/4323)). It carries Giga-specific node settings read by the Autobahn executor path; place it as its own top-level `[giga]` table in `app.toml`.

```toml
[giga]
# Giga-specific settings honored on the Autobahn node.
```

- Distinct from `[giga_executor]` (the evmone interpreter toggle) and from the SeiDB SC FlatKV routing (`[state-commit]` keys) — do not conflate the three.

---

## Node config from `sei.toml` (ConfigManager)

ConfigManager sources node configuration from a node's `sei.toml` file ([sei-chain#4043](https://github.com/sei-protocol/sei-chain/pull/4043), [#4045](https://github.com/sei-protocol/sei-chain/pull/4045)). `sei.toml` lives alongside the other config files under `$HOME/.sei/config/`, and ConfigManager reads it to resolve node section settings in addition to the established `app.toml` / `config.toml` / `client.toml`.

```
$HOME/.sei/config/
├── app.toml
├── config.toml
├── client.toml
├── sei.toml # ConfigManager node sections
├── genesis.json
├── node_key.json
└── priv_validator_key.json
```

> Minimum gas price, block gas limit, and SSTORE/storage gas are governance-adjustable — confirm live values at https://docs.sei.io/evm/differences-with-ethereum, and set `minimum-gas-prices` at or above the mainnet floor (`0usei` is local-dev only).


Expand Down Expand Up @@ -250,7 +318,6 @@ Both fields are read through the AppOptions/viper keys `evm.trace_allowed_tracer
| `26656` | TCP | P2P — must be open to join the network |
| `26657` | TCP | Tendermint RPC |
| `1317` | TCP | Cosmos REST API |
| `9090` | TCP | gRPC |
| `8545` | TCP | EVM JSON-RPC (HTTP) |
| `8546` | TCP | EVM JSON-RPC (WebSocket) |
| `26660` | TCP | Prometheus metrics (disabled by default) |
Expand Down Expand Up @@ -315,6 +382,30 @@ make install
sudo systemctl restart seid
```


---

## v6.8 Upgrade: Oracle Module Removal (one-way)

The v6.8 upgrade ([sei-chain#4319](https://github.com/sei-protocol/sei-chain/pull/4319)) removes the oracle module — its store, keeper, param subspace, protobuf schema, wasm query route, and tooling are deleted. Only the oracle `Msg` types remain decodable so historical blocks still trace. The change is **app-hash breaking at the upgrade height**, and the oracle store is dropped via `StoreUpgrades.Deleted`.

### Operator actions

- **Upgrade to v6.8 at the scheduled plan height.** An unupgraded (v6.7) binary has no `v6.8` upgrade handler and **halts at the plan height** with `UPGRADE "v6.8" NEEDED` rather than advancing — build and stage the v6.8 binary before the halt height as with any governance upgrade.
- **Downgrade to v6.7 is impossible after migration.** Once v6.8 has run and deleted the oracle store, a v6.7 binary **panics on reopen** (missing `store "oracle"`). Do not roll back the binary after the upgrade height; restore from a pre-upgrade backup if you must return to v6.7.
- The migration deletes the oracle store and removes the oracle module version from the version map. No oracle genesis state is exported after the upgrade.

### Post-upgrade behavior

- Oracle CLI is gone: `seid q oracle ...` returns `unknown command "oracle"`.
- Oracle gRPC/REST query and Msg endpoints are removed; a raw store query against `oracle` returns `no such store: oracle` (no longer the old deprecation error).
- The CosmWasm `oracle` query route is removed — contracts hitting it now get an unknown route.
- Oracle transactions submitted after the upgrade are rejected **before fees are charged** (previously rejected but still charged a fee and consumed a sequence number).

### Tooling module lists

The `oracle` entry is removed from all tooling module lists — `scripts/dump_app_state_for_height.sh`, the seidb `AllModules` list, and the iaviewer helpers. Scripts and iaviewer invocations that iterate the module list no longer include `oracle`; remove any hardcoded `oracle` references in your own dump/inspect wrappers after upgrading.

---

## Freeze Height (`--freeze-height` / `freeze-height`)
Expand Down Expand Up @@ -346,7 +437,6 @@ To serve historical EVM JSON-RPC from frozen nodes behind one endpoint, put [fro
### Validation constraints (startup fails if violated)

- `freeze-height` **cannot be combined with `halt-height` or `halt-time`**.
- `--freeze-height` **cannot be used with grpc-only mode**.
- **Full nodes only** — not supported in validator or seed mode (`mode = "validator"` / `mode = "seed"` in `config.toml`).
- **Not supported with Autobahn** (fails if `autobahn-config-file` is set).
- Must **not exceed `MaxInt64`** (`9223372036854775807`).
Expand Down
3 changes: 2 additions & 1 deletion skill/references/ecosystem/rpc-providers.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,8 @@ Public, community, and paid RPC endpoints for Sei. Use this as the source of tru
| `https://evm-rpc.sei-apis.com` | EVM JSON-RPC | Primary EVM endpoint |
| `https://rpc.sei-apis.com` | Cosmos Tendermint RPC | Native Cosmos RPC |
| `https://rest.sei-apis.com` | Cosmos REST/LCD | Cosmos SDK REST |
| `grpcs://grpc.sei-apis.com:443` | Cosmos gRPC | High-performance native |

> **Cosmos gRPC removed:** `seid` no longer runs the Cosmos gRPC (port 9090) or gRPC-Web (port 9091) servers — the `[grpc]` and `[grpc-web]` config sections are gone and no gRPC endpoint is served. The former `grpcs://grpc.sei-apis.com:443` endpoint no longer serves native gRPC. Query over Cosmos REST/LCD (`https://rest.sei-apis.com`) or Tendermint RPC (`https://rpc.sei-apis.com`) instead.

### Community (free)

Expand Down
8 changes: 8 additions & 0 deletions skill/references/ecosystem/staking-governance.md
Original file line number Diff line number Diff line change
Expand Up @@ -253,6 +253,14 @@ seid tx gov submit-proposal software-upgrade v5.9.0 \

### Expedited Proposal (Fast-Track)



> **App-hash-breaking upgrades delete state (e.g. v6.8).** The v6.8 upgrade removes the `oracle` module and **deletes its store** at the upgrade height via `StoreUpgrades.Deleted`, also removing the oracle module version from the version map. This is app-hash breaking at the plan height. Operational consequences a software-upgrade proposal implies:
> - Unupgraded (v6.7) binaries **halt** at the plan height instead of producing a divergent block.
> - A v6.7 binary **cannot reopen** a database already migrated by v6.8 — it panics on the missing oracle store. Downgrade past v6.8 is impossible once migration has run; back up data before upgrading.
> - After v6.8, oracle commands are gone (`seid q oracle ...` returns `unknown command "oracle"`) and store queries for oracle return `no such store: oracle`. Only oracle `Msg` types remain decodable so historical blocks still trace; oracle transactions submitted after the upgrade are rejected **without charging a fee** (`ErrDeprecated`).


```bash
seid tx gov submit-proposal software-upgrade emergency-patch \
--upgrade-height 20100000 \
Expand Down
3 changes: 2 additions & 1 deletion skill/references/networks.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,9 @@ description: Network information for Sei mainnet and testnet — chain IDs, RPC
| EVM RPC | `https://evm-rpc.sei-apis.com` | `https://evm-rpc-testnet.sei-apis.com` |
| Cosmos RPC | `https://rpc.sei-apis.com` | `https://rpc-testnet.sei-apis.com` |
| REST/LCD | `https://rest.sei-apis.com` | `https://rest-testnet.sei-apis.com` |
| gRPC | `https://grpc.sei-apis.com` | `https://grpc-testnet.sei-apis.com` |
| WebSocket (EVM) | `wss://evm-ws.sei-apis.com` | `wss://evm-ws-testnet.sei-apis.com` |

> **No Cosmos gRPC endpoint:** seid no longer runs the Cosmos gRPC or gRPC-Web servers (ports 9090/9091 are gone, along with the `[grpc]` and `[grpc-web]` config sections). Query the node over REST/LCD (`rest.sei-apis.com`) or Cosmos RPC (`rpc.sei-apis.com`) instead. Clients that previously used `grpc.sei-apis.com` must migrate to REST or Tendermint RPC.
| Explorer | https://seiscan.io | https://testnet.seiscan.io |
| Faucet | N/A | https://atlantic-2.app.sei.io/faucet |

Expand Down
Loading
Loading