Learn / Why

Less “trust the website.” That’s it.

This does not make prices safer. It makes statements checkable — if a team actually uses it. Lock (local) → Fingerprint (public) → Check (anyone). No token. No wallet required to check.

Nothing here makes a coin a good buy. Coins can still dump or vanish. This only answers: “is this file the same one they locked before?” A liar can still lock a lie. Studio is practice — not an official vault.

What’s broken today

People are asked to trust a website or a chat:

A roadmap PDF that can be swapped overnight
A screenshot that says “liquidity is locked”
A Telegram promise with nothing to check later
A “team vault” nobody can re-check on their own
Quiet edits after the pump

Hosts change pages. A public fingerprint from last week does not.

What we add

Lock (local)
The team locks the real file on a computer (letter, wallet list, terms). Other people don’t see the words unless they have the phrase. Studio is practice — not that official vault.
Fingerprint (public)
Same day, they post a tiny QAL stamp that means “this exact locked file.” The community keeps the file + a proof slip. There is now a public moment: this file, this time.
Check (anyone)
Open the file → make the fingerprint again → compare. If the website swaps the PDF, the old file still either matches or it doesn’t. No token. No wallet. You don’t need their server.
Changes leave a scar
Need a new story? Post a new version. The old one stays visible as “replaced.” Want to take it back? Mark it taken back. People can still read: they said A, then they moved to B.

What teams can lock

Use	Why a fingerprint helps
Pre-launch “we won’t mint more” letter	Locked before launch. Later edits need a new file and a visible “replaced” trail
Team wallet / multisig disclosure pack	People can prove the pack didn’t change — without posting every name to the whole internet
LP / treasury process document	Does not lock coins on-chain. It does prove the document they pointed to didn’t quietly change
Incident postmortem vault	After a mess, lock the write-up and stamp it so it can’t be quietly rewritten
Partnership / collab claims	Both sides can lock their own notes. That’s process — not magic trust

Side by side

Website / Telegram only

Editable after the fact
Hard to prove “same file as launch day”
You must trust the host

Locked file + public fingerprint

Fingerprint fixed in a public record
Anyone can check on their own computer
Take-back / replace is visible, not silent

What still does not get fixed

Bad tokenomics
Insider dumps
Fake social proof
Someone who locks garbage on purpose
A lost phrase (locked means gone if lost)

A public stamp is not an ID. A scammer can lock a lie and stamp the lie. What they can’t do as easily is swap which locked lie after people saved the file.

How the pieces fit

QEV = locker on your computer.
QAL = public stamp + history for that locker.
Solana = shared place the stamp is written.
You = the person who actually checks. No wallet required.

Official QAL program: 6cN9gD8LBqkEUhvT4LibnbBgXdCHeC5AgqvcFQQTNvnR

Abandoned, compromised id — not official: AFGfcVVNtucEjJXvL7QSrRLdujr7yWqnC8FdhP7rpixf

The point is not “safe coin.” It’s promises you can check in a market that runs on editable vibes.

Practice a lock Play the game Help build it Check a file