The participation problem

Token-weighted voting treats every holder as equally informed. A delegate who has been in the system for two years and reads every proposal carries the same per-token weight as a wallet that bought yesterday and votes for everything. Conviction — the costly signal that someone actually cares about a particular outcome — gets lost in the aggregation.

The result is apathy at the margin and whale dominance at the centre. Proposals pass with thin participation and narrow legitimacy. Treasury decisions get made by a handful of large holders who didn't necessarily read what they voted on.

What Signals does

Signals introduces initiative-scoped commitment voting. Supporters lock tokens behind specific initiatives and receive transferable ERC-721 positions representing their commitment. Voting weight scales with both stake and lock duration — but the locking is the point: it forces voters to prioritise, since tokens committed to one initiative can't simultaneously support another.

At a structural level, voting weight combines two factors:

$$W = g(s) \cdot f(L)$$

a concave transform $g(s)$ of stake $s$ that compresses million-to-one holdings into single-digit ratios, and a lock-duration factor $f(L)$ that turns time into a costly signal of commitment.

The output is a ranked list of community priorities backed by real opportunity cost, not just held-token totals. Initiatives that cross a configurable threshold proceed to formal governance; the rest serve as a continuously-updated read on what the community actually wants.

Capital allocation

Binary yes/no votes on individual proposals can't produce ranked community preferences. Signals can, because every commitment carries opportunity cost — tokens locked behind one initiative can't simultaneously support another. The aggregate of those commitments is a continuously-updated ranking of where the community wants capital deployed.

A single deployment supports multiple boards — grants, dev-tooling, events, research — each with independent thresholds, budgets, and eligibility rules. The structure handles a few common shapes:

• RFP evaluation. Service providers submit competing bids; supporters back their preferred provider; the first to cross the acceptance threshold wins.
• Pre-funded programmes. A treasury pre-allocates an annual budget. Proposals arrive continuously, get evaluated on merit, and are funded on acceptance without further governance votes.
• Discretionary budgets. Operational teams — events, marketing, tooling — run dedicated boards with pre-set budgets, removing governance overhead from routine expenditures.

The point isn't that any of these are impossible without Signals. It's that each becomes a continuous surface rather than a quarterly cycle, and the ranking it produces is a byproduct of how the mechanism is used — not a separate consensus exercise. Read the use-case docs.

What we've learned

The Signals research programme has produced an extensive empirical body of work, most recently a five-layer mechanism for meritocratic capital allocation calibrated against on-chain data from ENS, Optimism, and Uniswap. The full thesis lives in sub-linear commitment voting.

Status

Signals is in active development. For protocols considering Signals for their governance, get in touch.