Extension Chains: smart contracts for NoM

Development ╰ Funding | Staging
63

Open-source explorer for the XZNN EVM:

Who wants to do this deployment?

3 Likes
64

Legend. Thank you :pray:

2 Likes
65

I attempted to deploy a similar explorer but it wasn’t able to access the entire chain state via the RPC url you provided. Maybe I was doing something wrong.

That’s why I asked if we could run nodes on the testnet.
Blockscout documentation states that we require a full archival node.

66

The RPC is from a full archival node.

At the moment this is just a devnet with a limited number of validator nodes. A public testnet will follow.

What error did you get?

67

I can try to spin one up today

68

Which node variant are you using and which ports have you exposed?

69

The node variant is a fork based on exchain codebase.

I’ve exposed only the EVM port. You’ll be able to participate when I’ll announce the public testnet.

70

For the explorer frontend .env settings…

ETHEREUM_JSONRPC_VARIANT: 'ganache' # << What should this be??
ETHEREUM_JSONRPC_HTTP_URL:  https://ext-testnet.zenon.community:8545/ # CORRECT?
ETHEREUM_JSONRPC_WS_URL:  wss://ext-testnet.zenon.community8545/ # CORRECT?
INDEXER_DISABLE_INTERNAL_TRANSACTIONS_FETCHER: 'true'
INDEXER_DISABLE_PENDING_TRANSACTIONS_FETCHER: 'true'
DATABASE_URL: postgresql://postgres:@host.docker.internal:7432/blockscout?ssl=false
ECTO_USE_SSL: 'false'
SECRET_KEY_BASE: '56NtB48ear7+wMSf0IQuWDAAazhpb31qyc7GiyspBP2vh7t5zlCsF5QDv76chXeN'
CHAIN_ID: '1337'
API_V2_ENABLED: 'true' # NOTE SURE WHAT THIS IS WILL TEST
MIX_ENV: 'prod' # I ASSUME THIS IS CORRECT
71

@sol did you just setup the frontend only?

72

ETHEREUM_JSONRPC_VARIANT: 'ganache' # << What should this be??

  • I don’t know.

ETHEREUM_JSONRPC_HTTP_URL: https://ext-testnet.zenon.community:8545/ # CORRECT?

  • Remove the port

ETHEREUM_JSONRPC_WS_URL: wss://ext-testnet.zenon.community8545/ # CORRECT?

  • Remove this line entirely

CHAIN_ID: '73405'

  • Use 73405 as chainId
2 Likes
73

cool - I’ll mess with it today.

1 Like
74

Requesting 10k xZNN: 0xD63Aa61977493de5235Dc0Ecc6994035D9f16e7B

Thank you.

75

Any update @aliencoder ?

77

I’m finishing the dynamic Plasma proposal right now and after that I’ll be back working on extension chains.

2 Likes
78

Please remove the fee.

79

The devnet for the extension chain is up and running again.

All previous balances were preserved.

Extension chain RPC details:

Network name: XZNN
New RPC URL: https://ext-testnet.zenon.community
Chain ID: 73405
Currency symbol: xZNN
Block explorer URL: TBA

7 Likes
80

Requesting 5K xZNN

0x89A2279C8Fb664b97a1b71eFb3Fa169AFd75f6c4

81

The idea is to deploy a Tendermint light client as an embedded contract on NoM to provide a bridge between NoM and Cosmos based chains (the extension-chain is a Cosmos chain fork).

“Light clients (and full nodes) operating in the Proof Of Stake context need a trusted block height from a trusted source that is no older than 1 unbonding window plus a configurable evidence submission synchrony bound. This is called weak subjectivity.”

“IBC uses light clients in order to provide trust-minimized interoperability between sovereign blockchains. Light clients operate under a strict set of rules which provide security guarantees for state updates and facilitate the ability to verify the state of a remote blockchain using merkle proofs.”

1 Like
82

Are you thinking we do NOT use the bridge for connection between the L1 and Extension Chain?

83

For v1 we should use the bridge. Fastest go-to-market strategy.

2 Likes