Hackathon Overview

Sui Overflow is set to be a game-changer with over $1 million USD in prizes up for grabs. With seven diverse tracks, this hackathon provides an exciting opportunity for everyone, whether you're into DeFi, gaming, consumer apps, infrastructure, tooling, or the unique features of Sui’s Move programming language.

Key Tracks:

1. DeFi: Revolutionize decentralized finance with Sui’s architecture and programmable transaction blocks.

2. Gaming: Create immersive Web3 gaming experiences using dynamic NFTs and zkLogin integration.

3. Consumer and Mobile: Simplify blockchain for consumer apps, leveraging Sui’s features for enhanced user experiences.

4. Infra and Tooling: Build tools and infrastructure to support and enhance the Sui ecosystem.

5. Move: Develop applications and tools utilizing Move’s powerful features.

6. Randomness: Add innovative randomness features for security and engagement in various applications.

7. zkLogin: Create seamless user experiences using zkLogin for interoperability and enhanced security.

Ecosystem Bounties

In addition to the main tracks, Sui Overflow will feature ecosystem bounties sponsored by existing Sui projects. This means you can potentially qualify for both track prizes and bounties, maximizing your chances of winning.

Road to Sui Overflow

To prepare for the hackathon, Sui is offering workshops and in-person events hosted by expert engineers. These sessions will provide valuable insights into Sui technology, helping you sharpen your skills and deepen your understanding.

Basecamp Pitch and Polish

Get ready to refine your project at the Basecamp Pitch and Polish session. This is your chance to perfect your ideas and get valuable feedback in a supportive environment.

Start Building Now!

While the official registration opens on April 21st, you can start building your project today. Work done within 60 days prior to registration is eligible, so if you’ve started building something after February 20, 2024, you’re good to go.

Join the Community

Stay connected by joining the dedicated Sui Overflow Discord server and pre-registering for updates on the Sui Overflow website. Here, you can connect with potential teammates, brainstorm ideas, and get tips on how to win.

Organization of 0G DA

The 0G DA system is a well-oiled machine consisting of several key modules: DA Contracts, DA Nodes, and the DA Client. Let's break down each component and see how they work together seamlessly.

DA Contracts

These are the backbone of the 0G DA, managing the upload and verification status of DA data on-chain through smart contracts. They also handle information about DA signers and orchestrate signer elections using on-chain Verifiable Random Functions (VRF). Think of DA Contracts as the central hub, ensuring everything runs smoothly and securely.

DA Nodes

Operated by DA Signers, these nodes are the workhorses of the system. They take care of encoding verification, sign DA data, and earn rewards through storage mining. DA Nodes are crucial for maintaining the integrity and reliability of the data stored in the 0G DA.

DA Client

The DA Client is the gateway for users to access DA services. It’s further divided into three sub-components: Client, Encoder, and Retriever. Here’s how they function:

• Client: Acts as the interface for users to interact with the DA system.

• Encoder: Handles the erasure coding of data uploaded by users.

• Retriever: Fetches data from DA Nodes when users request to retrieve it.

Workflow of 0G DA

Now, let's dive into the workflow of how data is uploaded and downloaded in the 0G DA system.

Uploading Data

1. User Upload: Users upload their data to the Disperser module of the DA Client.

2. Encoding: The DA Client sends this data to the Encoder, which processes it through erasure coding, producing encoded data and an encoding proof.

3. Merkle Root Submission: The DA Client uploads the Merkle root of the encoded data to the DA Entrance contract, which then assigns a quorum to sign the uploaded data.

4. Signature Collection: The DA Client sends the encoded data to the DA Nodes in the assigned quorum to obtain their signatures. Once enough signatures are aggregated, the process moves forward.

5. On-Chain Confirmation: The aggregated signature is uploaded to the DA Entrance contract. The contract verifies the signature and stores the verified data commitment root.

Downloading Data

1. Data Request: Users request the DA Client to retrieve previously uploaded and verified DA data.

2. Forwarding Request: The DA Client forwards this request to the Retriever.

3. Quorum Identification: The Retriever checks the on-chain state stored in the DA Entrance contract to find the assigned quorum for the data.

4. Data Recovery: The Retriever requests the encoded rows from the DA Nodes in the assigned quorum and recovers the original data from these encoded rows.

Terminology: Blobs

In the 0G DA universe, blobs are the fundamental units of data posted by users. Each blob undergoes the rigorous process of encoding, verification, and storage to ensure data availability and integrity.

Architecture Overview