Roadmap and $WAKE

Everything on this page is a description of intent. None of it is built. No dates are promised, no token exists, and nothing here is a commitment or an offer. The status and disclaimers section at the bottom of this page states that in full, and it governs everything above it.

What is built is Phase 1, and it is documented in the rest of these docs: a signed, public index of trading agents whose code lives on IPFS. Everything below is what would need to be true for that index to become something more useful, and why.

Phase 1: what exists today#

For contrast, so the boundary is unambiguous. Today Wakehood has:

• Ed25519 identities generated in the browser, with no server-side account.
• Signed publishing, with the IPFS CID inside the signed payload.
• An enforced asset class and strategy taxonomy across crypto and tokenized real-world assets.
• A trust score that counts published agents and account age, and claims nothing else.
• No execution of agent code, ever.

That is the entire product. Anything not on that list is not in the product.

Phase 2: fork and subscribe (not built)#

Today, discovering an agent and using an agent are separate acts: you find code in the index and you take it away. Nothing flows back to the person who wrote it, which means the incentive to publish good work is purely reputational.

Phase 2 proposes making that relationship explicit:

• Fork. Take an existing agent as the starting point for your own, with the lineage recorded rather than lost.
• Subscribe. Follow an agent under terms set by its author.
• Automatic revenue share. Value from forks and subscriptions flows back to the original author without either party having to trust the other to pay.

The Fork button on an agent detail page is a placeholder for exactly this. It is the only placeholder in the product, and it does nothing today.

Phase 3: trust from real performance (not built)#

The Phase 1 trust score is deliberately shallow, and the trust score page explains at length why a score built on unverifiable, self-reported returns would be worse than no score at all.

Phase 3 is the intended answer to that problem:

• Trust derived from real trading performance, rather than from the act of uploading a file.
• Community staking, so that reputation has a cost attached and vouching for an agent means putting something at risk.

Both depend on infrastructure that does not exist here yet. Wakehood observes no trades today, because it runs no code today.

Phase 4: a CLI tool (not built)#

Publishing from a browser is fine for a first agent and irritating for a tenth. A command line tool would let a developer publish, sign, and manage agents from the same environment where the code is written, and would make the signing flow scriptable in CI.

The signing model would not change: keys stay local, the CID stays inside the signed payload, and the server keeps verifying signatures the same way.

Phase 5: the $WAKE token (not built, does not exist)#

Phase 5 proposes a token, $WAKE, with four utilities. To be completely clear before describing them: no such token exists, none has been issued, none is for sale, and no launch is promised. The four utilities are design intent, and they are listed here because a roadmap that hides its own economics is worse than one that states them.

1. Stake of Confidence#

Developers and the community stake $WAKE on an agent. Staking is a claim with something behind it: it costs you if you are wrong, which is the property that a reputation system built purely on uploads can never have.

2. Revenue Share Currency#

The unit of account for the fork and subscribe payments proposed in Phase 2, so that value moving between an author and the people building on their work has a defined settlement asset.

3. Reputation Slashing Insurance#

An insurance pool for subscribers, funded so that a betrayal of trust has a consequence and the people harmed have a claim, rather than being left with a broken agent and a shrug.

4. Governance over Taxonomy#

Holders vote on the asset class and strategy taxonomy: new categories, new tags, and what Explore can filter on. Today that list is curated by us, as documented in asset classes and strategies. Governance would move the decision to the people who actually publish.

Status and disclaimers#

Stated plainly, because this page is the one most likely to be misread:

• Nothing in Phases 2 through 5 is built. Everything on this page is intent, not product.
• No token exists. $WAKE has not been issued, minted, distributed, or sold. There is no contract address, no allocation, no presale, and no whitelist. Anyone offering you one is attacking you.
• No dates are promised. There is no timeline, and phases may be reordered, redesigned, or dropped entirely.
• This is not an offer. Nothing here is an offer, a solicitation, or a commitment to issue or sell any token or security, and nothing here is investment advice.
• Do not make decisions based on this page. The only thing you should rely on is what is documented as existing today, in the rest of these docs.

If you want the part that is real, start with the quickstart.