[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-568":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":22,"hasPages":22,"topics":23,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":29,"discoverSource":30},568,"fuel-core","FuelLabs\u002Ffuel-core","FuelLabs","Rust full node implementation of the Fuel v2 protocol.","",null,"Rust",57019,2865,221,161,0,2,45,"Other",false,"master",true,[24,25],"blockchain","fuel","2026-06-12 02:00:15","# Fuel Client\n\n[![build](https:\u002F\u002Fgithub.com\u002FFuelLabs\u002Ffuel-core\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002FFuelLabs\u002Ffuel-core\u002Factions\u002Fworkflows\u002Fci.yml)\n[![deepwiki](https:\u002F\u002Fdeepwiki.com\u002Fbadge.svg)](https:\u002F\u002Fdeepwiki.com\u002FFuelLabs\u002Ffuel-core)\n[![crates.io](https:\u002F\u002Fimg.shields.io\u002Fcrates\u002Fv\u002Ffuel-core?label=latest)](https:\u002F\u002Fcrates.io\u002Fcrates\u002Ffuel-core)\n[![docs](https:\u002F\u002Fdocs.rs\u002Ffuel-core\u002Fbadge.svg)](https:\u002F\u002Fdocs.rs\u002Ffuel-core\u002F)\n[![discord](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fchat%20on-discord-orange?&logo=discord&logoColor=ffffff&color=7389D8&labelColor=6A7EC2)](https:\u002F\u002Fdiscord.gg\u002FxfpK4Pe)\n[![twitter](https:\u002F\u002Fimg.shields.io\u002Ftwitter\u002Ffollow\u002Ffuel_network)](https:\u002F\u002Fx.com\u002Ffuel_network)\n\nFuel client implementation.\n\n## Versions currently used in networks\n\n| Network  | Version |\n|----------|---------|\n| Fuel Ignition | 0.47.4  |\n| Testnet | 0.48.0  |\n| Devnet | 0.48.0  |\n\n## Contributing\n\nIf you are interested in contributing to Fuel, see our [CONTRIBUTING.md](CONTRIBUTING.md) guidelines for coding standards and review process.\n\nBefore pushing any changes or creating pull request please run `source ci_checks.sh`.\n\n## Building\n\nIf you plan to use already pre-compiled binaries you can directly go to [Running a Ignition node](#running-a-ignition-node).\n\n### System Requirements\n\nThere are several system requirements including clang.\n\n#### MacOS\n\n```bash\nbrew update\nbrew install cmake\n```\n\n#### Debian\n\n```bash\napt update\napt install -y cmake pkg-config build-essential git clang libclang-dev\n```\n\n#### Arch\n\n```bash\npacman -Syu --needed --noconfirm cmake gcc pkgconf git clang\n```\n\n### Rust setup\n\nYou'll need `wasm32-unknown-unknown` target installed.\n\n```bash\nrustup target add wasm32-unknown-unknown\n```\n\n\n## Running a Ignition node\n\nIf you want to participate in the Ignition network with your own node you can launch it following these simple commands.\n\n### From pre-compiled binaries\n\nFollow : https:\u002F\u002Fdocs.fuel.network\u002Fdocs\u002Fnode-operator\u002Ffuel-ignition\u002Fmainnet-node\u002F\n\n### From source\n\nClone the `fuel-core` repository : \n```\ngit clone https:\u002F\u002Fgithub.com\u002FFuelLabs\u002Ffuel-core.git\n```\n\nGo to the latest release tag for ignition on the `fuel-core` repository :\n```\ngit checkout v0.45.1\n```\n\nBuild your node binary:\n```bash\nmake build\n```\n\nTo run the node follow : https:\u002F\u002Fdocs.fuel.network\u002Fdocs\u002Fnode-operator\u002Ffuel-ignition\u002Fmainnet-node\u002F\n\n## Running a Local network from source\n\nClone the `fuel-core` repository : \n```\ngit clone https:\u002F\u002Fgithub.com\u002FFuelLabs\u002Ffuel-core.git\n```\n\nBuild your node binary:\n```bash\nmake build\n```\n\nTo run the node follow : https:\u002F\u002Fdocs.fuel.network\u002Fdocs\u002Fnode-operator\u002Ffuel-ignition\u002Flocal-node\u002F\n\n## Setup to make contributions\n\n### Compiling\n\nWe recommend using `xtask` to build fuel-core for development:\n\n```sh\ncargo xtask build\n```\n\nThis will run `cargo build` as well as any other custom build processes we have such as re-generating a GraphQL schema for the client.\n\n### Testing\n\nThe [ci_checks.sh](ci_checks.sh) script file can be used to run all CI checks,\nincluding the running of tests.\n\n```shell\nsource ci_checks.sh\n```\n\nThe script requires pre-installed tools. For more information run:\n\n```shell\ncat ci_checks.sh\n```\n\n## Running\n\nThe service can be launched by executing `fuel-core run`. The list of options for running can be accessed via the `help` option:\n\n```console\n$ .\u002Ftarget\u002Fdebug\u002Ffuel-core run --help\n\nUSAGE:\n    fuel-core run [OPTIONS]\n\nOPTIONS:\n        --snapshot \u003CSNAPSHOT>\n          Snapshot from which to do (re)genesis. Defaults to local testnet configuration\n\n          [env: SNAPSHOT=]\n        ...\n```\n\nFor many development purposes it is useful to have a state that won't persist and the `db-type` option can be set to `in-memory` as in the following example.\n\n### Example\n\n```console\n$ .\u002Ftarget\u002Fdebug\u002Ffuel-core run --db-type in-memory\n2023-06-13T12:45:22.860536Z  INFO fuel_core::cli::run: 230: Block production mode: Instant\n2023-06-13T12:38:47.059783Z  INFO fuel_core::cli::run: 310: Fuel Core version v0.18.1\n2023-06-13T12:38:47.078969Z  INFO new{name=fuel-core}:_commit_result{block_id=b1807ca9f2eec7e459b866ecf69b68679fc6b205a9a85c16bd4943d1bfc6fb2a height=0 tx_status=[]}: fuel_core_importer::importer: 231: Committed block\n2023-06-13T12:38:47.097777Z  INFO new{name=fuel-core}: fuel_core::graphql_api::service: 208: Binding GraphQL provider to 127.0.0.1:4000\n```\n\nTo disable block production on your local node, set `--poa-instant=false`\n\n### Example\n\n```console\n$ .\u002Ftarget\u002Fdebug\u002Ffuel-core run --poa-instant=false\n2023-06-13T12:44:12.857763Z  INFO fuel_core::cli::run: 232: Block production disabled\n```\n\n### Troubleshooting\n\n#### Publishing\n\nWe use [`publish-crates`](https:\u002F\u002Fgithub.com\u002Fkatyo\u002Fpublish-crates) action for automatic publishing of all crates.\n\nIf you have problems with publishing, you can troubleshoot it locally with [`act`](https:\u002F\u002Fgithub.com\u002Fnektos\u002Fact).\n\n```shell\nact release -s GITHUB_TOKEN=\u003CYOUR_GITHUB_TOKEN> -j publish-crates-check --container-architecture linux\u002Famd64 --reuse\n```\n\nIt requires GitHubToken to do request to the GitHub. You can create it \nwith [this](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fenterprise-server@3.4\u002Fauthentication\u002Fkeeping-your-account-and-data-secure\u002Fcreating-a-personal-access-token) instruction.\n\n#### Outdated database\n\nIf you encounter an error such as\n\n```console\nthread 'main' panicked at 'unable to open database: DatabaseError(Error { message: \"Invalid argument: Column families not opened: column-11, column-10, column-9, column-8, column-7, column-6, column-5, column-4, column-3, column-2, column-1, column-0\" })', fuel-core\u002Fsrc\u002Fmain.rs:23:66\n```\n\nClear your local database using: `rm -rf ~\u002F.fuel\u002Fdb`\n\n#### File descriptor limits\n\nOn some macOS versions the default file descriptor limit is quite low, which can lead to IO errors with messages like `Too many open files` or even `fatal runtime error: Rust cannot catch foreign exceptions` when RocksDB encounters these issues. Use the following command to increase the open file limit. Note that this only affects the current shell session, so consider adding it to `~\u002F.zshrc`.\n\n```bash\nulimit -n 10240\n```\n\n#### Log level\n\nThe service relies on the environment variable `RUST_LOG`. For more information, check the [EnvFilter examples](https:\u002F\u002Fdocs.rs\u002Ftracing-subscriber\u002Flatest\u002Ftracing_subscriber\u002Ffilter\u002Fstruct.EnvFilter.html#examples) crate.\n\nHuman logging can be disabled with the environment variable `HUMAN_LOGGING=false`\n\n## Debugging\n\nSee the guide on [debugging](docs\u002Fdevelopers\u002Fdebugging.md) for an overview on running a debug build of a local node.\n\n## Docker & Kubernetes\n\n```sh\n# Create Docker Image\ndocker build -t fuel-core . -f deployment\u002FDockerfile\n\n# Delete Docker Image\ndocker image rm fuel-core\n\n# Create Kubernetes Volume, Deployment & Service\nkubectl create -f deployment\u002Ffuel-core.yml\n\n# Delete Kubernetes Volume, Deployment & Service\nkubectl delete -f deployment\u002Ffuel-core.yml\n```\n\n## GraphQL service\n\nThe client functionality is available through a service endpoint that expect GraphQL queries.\n\n### Transaction executor\n\nThe transaction executor currently performs instant block production. Changes are persisted to RocksDB by default.\n\n-   Service endpoint: `\u002Fv1\u002Fgraphql`\n-   Schema (available after building): `crates\u002Fclient\u002Fassets\u002Fschema.sdl`\n\nThe service expects a mutation defined as `submit` that receives a [Transaction](https:\u002F\u002Fgithub.com\u002FFuelLabs\u002Ffuel-vm\u002Ftree\u002Fmaster\u002Ffuel-tx) in hex encoded binary format, as [specified here](https:\u002F\u002Fgithub.com\u002FFuelLabs\u002Ffuel-specs\u002Fblob\u002Fmaster\u002Fsrc\u002Ftx-format\u002Ftransaction.md).\n","FuelLabs\u002Ffuel-core 是一个用 Rust 语言实现的 Fuel v2 协议全节点客户端。该项目提供了区块链网络中完整节点的功能，支持运行在不同的网络环境（如Ignition主网、测试网和开发网）下，并且通过持续集成确保代码质量和稳定性。它具备高度模块化的设计与良好的性能表现，适合对安全性和效率有较高要求的区块链应用场景，特别是对于想要参与Fuel网络维护或基于该协议进行开发的开发者来说是一个很好的选择。","2026-06-11 02:37:36","top_all"]