move CAIP-2 stuff out of readme

ChainAgnostic · Mar 13, 2024 · a80f98c · a80f98c
1 parent d9efbba
commit a80f98c
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 12 deletions.
diff --git a/tezos/README.md b/tezos/README.md
@@ -13,16 +13,7 @@ This document defines the applicability of CAIP schemes to the blockchains of th
 
 ## Syntax
 
-The namespace `tezos` refers to the Tezos open-source blockchain protocol in general. The main implementation is called [Octez][]. The [Tezos test network infrastructure][] provides an overview of the different chains maintained by the community. The Tezos Mainnet can be determined through the genesis block hash: `BLockGenesisGenesisGenesisGenesisGenesisf79b5d1CoW2`.
-
-### Chain IDs
-
-*For context, see the [CAIP-2][] specification and in particular the `tezos-caip2` profile thereof.*
-
-| Alias          | Chain ID                         |
-| -------------- | -------------------------------- |
-| tezos:mainnet  | tezos:NetXdQprcVkpaWU            |
-| tezos:ghostnet | tezos:NetXnHfVqm9iesp            |
+The namespace `tezos` refers to the Tezos open-source blockchain protocol in general. The main implementation is called [Octez][]. The [Tezos test network infrastructure][] provides an overview of the different chains maintained by the community. 
 
 ## References
 

diff --git a/tezos/caip2.md b/tezos/caip2.md
@@ -38,7 +38,8 @@ tezosB58CheckEncode('Net',
 
 ### Chain ID alias
 
-The Tezos community recognizes the different chains according to human readable names, which are called the "[Networks][]". The Octez RPC, for example, allows you to connect to three predefined networks:
+The Tezos community recognizes the different chains according to human readable names, which are called the "[Networks][]".
+The Octez RPC, for example, allows you to connect to three predefined networks by alias:
 
 ```bash
 # mainnet (default)
@@ -48,7 +49,9 @@ The Tezos community recognizes the different chains according to human readable
 > ./octez-node run --data-dir ~/tezos-ghostnet --network ghostnet
 ```
 
-There is currently no algorithm to connect the `chain ID` to the `network` as it is part of the Octez reference implementation of Tezos. In general it is determined by social consensus what chain ID is considered as `tezos:mainnet`. It is RECOMMENDED to use a separate chain registry to map an alias to the chain ID.
+There is currently no algorithm to connecting `chain ID`s to `network`s in the Octez reference implementation of Tezos.
+In general, social consensus determines which chain ID is considered the "tezos mainnet".
+It is RECOMMENDED to use a separate chain registry to map an alias to the chain ID.
 
 ### Backwards Compatibility