Change ChainDescriptions into blobs (#3787)

## Motivation

This will allow for easier initialization of the network at genesis,
among other things.

## Proposal

`ChainDescription` will become a blob, and `OpenChain` messages will be
removed. Calling `open_chain` will create the blob, and the chain will
actually get initialized when a block is proposed for it.

## Test Plan

Should be covered by CI.

## Release Plan

- Nothing to do / These changes follow the usual release cycle.

## Links

- [reviewer
checklist](https://github.com/linera-io/linera-protocol/blob/main/CONTRIBUTING.md#reviewer-checklist)
- #2390

Author: bart-linera

.github/workflows/rust.yml

@@ -64,7 +64,7 @@ jobs:
         cargo build --bin linera
         cargo run --bin linera -- resource-control-policy --block 0.0000001
         cargo run --bin linera -- resource-control-policy --block 0.000000
-        cargo run --bin linera -- faucet --amount 1000 --port 8079 a3edc33d8e951a1139333be8a4b56646b5598a8f51216e86592d881808972b07 &
+        cargo run --bin linera -- faucet --amount 1000 --port 8079 &
     - name: Run the remote-net tests
       run: |
         cargo test -p linera-service remote_net_grpc --features remote-net

CLI.md

@@ -720,12 +720,12 @@ Create an unassigned key pair
 
 Link an owner with a key pair in the wallet to a chain that was created for that owner
 
-**Usage:** `linera assign --owner <OWNER> --message-id <MESSAGE_ID>`
+**Usage:** `linera assign --owner <OWNER> --chain-id <CHAIN_ID>`
 
 ###### **Options:**
 
 * `--owner <OWNER>` — The owner to assign
-* `--message-id <MESSAGE_ID>` — The ID of the message that created the chain. (This uniquely describes the chain and where it was created.)
+* `--chain-id <CHAIN_ID>` — The ID of the chain
 
 
 

README.md

@@ -99,9 +99,9 @@ linera wallet init --faucet $FAUCET_URL
 INFO1=($(linera wallet request-chain --faucet $FAUCET_URL))
 INFO2=($(linera wallet request-chain --faucet $FAUCET_URL))
 CHAIN1="${INFO1[0]}"
-ACCOUNT1="${INFO1[3]}"
+ACCOUNT1="${INFO1[2]}"
 CHAIN2="${INFO2[0]}"
-ACCOUNT2="${INFO2[3]}"
+ACCOUNT2="${INFO2[2]}"
 
 # Show the different chains tracked by the wallet.
 linera wallet show

examples/Cargo.lock

@@ -2,15 +2,15 @@
 resolver = "2"
 members = [
     "amm",
-    "counter",
     "call-evm-counter",
+    "counter",
     "counter-no-graphql",
     "crowd-funding",
     "ethereum-tracker",
     "fungible",
     "gen-nft",
-    "how-to/perform-http-requests",
     "hex-game",
+    "how-to/perform-http-requests",
     "llm",
     "matching-engine",
     "meta-counter",

examples/Cargo.toml

@@ -64,9 +64,9 @@ INFO_2=($(linera wallet request-chain --faucet $FAUCET_URL))
 CHAIN_AMM="${INFO_AMM[0]}"
 CHAIN_1="${INFO_1[0]}"
 CHAIN_2="${INFO_2[0]}"
-OWNER_AMM="${INFO_AMM[3]}"
-OWNER_1="${INFO_1[3]}"
-OWNER_2="${INFO_2[3]}"
+OWNER_AMM="${INFO_AMM[2]}"
+OWNER_1="${INFO_1[2]}"
+OWNER_2="${INFO_2[2]}"
 ```
 
 Now we have to publish and create the fungible applications. The flag `--wait-for-outgoing-messages` waits until a quorum of validators has confirmed that all sent cross-chain messages have been delivered.

examples/amm/README.md

@@ -49,7 +49,7 @@ linera wallet init --faucet $FAUCET_URL
 
 INFO_1=($(linera wallet request-chain --faucet $FAUCET_URL))
 CHAIN_1="${INFO_1[0]}"
-OWNER_1="${INFO_1[3]}"
+OWNER_1="${INFO_1[2]}"
 ```
 
 Now, compile the `counter` application WebAssembly binaries, publish and create an application instance.

examples/counter/README.md

@@ -77,8 +77,8 @@ INFO_1=($(linera --with-wallet 1 wallet request-chain --faucet $FAUCET_URL))
 INFO_2=($(linera --with-wallet 2 wallet request-chain --faucet $FAUCET_URL))
 CHAIN_1="${INFO_1[0]}"
 CHAIN_2="${INFO_2[0]}"
-OWNER_1="${INFO_1[3]}"
-OWNER_2="${INFO_2[3]}"
+OWNER_1="${INFO_1[2]}"
+OWNER_2="${INFO_2[2]}"
 ```
 
 Note that `linera --with-wallet 1` is equivalent to `linera --wallet "$LINERA_WALLET_1"

examples/crowd-funding/README.md

@@ -64,10 +64,10 @@ linera wallet init --faucet $FAUCET_URL
 
 INFO_1=($(linera wallet request-chain --faucet $FAUCET_URL))
 CHAIN_1="${INFO_1[0]}"
-OWNER_1="${INFO_1[3]}"
+OWNER_1="${INFO_1[2]}"
 INFO_2=($(linera wallet request-chain --faucet $FAUCET_URL))
 CHAIN_2="${INFO_2[0]}"
-OWNER_2="${INFO_2[3]}"
+OWNER_2="${INFO_2[2]}"
 ```
 
 Now, compile the `fungible` application WebAssembly binaries, and publish them as an application

examples/fungible/README.md

@@ -61,8 +61,8 @@ INFO_1=($(linera wallet request-chain --faucet $FAUCET_URL))
 INFO_2=($(linera wallet request-chain --faucet $FAUCET_URL))
 CHAIN_1="${INFO_1[0]}"
 CHAIN_2="${INFO_2[0]}"
-OWNER_1="${INFO_1[3]}"
-OWNER_2="${INFO_2[3]}"
+OWNER_1="${INFO_1[2]}"
+OWNER_2="${INFO_2[2]}"
 ```
 
 Next, compile the `non-fungible` application WebAssembly binaries, and publish them as an application module: