sunriselayer / sunrise-da

Sunrise Data Availability Nodes

Sunrise DA

Golang implementation of Sunrise's data availability node types (light | full | bridge).

The sunrise-da types described above comprise the sunrise data availability (DA) network.

The DA network wraps the sunrise-core consensus network by listening for blocks from the consensus network and making them digestible for data availability sampling (DAS).

Continue reading here if you want to learn more about DAS and how it enables secure and scalable access to Sunrise chain data.

Table of Contents

• Sunrise DA
  • Table of Contents
  • Minimum requirements
  • System Requirements
  • Installation
  • API docs
  • Node types
  • Run a node
  • Network
  • Environment variables
  • Package-specific documentation

Minimum requirements

Requirement	Notes
Go version	1.22 or higher

System Requirements

See the official docs page for system requirements per node type:

• Bridge
• Light
• Full

Installation

git clone https://github.com/sunriselayer/sunrise-da.git
cd sunrise-da
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 sunrise-da public API is documented here.

Node types

• Bridge nodes - relay blocks from the sunrise consensus network to the sunrise 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.

Run a node

<node_type> can be: bridge, full or light.

sunrise-da <node_type> init

sunrise-da <node_type> start

Network

• Mainnet - the main network of Sunrise. Use tokens with real value
• Testnet - This network is used to test operations on the mainnet. Normally, the same environment as the mainnet is provided, but tokens have no value
• Private - a network for testing new features. It may contain critical bugs. Do NOT normally use

Run a bridge node

Bridge nodes connect the data availability layer and the consensus layer.

sunrise-da bridge init --core.ip <URI> --p2p.network <NETWORK>

The --core.ip gRPC port defaults to 9090. Normally, set up a RPC node running sunrise-app.

sunrise-da bridge start --core.ip <URI> --p2p.network <NETWORK>

Run a full node

Full storage nodes are Sunrise nodes that store all the data. Full storage nodes send block shares, headers, and fraud proofs to light nodes.

sunrise-da full init --p2p.network <NETWORK>
sunrise-da full start --core.ip <URI> --p2p.network <NETWORK>

Start a full node using RPC. The bridge and full nodes refer to bootstrap.go.

Run a light node

Light nodes ensure data availability. This is the most common way to interact with Sunrise networks. It does NOT require large storage or high-speed connections.

sunrise-da light init --p2p.network <NAME>
sunrise-da light start --core.ip <URI> --p2p.network <NAME>

Environment variables

Variable	Explanation	Default value	Required
SUNRISE_BOOTSTRAPPER	Start the node in bootstrapper mode	false	Optional

Package-specific documentation

• Header
• Share
• DAS

sunrise-da's Issues

Fix Integration Test

Implementation ideas

Other CI/CDs have been resolved. #6 Integration tests need to be fixed.

eh.Commit has previos block info

Implementation ideas

code

	// Make sure the header is consistent with the commit.
	if eh.Commit.Height != eh.RawHeader.Height {
		return fmt.Errorf("header and commit height mismatch: %d vs %d", eh.RawHeader.Height, eh.Commit.Height)
	}

error

2024-04-16T18:53:24.668+0900    ERROR   header/p2p      p2p/subscriber.go:114   invalid header  {"from": "<peer.ID 12*sHJ3v8>", "err": "header and commit height mismatch: 14 vs 13"}
2024-04-16T18:53:24.668+0900    ERROR   core    core/listener.go:252    listener: broadcasting next header      {"height": 14, "err": "validation failed"}
2024-04-16T18:53:29.669+0900    ERROR   header/p2p      p2p/subscriber.go:114   invalid header  {"from": "<peer.ID 12*sHJ3v8>", "err": "header and commit height mismatch: 15 vs 14"}
2024-04-16T18:53:29.669+0900    ERROR   core    core/listener.go:252    listener: broadcasting next header      {"height": 15, "err": "validation failed"}

If make this validation pass, nex validaton fail

	if hhash, chash := eh.RawHeader.Hash(), eh.Commit.BlockID.Hash; !bytes.Equal(hhash, chash) {
		return fmt.Errorf("commit signs block %X, header is block %X", chash, hhash)
	}

error

2024-04-16T20:19:00.897+0900    ERROR   core    core/listener.go:252    listener: broadcasting next header      {"height": 1040, "err": "validation failed"}
2024-04-16T20:19:05.903+0900    ERROR   header/p2p      p2p/subscriber.go:114   invalid header  {"from": "<peer.ID 12*sHJ3v8>", "err": "commit signs block 17A25A7514152847E7FFDE587BFDAF2D696FAB01A9ED0A30BCA2EBA096C1BAE1, header is block 48F4B3DBDFA1B60363C15AFD0B455642B67269910CEE64BA802D6C48B8AF2853"}
2024-04-16T20:19:05.903+0900    ERROR   core    core/listener.go:252    listener: broadcasting next header      {"height": 1041, "err": "validation failed"}
2024-04-16T20:19:08.979+0900    INFO    basichost       basic/natmgr.go:112     DiscoverNAT error:no NAT found
2024-04-16T20:19:10.909+0900    ERROR   header/p2p      p2p/subscriber.go:114   invalid header  {"from": "<peer.ID 12*sHJ3v8>", "err": "commit signs block 48F4B3DBDFA1B60363C15AFD0B455642B67269910CEE64BA802D6C48B8AF2853, header is block B8610D24F9139B784C121DE52365D13D453F2DAE58B179C70C34092909EAA48E"}
2024-04-16T20:19:10.909+0900    ERROR   core    core/listener.go:252    listener: broadcasting next header      {"height": 1042, "err": "validation failed"}

The previous and next hashes are matched.
The problem is that they are offset by one.

App Verison Problem

Bug

Run

make build
sudo make install
sunrise bridge init --core.ip sunrise-private-1.cauchye.net 
sunrise bridge start --core.ip sunrise-private-1.cauchye.net --p2p.network private

node starts up and begins communicating with the app

got error

2024-04-16T00:53:00.490+0900    ERROR   header/p2p      p2p/subscriber.go:114   invalid header  {"from": "<peer.ID 12*sHJ3v8>", "err": "app version mismatch, expected: 2, got 0"}
2024-04-16T00:53:00.490+0900    ERROR   core    core/listener.go:252    listener: broadcasting next header      {"height": 543, "err": "validation failed"}