Zenrock is a Cosmos SDK-based blockchain providing bedrock security infrastructure for omnichain operations. It specializes in managing wrapped assets (Bitcoin via zenBTC, ZCash via zenZEC, and more) with oracle consensus, MPC-based signing, and cross-chain settlement.
Core Features:
- π Wrapped Assets - Bitcoin deposits β zenBTC, ZCash deposits β zenZEC
- π€ Oracle Consensus - Vote extensions for multi-chain data validation
- π MPC Signing - Secure multi-party computation for transaction signing
- π Cross-Chain - Solana, Ethereum, and more via Sidecar oracle
- πͺ IBC Ready - Full Inter-Blockchain Communication support
π Start with the Developer Onboarding Guide - It covers:
- Getting up and running in 30 minutes
- Understanding the architecture
- First week checklist
- Common development tasks
Then read CLAUDE.md for detailed developer reference and AGENTS.md for architecture deep-dives.
- Overview
- New to the Team?
- Architecture
- Quick Start
- Contributing
- Commit & Release Workflow
- Resources
- Support
- License
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β zrChain (Cosmos Blockchain) β
β ββββββββββ¬ββββββββββ¬βββββββββββ¬ββββββββββββββββββββββββββ β
β βidentityβ treasuryβ validationβ zenbtc / dct / zentp β β
β β policy β mint β wasm β Other Custom Modules β β
β ββββββββββ΄ββββββββββ΄βββββββββββ΄ββββββββββββββββββββββββββ β
β β (gRPC) β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Sidecar Oracle (Off-Chain Service) β
β β’ Watches Bitcoin, ZCash, Solana, Ethereum networks β
β β’ Runs EigenLayer operator loops with local keystores β
β β’ Provides price feeds and block headers β
β β’ Reports consensus signals to validators β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
| Module | Purpose |
|---|---|
x/identity |
Keyrings, workspaces, and multi-sig management |
x/treasury |
Asset custody and signature request workflows |
x/zenbtc |
Bitcoin wrapped asset (production, v0) |
x/dct |
Digital Currency Tokens framework (v1+, extensible) |
x/validation |
Validator management and oracle consensus |
x/policy |
Approval policies and governance |
x/mint |
Token minting |
x/zentp |
Zenrock token protocol |
See CLAUDE.md for full module documentation.
./scripts/dev-setup.shRun the bootstrap script once after cloning to install everything in one shot. It:
- Installs Go 1.25+,
just,uv, and the full buf/protoc toolchain - Detects macOS/Linux package managers automatically
- Guides Docker Desktop/Engine installation where automation isnβt possible
Prefer to manage things manually? Make sure you still have Go 1.25+, make, Docker, and the proto toolchain exposed on your PATH.
# Install
git clone git@github.com:Zenrock-Foundation/zrchain.git
cd zrchain
make install
# Start local network (open 2 terminal tabs)
# Terminal 1:
./init.sh --localnet 1
# Terminal 2:
./init.sh --localnet 2
# Verify it's running
zenrockd statusSee Developer Onboarding Guide for detailed setup instructions and common commands.
zrchain/
βββ app/ # Blockchain setup and module wiring
βββ cmd/ # CLI binary entry points
βββ x/ # Custom modules (identity, treasury, zenbtc, dct, etc.)
βββ sidecar/ # Off-chain oracle service
βββ proto/ # Protocol Buffer definitions
βββ tests/ # End-to-end tests
βββ docs/ # Documentation
βββ Makefile # Build commands
Quick reference:
- π Development Guide β
docs/ONBOARDING.md - π§ Developer Reference β
CLAUDE.md - ποΈ Architecture Details β
AGENTS.md
Parallel development is driven by the Justfile wrappers around the scripts in scripts/git/:
just worktree-new(scripts/git/worktree-new.sh) β create a branch+worktree; when Graphite (gt) is installed, the script can callgt create -m β¦on the parent branch so the stack is tracked automatically.just worktree-switchβ jump into an existing branch/worktree; with Graphite it usesgt get/gt checkoutto stay in sync and can auto-track non-Graphite branches.just worktree-cleanupβ interactive cleanup of stale worktrees.
Each script still works without Graphite, but when the CLI is available you get prompted to opt-in so the branch metadata is captured for stacked PRs. This is the foundation for the graphite + worktrees + agent workflow used by our AI agents.
We appreciate all contributions to Zenrock and review them closely. See CONTRIBUTING.md for:
- Development guidelines
- Git conventions (commits, branches, PRs)
- Security considerations
- Code review process
Zenrock uses semantic-release alongside the Conventional Commits specification to publish new versions automatically. Commit messages must follow the type(optional-scope)!: description pattern:
feat: triggers a minor version bump.fixandperf: trigger a patch bump.- Commits that include
BREAKING CHANGEnotes (or usetype!: ...) trigger a major bump. - Other conventional types (
docs,chore,refactor,test, etc.) do not advance the version but must still follow the format.
See the Git conventions section for detailed guidance and examples.
| Document | For New Devs? | Topic |
|---|---|---|
| docs/ONBOARDING.md | β START HERE | Getting started, first steps, development setup |
| CLAUDE.md | β Recommended | Developer reference, commands, patterns, architecture |
| AGENTS.md | For deep dives | Wrapped asset flows, technical architecture |
| CONTRIBUTING.md | β Recommended | Contribution guidelines, git conventions, security |
- Zenrock Website - Project overview and roadmap
- Discord - Validator + contributor chat
- Telegram - Community updates
- Twitter - Updates and news
- π¬ Questions? - Ask in Discord or GitHub Issues
- π Found a bug? - Report it here
- π‘ Feature request? - Create an issue
Licensed under the Source Available License, Zenrock Foundation DAO. See LICENSE file for details.
