Proposals

What should we build around $requests?

Pitch it here. Every proposal is listed on this page for the community to see and argue about. The ones that get traction move to the Potential utility list, and from there to Status as a 200.

Submit a proposal

Takes two minutes. Be concrete: what gets built, who it helps, what it would cost.

Name or handle * Where to reach you

Category * Link

Title * The proposal *

0 / 2000

Listed publicly under your handle. Contact details stay private. No wallet needed.

202Accepted

Your proposal is in.

It is listed below under your handle. Share it on X with @RequestsToken so people can weigh in.

How a proposal becomes a 200

100Submit. It appears on this page straight away.
102Discuss. The community argues it out on X with @RequestsToken.
202Accepted. Proposals with traction get a card under Potential utility.
200Shipped. Built in public, then listed under Status with a link.

What makes a good one

Something a small team could ship in weeks, not a roadmap for a decade.
A clear link to the library, to Python, or to funding open source.
A number: what it costs, who it reaches, what it saves.
Open source by default. If it needs a repo, say which licence.
Nothing that needs price promises, yields or a presale.

Already on the table: automated buybacks, an Open Source Fund, the thanks tool and a public dashboard. See Potential utility. Kenneth's own early ideas are quoted there too.

Submitted so far

What should we build around $requests?

Submit a proposal

Your proposal is in.

Proposals, newest first.