Repo brief: ordinals/ord

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T03:10:46.346Z · commit 5241ef311e01

Verdict

Healthy — Strong maintenance signals

• Last commit 5w ago
• 25+ active contributors
• CC0-1.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

ord is a Bitcoin indexer, block explorer, and command-line wallet that implements Ordinal theory—a numbering scheme for satoshis that assigns and tracks serial numbers across transactions. It enables satoshis to be collected, traded, and inscribed with arbitrary data, turning individual sats into collectible digital artifacts with provenance tracking. Monorepo with Cargo workspace: main crate is /. under crates/ordinals/ (core ordinal logic: artifact.rs, cenotaph.rs, charm.rs, etching.rs), crates/mockcore/ (Bitcoin Core mock for testing), and specialized audit crates. Binary tools in bin/ (benchmark, flamegraph, forbid, graph, package, replicate, swap). Frontend HTML/CSS/JS assets…

Start here

Open these first:

• crates/ordinals/src/lib.rs — Core ordinals library exporting the fundamental types (Sat, SatPoint, Rune, Runestone) that all indexing and wallet logic…
• crates/ordinals/src/sat.rs — Defines the Sat type representing individual satoshis and their ordinal numbering—the conceptual foundation of the entire…
• crates/ordinals/src/runestone.rs — Implements the Runestone protocol (rune issuance and transfers), a major feature for handling digital artifacts beyond…
• crates/ordinals/src/rune.rs — Defines the Rune type and protocol mechanics; essential for understanding the rune (fungible token) system layered on…
• Cargo.toml — Workspace configuration and dependency manifest; contributors must understand the crate structure and dependency versions.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/ordinals/ord.git
cd ord
cargo build --release
cargo run -- --help

Requires Rust 1.89.0+ (from workspace config) and a running Bitcoin Core node for wallet/indexing commands.

Daily commands:

cargo run --bin ord -- server --http-port 80

Alternatively with Docker: docker build -t ord . && docker run -p 80:80 ord. Requires a synced Bitcoin Core node accessible via RPC (typically localhost:8332). Wallet commands require Bitcoin Core wallet named 'ord' t…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 65% of recent commits
• Bitcoin Core RPC endpoint must be accessible (defaults to localhost:8332); wallet commands auto-load the 'ord' wallet and can corrupt non-ordinal-aware wallets—never use with hot wallets. Satoshi numbering is…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.