SPORE
An idea launchpad for the IMD ecosystem · a personal, untested idea
read as pdf ↓
Whitepaper v1.0
October 2026

Contents

00Origin
01Summary
02Background: what IMD already has
03How SPORE works
04Ideas
05Voting
06Choosing the worker
07Building and launch
08Token supply of each project
09Fees and rewards
10The $SPORE token
11Swarm DAO
12Admin keys and governance
13Risks and limits
AParameters
BWhat SPORE needs from IMD
CGlossary
chain
Ethereum mainnet · Uniswap v4 pools paired with IMD
voting asset
locked sIMD (no new token needed to vote)
platform token
$SPORE (draw boost + protocol revenue)
status
design proposal · nothing deployed

Origin

This idea started with a question: what could a company look like if no one owned it?

Not a company with a founder, a team and a cap table. A network. A place where someone with an idea, but no way to build it, could still contribute. What they bring is their imagination. They leave it on the network, and the agents learn from it.

No one judges the ideas at the door. Good or bad, they all go in. The swarm decides what is worth building, what is worth building further, and where more effort should go.

Maybe that is what a company with no owner looks like. Maybe it is also how a billion-dollar company with no one in it gets made, one small piece of imagination at a time.

How far can one small piece of imagination go?

SPORE is a rough sketch of how this could work on IMD.

01Summary

The IMD swarm can already turn a written brief into deployed contracts, a token and a website, for 0.5 IMD per action. Two questions are still open. Which ideas deserve that work? Who is responsible for shipping each one? SPORE answers both with a weekly vote.

A personal idea, untested
This paper is one person's random idea about the IMD ecosystem. Nothing in it has been built, simulated or tested. I wrote it in the hope that it helps builders who come later. Some of the logic and ideas may be useful. Some may not be.
One assumption
This design assumes IMD can route the build work of a job to a named seat. IMD does not offer this today: the network picks seats itself. SPORE is published as an open proposal, and this feature is the main request to the IMD team (Appendix B).

02Background: what IMD already has

SPORE adds as little as possible on top of parts that already exist. Figures are as of 12 October 2026.

PartWhat it isHow SPORE uses it
IMDThe ecosystem token. Supply only goes down.Every SPORE project is paired with IMD.
sIMDThe IMD staking vault (ERC-4626). About 1.8M IMD staked.Locked sIMD gives voting power.
Seats2,000 NFTs. Each seat runs an AI worker that takes jobs from the network.Seats are the candidates to build a project.
Swarm jobsPaid requests (0.5 IMD each) to write, test, audit, deploy and publish sites.Builds and audits are bought from the swarm.
OracleA panel of seats answers a question. The answer is signed so contracts can verify it.Checks milestones and reads seat records.
Launch rules today10% of each launched token goes to the swarm: 2% to wallets with accepted work, 8% split across all connected seats (about 900–986 seats in recent launches).SPORE keeps the 10% and changes how it is split.
Custom pool hooksLaunches can ship an immutable Uniswap v4 hook. One live launch charges a 1% buy fee and burns 1% of sells.SporeHook collects fees in IMD.

03How SPORE works

Each week is an epoch. In one epoch, ideas are voted on, winners are picked, and a builder is drawn for each winner. Building and launch run in the following weeks.

fig.1 system mapdark = votes and tokens · green = trading fees
Authorsubmits an idea IMD holderlocks sIMD Seat holderenters own agents No seatbacks a seat Idea boardpublic idea or team project Weekly vote 1. vote on ideas 2. top K win 3. draw one builder per winning idea (more votes, higher odds) Builder (drawn seat)posts IMD bond, builds IMD swarmtests, audits, publishes SPORE factorymints token, opens pool X / IMD pool + SporeHookfees collected in IMD Fee split protocol share → voters who voted → $SPORE lockers the rest → treasury or team Swarm DAOseat holders run treasury votes entries delegate drawn passes launch trades public ideas yield One epoch = 7 days. Building and launch happen after the epoch closes.
Voters pick ideas and enter their agents. One builder is drawn per winning idea. The swarm checks the work. Fees from the new pool flow back to voters, $SPORE lockers and the treasury or team.

Who does what

RoleDoesGets
AuthorWrites the idea. A team can attach its own terms.Public idea: optional small reward. Team project: the team share it configured.
VoterLocks sIMD and votes each weekA share of protocol fees; a chance for their agents to be drawn
Seat holderEnters seats as builder candidatesIf drawn: 4% of the project, paid over time
Backer (no seat)Backs a seat holder's entry with votesPart of the builder share if that seat wins
SwarmTests, audits, publishes; all connected seats6% of each project (see §08)
Swarm DAODecides how the treasury is usedControl of treasury spending

04Ideas

Every idea is one of two types. The type is fixed at submission and shown on the idea card.

Type A: public ideaType B: team project
Who submitsAnyone. No owner after launch.A team that wants to launch its own project on SPORE.
Token splitFixed default (§08)Set by the team, inside limits (§08)
Trading feesProtocol share, then the rest to the SPORE treasuryProtocol share, then the rest as the team configured
Who pays for the buildSPORE treasuryThe team, or the treasury if the DAO approves
After launchThe Swarm DAO decides on upkeep and fundingThe team runs it

The idea card shows, before anyone votes: the type, the brief, the token split, where fees go, team vesting (Type B), and which seats have entered to build it.

Submitting needs a small deposit, returned if the idea reaches 10% of the vote threshold. This keeps spam off the board.

05Voting

Voting power

Voting does not spend your power

Like Curve, voting only points your power at ideas. Your veIMD stays locked and comes back in full every epoch, so you can vote again the next week. What a vote leaves behind is a vote receipt: "in epoch N, this wallet gave W votes to idea X." Receipts decide your agent's chance in the draw (§06) and your share of fees (§09).

One epoch

fig.2 epoch timeline7 days, repeats every week
day 1234567→ idea voting · enter your seats · bribes open builder draw window build starts snapshot of voting power top K ideas win entry list committed on-chain builder drawn bond posted Ideas that do not win stay on the board for up to 3 epochs. Their votes carry over and can grow.
Votes are read from the snapshot on day 1. Locking during the week counts from the next epoch.

Rules

06Choosing the worker

Each winning idea gets one builder, drawn at random from the seats entered for it. The draw is weighted: more support gives better odds, but no one is certain to win. This keeps one large holder from taking every build.

Entering

Backing a seat (for holders without a seat)

The draw

# score of entered seat i
score_i = sqrt(own votes on seat i + backer votes on seat i)
        × boost_i      # 1.0 – 2.5, from the wallet's locked $SPORE
        × quality_i    # 0.8 – 1.2, from the seat's accepted-work rate

chance_i = score_i / sum of all scores for this idea

# randomness: the entry list and scores are committed first;
# the seed is the block randomness (prevrandao) of a later block

The square root means 4× more votes gives 2× the score, not 4×. That limits the advantage of holders with a lot of IMD and few seats.

fig.3 example draw for one ideaillustration, not a forecast
entryvotes√votesboostscorechance of being drawn large holder40,0002001.0×200 50% mid holder10,0001001.5×150 37.5% small holder2,500501.0×50 12.5% Without the square root the large holder would have a 76% chance. All three still have a real chance. That is the point of a draw instead of "most votes wins".
Quality is 1.0 for all three here. The mid holder locked $SPORE for a 1.5× boost.

After the draw

07Building and launch

  1. The builder takes the brief and runs the build through the IMD swarm, with the main build step routed to the builder's own seat (this needs the IMD feature in Appendix B). Other seats test and audit as usual.
  2. The work must pass the IMD audit panel with no critical or high findings.
  3. The SPORE factory mints the token, opens an X/IMD Uniswap v4 pool with SporeHook, and sets up all payouts and vesting.
  4. Milestone M1 is reached when the contracts are deployed and the pool is live.

SporeHook

08Token supply of each project

Every project keeps 10% for the swarm. SPORE changes how that 10% is split so the builder gets much more than an average seat.

fig.4 supply split, starting values% of total supply
Type A · public idea pool 85% swarm 10% treasury 4% protocol 1% Type B · team project (example inside the limits) pool 70% team 19% swarm 10% protocol 1% Type B limits: pool ≥ 60%, swarm = 10%, protocol ≥ 1%, team ≤ 25% with forced vesting.
The pool share is placed one-sided from the opening price upward. The protocol holds the pool position permanently.

How the swarm's 10% is split

PartShareWhoPaid how
Builder4%The drawn seat (minus its backer share r)25% at M1, the rest evenly over 90 days. Unpaid part is cancelled if the builder quits.
Build helpers2%Seats with accepted work on this project (tests, audits, site)Evenly over 30 days
All active seats4%Every seat online at launch with recent accepted workEvenly over 30 days

For comparison, a seat in today's IMD launches receives about 0.009% (8% split across about 900 seats). One SPORE builder seat receives 4%. That gap is the reason seats compete to build.

09Fees and rewards

Project trading fees never go to voters directly. Voters are paid only from the protocol's own share, and only if they voted.

fig.5 where trading fees goIMD side of fees
project poolhook fee + LP fee protocol shareA: 20% · B: at least 10% the restA: treasury · B: team's choice 30% → voter poolonly locks that voted 70% → $SPORE lockerslocked $SPORE Swarm DAO / teamdecides use
The protocol share has a floor written into the factory. A team cannot configure below it.

The voter pool, like a staking yield

What you doVoter poolChance to build
Lock onlynonenone
Lock and voteequal partif you entered a seat
Vote for a project that launches and tradesequal part + project part for 6 monthsif you entered a seat
Back a seat (no seat of your own)same as votingbacker share r if that seat is drawn

10The $SPORE token

Voting does not need $SPORE. Locked sIMD is enough. $SPORE has two uses:

Launch. $SPORE launches on SPORE itself, as the first Type B project, paired with IMD and with SporeHook. Its swarm 10% goes to seats like any other project. The first holders are therefore seat holders, who are also the people who want the boost.

Check. If most protocol income comes from trading $SPORE itself rather than other projects, the token's yield is mostly circular. SPORE will publish that ratio every epoch.

11Swarm DAO

The swarm acts as a judge for things that have no owner.

12Admin keys and governance

13Risks and limits

RiskWhat it meansHow SPORE handles it
Builder routingIMD cannot yet route a job to a chosen seat.Proposed as an IMD feature (Appendix B). Without it, the builder builds with its own agent and the swarm only audits.
DemandRewards are paid in new project tokens. Most new tokens have little buying interest.Only K projects per epoch. Fee-weighted voter rewards favour ideas that get used.
ConcentrationLarge holders and holders of many seats have more votes and more entries.A weighted draw with a square root instead of "most votes wins", a 3-seat entry limit per wallet, and public vote records.
Wallet splittingPer-wallet limits can be bypassed with more wallets.Not fully solvable on-chain. Seat counts are a hard limit, and splitting IMD across wallets adds no seats.
Builds take timeA build can take weeks, so projects in progress pile up.K is lowered when many builds are open. A 21-day limit to reach M1, then a redraw.
Launch-day sellingAll non-pool shares cost nothing, and new pools have no buyers below the opening price.Every non-pool share vests over time.
DAO self-interestDAO members can direct funds to builds they take part in.Per-epoch spending cap and public spending.
Shared sIMDimdUSD also uses sIMD as collateral.The same sIMD cannot do both. Collateral cannot vote.
IMD dependencySeat records and the oracle are run by IMD.SPORE only reads them. Milestones can fall back to a multisig decision.
LegalFee sharing to voters may be treated as a financial product in some places.Receipts cannot be transferred at first. Get legal advice before launch. This document is not legal or investment advice.

AParameters (starting values)

ParameterValueChangeable by owner
Epoch length7 daysyes
Winning ideas per epoch (K)2yes
Idea carry-overup to 3 epochsyes
Lock unwind13 weeksyes
Seats entered per wallet per idea3yes
Backer share cap (r)60%no
$SPORE boost1.0–2.5×curve: yes · cap: no
Quality factor0.8–1.2yes
Swarm share of supply10% (4 / 2 / 4)total: no · split: yes
Builder vesting25% at M1, rest over 90 daysyes
Time to reach M121 daysyes
Protocol fee shareA: 20% · B: ≥ 10%floor: no
Protocol supply share≥ 1%floor: no
Team share (Type B)≤ 25%, forced vestingcap: no
Voter pool30% of protocol fees (70% equal / 30% by project fees, 6 months)yes
Hook fee0.5–1% on buysfixed per pool at launch
Parameter change delay48 hoursno

BWhat SPORE needs from IMD

  1. Route a job to a named seat. A field such as leadSeat on a job or launch request, so the main build step goes to the drawn builder. All other steps can still be dispatched by the network.
  2. Signed seat records. Accepted-work counts per seat, signed by the IMD oracle, so contracts can read seat quality without trusting a server.
  3. Per-project work records. Which seats did accepted work on a given project, so the 2% build-helper share can be paid on-chain.

In return, SPORE brings new paid jobs to the swarm, locks sIMD for long periods, and pairs every project with IMD.

CGlossary

EpochOne 7-day voting round.
sIMDThe share token of the IMD staking vault.
veIMDVoting power from locked sIMD.
SeatAn IMD NFT that runs one AI worker.
SwarmAll IMD seats working on the network.
BuilderThe seat drawn to build a winning idea.
BackerA voter without a seat who supports a seat's entry.
Vote receiptThe on-chain record of how many votes a wallet gave an idea in an epoch.
SnapshotThe reading of voting power taken at the start of each epoch.
M1Milestone: contracts deployed and pool live.
SporeHookThe fee hook attached to every SPORE pool.
BribeVaultContract where anyone can pay voters to vote for an idea.
Swarm DAOSeat holders voting on treasury use.

About this paper. SPORE is a personal idea, written quickly and not tested. It imagines what could happen if the swarm's share were not a fixed 10% split evenly, but something agents could compete and bribe for. Take what is useful and leave the rest.

Written by @justlikea_g6 · x.com/justlikea_g6

Version 1.0 · October 2026. All figures about IMD come from public IMD docs and on-chain reads as of 12 October 2026. Nothing here is an offer, investment advice or legal advice.

SPORE

To you, the clever and crafty, bitter beyond all bitterness, who has sinned against the gods in bestowing honors upon creatures of a day—to you, thief of fire, I speak.

— Hermes to Prometheus · Aeschylus, Prometheus Bound (tr. H. W. Smyth)