Layer3: onchain activations, CUBEs, and Builder growth

Layer3: onchain activations, CUBEs, and Builder growth. Layer3 is a consumer gateway (wallet, discover, trade, stake, earn) plus a Builder surface for protocols to ship no-code Activations — guided, verifiable onchain tasks with rewards — and to mint CUBEs as credentials for completed work.

Click to zoom

Two audiences, one stack

Marketing claims (as of 2026 site copy) sit in the multi-million user / hundreds-of-millions actions range across 40+ chains and 500+ apps — treat numbers as marketing; verify current stats on the product and docs before quoting in a grant or IR deck.

Activations

An Activation is Layer3's unit of growth work: a structured sequence of onchain (and sometimes offchain) steps — bridge, swap, stake, mint, follow — that a wallet completes for rewards (tokens, XP, CUBEs, perks). Docs describe them as action–reward units: attention and verified usage, not pure social points.

• No-code builder for teams (templates, reward budgets, chain targets).
• Verification layer that only unlocks claims when steps succeed onchain.
• Distribution across a large multi-chain set (product cites 50+ for rewards).

DevRel use: ship a first-week “learn the product” path that ends in a real mainnet action, not only a Discord role.

CUBEs

CUBEs — Credentials to Unify Blockchain Events — are onchain credentials that record completed quest activity. Open-source contract work lives under layer3xyz/cubes: ERC-721-style credentials attesting multi-chain, multi-tx, multi-dapp journeys.

Quest lifecycle (simplified)
  initializeQuest(...)     // emit quest metadata / communities
  user completes steps     // verified off product + onchain
  signer → EIP-712 auth    // mint authorization
  user → mintCubes(...)    // credential onchain
  events → indexers / perks / future eligibility

CUBEs are the durable identity layer under rewards and airdrop-style targeting — closer to “proof of journey” than a points balance alone.

L3 token and staking

L3 is the network token users stake for boosted rewards, governance, and support messaging. Tokenomics, protocol, and audit detail are pointed at Layer3 Foundation docs from the main guidebook — use those as source of truth for supply and governance, not the marketing homepage.

Builder playbook (protocol teams)

1. Open Builder and create a Space for your brand/protocol.
2. Design an Activation: required txs, chain(s), success criteria, reward inventory (token budget, CUBE, XP).
3. Prefer mainnet actions that match real product loops (first swap, first deposit) over empty faucet spam.
4. Fund rewards; set claim windows; publish.
5. Read completion and wallet analytics; iterate difficulty and copy.
6. On Solana specifically: confirm CUBE mint / activation gas UX and any “CUBEs on Solana” style journeys in-app before promising free mints.

Solana angle

Layer3 is omnichain. Solana shows up as a first-class destination for activations and CUBE mint journeys (e.g. in-app “CUBEs on Solana” style content). For Solana DevRel, treat Layer3 as a distribution and credential channel next to bounty boards and in-product tutorials — not as a replacement for your own docs or Anchor templates.

Related internal reads: Torque MCP incentives, Gibwork bounties.

Limits

• Quest farms and sybil noise are industry-wide; design activations with economic or skill friction.
• CUBE mint and reward claims can require gas / inventory — document costs for users.
• Builder is primarily product UI; do not assume a full public REST “create quest” API without checking current Builder/Intel docs.
• Multi-chain claims need careful wallet UX (wrong network = support load).

People and links

Resources

• Layer3 docs (platform + builder)
• CUBE contracts
• layer3.xyz