Polkadot Builder Party - Hackathon Idea List

1

This thread collects ideas for what to build in the Polkadot Builder Party hackathon.

The motto is “radically open, radically useful”, so our great wish is to have apps built that are useful and practical. To get there, we need to share ideas and wishes of what we want to see…

  • If you are a community member and you always had this one idea you wished someone would build, share it here.
  • If you are a hackathon participant and you have some idea but it still needs brainstorming or refinement or that final kicker, share it here so we can brainstorm together.

The best products are often born out of throwing ideas through the room until something wild comes up. Let’s use this thread to create great ideas!

11 Likes
2

We’re adding support for SDKs (subxt, polkadotjs, and can explore supporting papi) against the following chains/softwares https://ai.tangle.tools, our vibecoding platform on Tangle. Current support is Rust/TS libraries, but would love to know if others are interested for us to add context for other repos/projects. Think of it as a context management pipeline for these projects that auto-classifies prompts to match and guide the agent. It might be a great resource for hackathon participants to get started on any idea.

  • Polkadot
  • Phala
  • Moonbeam
  • Hydration
  • Hyperbridge
  • Parasail
  • Xcm
  • Tangle
3

Cross-chain Liquidity Aggregator – Find the best yields across the Polkadot parachain ecosystem and deposit directly through one unified interface. :eyes:

4 Likes
4

Welcome to all the Builder party hackathon participants! :waving_hand:

Here are a few hackathon project ideas I could think of:

  • Use-cases with multi-chain interactions that just require one call to sign. This will be a massive improvement in multichain UX, and one of the first in blockchain ecosystems in general. Check Empowered XCM Origins

example usecase: Set Identity on People Chain directly through your DOT on Asset Hub. Two different chains. One call to sign!

  • A kick-ass UI for setting Proxies and/or using their functionalities. Polkadot lets you create proxies for various key utilities, but there is no webpage/app where you can create and manage all of them in a single place.

  • Vesting DOT transfer suite - allows for vested DOT transfers with linear or cliff unlocks and unlocking the vested tokens as required.

  • AI AI-powered app that asks some targeted questions, looks at the past on-chain voting history, crunches the referenda metadata/data and picks the best OpenGov delegate aligning with the views and ideology, and creates a seamless delegation/undelegation UI/UX

  • An on-chain voting app for hackathon submissions :slight_smile: Currently, we have 3 submissions that will win a community vote prize on Devpost. But if you submit a fully functional on-chain voting app that pulls in Devpost submissions onto your UI and allows for people to vote on-chain with DOT, that would be awesome!

I will keep adding to this list, but as one of the organizers, these are my top picks for now.

3 Likes
5

Some ideas…

Track 1 (build on top of chains)

  • Private mesaging/chat on Frequency
  • Social app that can switch between “Twitter”, “Instagram”, “Facebook”, and “Forum” mode on Frequency
  • decentralized, curated news aggregation: OriginTrail + nice frontend
  • Order and pay for 3D printing from home via Robonomics or peaq
  • stablecoin app on Hub
  • automatically trigger trades based on signals with Integritee
  • build an AI that controls a robot with Phala and peaq/Robonomics
  • build an evolutionary AI that trades and replicates itself with slight parameter changes to other instances if it is profitable on Phala

Track 2 (build your chain)

  • Data Availability chain

Track 3 (experiments)

  • 2D Network explorer of chains and their XCM connections and activity (like this but more sophisticated)
  • call Polkadot primitives via Ethereum smart contracts: calls on the smart contract trigger XCM messages through Snowbridge v2
  • Polkadot DeFi explorer
  • Uniswap X solver for Polkadot/Hyperbridge/Hydration
  • bring Skybreach to Kusama Hub
  • build a Memechain template to launch memecoins on their own chain
  • build a messaging layer on XCM
5 Likes
6
  • A plugin / library so that every wallet / UI supports fee payment in any asset.
  • Any application that is just “on Polkadot” and does not expose any details of chains to users.
4 Likes
7

Disposable blockchains :face_with_monocle:

2 Likes
8

tell us more :eyes:

9

I cooked up a bunch of ideas a few months ago with the help of @bgodlin and some other ecosystem agents for the Synergy Hackathon at Web3 Summit. There’s too many to paste all in here so I put them in this Notion page together for anyone to check out.

Ideas are categorized under “Social and Governance”, “Payments and Finance” and “Tooling”. Each idea presents the problem space, proposed solution and guidelines for implementing a POC.

Happy hacking!

3 Likes
10

When is the deadline and the registration? Just seen this.

11

I have an idea about enabling energy analytics between People / Food (agriculture) / Energy (infra & tech). I have some idea I can expand more if it gains traction.

I think it would be interesting to track US$/Kwh parity and see if there are any imbalances. Thank you!

1 Like
12

Hackathon idea: Polkadot MCP for AI Agent intelligence and action

–

Hey All, Daniel from OnFinality here!

We’re testing private beta of our AI Assistant aimed at helping with polkadot teams’ and networks’ community management and growth. Simply put, we can answer deep technical community discord questions by combining an LLM assistant with live blockchain data sources.

So far, the most impressive functionality is the ability to autonomously understand and query Polkadot data from SubQuery. Just point it to the SubQuery endpoint and it will magically understand the data structure & fire off its own queries, without manual training or programming, to answer real on-chain questions.

Think:
”Which validators should I delegate to for the most rewards?”
”Which Polkadot token is the most traded on Hydration?”

Hackathon
There is limitless room to extend our platform, and indeed any other AI Agents, with Polkadot specific AI plugins (MCPs) for any use case you can imagine; integrating existing (or brand new!) data sources, oracles, and even performing on-chain actions.

Ideas
Here are a few helpful Polkadot MCPs I’ve come up with in only a few minutes, but it really is limitless - anything a person might want to do on Polkadot could be used by, or performed by, an AI agent

  • Complex cross chain data sources such as Polkadot XCM transfers
  • Oracles for useful off-chain truths
  • Polkadot RPC interactions (reading data or performing on chain activities)
  • Staking - reward and validator

Collaboration
We are happy to provide participants early access and integration into our AI Assistant so that you’ll have a fully functional Polkadot AI Agent to show off at the hackathon.

We can also add you to our MCP marketplace with ongoing revenue share if you fully own the MCP and its data/IP (e.g. not connecting to third party companies APIs)

Of course AI MCPs will be used by everybody - not limited to OnFinality’s platform! We hope that by providing an easy path to market we can generate more interest and get people to act on their creativity :smiley:

Cheers,
Daniel

2 Likes
13

Great list @sacha – thanks!

In Social and Governance, DAO Voting Pools: Collective OpenGov Participation gets my attention, as it’s related to my interest in general-purpose accessible DAO tooling. If there is a need for that on Polkadot (as I hypothesise in DAO tooling for project teams ), then DAO Voting Pools is one use case for it. There is no point in features like:

  • Import active OpenGov proposals for member voting,
  • Auto-execute OpenGov vote using DAO treasury, or
  • Compare DAO decision vs actual OpenGov outcome

until you support the other use cases listed, all of which are needed in any DAO.

Building generic accessible DAO tooling is a lot of effort, if it’s just to support those three uses. OTOH, if we already had such tooling, then building DAO voting pools would be much easier.

I am also curious, if off-chain discussion and voting eg in Discord is the problem, then why not use OpenSquare? It’s offchain, and doesn’t auto-execute but it does (I assume) auto-import proposals, and keep good records.

Also, regarding auto-execute, a key contribution of voting collectives is the rationale. Are we going to AI-generate this?

All that aside, I am interested in use-cases for general purpose DAO tooling. What is the use case hot enough to kick start accessible general purpose DAO tooling (eg building on the the Virto communities pallets on Kreivo)?

Another approach, would be to extend or add to the core OpenGov pallets, to support sub-DAOs for voting collectives. Again, this begs the question: is that the hottest use case for sub-DAOs?

Finally, this links to another idea I am interested in. Rather than sub-DAOs, should we not envisage a network of DAOs, with defined relationships? Sure, one DAO could be subordinate to another, like a Department. Others might simply be members of each other, like an individual (or agent) member. In that case, voting in each other’s referenda would be pretty ordinary. The Technical DAO votes in some Marketing DAO referenda and vice versa.

14

Hi All, this document lists suggested workshops from Unique Network. Since we are aiming for participation from web2 developers we have tailored our workshops around that:

HI @radha and @alice_und_bob pls feel free to leave your comments and suggestions in the doc. Thanks!

1 Like
15

Hey all!

We’re excited to see this hackathon take place! Thanks to the organizers for this set up!

Here’s how the UX Bounty would like to participate:

  1. We like all the ideas listed above, with a special love for @joepetrowski ‘s idea:
    ”A plugin/library so every wallet/UI supports fee payment in any asset”
    =>     This idea could turn into a $30K grant after the hackathon, as part of our goal to improve UX & DevEx.

  2. To all the winners, we will offer them the possibility to get support after the hackathon. This includes:

    1. Mentoring from UX Designers, Product Owners and Developers (up to 1,000$)
    2. UX Audits (up to 2,000$)

  3. Finally, we have launched a platform where you can share a bug, a frustration or a suggestion, and get rewarded for helping improve DevEx and UX in Polkadot.
    => To the builders, take this opportunity to share your feedback and get rewarded!

As always, we are available if anyone has questions :slight_smile:

Happy building to everyone!

UX Bounty team

4 Likes
16

I’ve spent a fair bit of time exploring how to make this real. Short version: the ideal place for this logic is inside wallets/extensions (and, for offline flows, in the tools that talk to them). Today, though, native wallet support isn’t feasible because of how dApps communicate with wallets. Solving it “from the outside” is technically possible, but only in a library-specific way and with a rather suboptimal UX.

If someone wants to pursue a library-specific path right now, it’s absolutely doable with PAPI by writing a PolkadotSigner enhancer/middleware, similar to the one we used for remote proxies. You can even enhance the whole client so the middleware is always applied whenever a transaction is created.

The more durable route is to standardize the interface for creating transactions. With an interoperable transaction interface (see: createTransaction), this becomes solvable in a generic, library-agnostic way. Also, wallets could then integrate this functionality natively. That’s not possible with the current signPayload pattern that dApps use to talk to wallets.

One scope note: to my knowledge, paying fees via the ChargeAssetTxPayment extension is supported on AssetHub today. It may be prudent to limit the scope to transactions created for chains that have the ChargeAssetTxPayment extension available.

As I’ve told you in the past: throwing money at patches can unintentionally cement the underlying architectural issues that are the root-cause of many of our UX challenges.
It would be wiser to invest these resources into standardizing the infrastructure and interfaces that the ecosystem needs to unlock truly seamless UX and DevEx, rather than funding stopgap solutions that might ossify today’s limitations.

5 Likes
17

7 ideas to build on Polkadot.

  1. A Perp Dex for Polkadot based on Aster Dex success.

  2. A Money Market/ Lending platform that includes crypto, stocks and RWA.

  3. AI builder dapp( An artificial intelligence developer that builds what the user ask to build) example: I ask for create a memecoin and the ai dev dapp build all the code and everything necessary or I ask for a fork of compound and the AI DEV develop it for me on Polkadot).

  4. A prediction market.

  5. A Casino :slot_machine: Polkadot native dapp.

  6. A Global University free open source dapp that teach students all materias.

  7. A Final Fantasy saga game new edition that use Polkadot tech and rewards gamers with real money for playing. Play to enjoy and earn.

18

Hello everyone,
Apostol, one of the BD leads from Acurast! We had two main ideas that I believe would be interesting use-cases as they are also Web2 Native but use the underlying blockchain technology.

1.Distributed Scrapers
The first practical use case we expect is using Acurast as a decentralized scraping resource. What makes Acurast valuable here is that a single smartphone can provide both the scraping compute and the network egress (the device’s mobile IP), removing the separate cloud-compute combined with external-proxy rotations used by many scrapers. That can simplify architecture and remove one source of latency and proxy cost.

You can look through the puppeteer example that leverages the mobile WebView here:

https://github.com/Acurast/acurast-example-apps/tree/main/apps/app-puppeteer

You will need a “collection endpoint” that you host to simplify the actual collection of the data your scraper collected.

2.Confidential Agents
As a computing service, Acurast is able to run inference for models up to 13B in parameters. Additionally, all the smartphones that are onboarded onto the network have a TEE, allowing for all compute that goes through the network to stay confidential and not be tempered with. This makes it ideal for developers who want to run cheaper and confidential smaller LMs. One use-case we have been thinking of is how this can be used for reinforcement learning inference. We are in the exploratory stages of doing this with Fortytwo.

You can look through our documentation herewith which explains how to specifically run an LLM using Acurast:

https://docs.acurast.com/developers/llm-on-acurast/

1 Like