base on Main repository for the Linera protocol # <img src="https://github.com/linera-io/linera-protocol/assets/1105398/fe08c941-93af-4114-bb83-bcc0eaec95f9" width="250" height="85" /> [](LICENSE) [](https://github.com/linera-io/linera-protocol/actions/workflows/docker-compose.yml) [](https://github.com/linera-io/linera-protocol/actions/workflows/rust.yml) [](https://github.com/linera-io/linera-protocol/actions/workflows/documentation.yml) [](https://x.com/linera_io) [](https://discord.com/invite/linera) <!-- [](https://github.com/linera-io/linera-protocol/actions/workflows/kubernetes.yml) --> [Linera](https://linera.io) is a decentralized blockchain infrastructure designed for highly scalable, secure, low-latency Web3 applications. ## Documentation Visit our [developer page](https://linera.dev) and read our [whitepaper](https://linera.io/whitepaper) to learn more about the Linera protocol. ## Repository Structure The main crates and directories of this repository can be summarized as follows: (listed from low to high levels in the dependency graph) * [`linera-base`](https://linera-io.github.io/linera-protocol/linera_base/index.html) Base definitions, including cryptography. * [`linera-version`](https://linera-io.github.io/linera-protocol/linera_version/index.html) A library to manage version info in binaries and services. * [`linera-views`](https://linera-io.github.io/linera-protocol/linera_views/index.html) A library mapping complex data structures onto a key-value store. The corresponding procedural macros are implemented in `linera-views-derive`. * [`linera-execution`](https://linera-io.github.io/linera-protocol/linera_execution/index.html) Persistent data and the corresponding logic for runtime and execution of Linera applications. * [`linera-chain`](https://linera-io.github.io/linera-protocol/linera_chain/index.html) Persistent data and the corresponding logic for chains of blocks, certificates, and cross-chain messaging. * [`linera-storage`](https://linera-io.github.io/linera-protocol/linera_storage/index.html) Defines the storage abstractions for the protocol on top of `linera-chain`. * [`linera-core`](https://linera-io.github.io/linera-protocol/linera_core/index.html) The core Linera protocol, including client and server logic, node synchronization, etc. * [`linera-rpc`](https://linera-io.github.io/linera-protocol/linera_rpc/index.html) Defines the data-type for RPC messages (currently all client &#x2194; proxy &#x2194; chain &#x2194; chain interactions), and track the corresponding data schemas. * [`linera-client`](https://linera-io.github.io/linera-protocol/linera_client/index.html) Library for writing Linera clients. Used for the command-line client and the node service in `linera-service`, as well as the Web client in [`linera-web`](https://github.com/linera-io/linera-web/). * [`linera-service`](https://linera-io.github.io/linera-protocol/linera_service/index.html) Executable for clients (aka CLI wallets), proxy (aka validator frontend) and servers. * [`linera-sdk`](https://linera-io.github.io/linera-protocol/linera_sdk/index.html) The library to develop Linera applications written in Rust for the Wasm virtual machine. The corresponding procedural macros are implemented in `linera-sdk-derive`. * [`examples`](./examples) Examples of Linera applications written in Rust. ## Prerequisites See [`INSTALL.md`](./INSTALL.md) for software requirements to develop in this repo. ## Quickstart with the Linera CLI tool The following commands set up a local test network and run some transfers between the microchains owned by a single wallet. ```bash # Make sure to compile the Linera binaries and add them in the $PATH. # cargo build -p linera-storage-service -p linera-service --bins export PATH="$PWD/target/debug:$PATH" # Import the optional helper function `linera_spawn`. source /dev/stdin <<<"$(linera net helper 2>/dev/null)" # Run a local test network with the default parameters and a number of microchains # owned by the default wallet. This also defines `LINERA_TMP_DIR`. linera_spawn \ linera net up --with-faucet --faucet-port 8080 # Remember the URL of the faucet. FAUCET_URL=http://localhost:8080 # If you're using a testnet, start here and run this instead: # LINERA_TMP_DIR=$(mktemp -d) # FAUCET_URL=https://faucet.testnet-XXX.linera.net # for some value XXX # Set the path of the future wallet. export LINERA_WALLET="$LINERA_TMP_DIR/wallet.json" export LINERA_KEYSTORE="$LINERA_TMP_DIR/keystore.json" export LINERA_STORAGE="rocksdb:$LINERA_TMP_DIR/client.db" # Initialize a new user wallet. linera wallet init --faucet $FAUCET_URL # Request chains. INFO1=($(linera wallet request-chain --faucet $FAUCET_URL)) INFO2=($(linera wallet request-chain --faucet $FAUCET_URL)) CHAIN1="${INFO1[0]}" ACCOUNT1="${INFO1[1]}" CHAIN2="${INFO2[0]}" ACCOUNT2="${INFO2[1]}" # Show the different chains tracked by the wallet. linera wallet show # Query the chain balance of some of the chains. linera query-balance "$CHAIN1" linera query-balance "$CHAIN2" # Transfer 10 units then 5 back. linera transfer 10 --from "$CHAIN1" --to "$CHAIN2" linera transfer 5 --from "$CHAIN2" --to "$CHAIN1" # Query balances again. linera query-balance "$CHAIN1" linera query-balance "$CHAIN2" # Now let's fund the user balances. linera transfer 5 --from "$CHAIN1" --to "$CHAIN1:$ACCOUNT1" linera transfer 2 --from "$CHAIN1:$ACCOUNT1" --to "$CHAIN2:$ACCOUNT2" # Query user balances again. linera query-balance "$CHAIN1:$ACCOUNT1" linera query-balance "$CHAIN2:$ACCOUNT2" ``` More complex examples may be found in our [developer manual](https://linera.dev) as well as the [example applications](./examples) in this repository. ## Contributing We welcome contributions from the community! If you'd like to contribute to the Linera protocol: 1. Fork the repository 2. Create a feature branch (`git checkout -b feature/amazing-feature`) 3. Commit your changes (`git commit -m 'Add some amazing feature'`) 4. Push to the branch (`git push origin feature/amazing-feature`) 5. Open a Pull Request For detailed guidelines, see our [contribution guide](./CONTRIBUTING.md). ", Assign "at most 3 tags" to the expected json: {"id":"11821","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"