base on Fuel Network Rust SDK # fuels-rs [](https://github.com/FuelLabs/fuels-rs/actions/workflows/ci.yml) [](https://crates.io/crates/fuels) [](https://docs.rs/fuels) [](https://discord.gg/xfpK4Pe) Rust SDK for Fuel. It can be used for a variety of things, including but not limited to: - Compiling, deploying, and testing [Sway](https://github.com/FuelLabs/sway) contracts; - Launching a local Fuel network; - Crafting and signing transactions with hand-crafted scripts or contract calls; - Generating type-safe Rust bindings of contract methods; - And more, `fuels-rs` is still in active development. ## Documentation See [the `fuels-rs` book](https://fuellabs.github.io/fuels-rs/latest/) ## Features - [x] Launch Fuel nodes - [x] Deploy contracts - [x] Interact with deployed contracts - [x] Type-safe Sway contracts bindings code generation - [x] Run Sway scripts - [x] CLI for common operations - [x] Local test wallets - [ ] Wallet integration - [ ] Events querying/monitoring ## FAQ ### What dependencies do I need? - [The latest `stable` Rust toolchain](https://docs.fuel.network/guides/installation/#installing-rust); - [`forc` and `fuel-core` binaries](https://docs.fuel.network/guides/installation/#installing-the-fuel-toolchain-using-fuelup). ### How can I run the SDK tests? First, build the test projects using `forc`: ```shell forc build --release --path e2e ``` Then you can run the SDK tests with: ```shell cargo test ``` You can also run specific tests. The following example will run all integration tests in `types.rs` whose names contain `in_vector` and show their outputs: ```shell cargo test --test types in_vector -- --show-output ``` ### How to run WASM tests? You need to have wasm32 as a target, if you don't already: ```shell rustup target add wasm32-unknown-unknown ``` You also need `wasm-pack`, if you don't already: ```shell cargo install wasm-pack ``` Navigate to `packages/wasm-tests` and run `wasm-pack test`. ### What to do if my tests are failing on `master` Before doing anything else, try all these commands: ```shell cargo clean rm Cargo.lock forc build --release --path e2e cargo test ``` ### Why is the prefix `fuels` and not `fuel`? In order to make the SDK for Fuel feel familiar with those coming from the [ethers.js](https://github.com/ethers-io/ethers.js) ecosystem, this project opted for an `s` at the end. The `fuels-*` family of SDKs is inspired by The Ethers Project. ### How can I run the docs locally? Install `mdbook` by running: ```shell cargo install mdbook ``` Next, navigate to the `docs` folder and run the command below to start a local server and open a new tab in your browser. ```shell mdbook serve --open ``` You can build the book by running: ```shell mdbook build ``` ", Assign "at most 3 tags" to the expected json: {"id":"1581","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"