Skip to content

feat: live midnight stagenet <-> sepolia NIGHT bridge deployment - #3

Open
ctoyan wants to merge 3 commits into
midnight-v1from
feat/midnight-stagenet-deployment
Open

feat: live midnight stagenet <-> sepolia NIGHT bridge deployment#3
ctoyan wants to merge 3 commits into
midnight-v1from
feat/midnight-stagenet-deployment

Conversation

@ctoyan

@ctoyan ctoyan commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

Registry entries for the currently running stagenet <-> sepolia NIGHT bridge: midnight core addresses with the deploy-block index.from, the sepolia-side hook stack (dedicated MerkleTreeHook, InterchainGasPaymaster, StorageGasOracle, aggregation hook and its factory), rpcConsensusType: fallback for sepolia, and the NIGHT warp route config including the midnight IGP token entry.

Merging this also makes the Explorer's registry-fed panels resolve for the deployment (it reads this branch).

🤖 Generated with Claude Code

ctoyan added 3 commits August 21, 2026 19:31
Core addresses and index.from for the current stagenet deployment, the
sepolia-side hook stack (own merkle tree hook, IGP, oracle, aggregation
hook and factory), fallback RPC consensus for sepolia, and the NIGHT
warp route config with the midnight IGP token entry.
The runtime registry reads the combined warpRouteConfigs.yaml, which
still carried the pre-reset route; cd42c5c only updated the per-route
files. Schemas are left untouched: regenerating them against the public
SDK drops the midnight protocol and token standards.
The generated warp-core config stamped the synthetic's sNIGHT symbol on
both legs and dropped the 1e12 scale, so the Explorer showed raw wire
amounts and sNIGHT as the origin token for Midnight.
@ctoyan ctoyan self-assigned this Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant