Resources

Written when it's worth reading.

Guides, documentation, research, and product updates will publish here. This page is not padded with generated posts to look active — instead, below is the content architecture, the specific pieces in progress, and how far along each one is. If you need something on this list now, ask and we will prioritise it.

Streams
Four
Pieces in progress
Eight
Published
None yet
Filler posts
Zero

Streams

Four kinds of writing, different jobs.

Each stream has a defined audience and standard. Mixing operator guides with engineering reference is how documentation becomes unusable for both.

Guides

Drafting

Operational walkthroughs for a specific job: preparing a distribution list, structuring a cliff, arming a strategy safely.

Project operators

Documentation

Outlined

Module reference — configuration options, validation rules, state transitions, and the service interfaces behind them.

Engineers

Research

Planned

Longer analysis on market structure, distribution outcomes, and unlock mechanics. Published with method and data source stated.

Technical and strategic

Product updates

Planned

What shipped in each module, what changed in behaviour, and what was deprecated. Dated entries, no roadmap theatre.

All users

In progress

What is actually being written.

Each entry below is a real planned piece with a defined scope, not a title placeholder. Status is honest: drafting means text exists, outlined means structure exists, planned means neither yet.
GuideDrafting

Token launch checklist

The sequence that has to be finished before a mainnet deployment: ownership model, supply decisions, liquidity plan, distribution list hygiene, and the controls that need to exist on day one rather than week three.

GuideDrafting

Understanding token vesting

Cliffs, linear release, unlock frequency, and revocation — what each parameter does to a holder's incentives, and the schedule mistakes that create a sell wall the quarter after launch.

GuideOutlined

Token distribution strategies

Choosing between airdrop, claim, and direct allocation. Batch sizing and gas economics, eligibility criteria that survive scrutiny, and how to handle the failure and retry path without double-paying.

ResearchOutlined

Building token utility

Where utility actually changes holder behaviour versus where it is decorative. Staking, gamification, and access mechanics assessed on retention rather than announcement value.

ResearchOutlined

Market liquidity infrastructure

How spread, depth, and order frequency interact on thin books. What a market-making configuration can and cannot achieve, and the guardrails that keep a strategy from becoming the dominant participant.

GuidePlanned

Blockchain migration

Moving a live token between chains: snapshot and eligibility, bridge versus redeploy, holder communication, wallet risk controls, and the accounting reconciliation nobody scopes for.

GuidePlanned

Web3 security for project teams

The operational half of security: key custody, exchange API permissions, multisig thresholds, rotation when someone leaves, and dual control on treasury movement.

ResearchPlanned

Token analytics that matter

Holder concentration, transfer patterns, liquidity depth, and unlock proximity — which indicators predict trouble, and which are vanity metrics that look good in an update post.

Documentation

What the reference will cover.

Module documentation is written against the same typed interfaces the Console uses, so it describes real behaviour rather than intended behaviour.
  • Module configuration reference with every field, constraint, and default
  • Service interface definitions for generation, vesting, airdrop, staking, and market making
  • State machines for campaigns, schedules, and strategy lifecycle
  • Validation rules and error semantics, including retry behaviour
  • Environment and permission model for organizations, projects, and roles
  • Webhook and event payloads once the API surface is issued

Until it publishes

The Console sandbox is the most complete documentation that currently exists. Every module runs on fabricated data with its validation rules, states, and controls active — you can read the behaviour by using it.

Editorial standard

  • No piece publishes without a named scope and a real conclusion
  • Data and method stated, or the claim is removed
  • No recycled listicles or search-bait titles
  • Corrections are dated and left visible rather than quietly edited

Requests

Need one of these sooner?

If a specific guide would unblock a decision you are making, tell us which one. We will send what exists in draft and prioritise finishing it.