[Feature] - Add Chain Agnostic Blockchain Reference

[0xzoz]

Add Chain Agnostic Blockchain Reference

• Define a CAIP-2 blockchain reference for Sui.

Motivation

To be able to reference SUI for an integration I am looking at completing for Ceramic Network there is a need to have a blockchain reference in Chain Agnostic. This will be the discussion point for the CAIP that I will be submitting shortly.

[0xzoz]

Hey team, here is a draft. I'm not sure how far the discussions are regarding a reference framework or if there is any information available publicly. Any insight?

[0xzoz]

This PR and conversation have been moved to the namespace repository ChainAgnostic/namespaces#43

[joyqvq]

wondering what support for this does the sui repo need? does signature needs to commit to this namespace or this is for other usages?

the rfc looks fine to me otherwise to give identifier for network names.

[0xzoz]

Thanks for querying @joyqvq. Nothing is needed in the Sui repo. This was created to provide a place for discussions(as specified in the PR request criteria from Chain Agnostic).

What's required is documentation and/or verification that the namespaces for the sui network are what is specified in the CAIP. While looking in the repo and discord I could see no standard to what sui networks are referred as.

For reference the CAIP has the following sui references:

# Sui mainnet
sui:mainnet
# Sui testnet
sui:testnet
# sui devnet
sui:devnet

Other blockchain CAIPs may provide more context and can be found here

[bumblefudge]

namespaces editor here!

many namespaces opt for a hash (or subset of a hash) of the genesis block, rather than a concise string identifier, to prevent forks sharing an identifier on systems where a node can return the genesis hash of its chain. Reading around the CAIP-2 profiles in namespaces provides some context on different approaches to chain identification; I leave it to the sui team to decide if the referent of "mainnet" and "testnet" will remain constant or if there is a dispute/ambiguity resolution mechanism built into the node RPC's info/help/etc commands :D

[0xzoz]

Thanks for the insight @bumblefudge. Thats some good information to keep in mind and makes a lot of sense. I'm not sure if that works for all networks though considering Devnet is dynamic and will change regularly(well,it has been in these early stages). Still waiting on some input from the team but it looks like there has been the appoach of naming via 'testnet' and 'devnet' here.