Wen Open Lab · open integration

Wen Open Lab: Open IntegrationStage 0 · Roadmap

English · Italiano · 中文 · 한국어

Wen space coin over Solana
From story to tools: the Lab begins

Watch: the Lab in 38 seconds

Wen checks a receipt the way a machine would, then the six models and the 37 checks behind them. Everything in the video is open code you can run yourself.

More Wen videos: all Lab videos · YouTube channel @wen-coin.

The player loads from YouTube only after you press play.

Knowing what Wen is was the first step. The Lab is the second: we take the open tools behind Wen — the WNS token layout, Solana Token-2022 and Solana Pay — and build free, working models that a developer, a shop, a fintech team or a bank can study, test and reuse. Everything is open, step by step, in public.

Why this exists

The almanac explains Wen in depth: the poem, the airdrop, the WNS standard, the link with Jupiter and Solana. But description alone is not utility. Utility starts when someone can take a model, run it, check it and build on it. The Lab does exactly that, and does it in the open, so that the value of Wen's technical heritage is shared freely rather than locked away.

Where it applies

SphereWhat the Lab givesStage
B2C e-commerceTamper-proof receipts and warranty cards as NFTs, payment links and order confirmation1, 4
Creators and marketplacesRoyalties enforced by the token itself, not by a platform's goodwill2
B2B tradeSettlement with a built-in fee, approved counterparties only, mandatory invoice number3
Acquiring and fintechA technical bridge from on-chain payment to the merchant's order system, plus a cost and speed model4, 5
EveryoneA clear map of benefits, limits and next steps★

The roadmap, built in the open

  1. 0 · Roadmap and rules. This page: purpose, spheres, open use policy, verification log. live
  2. 1 · Receipts and warranty. A Token-2022 NFT with the WNS layout: proof of purchase without personal data, optional soulbound warranty. 12 checks passed
  3. 2 · Creator royalties. Read which program enforces royalties on an NFT and transfer it so the hook runs. hook read verified
  4. 3 · B2B invoices. Transfer fee, approved counterparties, mandatory invoice memo. 9 checks passed
  5. 4 · Payments bridge. Solana Pay link, payment watcher, validation, webhook to the shop. link verified
  6. 5 · Simulator. Compare card acquiring and on-chain payments with your own numbers. interactive
  7. ★ · Benefits and use. Who gains what, where it fits, and where it does not. live
  8. 6 · Devnet: repeat it yourself. A published script runs Models 1 and 3 on public devnet and prints explorer links. Anyone can repeat it with a new, empty wallet. ready to run
  9. ✓ · Trust chain. Every key claim with its status and sources: verified, reported, opinion, unverified or conflicting. live
  10. ✎ · Ten walkthroughs. The Lab in plain words: ten "did you know" walkthroughs with key code, tests and limits; new Models 5 (receipt verifier) and 6 (token inspector). 37 checks passed
  11. 7 · Wen Counter. A free point of sale in the browser: Solana Pay QR, receive-only, wallet as identity, a savings ledger, a downloadable kit. 57 checks passed
  12. 7.1 · Receive-only safety. The protocol, the solar-system picture of the legal side, till wallets with daily collection, and every check. live

Verification log

Models 1–6 are executed inside LiteSVM, a local Solana virtual machine that runs the real SPL Token-2022 and Memo programs, without network access and without real funds. The negative cases matter as much as the positive ones: a soulbound receipt must refuse to move, a payment without an invoice memo must fail. Output of the last run (November 9, 2026, 41 checks):

PASS  M1 receipt minted (soulbound=true)
PASS  M1 supply is exactly 1, decimals 0, mint authority removed
PASS  M1 metadata inside the mint: name, order hash, warranty date  — warranty_until=2027-10-10
PASS  M1 buyer holds the receipt
PASS  M1 soulbound receipt cannot be transferred  — rejected by Token-2022
PASS  M1 nobody can mint a second copy
PASS  M1 receipt minted (soulbound=false)
PASS  M1 supply is exactly 1, decimals 0, mint authority removed
PASS  M1 metadata inside the mint: name, order hash, warranty date  — warranty_until=2027-10-10
PASS  M1 buyer holds the receipt
PASS  M1 transferable receipt can be resold or gifted
PASS  M1 nobody can mint a second copy
PASS  M3 settlement mint created (fee 0.25% cap 50, frozen by default)
PASS  M3 seller account requires an invoice memo
PASS  M3 issuer funds the buyer account
PASS  M3 payment WITHOUT an invoice memo is rejected  — Program log: Error: No memo in previous instruction required for recipient to receive a transfer
PASS  M3 payment to a NOT approved company is rejected (account frozen)  — Program log: Error: Account is frozen
PASS  M3 invoice INV-2026-0042 paid with memo to approved company
PASS  M3 invoice number is recorded on-chain (memo in logs)
PASS  M3 seller received amount minus fee; fee withheld for the platform  — received 997.5, fee 2.5
PASS  M3 fee cap works (fee on 100,000 is 50, not 250)
PASS  M3 fee rounds up like Token-2022 (401 base units: fee 2, not 1) and the payment goes through
PASS  M3 expectedFee equals the Token-2022 fee formula on edge amounts  — 10 amounts
PASS  M3 a WRONG invoice number still passes the on-chain memo rule (known limit: reconcile off-chain)
PASS  M3 reconciliation accepts the right invoice and rejects the wrong one
PASS  M2 NFT mint created with a transfer hook
PASS  M2 hook program read from the mint = WNS royalty distribution  — diste3nXmK7ddDTs1zb6uday6j4etCa9RChD8fJ1xay
PASS  M4 payment link round-trips: recipient, amount, token, reference, memo  — solana:WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk?amount=10…
PASS  M4 every order gets a unique reference
PASS  M5 genuine soulbound card passes every check  — 8 checks
PASS  M5 a different order is rejected (hash mismatch)  — order hash matches the buyer's order
PASS  M5 a card from another issuer is rejected  — issued by the expected shop (update authority)
PASS  M5 an expired warranty is rejected  — warranty still valid
PASS  M5 a wallet that does not hold the card is rejected  — held by the expected wallet
PASS  M5 a transferable (not soulbound) card is flagged  — soulbound: NonTransferable extension present
PASS  M6 classic SPL mint: no extensions, both authorities reported  — Mint authority is set / Freeze authority is set
PASS  M6 Token-2022 mint created with permanent delegate and transfer fee
PASS  M6 permanent delegate is flagged for holders
PASS  M6 transfer fee is read from the mint (1% capped)  — PermanentDelegate, TransferFeeConfig
PASS  M6 removed authorities are reported as none
PASS  M6 a wallet address is refused, not parsed as a mint

ALL CHECKS PASSED

Two real pitfalls were found while building, which is exactly why the rule is "verify your own model": the npm package @wen-community/wen-new-standard has been removed as malicious, and recent versions of @solana/spl-memo point to a different memo program than the canonical one Token-2022 checks. Both are handled in the code.

Run it yourself

# get the files from lab/code/ (package.json, tsconfig.json, src/, test/)
npm install
npm run typecheck   # TypeScript, strict mode
npm test            # local Solana VM, no network, no real funds

For devnet: create a wallet with the Solana CLI, request devnet SOL, then set KEYPAIR and optionally RPC_URL before calling the send functions in each file. Start with a fresh, empty wallet.

Background reading

Wen in pictures

Wen cat in open space
Open by default
Wen star of open code
Every stage is public
Wen UFO coin explorer
Exploring real use cases
Wen new standards, open protocol
Built on open standards
Wen energy for builders
Energy turned into utility

Where Wen fits in this model

Wen is the reason this Lab exists. The WEN story brought WNS, the Token-2022 standard behind these models, to a mass audience (the fungible WEN token itself uses the original SPL Token program). Each model below shows an optional, honest place for WEN: as a payment or tip option, a loyalty reward, or simply the community signature of the work. The rails themselves are open and work with any token.

The Wen thread: one contract, everywhere

Every model in the Lab is free and open, and every one carries the same signature: the $WEN token contract. Copy it, repeat it in your own docs, and always verify it against an explorer before use.

WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk

Check: Solana Explorer · how to find the contract ID

Open use policy

  • Free and open. All Lab code is released under the Apache License 2.0, the same license as the Wen Program Library. Use it, change it, ship it, commercially or not; keep the license notice.
  • Open tools only. Built on public, documented tools: Solana SPL Token-2022 (Token Extensions), the token layout of the Wen New Standard (WNS), Solana Pay, and LiteSVM for local testing.
  • The rule: always verify your own model. Run the tests, start on devnet, read the official documentation, review every account and amount, and get an independent audit before any mainnet use. A model that is not checked is not a model, it is a guess.
  • Not audited, not advice. These are educational examples. They are not financial, legal or tax advice, and not a licensed payment or banking product. Payments, stablecoins and acquiring are regulated activities in most countries.
  • Security. Never paste a private key into a website. Do not install the npm package @wen-community/wen-new-standard: npm removed it as malicious. Build from official sources.

Spoken by Wen, for the community. More in our editorial and data policy.

Wen Open Lab · roadmap · all code · Wen Program Library on GitHub

Wen the kitten in a white space suit holds a glowing blue blade in a desert under two suns
Wen sets out with an open toolkit: six Token-2022 models with tested code, free for everyone.