Fees route back. Receipts over promises.
TrustLayer is a transparent reward layer for Solana meme launches. It turns fee flow, technical checks, Founding 100 receipts, and payout proof into a public product buyers can inspect.
First launch, first receipts.
For the first $TrustLayer token launch only, the first 100 unique wallets that buy at least 1 SOL worth of tokens and hold for at least 10 minutes can earn Founding Receipt status.
A public early-holder list for the first wallets that support the launch and still meet the rules at snapshot time.
Qualification is based on cumulative buy volume from the wallet during the launch window.
The wallet needs to keep the qualifying position through the 10-minute hold check.
Team wallets, treasury wallets, obvious duplicate entries, and ineligible wallets can be excluded.
The wallet must still hold $TrustLayer at the announced snapshot time to keep Founding Receipt status.
Qualified wallets can be shown on a public Founding 100 page with receipt number and status.
Public recognition as one of the first 100 qualifying wallets.
Eligible wallets can receive a defined boost in the first reward cycle. Payouts remain variable.
Founding Receipt wallets can receive priority for future TrustLayer allowlists or beta features.
One page buyers can actually trust.
Every boarded token gets a live dashboard showing vault balances, payout logic, verification state, reward cycles, and holder eligibility.
$TRUSTDEMO
If things go wrong, holders have a defined backstop.
Dev dump threshold, liquidity removal, authority abuse, stopped routing, or emergency review.
Wallets holding before the event, excluding disclosed team wallets and obvious farming clusters.
Reserve matures into holder bonus rewards, ongoing reserve, liquidity support, and a small success fee.
Amount held x time held = stronger payout weight.
reward_weight = average_balance x hold_time_multiplier
holder_payout = wallet_weight / total_weight x holder_pool
current_holder_pool = 18.42 SOL x 70% = 12.894 SOL
No launchpad required. Board existing tokens first.
- Register tokenSubmit mint, dev wallets, socials, and requested split.
- Create vaultContract config defines reward, protection, and platform shares.
- Go publicDashboard, verification status, badge, and payout history become shareable.
Every cycle should leave a receipt.
The proof page turns routed fees into a public manifest: fee inflow, holder payouts, protection reserve, platform fee, formula inputs, and the manifest hash in one place.
$RECEIPTS demo
Loading the public payout manifest.
Wallet-level payout accounting.
TrustLayer verifies specific technical and operational requirements. It does not guarantee price, profit, liquidity, reimbursement, or investment safety.
Scan the token before the badge goes live.
TrustLayer verification starts with the mint itself. The scanner rejects hidden token controls, surprise extensions, live authorities, transfer traps, and fee rerouting inside the token.
Paste a Solana mint address.
No mint checked yet.
Paste a mint address to check it against the hosted TrustLayer scanner API.
Fee routing not checked yet.
Run a mint scan to check the Pump.fun fee-sharing route status for the same token.
A public board for every token using the standard.
The directory is the social proof layer: traders can scan which projects are funded, which are paying, and which lost verification before they buy.
The badge has to mean something.
TrustLayer should never be a logo anyone can rent forever. Verification is live, rule-based, and revocable when the fee flow or project behavior breaks.
Dashboard active
Token data is visible, but reward routing has not earned verified status yet.
Vault funded + payout flow active
Fees are entering TrustLayer and reward cycles are publicly tracked.
Reserve active + dev wallets disclosed
Protection reserve rules are configured and project wallets are visible.
Trust signal removed
Routing stopped, suspicious wallet behavior appeared, or project rules were broken.
Built so incentives are visible.
The first contract does not need to replace pump.fun. It makes the fee flow auditable once a project routes funds into TrustLayer.
Contract vault split
Routed fees are split by public rules into holder rewards, protection reserve, and TrustLayer revenue.
Off-chain holder math
Backend indexing handles balances, time held, caps, and scoring so the chain is not wasted on heavy math.
On-chain receipts
Payout cycles, vault deposits, and batch hashes are logged so users can verify the system did what it said.
Quality scores
TrustLayer separates real reward flow from circular deposits, unclear fee claims, and creator extraction.
Launch on Pump.fun. Route fees. Verify on TrustLayer.
This is the beginner path from an empty wallet to a public TrustLayer receipt: create the coin, route Pump.fun creator fees to the TrustLayer wallet, lock the route where available, then publish evidence buyers can inspect.
Use the wallet that will create the token. This wallet should be one you are comfortable disclosing later as the project creator wallet.
Enter the token name, ticker, image, description, and socials. After the coin is created, copy the token mint address and the Pump.fun launch page link.
On the token's Pump.fun creator controls, open the fee-sharing or creator-fee settings for that specific coin. This is where the creator-fee recipient is changed.
Paste the TrustLayer project wallet shown in onboarding and set it as the 100% recipient of Pump.fun creator fees. Save the change before moving on.
After the recipient is correct, revoke fee-sharing admin access if the option is available. If the route cannot be locked, TrustLayer marks that risk clearly.
Paste the token mint, Pump.fun link, project socials, creator wallet, and fee-route evidence into TrustLayer onboarding.
TrustLayer checks token controls, blocked Token-2022 extensions, mint/freeze authority, the configured fee wallet, the 100% route, and the admin-revoked status.
When the checks pass, share the TrustLayer receipt page. Buyers can see the fee route, vault inflows, payout logic, and verification status in one place.
Token name, ticker, project image, launch description, public socials, token mint, project wallet list, intended split, and access to the fee-sharing setup.
Token controls, blocked extensions, disclosed wallets, 100% fee route recipient, revoked admin status, vault configuration, manifest status, and badge eligibility.
A public project page with scanner results, vault balances, payout formula, cycle receipts, reserve accounting, and warning or revoked status if rules break.
Ask TrustLayer before you trust a launch.
Ask product, scanner, onboarding, reward, and Founding 100 questions. The assistant is constrained to TrustLayer context and should not provide trading advice or price predictions.
Fast answers from the product docs.
Use this for basic product education: how fee routing works, what the scanner checks, how Founding 100 works, and what a verified receipt means.
What is TrustLayer?
TrustLayer is a contract-backed reward and proof layer for Solana meme coin projects. It tracks routed fees, vault splits, token safety checks, payout manifests, and verification status.
Does TrustLayer make a token safe?
No. TrustLayer verifies specific technical and operational requirements. Meme coins remain speculative, liquidity can move fast, and users can lose money.
How do holder payouts work?
Routed fees are split by public rules. Holder payouts are calculated from eligible balance and time-held snapshots, then published in a cycle manifest.
Why does time held matter?
Reward weight uses average balance and a hold-time multiplier, so wallets that hold more for longer can receive a stronger share of the holder pool.
What is the protection reserve?
It is a visible reserve bucket funded by routed fees under the project split. It is not an insurance policy or guaranteed reimbursement.
What if there is no rug or failure event?
Reserve handling is project-configured and public: keep building the reserve, run a bonus holder cycle, support liquidity, or follow a defined success split.
What does the badge check?
No live mint or freeze authority, no blocked Token-2022 controls, no hidden hooks, disclosed project wallets, visible routing, vault proof, and payout status.
Can a project lose verification?
Yes. Stopped routing, unsafe token controls, undisclosed wallets, or broken proof flow can move a project to warning or revoked status.
Do traders need to log in?
No. Public dashboards and manifests are readable without an account. Wallet connection is only needed for actions that require signing.
How does a dev board a token?
Create the coin, set the TrustLayer wallet as the fee-sharing recipient, revoke admin access, submit the mint and project wallets, pass checks, then publish the dashboard and badge status.
Can a dev stop routing fees later?
A TrustLayer verified route requires the expected recipient allocation and revoked admin status. If the route is not locked or breaks, the project should not stay verified.
Is this a full launchpad?
The first phase is a pre-launchpad layer for existing launches. A full launchpad can come later after the proof layer is reliable and battle-tested.
Free to start. TrustLayer earns from real activity.
Early projects can apply for no-upfront-cost onboarding. Platform fees come from routed inflows, not from charging builders before they prove demand.
Manual approval, higher routed take-rate, public dashboard, and badge status.
Lower routed take-rate after the first rollout, with the same public proof standards.
Featured placement, custom splits, KOL launch coordination, and priority support.
Board a token without changing its code.
First rollout is invite/manual approval so clones and low-effort copycats do not dilute the standard before the contract workflow is live.