OPEN PANEL — Tokenization & DAO Track

The collectible / membership / governance layer under the OPEN PANEL · VARIANT masthead, and the legal wrapper that issues it. Covers token nature, the $LONGBOX handle set, chain & infra, the DAO’s wrapper-as-steward, utility, launch sequencing, and risk. Status: DRAFT v0.1 — not legal or financial advice; every structure here requires qualified securities, tax, and offshore counsel before any deploy or sale. Conform to CANON.md; where this doc and CANON disagree, flag it, don’t silently diverge (CANON is being amended in parallel to make Structure B / PBC-center the default — see §1). Author: tokenization session 2026-06-13.

0. Thesis (one line)

The token is a collectible / membership / governance layer — NOT a cashflow instrument. $LONGBOX gives holders access, voice, and collectibles under the VARIANT masthead; the universe’s royalties stay in the Rights & Royalty LEDGER (CANON §6 #4), away from the consumer token, so the token is never a security-by-design.

1. The two-layer architecture

The single most important decision in this track is a separation: the “fun” consumer coin and the “serious” IP-rights/royalty rails are two different layers that never touch each other’s money. Real royalty mechanics live in the LEDGER (off-chain) or its on-chain mirror (Story Protocol); the consumer coin carries no claim on them.

Layer	What it is	Where it lives	Carries cashflow?
Consumer / collectible coin	$LONGBOX — membership, governance, access, collectible drops	Base, via Zora Coins Protocol	No — non-financial by design
IP rights & royalty registry	programmable licenses + royalty modules mirroring the LEDGER	Story Protocol ($IP) or off-chain LEDGER only	Yes — but routed to the PBC (OPEN PANEL · VARIANT), never to token holders

Wire diagram

                    ┌────────────────────────────────────────────────┐
                    │   WRAPPER  —  Cayman Foundation Co. / WY DUNA   │
                    │   • holds TREASURY   • holds MISSION-LOCK       │
                    │   • ISSUES $LONGBOX  • = Structure-C steward    │
                    └───────┬───────────────────────┬────────────────┘
            ══mission-lock══╝                       │ issues $LONGBOX
                 ║ (control)                         ▼
                 ▼                          ┌──────────────────────┐
   ┌────────────────────────────────────┐  │   TOKEN HOLDERS       │
   │        OPEN PANEL, INC.            │  │  governance · access  │
   │   Delaware Public Benefit Corp     │  │  · collectibles       │
   │   ┌────────────┐  ┌─────────────┐   │  │  ✗ NO cashflow        │
 ◀─│   │ OPEN PANEL │  │   VARIANT    │   │  └──────────────────────┘
free│   │ free reader│  │ licensing ·  │   │
read│   └────────────┘  │ VARIANT eds. │   │
ers │                   └──────┬───────┘   │
   │   owns IP + marks ·       │ licensing │
   │   OPERATES the company    │  $$       │
   └───────────────────────────┼───────────┘
                               ▼
                    ┌──────────────────────────────────┐
                    │  RIGHTS & ROYALTY LEDGER (CANON §6)│  works→rights→grants→
                    │  off-chain  ◀──mirror──▶  Story    │  licensees→royalty→payouts
                    │  Protocol ($IP) registry  (opt.)  │
                    └───────────────┬──────────────────┘
                                    ▼
                        royalties → the PBC (OPEN PANEL · VARIANT) → mission + creator pay
                        (NEVER to $LONGBOX holders)

  Legend:  solid box = required entity   ┌┄┄┐ dashed = optional component
           ──label──▶ = what flows ($ · IP · royalties · free comics)
           ══heavy══▶ = CONTROL / mission-lock direction
           ◀─free─ to READERS = the always-free output

Note vs CANON: CANON §1 currently lists OPEN PANEL FOUNDATION as a 501(c)(3) and VARIANT as an arm’s-length sister. This doc is written to the amended architecture (Structure B, PBC-center) per ENTITY_STRUCTURE_REVIEW.md §7 and the parallel CANON edit. The WRAPPER is the Structure-C steward entity (mission-lock holder) introduced early, here to issue and govern the token rather than to lock permanence. The PBC operates; the wrapper **stewards

issues**.

2. Token nature decision — membership/collectible/governance vs royalty-RWA

⚠️ HARSH TRUTH — a royalty-backed token is almost certainly a security
Section titled “⚠️ HARSH TRUTH — a royalty-backed token is almost certainly a security”

A token that pays holders a share of the universe’s royalties is investment of money + common enterprise + expectation of profit from the efforts of others — the Howey test, three for three. It is a security under US law. Worse: a public token sale is itself a regulated activity — an unregistered securities offering in the US, and a regulated virtual-asset service under the Cayman VASP Act if issued through a Cayman wrapper. There is no clever ticker or “utility” garnish that launders this. Do not ship a royalty-dividend token on the open market. If royalty-RWA is ever wanted, it is a deliberate, counsel-led Reg-D / Reg-S / RWA path with KYC, accreditation, and transfer restrictions — a different product, sold to a different audience, behind a different legal wall.

	Membership / collectible / governance (RECOMMENDED)	Royalty-RWA (defer; counsel-only)
What holders get	access tiers · governance · collectible drops · VARIANT EDITION entitlements	a contractual share of LEDGER royalties
Howey exposure	Low — no profit-from-others’-efforts if utility is real & non-financial	High — a textbook security
Sale mechanism	open mint on Base/Zora, fiat onramp, no KYC gate	private placement; Reg-D (US accredited) / Reg-S (offshore); KYC + accreditation
Cayman VASP Act	issuance still needs review, but a non-financial collectible is far lighter	full VASP registration / licensed-issuer analysis
Secondary market	freely tradable as a collectible	transfer-restricted; lock-ups
Cashflow to holders	None (royalties stay in the LEDGER)	Yes (the whole point — and the whole risk)
Verdict	Ship this.	Only as a separate, deliberate, walled product.

Recommendation: issue $LONGBOX as the non-financial membership/collectible/governance token. Keep every royalty mechanic in the LEDGER / Story layer (§4). Treat royalty-RWA as a distinct future product that does not change the consumer token’s nature.

3. $LONGBOX — naming + handle set

Summarized from brand/NAMING_CLEARANCE.md (cross-link for full diligence). The longbox is the cardboard archive where collectors store back issues — on-thesis for the collectible/DAO layer. It is weak as a standalone masthead (generic in comics + a dead-startup ghost), so it sits under OPEN PANEL / VARIANT, never over them.

Asset	Pick	Status	Action
Domain (primary)	longbox.foundation	✅ free (no NS)	register — matches the wrapper
Domain (short)	longbox.box	✅ free	register as redirect
ENS	longbox.eth	🟡 no address set → likely free	verify on app.ens.domains; register if open
Token ticker	$LONGBOX	✅ no notable token	claimed at deploy time, after the wrapper exists
Socials	@longboxdao (X · Telegram · Discord)	⚠️ manual — bare `@longbox` likely gone	register the `…dao` convention across all three at once
Trademark	LONGBOX	dead `LONGBOX DIGITAL` mark (abandoned 2010); generic in comics	fine for a sub-brand; run a real USPTO knockout pre-launch

Caveats (do not bury): the term is weak / generic (low trademark distinctiveness), and “Longbox Digital” — the “iTunes for comics” that collapsed in 2011 — is a ghost on the name. Manage the narrative; this is a sub-brand under VARIANT, not the company.

4. Chain & infra

Concern	Choice	Why
Consumer coin chain	Base (Coinbase L2)	reach, Coinbase-grade prestige, fiat onramps
Issuance protocol	Zora Coins Protocol	creator-coin issuance, perpetual-royalty + fee-share rails, on Base
IP-rights / royalty registry	Story Protocol ($IP) — or off-chain LEDGER only	programmable on-chain licenses + royalty modules

How Story mirrors the LEDGER. CANON §6 #4 defines the Rights & Royalty LEDGER as the canonical model of works → rights → grants → licensees → royalty terms → payouts. Story Protocol’s IP Assets + Licensing + Royalty modules can be a 1:1 on-chain mirror of that schema: each work registered as an IP Asset, each grant as a programmable license, each payout flowing through Story’s royalty module. The off-chain LEDGER remains the system of record; Story is an optional public, programmable replica for licensees who want on-chain enforcement.

Critical wiring: the Zora coin (Base) and the Story registry are not connected by cashflow. Zora’s “perpetual royalties” here mean trading-fee economics on the collectible itself (which accrue to the treasury, not to holders as a dividend) — they are not the universe’s IP royalties. The universe’s royalties move only through the LEDGER/Story layer to the PBC (OPEN PANEL · VARIANT). Keeping these two royalty meanings apart is what keeps $LONGBOX non-financial.

5. Legal wrapper = steward

The DAO needs a legal person to hold its treasury, sign contracts, and limit member liability. Two wrappers fit, and the wrapper doubles as the Structure-C steward / mission-lock entity from ENTITY_STRUCTURE_REVIEW.md §3 — it holds the mission-lock and issues the token while the PBC operates the company.

	Cayman Foundation Company	Wyoming DUNA
Form	ownerless foundation company (Cayman Foundation Companies Act)	Decentralized Unincorporated Nonprofit Association (WY 2024)
Members	none required (ownerless) — clean for a DAO	members are the token holders
Liability shield	strong; established offshore DAO wrapper	limited-liability for members; US-domestic
Token issuance	well-trodden, but engages the VASP Act	newer, less tested; US securities law still applies
Tax / jurisdiction	offshore; no Cayman direct tax, but US-nexus + CFC rules need counsel	US-domestic; simpler tax story, smaller legal corpus
Mission-lock fit	foundation’s objects can hard-code the mission → strong steward	nonprofit purpose can carry mission, but thinner caselaw
Best when	global token, offshore treasury, max liability separation	US-centric, want domestic simplicity, smaller raise

How it slots into Structure C. In ENTITY_MODELS_DIAGRAMS.md C, a Perpetual Purpose Trust (or golden-share holder) sits above OPEN PANEL, INC. holding voting control + mission-lock. The token wrapper is that steward, introduced early: it holds the treasury and the mission-lock (charter objects = “comics free forever; IP serves the mission”) and issues $LONGBOX. The PBC stays the for-profit operator. When the operator commits to permanence, the wrapper’s mission-lock hardens into the full Structure-C trust with no re-platforming — the steward already exists.

Flag vs CANON: CANON does not yet name an offshore/steward entity. This wrapper is an addition proposed by this track, consistent with the Structure-C path the entity review already recommends. Operator + counsel ratify before it lands in CANON.

6. Utility — what the token actually does (non-financial)

Every utility below is access, voice, or collectible — never a claim on cashflow. This is the line that keeps $LONGBOX clear of Howey.

Utility	Mechanic	Why it’s non-financial
Access tiers	hold/stake N $LONGBOX → early reads, beta reader features, creator AMAs	a membership perk, not a return
Governance scope	vote on mission-bounded matters: which outreach programs the treasury funds, community VARIANT EDITION themes, brand/community decisions	governs spending & curation, not profit distribution
Collectible drops	token-gated mints of covers, variant art, numbered editions	the collectible is the good received
VARIANT EDITION entitlements	token unlocks premium/collectible editions (entitlement check per CANON §4 DRM stance)	consumption right, not yield
Reputation / status	longstanding-holder badges, collector tiers	social, not financial

Out of scope on purpose: no revenue share, no royalty pass-through, no buyback-and-burn framed as price support, no staking “yield.” Governance is mission-bounded — holders steer community and outreach choices, not the PBC’s profit.

7. Launch sequencing

Hard gate: do NOT deploy the token before the wrapper exists. Issuing a token with no legal person behind it is the fastest path to personal liability and an unregistered-offering problem. Wrapper first, always.

Phase 0 — wrapper formation. Stand up the Cayman Foundation Co. or WY DUNA with counsel; charter objects encode the mission-lock. Treasury account, multisig, signers.
Phase 1 — registrations (operator-executed, per NAMING_CLEARANCE §7): domains, ENS, @longboxdao socials. USPTO knockout on LONGBOX.
Phase 2 — LEDGER / Story layer. Stand up the off-chain LEDGER (CANON §6 #4); decide Story Protocol mirror yes/no (§9). This is independent of the consumer coin and can lead it.
Phase 3 — token design & audit. Finalize utility (§6), governance scope, supply, vesting. Securities counsel signs the non-financial memo. Smart-contract audit.
Phase 4 — deploy $LONGBOX on Base via Zora. Ticker claimed at deploy. Open mint + fiat onramp. Only after Phases 0–3.
Phase 5 — governance go-live. Open mission-bounded voting; first collectible drop.
Later — permanence. When the operator commits, harden the wrapper into the full Structure-C trust (no teardown).

8. Risk register

#	Risk	Severity	Mitigation
1	Securities re-characterization — a regulator reads $LONGBOX as an investment contract	High	Keep it strictly non-financial (§6); no yield/buyback/royalty language; counsel memo; royalty-RWA stays a separate walled product
2	Mission-washing — “for-profit giving comics away + a token” reads as a funnel, not a gift	Medium	PBC charter + wrapper mission-lock carry the credibility; brand voice must not overclaim charity it isn’t (mirrors ENTITY_STRUCTURE_REVIEW §6 #2)
3	Wrapper-jurisdiction risk — Cayman VASP Act exposure; US-nexus / CFC tax surprises; DUNA novelty	Medium–High	Pick wrapper with counsel (§5); VASP analysis before issuance; structure US-nexus deliberately
4	Ticker ghost — “Longbox Digital” failure + generic mark dilute the name	Low–Med	Sub-brand under VARIANT, not the masthead; manage the narrative; real TM knockout pre-launch
5	Custody / key risk — treasury multisig compromise; signer loss	Medium	Multisig with quorum, hardware signers, documented recovery; insure where feasible
6	Governance capture — whale accumulation steers community votes	Medium	Mission-bounded scope caps blast radius; quorum + vote caps; mission-lock is wrapper-held, not vote-amendable
7	Two-royalty confusion — Zora trading “royalties” mistaken for universe royalties	Med	Treasury-only accrual, never distributed as dividend; document the firewall (§4)

9. Open decisions (interview the operator)

Token nature — non-financial membership/collectible/governance (recommended) vs royalty-RWA (securities-heavy, counsel-only, separate product)?
Chain — Base/Zora (recommended) confirmed, or reconsider (e.g. Solana)?
Wrapper jurisdiction — Cayman Foundation Company vs Wyoming DUNA?
Story Protocol — mirror the LEDGER on-chain via Story ($IP), or stay off-chain-only for the royalty/rights layer at launch?

Companion to ENTITY_STRUCTURE_REVIEW.md, ENTITY_MODELS_DIAGRAMS.md, and brand/NAMING_CLEARANCE.md. Defers to CANON.md; where they disagree, CANON governs once amended. Not legal or financial advice — securities, tax, and offshore counsel confirm every structure before any deploy or sale.