Flare Summer Signal

# Introduction

Flare Summer Signal is an open online hackathon for builders creating real products on Flare.

Participants can build from scratch, bring an existing project, or port an existing product to Flare. The program focuses on two areas: interoperable asset products and private applications built with Flare Confidential Compute.

# Timeline

**June 29** Registration + Development opens

**August 14** Final submission deadline

**August 15-21** Judging period

**August 24** Winner announcement ceremony

# Prizes

## **Bounty 1 — Interoperable Asset Products**

**Prize pool:** $6,000

**1st place:** $4,000

**2nd place:** $2,000

## **Bounty 2 — Confidential Compute Apps**

**Prize pool:** $6,000

**1st place:** $4,000

**2nd place:** $2,000

# S**ubmission Requirements**

Each final submission should be clear enough for judges to understand the product, test the demo where possible, and evaluate the quality of the Flare integration.

Submissions should include:

- Project name.

- Selected bounty or bounties.

- Short product description.

- Target user.

- Demo link, video, or working app link.

- GitHub repo or technical materials.

- Explanation of how the project uses Flare.

- Explanation of what was newly built, ported, integrated, or improved during the program.

- Smart contract addresses or relevant deployment details, if applicable.

- Short roadmap or next steps.

Teams are also encouraged to share:

- Whether the project was deployed on Coston2, Songbird, or Flare Mainnet.

- How far they got with user acquisition, distribution, testing, or real user feedback.

- Any early usage, community interest, pilot users, partner conversations, or traction signals.

These are not strict requirements, but they help judges evaluate how seriously the team approached product distribution and whether the project has potential beyond the hackathon.

# Existing Projects

Existing projects are welcome.

Teams bringing an existing product should clearly separate:

- What existed before the hackathon.

- What was newly built during the hackathon.

- What was ported, integrated, or improved on Flare.

- Why the new work is meaningful for users, developers, or the Flare ecosystem.

This allows the hackathon to support more serious product work instead of forcing every team to build from zero.

# Judging Criteria

Eligible submissions will be judged based on:

**Product usefulness** - Does the product solve a real user, developer, ecosystem, or infrastructure problem?

**Flare integration quality** - Is Flare used in a meaningful way, or is the integration superficial?

**Technical execution** - Does the demo work? Is the architecture credible and understandable?

**Evidence of new work** - Did the team clearly show what was newly built, ported, integrated, or improved during the program?

**Clarity and future potential** - Can the team explain the product, user, integration, and next steps clearly? Does the project have a credible path beyond the hackathon?

# Useful Links

Flare Hackathon Telegram Group:[ https://t.me/+5Vn6ZKhr6KI3NjIx](https://t.me/+5Vn6ZKhr6KI3NjIx)

Materials for Developers:[ https://dev.flare.network/](https://dev.flare.network/)

# Contact us

Contact us via Flare Hackathon Telegram Group:[ https://t.me/+5Vn6ZKhr6KI3NjIx](https://t.me/+5Vn6ZKhr6KI3NjIx)

# About us

Flare is an EVM-compatible layer 1 built to unlock DeFi for assets that do not have native smart contracts, starting with XRP through FAssets.

The hackathon is organized by Flare to support builders exploring new product opportunities across interoperability, DeFi, and confidential compute.