Open
Build bounty
14 days 20h left
Create an AI support assistant — demo 8
The problem
A clearly scoped demonstration brief for testing the LucidPing bounty board, founder workflow and contributor discovery.
Done means all of this
The founder wrote this list before anyone claimed the bounty, and it's what gets checked at delivery. Nobody holds the money here, so this list — agreed up front, in public — is what stands in for a contract. If something you consider essential isn't on it, settle that in writing before you start.
No acceptance criteria were listed. That makes "done" a matter of opinion, and there's no escrow here to arbitrate it — get the definition in writing from Freya before you commit any time.
Stack
Python, automation
Posted
2 days ago
Claim window
until 17 Nov 2026
Claims so far
0
How this bounty ends
1
You claim it
One person holds a bounty at a time, so nobody duplicates the work. Claiming takes it off the board immediately — get access and agree the details with Freya straight away.
2
You ship it and mark it delivered
Deliver against the criteria above — that list, not a conversation afterwards, is what "done" means here. Add a link if there is one.
3
They confirm and pay you directly
$400 goes from Freya to you — LucidPing never touches it. Confirming payment here is what updates the public record in the sidebar, which is why founders who want to keep posting do it.
If the deadline passes while a claim is still open and undelivered, the claim lapses automatically and the bounty goes back on the board — so a claim you can't start on is better handed back than held.