Design proposals for Hash Chain, the privacy Layer 0: its own network with its own validators, where accounts, payments, swaps, assets and apps are private by default, connected to Ethereum, Base, Robinhood Chain and Monero.
STATUS: pre-launch, spec stage. Every HIP here is a proposal. Nothing described is deployed or audited. A Draft HIP is not a decision. The protocol spec describes the current design, and HIPs are how changes to it are proposed, argued and recorded.
A HIP is a short design document that describes one change, explains why, and records the objections. It is modelled on Ethereum Improvement Proposals and Bitcoin Improvement Proposals. Anyone can write one. The full rules are in HIP-1.
Every HIP starts with this front matter. scripts/check-frontmatter.sh enforces it.
| Field | Required | Value |
|---|---|---|
hip |
Yes | The HIP number. Must match the file name, so hip: 2 lives in hips/hip-0002.md. |
title |
Yes | A short plain title. |
author |
Yes | Who wrote it. |
status |
Yes | One of the statuses below. |
category |
Yes | One of the categories below. |
created |
Yes | Date in YYYY-MM-DD format. |
requires |
No | Comma separated HIP numbers this one depends on, for example 1, 2. Each must exist. |
| Status | Meaning |
|---|---|
| Idea | Discussed informally in an issue. |
| Draft | A pull request is open and the author is working on the text. |
| Review | The author asks for wider review. |
| Last Call | A final review window of at least fourteen days. |
| Final | Accepted. Only corrections and clarifications from here. |
| Withdrawn | The author has withdrawn the proposal. |
| Stagnant | No activity for six months. Can be revived. |
| Category | Scope |
|---|---|
| Core | Consensus, validators, staking, accounts, proofs, privacy mechanisms |
| Networking | Peer to peer communication and data propagation |
| Interface | APIs, SDKs, wallet behaviour, app and token standards |
| Connection | Links to Ethereum, Base, Robinhood Chain and Monero |
| Meta | The HIP process itself |
| Informational | Background and guidelines with no required adoption |
| HIP | Title | Category | Status |
|---|---|---|---|
| 1 | HIP Purpose and Process | Meta | Final |
| 2 | Scoped view keys | Core | Draft |
| 3 | Monero swap timelock parameters | Connection | Draft |
| 4 | Shielded fee payment | Core | Draft |
| 5 | Direct swap corridors for ETH and Monero | Connection | Draft |
- Open an issue with the "HIP idea" template and discuss the idea in public.
- Copy hip-template.md and fill it in. Keep to plain language and mark undecided points as "to be specified".
- Run
scripts/check-frontmatter.sh,scripts/check-sections.sh,scripts/check-index.shandscripts/check-links.sh. - Open a pull request with one HIP. An editor assigns the number.
- Respond to feedback in the open. The HIP moves through Review and Last Call to Final.
See CONTRIBUTING.md for the style guide.
- protocol-spec: the written design of Hash Chain.
- xmr-swap-model: a research model of the Monero swap, used by HIP-3.
- protocol-spec research notes: background for several HIPs, such as HIP-4.
Security reports go through SECURITY.md. Participation is governed by the Code of Conduct.
- Website: https://hashchain.network
- X: https://x.com/hashchainL0
- GitHub: https://github.com/HashChainL0
Proposal text is released under CC0 1.0. The Hash Chain name and logo are covered separately in the brand kit.