Loading…
Transparency
We ship in public where it matters. Inspect the code, suggest fixes, and hold us accountable—without trusting a black box.
Commerce and community both require trust. Publishing source is how we earn it: you can diff our claims against the implementation, file issues when something drifts, and contribute improvements the same way you would any other project you rely on.
Privacy and commerce both require trust. Publishing source lets you verify what we claim—especially around AI, payments, and crypto. Repos may span multiple packages; we group them by surface area below. Swap links in your deployment via NEXT_PUBLIC_GITHUB_* env vars.
This is not a stunt—open repositories are how we invite review from security researchers, partners, and customers who want receipts. When you find a bug, open a PR or a ticket; we triage security issues separately from feature work.
Next.js storefront, checkout, membership, and customer-facing UI.
The marketing site, cart, crypto checkout, and account areas you interact with every day. This is the largest surface area—most of what you see in the browser is represented here.
On-chain programs, token logic, and integration contracts.
Money-moving code deserves the same scrutiny as the storefront. Programs for staking, rewards, and checkout integrations are published so wallets and auditors can verify invariants.
Storefront AI chat, Venice integration, RAG pipeline, and admin tooling.
The same surfaces you use in production—streaming chat, character routing, retrieval over your data, and operator tools—are what we ship in the repo so you can diff behavior against claims.
Native apps and mobile experiences when published — track the repo for releases.
When mobile clients ship, their source lands here first. Follow releases for TestFlight / Play tracks, deep links into the store, and wallet connect flows that match the web.
Clone the repo, run the build, and compare network behavior to what you see on the live site. If something is unclear, open a discussion or issue—we would rather fix the docs than leave ambiguity in place.
We welcome focused PRs: docs, tests, accessibility, and performance wins all count. For larger changes, open an issue first so we can align on scope and avoid duplicate work.
Inspired by teams who put privacy first and ship in the open source. — we’re building the same muscle for culture and crypto.