Monolythium/Build/GitHub

GitHub.

The selected links below were publicly visible when checked on 16 July 2026. Repository counts, visibility, and release artifacts can change, so this page avoids fixed totals: verify the current state directly on GitHub. Core-source review remains a separate diligence gate.

· Public visibility checked 2026-07-16

Verify again on GitHub.

Public repository visibility does not prove a tagged release, artifact signature, network compatibility, or capability activation.

Repository	Description
monolythium/mono-core-sdk	Versioned Rust and TypeScript client source. Match packages, examples, and protocol version before use.	↗
monolythium/mono-studio	Developer-tooling project. Inspect repository visibility, current scope, and release status directly on GitHub.	↗
monolythium/chain-registry	Registered network identities and endpoint metadata. Registry presence is not liveness or finality evidence.	↗
monolythium/lyth_mcp	MCP integration workspace. The isolated Stele package has exactly three read/status tools; Stele transaction tools remain gated.	↗
monolythium/monoscan	Explorer project for development network 69420. Its underlying RPC was stale as observed on 16 July 2026.	↗
monolythium/browser-wallet	Monolythium browser wallet — Manifest V3 extension using standard BIP-39-to-ML-DSA-65 recovery and an encrypted extension-local vault. PQM-1 is removed.	↗
monolythium/monarch-desktop	Operator-console project. Verify source visibility, artifacts, signatures, and supported actions at the repository.	↗
monolythium/monarch-os-talos	Operator-system project. A repository link does not attest that a signed installer or supported hardware release exists.	↗
monolythium/protocore	Node-binary release channel. Verify the current tag, checksums, signatures, provenance, SBOM, and network compatibility directly; none are implied by this index.	↗
monolythium/mono-blog-content	Markdown source for monolythium.com/blog. Open so anyone can verify what was published and when.	↗
monolythium/.github	Organization profile, security policy, and shared community health files.	↗

· Restricted source posture

Not public release evidence.

Core-source review and other restricted workspaces remain separate diligence gates. This site does not publish internal documents, private repository names or metrics, file paths, or future visibility promises.

Public boundary

Use only material deliberately published through canonical public repositories.

A product name, roadmap entry, package name, or binary channel does not provide source-level review. Ask for explicit access and release evidence through the diligence process; do not rely on inferred repository inventory.

Source on GitHub.

The org page is the canonical index. Each repository carries its own CONTRIBUTING guide — read it before opening a PR.

github.com/monolythium ↗