An open group learning, building and sharing value onchain.
Learn how onchain systems work, find useful tools and turn understanding into skills. Open knowledge, shared and improved together.
Onchaination is an open, multichain, multilingual knowledge and contribution hub, built in public. It welcomes curious people and makes the same knowledge available to agents.
Choose the path that matches what you want to do. Each has an example to explore or improve:
| Path | Purpose | Example |
|---|---|---|
| 📚 Learn | Understand something | What happens when you send a transaction? |
| 🛠️ Tools | Use an interface | Network fee calculator |
| 🎯 Strategies | Pursue an outcome | Make your first transfer easier to verify |
| ⚡ Skills | Perform a procedure | Check a transaction on a block explorer |
Start learning · Search · Contribute · Join Telegram
More examples for each path
- Learn explains concepts and mechanisms: wallets, stablecoins, AMMs, lending, collateral, liquidation, and account abstraction.
- Tools covers useful interfaces: wallets, protocols such as Aave and Uniswap, explorers, calculators, dashboards, and libraries.
- Strategies combines knowledge, tools, and skills toward goals such as borrowing without selling, managing liquidation risk, or providing liquidity. These pages describe assumptions, risks, and trade-offs, not promises of returns.
- Skills gives concrete procedures: send USDC, read a smart contract, sign a message, or check a health factor. A skill should be clear enough to follow, test, and reuse.
Users and contributors are not separate groups. Onchaination should grow from real questions, real usage, and real contributor experience. If something is missing, confusing, outdated, or wrong, improve it.
Make the smallest useful contribution you can.
A useful contribution might be a correction, a clearer explanation, a tool you use, a strategy, a skill, a translation, a question that exposes missing knowledge, or a review of someone else’s work.
Before publishing a top-down list of “best” tools, ask what people actually use, recommend, struggle with, or want to understand.
Understand before influence.
The usual flow is edit Markdown → open a pull request (PR) → review → merge. Once publishing is configured, merged changes deploy automatically. See CONTRIBUTING.md for how to make your first contribution.
The four paths organize knowledge by purpose. Tags connect related topics across them, while each section-and-folder path supplies its knowledge identity:
- path without locale = knowledge identity — for example,
learn/transaction, shared by every translation. - locale prefix = language context — English is unprefixed; other supported languages prefix the same path.
- tags = topic graph — shared topics that connect items across paths.
For example, one topic can lead you from learning how AMMs work, to choosing a DEX, to understanding a liquidity strategy, to following a skill to create a position.
Knowledge lives in Markdown: simple text files that remain useful when read directly on GitHub. GitHub is the canonical record of contribution history; the website renders and connects that knowledge for discovery and use. Humans and agents share the same four paths and source material.
Content is chain-neutral, with network differences named explicitly. Current examples cover Ethereum and Solana where relevant, and other chains are welcome. Translations are versions of the same item, and English is the required canonical source representation.
Onchaination is an open group learning, building and sharing value onchain.
Knowledge should be accessible, inspectable, and portable.
Onchaination is chain-neutral and multichain.
Technologies should be evaluated by what they enable, not by which ecosystem they belong to.
Understanding is most useful when it can be applied.
Questions, corrections, tutorials, tools, experiments, strategies, code, and experience can all create value for someone else.
Do not introduce infrastructure, governance, token economics, leaderboards, automated reward systems, or other abstractions before there is a concrete need.
Important decisions, contributions, and technical rules should be understandable and inspectable.
Identity belongs to the participant. A public key is its root; wallets and social accounts are claims about it. Claims must be proven when attribution or rewards depend on them.
GitHub records contributions. Useful work by humans and agents deserves attribution; rewards may recognize that work but are never promised for every contribution. Identity and rewards must remain optional for learning and contributing.
Onchaination is not tied to one blockchain, a DAO by default, a token project, an investment club, or a content company with creators on one side and an audience on the other. It is an open group learning from each other, building useful things, and sharing value onchain.
v0.1 — knowledge first. The current implementation is Phase 1 / knowledge foundation.
It includes foundational context across Learn, Tools, Strategies and Skills, with localization support.
Identity, passkeys, verified claims, attribution infrastructure, rewards, and reward destinations are later work, not shipped features. SPEC.md’s implementation order separates the current foundation from the Phase 2 design.
Rewards may initially be manual; points, leaderboards, automatic payouts, reputation algorithms, and an Onchaination token are not required.
Useful knowledge should ship before identity infrastructure needs to be complete. The aim is the smallest useful network around useful knowledge: one explanation, one tool, one strategy, one skill, one contribution at a time.
The canonical repository is github.com/onchaination/hub.
hub/
├── README.md
├── CONTRIBUTING.md
├── SPEC.md
├── learn/
├── tools/
├── strategies/
├── skills/
├── web/
├── .onchaination/
└── .github/
The four knowledge directories stay at the top level. web/ renders them; cloud/ is reserved for Phase 2 identity, verification, and attribution services and does not exist yet. See SPEC.md for the architecture and web/README.md for the code map.
The Phase 2 identity design uses a participant-controlled public key, with passkeys / WebAuthn as the default for humans. External accounts are claims, self-declared until proof matters. Its attribution path is contribution / referral → Onchaination ID → reward destination, without making a chain or login provider the identity authority.
Install Node.js 24 or newer, then run from the repository root:
npm ci
npm run devOpen http://localhost:4321. Markdown changes reload the site. No environment variables, API keys, database, or cloud account are needed.
To check and preview the complete site, including search:
npm run check
npm test
npm run build
npm run previewEach folder is one stable item, with one Markdown file per language.
English (en.md) is required and supplies shared tags, level and related paths. Translations are Markdown files beside it. The supported interface languages are en, uk, es, pt, de etc.; adding another language requires registering it and supplying UI strings. Missing article translations are allowed: the selected interface remains localized while the article falls back to English. Page lists and search retain the complete knowledge base.
English uses /learn/transaction/; another locale, for example Ukrainian, uses /uk/learn/transaction/. Stored translation sources remain directly readable, for example /learn/wallet/uk.md. Stored translations have self-canonical URLs and genuine language alternates; fallback views canonicalize to English. Optional browser Auto-translate starts off, changes presentation only, and never replaces repository translations. See how to translate an item.
- Markdown and agent access: static HTML, clean
.mdroutes,/llms.txt, widgets, and Learn with AI context offer interfaces over the same canonical knowledge. The fee widget has separate ETH and SOL calculations. - Browse and search: Tags connect related topics, while levels group knowledge for beginner, intermediate, and advanced users. Pagefind generates the static search index at build time, so use
npm run previewafter building to test search. - Publishing: the GitHub Actions workflow validates pull requests and can deploy the static site after GitHub Pages and DNS are configured. See publishing setup.
Knowledge belongs in GitHub. Discussion belongs in Telegram: updates and the forum.
For page discussions, a maintainer must link the updates channel to @onchaination_chat and post each page’s clean English URL once. The separate forum remains @onchaination_group. Every language view passes the same explicit discussion URL derived from its locale-independent path, independently of its SEO canonical. Readers can then load the shared embedded thread; Telegram holds the comments, with no comments stored in Markdown or a separate database. Local builds do not configure channels or publish posts. See Telegram setup.
onchaination.org · GitHub · Telegram · X