Shielded Documentation
Shielded is a standardized, on-chain pledge that makes token launches legible. It creates a public, verifiable record tied to a creator and a mint, so anyone can check it.
What is Shielded?
A simple on-chain commitment that anyone can verify.
Shielded stores a pledge account derived from creator + mint (deterministic PDA). This makes it globally discoverable and verifiable.
Every pledge has a shareable proof page /p/<creator>/<mint> that reads on-chain state and shows what the creator committed to.
You get a credible, easy-to-share signal: “this launch has a verifiable pledge”. That increases trust, reduces confusion, and helps your community verify facts fast.
How to use it (Creator workflow)
The happy path for a token creator.
- 1) Create pledge
Go to /app, paste the mint, pick pledge settings, connect your wallet, and create.
- 2) Share proof
You’ll get a proof link like /p/<creator>/<mint>. Share it on socials / Telegram / website.
- 3) Anyone verifies
Users, bots, and UIs can verify the pledge by reading the PDA on-chain. No “trust me bro”.
Create the pledge before heavy marketing. The earlier you commit, the stronger the signal.
Proof links
What users see on /p/<creator>/<mint>.
- • Program ID
- • PDA (derived pledge account)
- • Pledge type
- • Duration / Max sell (if configured)
- • Metadata hash + timestamp
The proof page will show Not shielded and can offer a CTA to “Shield this token” which brings you back to the create flow with prefilled creator + mint.
Integrations
Where Shielded fits in a real launch ecosystem.
Shielded can be integrated into existing launch flows (pump.fun / Bags). The main idea: the creator commits a pledge and the UI can display / enforce / verify it.
Any bot or explorer can verify the pledge directly by PDA + program ID. This is how Shielded becomes “infrastructure”, not only a website.
Pre-launch shielding (commit before listing), composable verification badges, and partner launcher integrations that read pledge state by default.
Monetization
How Shielded can generate revenue in a user-aligned way.
You can charge a small fee for premium pledge types, advanced metadata, or “verified creator” features. The free tier can remain fully usable.
Launchpads / tooling partners can pay for deep integration, analytics, or a dedicated verification endpoint / badge program.
Examples: branded proof pages, team dashboards, pledge history, alerting, and automatic posting / social templates.
The more UIs and bots verify Shielded by default, the more creators want it. Monetization should amplify trust — never reduce it.
Monetize upgrades and distribution, not fear. Shielded should feel like a trust primitive, not a paywall.
FAQ
Common questions from creators and users.
No. Shielded is a verification layer. It complements launchpads by making commitments easy to read and verify.
The pledge ties to a creator wallet. If a pledge exists, it’s verifiable on-chain. UIs should always show the creator address clearly.
The pledge is a public commitment. If you add updates later, do it transparently (versioning / revocation policies can be added).
Proof page, bots, and explorers can read the pledge PDA and decode the fields. That’s the whole point: open verification.