A Dispatch · Issue I

The Thread Contest

five angles on BLOK Capital — pick one, teach it well

An open call to the global cohort of builders and creators. Write a thread that teaches the BLOK Capital protocol — the Garden Model, the Smart Wallet Architecture, the decentralized wealth engine. The clearest voices win the issue.

Angles
V
Chapters
Languages
IV
Accepted
Visuals
II+
Required
Points
XXX
On education
Chapter I
Contents

Five chapters. Pick the one you can teach.

An editorial table of contents — each entry a full dispatch on one corner of the protocol.

Contents
I

Garden Model

p.01

Everyone deserves a garden.

BLOK Capital reframes wealth as a cultivated ecosystem — where capital compounds like soil, strategies grow like crops, and community tends the yield.

§ Technical

The Garden Model composes modular vaults into seasonal strategies. Each vault exposes a uniform interface for deposits, yield accrual, and rebalancing, while the garden coordinator allocates across vaults based on on-chain signals and governance-set weights.

§ Use cases

  1. Long-horizon personal wealth gardens with programmable risk zones
  2. Community-curated treasuries that rotate strategies each season
  3. On-chain index products that compose garden vaults as building blocks
Plate IIllustrative
II

Smart Wallet Architecture

p.02

Accounts that think for themselves.

The SWA turns a wallet from a keypair into a programmable agent — with policies, recovery, session keys, and protocol-native automation baked in.

§ Technical

SWA is built on account abstraction primitives: a smart contract account validates user operations through a pluggable policy module. Bundlers submit signed intents; paymasters sponsor gas in the protocol token; session keys scope permissions by time, target, and value.

§ Use cases

  1. One-click strategy execution without managing nonces or gas
  2. Inheritance and multi-guardian social recovery flows
  3. Agent-delegated rebalancing inside tight policy bounds
Plate IIIllustrative
III

Protocol Architecture

p.03

A modular stack, not a monolith.

BLOK Capital separates concerns into vault primitives, strategy modules, oracle adapters, and governance — so every layer can evolve without forking the base.

§ Technical

The protocol is layered: (1) a vault kernel enforcing accounting invariants; (2) a strategy registry of audited modules; (3) an oracle layer normalizing price and risk feeds; (4) a governance surface mediating upgrades via timelock. Strategies plug in through a typed ABI, enabling isolated risk.

§ Use cases

  1. Auditable upgrades that ship without migrating user funds
  2. Third-party strategists publishing modules into the registry
  3. Permissionless composition of vaults inside other protocols
Plate IIIIllustrative
IV

Decentralized Wealth Management

p.04

Private banking, public rails.

Legacy wealth management hides behind relationship managers and opaque fees. BLOK Capital exposes strategy, performance, and cost on-chain — available to anyone with a wallet.

§ Technical

Every mandate is a vault with a published strategy, a public fee schedule, and streaming NAV. Managers earn performance fees enforced by smart contract; clients can exit atomically. There is no account minimum — only the unit size of a single share.

§ Use cases

  1. Retail-accessible portfolios previously gated behind six-figure minimums
  2. Real-time performance dashboards replacing quarterly PDFs
  3. Cross-border mandates settled without correspondent banking
Plate IVIllustrative
V

Financial Inclusion & Vision

p.05

Wealth, as a public utility.

The long arc of BLOK Capital: shrink the distance between capital and opportunity, so a student in Lagos and a steward in Zurich reach the same yield surface.

§ Technical

Inclusion is engineered, not decreed: unit economics that make micro-deposits viable, fiat on-ramps abstracted behind the SWA, and educational scaffolding that turns first-time users into informed participants — all coordinated through the same protocol used by institutions.

§ Use cases

  1. Dollar-denominated savings for users in high-inflation economies
  2. Community pools where small deposits compound through shared strategy
  3. Curriculum integrations where learning unlocks allocation rights
Plate VIllustrative
Chapter II
Evaluation

How entries are read.

Four axes, weighted and plainly stated.

Four axes
  1. I30%

    Educational Value

    Is the concept measurably clearer after reading?

  2. II25%

    Technical Accuracy

    Does it reflect the whitepaper — not marketing, not hype?

  3. III25%

    Creativity & Engagement

    Novel framing, strong hooks, visuals that earn the scroll.

  4. IV20%

    Community Impact

    Replies, saves, quote-tweets — signal from real builders.

Bars are scaled relative to the highest-weighted axis for legibility.

Chapter III
The articles

Six clauses. Read them once, then read them again.

Most disqualifications are preventable.

ArticlesSix clauses, strictly read
  1. Follow @BLOKCapital on X

    Entries from non-followers will be skipped.

  2. Retweet the contest announcement

    Must be the main pinned post.

  3. Tag @BLOKCapital and use #BLOKCapital

    Both are required in the root tweet.

  4. Include at least two visuals in your thread

    Diagrams, charts, or original illustrations.

  5. Align your thread with the BLOK Capital whitepaper

    Speculation welcome — fabrication isn't.

  6. Submit the thread URL via the official form

    Entries are only counted once submitted.

Chapter IV
Languages

Write where your audience already reads.

EnglishEN
EspañolES
PortuguêsPT-BR
FrançaisFR

Write in the language where your audience already reads.

Chapter V
Editors' notes

Two letters to the contributors.

The protocol has its documentation. What it needs from you is good writing.

Letter ITo the builders

Builders,

Architecture first, narrative second. Lead with the kernel — the vault invariants, the accounting primitives, the upgrade paths. Treat every claim as a surface that another engineer might have to audit, integrate against, or extend.

  • Reference ERCs, invariants, and security boundaries.
  • Ship at least one diagram of the data flow.
  • Cite the whitepaper section; link commits when relevant.
If a senior engineer reads your thread, they should know where to start contributing.

— The Builders

Letter IITo the creators

Creators,

Start from a human moment. Translate before you explain — every term earns its place. The protocol already has its documentation; what it needs from you is a version that reads the way a good essay does.

  • Open with a hook that reframes how wealth usually works.
  • Pair every claim with a concrete example.
  • Close with a line the reader will quote.
If a curious friend reads your thread, they should want to show it to someone.

— The Creators

From the Editors

Send us your best thread.

One angle. One thread. One link. The clearest voices go to print — not the loudest ones.

— The BLOK Capital Editors