Community and learning¶

Use these links to ask questions, follow project updates, learn from examples, and contribute corrections. Public chat and third-party content can be wrong or outdated; verify technical advice against current versioned documentation and source code.

Official project sources¶

• Koinos website — project information and official links.
• Koinos documentation — published guides and references.
• Koinos GitHub organization — source repositories, releases, and issue trackers.
• Koinos Docs repository — documentation source and contribution history.

Discussion channels¶

• Koinos Telegram — public community discussion.
• Koinos Discord — community and developer discussion.
• Koinos on X — project announcements and links.

No moderator or contributor should ask for a recovery phrase, WIF, or private key. Do not treat a direct message as proof of identity. Reproduce technical advice on a test account or test network before applying it to valuable assets or production infrastructure.

Articles, videos, and learning paths¶

• Koinos YouTube contains project presentations and tutorials.
• Koinos Network on Medium contains project articles and announcements.
• Getting Started is the recommended path for new users.
• Interacting with Koinos covers wallet, API, and transaction workflows.
• Smart Contracts covers contract development.
• Node Operators covers running node infrastructure.
• Architecture explains protocol and service design.

Older articles and videos may reference obsolete releases or networks. Check the publication date and compare commands, endpoints, and package versions with the current canonical repository before using them.

Contribute or report stale documentation¶

For a small correction, open a pull request against koinos/koinos-docs. For a broken link, obsolete instruction, or uncertain technical claim, open a documentation issue with:

• the affected page URL and section;
• the statement or link that appears stale;
• the current canonical source, tag, or commit;
• the date and network on which you verified the problem.

Check a repository's CONTRIBUTING.md and target branch before opening a pull request.

Propose a Resources entry¶

Open a documentation issue or pull request with enough evidence to verify the entry:

1. Category and concise factual purpose.
2. Maintainer and whether it is official, community-maintained, or third-party.
3. Canonical site and source repository, when source is public.
4. Supported Koinos network or networks.
5. Current release, package, tag, or immutable commit for technical claims.
6. Verification date and known limitations.

An ecosystem directory or project name can be used for discovery, but it is not enough evidence by itself. Entries that cannot be independently verified may be left out until current canonical evidence is available.