bitcoin-only-dev-bounties-spec

Live prototype: https://bitcoin-bounties.lightning-answers.com/

WIP Implementation: https://github.com/ko-redtruck/bitcoin-only-open-source-bounties-express

The site should give visitors an overview over all available Bitcoin bounties and let users filter by programming language, projects and type of work (frontend, backend,...) . We do not expect all bounty issuers to post their bounties themselves, so users can publish bounties linked to posts from Twitter or GitHub. If someone anonymous (Login with LNURL-Auth) wants to start a bounty the person should send the funds to OpenSats to ensure the payment is made if the task has been fulfilled. In cases of dispute separate moderators or OpenSats board decides if the bounty is paid out.

Normal users also have the option to give OpenSats control over the funds to get higher trust. Users can also pledge a bounty to an already existing task/issue. They can add/clarify their own conditions which should not differ much from the existing conditions.

Furthermore users can post an issue/task they see the need for without adding a bounty. These act as a sort of fundraisers, where users who also think this issue is important can pledge funds. As soon as someone adds a bounty to an unfunded issue it is marked as a bounty and displayed more prominently.

Lightning Integration

• "Add instant bounty"/"Pay bounty" --> let anon or logged in users instantly add funded bounties
• funds paid when pull request merged or when specified like in the payout conditions
• upvote/like option for logged in users: to upvote you have to pay a bounty (amount free to choose)
• upvote option should hopefully incentize more users to pay bounties

MVP:

• Login with Twitter (:x:), GitHub (:heavy_check_mark:)
• create new bounty (:heavy_check_mark:)
• add bounty (1. from yourself, 2. from yourself + web announcement link, 3. from someone else + web announcement link (reference) ) (:heavy_check_mark:)
• main page (bounties): sort by total bounty amount (:heavy_check_mark:), date (:x:)
• an email address for disputes (:x:)

Additional Features (most important to less important):

• moderator functionality in UI (:x:)
• filter by repo/project, programming language, work type (frontend/ui vs wallet backend vs webserver vs ...) (:x:)
• upvotes (You can only upvote comments, if you want to "upvote" an issue/bounty add your own bounty to signal support) (:x:)
• comments (:x:)
• lnurl-auth login (:x:)

• give control over funds to OpenSats (payment functionality) → marked as “funding secured” (:x:)
• add dispute/claim (:x:)

Rough/incomplete enitity relationship diagram:

SQL TABLE DESIGN

await client.query(` CREATE TABLE IF NOT EXISTS Identities(
      id SERIAL PRIMARY KEY,
      url VARCHAR(128) UNIQUE,
      name VARCHAR(64) UNIQUE
  )`)

  await client.query(` CREATE TABLE IF NOT EXISTS Users(
    id SERIAL PRIMARY KEY,
    provider_id VARCHAR(128),
    provider_name VARCHAR(32),
    created_on TIMESTAMP NOT NULL,
    identity_id INTEGER REFERENCES Identities(id),
    privilege_level INT DEFAULT 0,
    UNIQUE(provider_id,provider_name)
  )
    `)

  await client.query(`CREATE TABLE IF NOT EXISTS Issues(
    id SERIAL PRIMARY KEY,
    user_id INTEGER NOT NULL REFERENCES Users(id),
    created_on TIMESTAMP NOT NULL,
    title VARCHAR(100) NOT NULL UNIQUE,
    link VARCHAR(128) UNIQUE,
    condition_text TEXT NOT NULL,
    description TEXT
  )`)

  await client.query(`CREATE TABLE IF NOT EXISTS Bounties(
    issue_id INTEGER NOT NULL REFERENCES Issues(id),
    user_id INTEGER NOT NULL REFERENCES Users(id),
    identity_id INTEGER NOT NULL REFERENCES Identities(id),
    amount INTEGER NOT NULL,
    created_on TIMESTAMP NOT NULL,
    funding_secured BOOLEAN DEFAULT false,
    announchment_link VARCHAR(128),
    payed_out_to INTEGER REFERENCES Identities(id),
    PRIMARY KEY(issue_id,identity_id)
  )
`)


  await client.query(`CREATE TABLE IF NOT EXISTS Comments(
    id SERIAL PRIMARY KEY,
    user_id INTEGER NOT NULL REFERENCES Users(id),
    text TEXT NOT NULL,
    issue_id INTEGER REFERENCES Issues(id),
    comment_id INTEGER REFERENCES Comments(id)
  )
    `)

  await client.query(`CREATE TABLE IF NOT EXISTS Votes(
    user_id INTEGER NOT NULL REFERENCES Users(id),
    comment_id INTEGER NOT NULL REFERENCES Comments(id),
    PRIMARY KEY(user_id,comment_id),
    weight INTEGER DEFAULT 1
  )`)

Urls

• /sign-up

• /auth/login

• /auth/login/Github

• /auth/login/Twitter

• /auth/login/LNURL-Auth

• /post/issue (without bounty) [GET,POST]

• /post/issue/close [POST]

• /post/bounty (issue with bounty) [GET,POST]

• /post/bounty/pay [POST] --> marked as payed out

• /post/bounty/add [POST]

• /post/comment [POST]

• /post/upvote [POST]

• /issues [GET]

• /issues&bounty=true [GET]

• /issues/ [GET]