Token Cap-Table Management: Equity and Tokens on One Ledger

A traditional startup has one cap table. A Web3 startup has two: an equity ledger (shares, options, SAFEs) and a token ledger (warrants, side letters, grants), and the same rounds dilute both. Managing them as disconnected spreadsheets is how founders end up not knowing who owns what. This article is about the operational discipline of running the two ledgers together: why one-ledger thinking understates dilution, how a financing round corrupts the picture if it is not handled deliberately, and where custodian reconciliation and accounting fit. The instruments themselves are covered elsewhere; this is the management layer for the fundraising instrument stack.

The discipline in brief

• A Web3 company runs two ownership ledgers: equity (shares, options, SAFEs) and tokens (warrants and side letters, plus grants).
• They interact. Rounds and grants dilute both, and modelling only one understates dilution.
• A token cap table is not a token allocation plan: the plan is the intent, the cap table is the evolving reality, and the two must reconcile.
• Custodian integration lets the token ledger be reconciled on-chain, which is the analogue of reconciling a share register.
• Tooling records and models; it does not decide legal ownership or securities status, which remain counsel's call.
• The mechanics are document- and jurisdiction-specific. Confirm with counsel and your accountant; nothing here is legal or accounting advice.

Two ledgers, one company

They have different holders, triggers and treatment, but the same financing and grant decisions touch both. The only correct view is the combined, fully diluted picture across equity and tokens together.

Why one-ledger thinking understates dilution

SAFEs convert into equity and dilute the equity ledger; token warrants and side letters resolve into tokens and dilute the token ledger; employee equity and token grants dilute their respective ledgers as they vest (see Web3 employee token grant structuring). Because rounds and grants hit both, modelling only the equity side systematically understates the founder's true diluted position. The fully diluted model must span both ledgers.

Cap table vs allocation plan

A token allocation plan sets intended percentages across team, investors, treasury and community; a token cap table tracks the actual instruments, holders, vesting and dilution over time. The plan is the intent; the cap table is the evolving reality. They should reconcile, and the discrepancies are exactly what disciplined cap-table management surfaces.

Why custodian integration matters

Tokens, unlike share certificates, settle on-chain and are often held with institutional custodians. Cap-table tooling that integrates with custodians can reconcile recorded token positions against what is actually held and distributed, the on-chain analogue of reconciling a share register. That reconciliation is part of the cap table being defensible, not an optional extra.

Governance framework: managing the dual-ledger through a financing round

The moments that most commonly corrupt a dual-ledger cap table are financing rounds and grant events, because they touch both ledgers simultaneously and the two ledgers are rarely updated at the same time:

Pre-round preparation:

• Before any term sheet is signed, the existing combined cap table (equity + token) is confirmed as current and accurate. Every outstanding instrument — SAFEs, token warrants, side letters, unvested grants on both ledgers — is verified against the underlying documents.
• A fully diluted model is built covering both ledgers: what does the round look like if all SAFEs convert, all token warrants are exercised, and all unvested grants vest? Founders who skip this step regularly discover post-round that the combined dilution was materially higher than the equity-only view suggested.
• The cap-table model is reviewed by counsel before the round closes. Counsel confirms that the instrument terms in the cap table match the actual documents.

During the round:

• New investors receiving both equity and token rights (via a warrant or side letter alongside the equity investment) are added to both ledgers simultaneously, with all instrument details captured: valuation, trigger events, vesting start date, cliff, and schedule.
• Any amendment to existing instruments (e.g. a SAFE with a side letter being amended in connection with the round) is reflected in both ledgers immediately.

Post-round reconciliation:

• Within 30 days of a round closing, the cap table is reconciled against all executed documents. The reconciliation is a formal document: each instrument on the cap table has a corresponding executed document, with the document date, parties, and key terms verified.
• For tokens already distributed, the cap-table record is reconciled against the on-chain distribution — matching recorded addresses and amounts to what was actually distributed and held.

Implementation checklist: building a defensible token cap table

A token cap table is not just a spreadsheet with allocation percentages. The following covers the minimum required to make it defensible:

1. Instrument-level detail: for every token warrant, side letter, or grant, record: the holder, the instrument type, the total token amount, the vesting schedule (total duration, cliff, periodic vesting), the trigger event (if any) required before vesting begins, and the document reference.
2. Version control: every change to the cap table is a new version, not an overwrite. The prior version is retained. The change log records: date, nature of change (new issuance, exercise, vesting event, amendment), the person who made the change, and the document authorising it.
3. Vesting tracking: unvested grants are tracked separately from vested but undistributed grants and from already distributed tokens. The cap table shows the current position at each level, not just the total grant size.
4. Reconciliation to on-chain: at least quarterly, and after any distribution event, the cap table's record of distributed tokens is reconciled to the actual on-chain balances in the relevant wallets or custodian accounts. Discrepancies are investigated.
5. Counsel sign-off cadence: the cap table is reviewed by counsel at minimum annually and before any new financing round, grant programme, or secondary transaction.

Accounting treatment: instruments on both ledgers

The token cap table has specific accounting implications that go beyond the governance record:

Equity instruments (SAFE, options, shares):

• SAFEs are financial instruments — they are recognised on the balance sheet at fair value or as financial liabilities/equity components per the applicable framework. Confirm the classification with your accountant; a SAFE is not always an equity instrument under all frameworks.
• Share options are recognised as equity-settled share-based payments per the applicable standard (IFRS 2 or ASC 718). The expense is recognised over the vesting period at the grant-date fair value.
• Shares issued in a priced round are recorded at the issue price with any premium over par value allocated to additional paid-in capital.

Token warrants and side letters:

• The accounting treatment depends on the instrument's terms and the applicable framework, and is highly counsel- and accountant-specific. A token warrant that gives the holder a right to receive tokens at a future date may be a derivative, an equity instrument, or a liability, depending on its structure. Do not assume a classification without specific advice.
• If the token warrant represents a prepayment for tokens to be issued from the treasury (a typical structure for investor token warrants), the prepayment is recognised as a liability (obligation to deliver tokens) or as equity (if it meets the criteria for equity classification) at inception.

Token grants to employees and service providers:

• Employee token grants are typically accounted for as share-based payments (by analogy, if the applicable framework does not specifically address token grants). The expense is recognised over the vesting period at the fair value of the tokens at the grant date (or measured date per the framework).
• For grants to non-employees, the expense is typically recognised at the fair value of the tokens at the vesting date or the service completion date.
• The vesting schedule in the cap table feeds the accounting entries: each cliff and periodic vesting event generates an expense recognition entry. The cap table's vesting schedule and the accounting system's amortisation schedule must match.

Practical guidance

1. Maintain both ledgers as one combined picture, equity and tokens together.
2. Model fully diluted across both: SAFEs, warrants, side letters and grants.
3. Reconcile the allocation plan against the actual cap table to surface discrepancies.
4. Reconcile token positions against custodian and on-chain reality, the share-register analogue.
5. Keep instrument terms structured (conversion, exercise, vesting), since they feed dilution and accounting.
6. Confirm the legal, securities and accounting treatment with counsel and your accountant; tooling does not decide it.

Choosing a cap-table tool

For a Web3 cap table, the configuration that matters is whether the tool can hold both ledgers and reconcile the token side against on-chain reality, not just model equity. When you evaluate one, confirm that it represents both the equity and token ledgers and your specific instrument terms, and that it connects to your custodians for on-chain reconciliation. Pulley administers token and equity cap tables together and connects to institutional custodians for that reconciliation; Carta administers equity cap tables broadly. Both record and model instruments, dilution and vesting, but neither determines legal ownership or whether a token right is a security; that stays a counsel determination.

How Wag3s fits

Wag3s HR records the instrument and grant data behind both ledgers, the SAFE conversion terms, the token-warrant and side-letter terms, and the vesting schedules, as structured, auditable inputs to cap-table and equity- and token-compensation reporting. The legal, securities and accounting treatment stays a determination for counsel and your accountant; Wag3s supports that work rather than replacing it. See the HR product page.

Further reading

• Web3 Fundraising Instrument Stack
• SAFE vs SAFT vs Token Warrant
• Post-Money SAFE Explained
• Token Warrant vs Token Side Letter
• Web3 Employee Token Grant Structuring
• Token Vesting & Cliff Accounting

Sources

• IFRS — IFRS 2 Share-based Payment and IAS 19 Employee Benefits: share options and many token grants are recognised as share-based payments over the vesting period, the accounting that the cap table's vesting schedule has to feed.
• FASB — ASU 2023-08: US GAAP fair-value measurement of crypto assets, relevant where distributed tokens sit on the balance sheet alongside the token ledger.
• Y Combinator — Safe financing documents: the SAFE terms that determine how the equity ledger dilutes on conversion (see post-money SAFE explained).

The dual-ledger structure itself, custodian reconciliation, and the securities or accounting classification of any token instrument are document- and jurisdiction-specific, with no single official authority that settles them; confirm with counsel and your accountant. Nothing here is legal or accounting advice.