Key Components of Dill

1. Consensus Layer:

• The consensus layer in Dill is maintained by a network of Dill Nodes. These nodes are responsible for ordering transactions and blob data, which are then organized into blocks. Using advanced techniques like 2D Erasure Coding (EC) and KZG commitments, the blocks are sharded and propagated across various column subnets. This ensures that the data is efficiently distributed and remains available throughout the network.

2. Data Availability Sampling (DAS):

• Data availability is a critical function in modular blockchains. Dill employs a sampling method to verify the integrity and availability of blocks. Validator nodes sample one or more columns from the block, and based on these samples, they cast votes to either validate or reject the block. Light clients, which operate with limited resources, rely on these samples to make informed decisions on block acceptance.

3. Blobstream:

• Blobstream is a mechanism that ensures the correct storage of blob data by the Dill network. After a block containing blob data is generated, an attestation is created and sent to the Attestation Bridge. The bridge then generates a proof and uploads it to a Blobstream Contract within an Ethereum Virtual Machine (EVM) environment. This process allows Rollups to verify that their blob data has been correctly stored.

Subnet & Sharding

Dill mitigates network congestion during block propagation through a sharding mechanism. The blob data within a block is divided into multiple shards, each forming a column. These columns are then propagated across different sampling subnets. This sharding approach reduces the amount of data that each validator node needs to handle, enhancing the network’s throughput.

2D Erasure Coding (EC)

To further enhance data availability, Dill implements 2D Erasure Coding (EC). This method involves expanding data across two dimensions, making it more challenging for an attacker to hide data unavailability. Compared to 1D EC, 2D EC requires less data extraction to detect unavailability, making it a more efficient and secure solution for data redundancy.

KZG Commitments

Dill utilizes KZG (Kate-Zaverucha-Goldberg) commitments for verifying blob data. This polynomial commitment scheme offers several advantages over traditional methods like Merkle proofs. Notably, KZG commitments remain constant in size regardless of the data’s scale, and they can be used to commit to and verify EC-extended data, reducing the need for fraud proofs.

Data Availability Sampling (DAS)

In the Dill system, there are two primary data sampling methods:

• Full Nodes: These nodes participate in P2P subnets to propagate and sample entire columns of data.
• Light Nodes: These nodes perform targeted sampling of individual cells (the intersection of a row and a column in the 2D EC scheme) to verify block data.

These methods ensure that both full and light nodes can effectively contribute to and verify the network’s data availability.

Versatility in Blockchain Development

Airchains Framework supports multiple virtual machines, offering unparalleled flexibility for diverse blockchain projects:

Ethereum Virtual Machine (EVM) Support: Seamlessly integrate with Ethereum’s ecosystem, leveraging familiar technology to accelerate your development process.

Solana Virtual Machine (SVM) Integration: Harness the speed and efficiency of Solana’s blockchain system with smooth integration and optimal performance.

CosmWasm Compatibility: Interconnect different blockchain networks with CosmWasm, enabling the creation of sophisticated applications spanning across diverse ecosystems.

Flexible Data Storage Options

Choose how you store your blockchain data with leading layers such as Celestia and Avail, tailoring data storage solutions to suit the specific requirements of your project.

Advanced Security Features

Security is paramount in the blockchain landscape. Airchains Framework implements zero-knowledge proofs to enhance the security and efficiency of your blockchain projects, ensuring the integrity and confidentiality of your data.

Seamless Integration with Airchains Main Chain

Experience seamless integration as your blockchain solutions settle effortlessly on Airchains’ settlement chain. This integration ensures reliability, scalability, and consistency across your projects.

Airchains Framework is more than just a development toolkit — it’s a gateway to innovation, enabling developers to create, innovate, and scale their blockchain solutions with confidence. Join us in simplifying blockchain development and discover the limitless possibilities with Airchains Framework.

Unleash your creativity. Build with Airchains Framework today.

ZeroGravity 数据可用性（0G DA）系统是一个可扩展的数据可用性服务层，直接构建在去中心化存储系统之上，通过最小化广播所需的数据传输量来解决可扩展性问题。其通用的去中心化存储设计进一步使其能够支持各种来自不同场景的可用性数据类型，不仅限于 Layer 2 网络，还包括分布式 AI 基础设施。

在非正式术语中，数据可用性是指确保任何希望检索数据的人都可以获取到该数据的保证。0G DA 专注于提供具有高安全性和吞吐量的数据可用性。

从高层次上看，数据可用性系统接受通过某些接口的数据块，然后通过另一个接口使其可供检索者使用。

0G 的存储层包括与独立共识网络连接的存储网络。每个存储节点通过向部署在共识网络上的智能合约提交特定数据的可访问性证明来积极参与挖矿过程。一旦智能合约验证了证明，存储节点将获得相应的奖励。通过奖励更多地存储属于同一分区的数据，可以实现分区，这种基于激励的机制奖励节点的贡献，而不是惩罚节点的不当行为，因此可以更好地鼓励节点参与网络的维护，从而促进网络在实践中实现更好的可扩展性。0G 存储还设计为具有多个抽象和结构层的通用存储系统，包括用于存档非结构化数据的追加日志层，以及用于管理可变和结构化数据的键值层。这使得 0G 能够支持可靠的数据索引和来自 Layer 2 和 AI 场景的更多种类的可用性数据类型。

技术整合与模块化架构

Initia 的核心特点之一是技术整合与模块化架构。它采用了 Cosmos SDK，这是一种高效和模块化的区块链应用开发框架。通过整合 Cosmos 生态系统的丰富资源和互操作性原则，Initia 实现了与 Cosmos 生态内其他区块链的无缝互操作，进一步推动了区块链生态的发展。

Layer 2 应用链（Minitias）集成

Initia 通过 Initia Rollup 框架将底层 Layer 1 与 Layer 2 应用链集成，这些应用链被官方称为「Minitias」。这种集成使得开发者能够轻松启动 Layer 2，并即时支持各种以太坊和 Cosmos 网络，从而提供更强大的开发者体验和更丰富的应用功能。

激励计划和开发者友好性

Initia 通过激励计划和开发者友好的生态系统，吸引了开发者和项目加入。持有 Initia 的治理代币 INIT 的人可以参与对 Initia 的 Layer 2 进行投票，讨论代币激励的分配，并设定关键绩效指标（KPI）。这种激励机制鼓励开发者在 Layer 2 上建设活跃的生态，并为其提供额外的营销激励措施，以吸引更多用户和项目。

跨链互操作性和生态整合

Initia 的架构设计着重于跨链互操作性和生态整合。它利用 Cosmos 的 IBC 协议实现与 Cosmos 生态系统内其他区块链的通信，从而促进不同区块链之间的资产流动和互操作。这种深度整合使得 Initia 公链成为区块链生态系统中的重要组成部分，为开发者和用户提供了全面且强大的区块链生态体验。

生态成员和发展规划

Initia 的开发团队具有丰富的区块链开发和生态建设经验，其中核心开发人员曾在 Terraform Labs 工作。除了技术实力之外，Initia 还吸引了多个投资机构和天使投资者的支持，为其发展提供了强大的资金和资源支持。

未来，Initia 将继续推进其发展计划，预计在第二季度正式启动主网。其激励测试网的启动将进一步推动生态系统的建设和发展，为开发者和用户提供更丰富、更创新的区块链应用和服务。

结语

总体而言，Initia 公链以其创新的技术整合、开发者友好的生态系统和跨链互操作性，展示了成为区块链行业领先项目的潜力和决心。作为 Cosmos 生态系统中的重要组成部分，Initia 将继续推动区块链生态系统的整合和发展，为开发者和用户带来更多创新和便利。随着主网的启动和生态建设的深入推进，我们期待看到 Initia 在区块链领域的持续创新和发展。

ATTENTIONS:

if Your server OS is debian 11/12, ubuntu 2204/2304, fedora 37/38, you can use pre-compiled binaries to run the avail node. This is the easiest way.

if Your can not use pre-compiled binaries to run the avail node. I advise you to use docker way.

1. hardware requirements

This is the hardware configuration required to set up an Avail node:

Component Minimum Recommended

RAM: 4GB 8GB

CPU (amd64/x86 architecture): 2core 4core

Storage (SSD): 20–40GB 200–300GB

This guild uses ubuntu 2204 to deploy the avail full node from compiling the source code.

ssh to your node server and follow me.

Install dependencies

sudo apt update -y

sudo apt install build-essential git curl clang libclang-dev make libssl-dev protobuf-compiler -y

Install Rust

curl --proto ‘=https’ — tlsv1.2 -sSf https://sh.rustup.rs | sh

source ~/.cargo/env

Create a work directory and dowload avail source code

mkdir avail_node

cd avail_node

git clone https://github.com/availproject/avail.git

Compile source

cd avail

git checkout v1.8.0.0

cargo build --release -p data-avail

A cup of coffee and waiting for compiling finish, you will find log

Finished release [optimized] target(s) in 52m 58s

Now we can try to run node

cp target/release/data-avail ..

cd ..

mkdir data

./data-avail --base-path $(pwd)/data --chain goldberg --name YOUR_NODE_NAME_HERE

If you find log bellow in your terminal, node run successfully, now press CTRL-C to terminate node running, then run node using screen or systemd:

Syncing, target=#621376 (8 peers), best: #797 (0xf462…59a4), finalized #512 (0xea92…03c9), ⬇ 273.0kiB/s ⬆ 16.2kiB/s

run node with screen

screen -mS avail

./data-avail --base-path $(pwd)/data --chain goldberg --name YOUR_NODE_NAME_HERE

Now your node is running, pls check it in https://telemetry.avail.tools/. You can click ctrl-a d to detached from screen, or run “screen -x avail” to attach into screen again.

If you don’t want to use screen, you can use systemd to run the avail node.

create avail.service file, change YOUR_NODE_NAME_HERE to your actual node name and paste bellow totally to your terminal.

cat > avail.service <<EOF
[Unit]
Description=Avail
After=network.target network-online.target
Requires=network-online.target

[Service]
Type=simple
ExecStart=$(pwd)/data-avail --base-path $(pwd)/data --chain goldberg --name YOUR_NODE_NAME_HERE
Restart=always
RestartSec=120

[Install]
WantedBy=multi-user.target
EOF

move avail.service to system /lib/systemd/system and run it.

sudo mv avail.service /lib/systemd/system/

sudo systemctl daemon-reload

sudo systemctl enable avail

sudo systemctl start avail

now your node is running, you can check the node status, and find the log bellow.

Syncing, target=#621376 (8 peers), best: #797 (0xf462…59a4), finalized #512 (0xea92…03c9), ⬇ 273.0kiB/s ⬆ 16.2kiB/s

sudo systemctl status avail

sudo journalctl -f -u avail

We recommend downloading the pre-compiled binary for speed and convenience.

ATTENTIONS: if Your server OS is not debian 11/12, ubuntu 2204/2304, fedora 37/38, pls use docker to run the avail node.

1. hardware requirements

This is the hardware configuration required to set up an Avail node:

Component Minimum Recommended

RAM: 4GB 8GB

CPU (amd64/x86 architecture): 2core 4core

Storage (SSD): 20–40GB 200–300GB

2. OS requirements

stable Linux server distributions, recommended ubuntu 2204/2304; debian 11/12; fedora 37/38

This guild uses ubuntu 2204 to deploy the avail full node.

ssh to your node server and create a directory avail

mkdir avail

cd avail

Download the latest pre-compiled binaries(version 1.8.0.0) for ubuntu 2204 from github.com, uncompress it and change name to data-avail

wget https://github.com/availproject/avail/releases/download/v1.8.0.0/amd64-ubuntu-2204-data-avail.tar.gz

tar xf amd64-ubuntu-2204-data-avail.tar.gz

mv amd64-ubuntu-2204-data-avail data-avail

Try to run node

./data-avail --base-path $(pwd)/data --chain goldberg --name YOUR_NODE_NAME_HERE

If you find log bellow in your terminal, node run successfully, now click CTRL-C to terminate node running, then run node using screen or systemd:

Syncing, target=#621376 (8 peers), best: #797 (0xf462…59a4), finalized #512 (0xea92…03c9), ⬇ 273.0kiB/s ⬆ 16.2kiB/s

run node with screen

screen -mS avail

./data-avail --base-path $(pwd)/data --chain goldberg --name YOUR_NODE_NAME_HERE

Now your node is running, pls check it in https://telemetry.avail.tools/. You can click ctrl-a d to detached from screen, or run “screen -x avail” to attach into screen again.

If you don’t want to use screen, you can use systemd to run the avail node.

create avail.service file, change YOUR_NODE_NAME_HERE to your actual node name and paste bellow totally to your terminal.

cat > avail.service <<EOF
[Unit]
Description=Avail
After=network.target network-online.target
Requires=network-online.target

[Service]
Type=simple
ExecStart=$(pwd)/data-avail --base-path $(pwd)/data --chain goldberg --name YOUR_NODE_NAME_HERE
Restart=always
RestartSec=120

[Install]
WantedBy=multi-user.target
EOF

move avail.service to system /lib/systemd/system and run it.

sudo mv avail.service /lib/systemd/system/

sudo systemctl daemon-reload

sudo systemctl enable avail

sudo systemctl start avail

now your node is running, you can check the node status, and find the log bellow.

Syncing, target=#621376 (8 peers), best: #797 (0xf462…59a4), finalized #512 (0xea92…03c9), ⬇ 273.0kiB/s ⬆ 16.2kiB/s

sudo systemctl status avail

sudo journalctl -f -u avail

If your node can not run successfully, you can try other methods such as docker or compile node from source.

ATTENTIONS: if Your server OS is debian 11/12, ubuntu 2204/2304, fedora 37/38, you can use pre-compiled binaries to run the avail node.

1. hardware requirements

This is the hardware configuration required to set up an Avail node:

Component Minimum Recommended

RAM: 4GB 8GB

CPU (amd64/x86 architecture): 2core 4core

Storage (SSD): 20–40GB 200–300GB

This guild uses ubuntu 2004 to deploy the avail full node.

ssh to your node server and install docker daemon. if your server os is not ubuntu, pls refer to https://docs.docker.com/engine/install/ubuntu/

for pkg in docker.io docker-doc docker-compose docker-compose-v2 podman-docker containerd runc; do sudo apt-get remove $pkg; done

sudo apt-get update
sudo apt-get install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg

echo \
“deb [arch=”$(dpkg --print-architecture)” signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
“$(. /etc/os-release && echo “$VERSION_CODENAME”)” stable” | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

run your avail node, change YOUR_NODE_NAME_HERE to your actual node name

mkdir avail

cd avail

sudo docker run -v $(pwd)/state:/da/state:rw -v $(pwd)/keystore:/da/keystore:rw -e DA_CHAIN=goldberg -e DA_NAME=YOUR_NODE_NAME_HERE -p 30333:30333 -p 9615:9615 -p 9944:9944 -d --name=avail --restart unless-stopped availj/avail:v1.8.0.0 --rpc-cors=all --rpc-external --rpc-methods=unsafe --rpc-port 9944

now your node is running, you can check the node status, and find the log bellow.

Syncing, target=#621376 (8 peers), best: #797 (0xf462…59a4), finalized #512 (0xea92…03c9), ⬇ 273.0kiB/s ⬆ 16.2kiB/s

sudo docker ps -a

sudo docker logs -f avail

If your node can not run successfully, you can try other methods such as compile node from source.