How grants work

How grant dates move

Each project has a far horizon — the latest we currently estimate for that grant. Signed-in votes pull that date closer to now. The closer date is still an estimate, not a promise to pay.

Base horizon

We set a base date per project. That is the slowest case: if support stays thin, this is the horizon we show.

How a vote pulls

Only signed-in votes pull a grant date. Guest votes still show as community opinion. The pull uses two numbers: how many signed-in votes that project has, and how many signed-in votes exist in total.

If a project leads, its date moves in. If later signed-in votes go to other projects, its share shrinks and the date can move back out. The ratio has to hold as the pool grows.

Why this cannot jump overnight

A project needs at least 3 signed-in votes before its date moves. One network cannot cast that many votes, so one household cannot pull a date by itself.

We add 40 silent votes to the pool. The first real votes move little. Even a unanimous sweep only travels 50% of the way from the base date to one year from today. No pulled date can fall sooner than 365 days from now.

The formula

If a project has fewer than 3 signed-in votes, pull is zero. Otherwise pull = project votes / (all signed-in votes + 40), capped at 50%. The shown date sits that far along the line from the base date to one year from today.

We compute that date on our side. If the check fails, you see the base date, not a closer one.

Worked examples

These rows show pull only, not the calendar date. Same formula the site uses. Counts are signed-in votes.

CaseSessionGrapheneOSSession pullGrapheneOS pull
No votes yet000%0%
One network only200%0%
Just enough to move307%0%
A small lead10518%9%
A clear lead401044%11%
A large tie10010042%42%
A monopoly1000050%0%

Not a promise

Listing a project, collecting votes, or showing a closer date does not create an obligation to fund. Grant decisions stay with us. See ourTerms of Service.