
The Ustadept Foundation is a community-led, non-profit-minded initiative that exists to protect the core promises of Ustadept and USTA:
Keep it verifiable.
USTA itself is intentionally simple: a fixed-supply ERC-20 on Ethereum, minted once at deployment, with no “owner mint / emissions” levers and no profit promises. That simplicity is not a lack of ambition — it’s a deliberate safety feature.
The Foundation’s job is to make sure the ecosystem around that simple token stays practical, truthful, and hard to impersonate.
Why the Foundation exists
Crypto projects don’t usually fail because the code compiles. They fail because:
We created the Foundation to counter those failure modes with a single principle:
Proof over statements.
USTA already commits to that culturally (useful, verifiable, human, open, reliable). The Foundation is the operational layer that enforces it.
What we provide
Ecosystem support (open-source, docs, education)
We support USTA and Ustadept through:
Open-source development and maintenance
Documentation that prioritizes clarity over marketing
Educational materials that teach verification (how to check links, contracts, deployments, and releases)
This isn’t “community theater.” The repo is the work surface, and evidence lives in commits, diffs, and on-chain facts.
Brand & user-safety defense (anti-scam by design)
USTA is easy to imitate. So we make “official” extremely strict:
If a link isn’t listed in docs/OFFICIAL-LINKS.md, treat it as unofficial.
That file is not decoration — it is the community’s safety rail:
We also explicitly warn about phishing/impersonation as a top ecosystem risk.
A public trailmap (coordination without closed doors)
The Foundation publishes and maintains a public coordination trail:
“Roadmaps” often become vapor. A trailmap is different: it’s a visible, auditable path made of issues, milestones, PRs, and tagged releases.
In practice, this means:
Our operational standards
Official references must be boring and explicit
The Foundation maintains a single source of truth for what is “official.”
This is how we prevent “trust me bro” from becoming policy.
Verification is part of the release, not an afterthought
USTA’s tooling reflects a bias toward safe operations. For example, the mainnet deploy script includes hard guards and requires explicit confirmation before deployment.
This is the mindset we keep across the ecosystem: fewer surprises, fewer foot-guns, fewer “oops.”
Security is a process, not a vibe
If you find a vulnerability, the Foundation expects responsible disclosure and provides a clear reporting path:
Email: ustadept@ustadept.com
Subject: [SECURITY] USTA Token Vulnerability Report
Scope includes smart contracts and deployment/verification tooling, and no guaranteed timeline is promised (honesty beats fake deadlines).
What the Foundation is not
To keep expectations clean:
How you can participate
Builders
Educators & translators
Community defenders
Official references
These are the official references published by the project:
Canonical token contract (Ethereum mainnet, USTA v1):
The line we’ll keep repeating
USTA is a meme/community token — but we don’t run it like a joke.
We run it like a craft.
Motto: USTA bilir.