You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Cardano has two easily-usable networks: "mainnet" and "testnet". However, in the future, we expect more networks to exist and so we need some way to refer to these networks to be able to write better multi-network applications and systems.
15
20
16
-
## Terminology
17
-
18
-
### Existing network IDs
21
+
## Motivation: why is this CIP necessary?
19
22
20
23
Cardano currently has three ways to refer to a network:
21
24
- The "network ID" included in every address and also optionally present in the transaction body. This only stores 16 possibilities (4 bits)
22
25
- The "network magic" used for Byron addresses and in the handshake with other nodes in the network layer. This is a random 32-bit number
23
26
- The genesis block hash (a 28-byte number)
24
27
25
-
## Motivation
26
-
27
28
Blockchains can have multiple deployments of the same codebase. For example:
28
29
29
30
1. Test networks where the base asset has no value (so devs can test at no cost)
@@ -54,15 +55,21 @@ When representing these networks in a human-readable string, the following forma
54
55
cip34:NetworkId-NetworkMagic
55
56
```
56
57
57
-
# Rationale
58
+
# Rationale: how does this CIP achieve its goals?
58
59
59
60
We pick this format for the following reason:
60
61
- The network ID is too small to be used by itself. You can see from [chainlist](https://chainlist.org/) that 16 possibilities is too few
61
62
- The genesis hash is too long and user-unfriendly to be used.
62
63
63
-
# Reference implementation
64
+
## Path to Active
65
+
66
+
### Acceptance Criteria
67
+
68
+
-[ ] There are at least two (from different providers) wallets, libraries, CLI packages, or other tools which use this standard for network identification.
0 commit comments