base on Celestia Data Availability Nodes # Celestia Node [](https://pkg.go.dev/github.com/celestiaorg/celestia-node) [](https://github.com/celestiaorg/celestia-node/releases/latest) [](https://github.com/celestiaorg/celestia-node/actions/workflows/go-ci.yml) [](https://goreportcard.com/report/github.com/celestiaorg/celestia-node) [](https://codecov.io/gh/celestiaorg/celestia-node) [](https://deepwiki.com/celestiaorg/celestia-node) Golang implementation of Celestia's data availability node types (`light` | `full` | `bridge`). The celestia-node types described above comprise the celestia data availability (DA) network. The DA network wraps the celestia-core consensus network by listening for blocks from the consensus network and making them digestible for data availability sampling (DAS). Continue reading [here](https://blog.celestia.org/celestia-mvp-release-data-availability-sampling-light-clients) if you want to learn more about DAS and how it enables secure and scalable access to Celestia chain data. ## Table of Contents - [Celestia Node](#celestia-node) - [Table of Contents](#table-of-contents) - [Minimum requirements](#minimum-requirements) - [System requirements](#system-requirements) - [Supported architectures](#supported-architectures) - [Installation](#installation) - [API docs](#api-docs) - [Node types](#node-types) - [Run a node](#run-a-node) - [Quick Start with Light Node on arabica](#quick-start-with-light-node-on-arabica) - [Environment variables](#environment-variables) - [Package-specific documentation](#package-specific-documentation) - [Code of Conduct](#code-of-conduct) ## Minimum requirements | Requirement | Notes | | ----------- |----------------| | Go version | 1.25 or higher | ## System requirements See the [official docs page](https://docs.celestia.org/how-to-guides/nodes-overview#data-availability-nodes) for system requirements for each node type. ## Supported architectures Celestia-app officially supports the following architectures: - `linux/amd64` - `linux/arm64` - `darwin/amd64` (macOS Intel) - `darwin/arm64` (macOS Apple Silicon) Only these four architectures are officially tested and supported. ## Installation ```sh git clone https://github.com/celestiaorg/celestia-node.git cd celestia-node make build sudo make install ``` For more information on setting up a node and the hardware requirements needed, go visit our docs at <https://docs.celestia.org>. ## API docs The celestia-node public API is documented [here](https://node-rpc-docs.celestia.org/). ## Node types - **Bridge** nodes - relay blocks from the celestia consensus network to the celestia data availability (DA) network - **Full** nodes - fully reconstruct and store blocks by sampling the DA network for shares - **Light** nodes - verify the availability of block data by sampling the DA network for shares More information can be found [here](https://github.com/celestiaorg/celestia-node/blob/main/docs/adr/adr-003-march2022-testnet.md#legend). ## Run a node `<node_type>` can be: `bridge`, `full` or `light`. ```sh celestia <node_type> init ``` ```sh celestia <node_type> start ``` Please refer to [this guide](https://docs.celestia.org/how-to-guides/celestia-node/) for more information on running a node. ### Quick Start with Light Node on arabica View available commands and their usage: ```sh make node-help ``` Install celestia node and cel-key binaries: ```sh make node-install ``` Start a light node with automated setup: ```sh make light-arabica-up ``` This command: - Automatically checks wallet balance - Requests funds from faucet if needed - Sets node height to latest-1 for quick startup - Initializes the node if running for the first time Options: ```sh make light-arabica-up COMMAND=again # Reset node state to latest height make light-arabica-up CORE_IP=<ip> # Use custom core IP ``` ## Environment variables | Variable | Explanation | Default value | Required | | ----------------------- | ----------------------------------- | ------------- | -------- | | `CELESTIA_BOOTSTRAPPER` | Start the node in bootstrapper mode | `false` | Optional | ## Package-specific documentation - [Header](./header/doc.go) - [Share](./share/doc.go) - [DAS](./das/doc.go) ## Code of Conduct See our Code of Conduct [here](https://docs.celestia.org/community/coc). ", Assign "at most 3 tags" to the expected json: {"id":"4367","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"