# ZIP-0001 Purpose, Process, and Guidelines | Consolidated Discussion
**URL:** https://forum.hypercore.one/t/zip-0001-purpose-process-and-guidelines-consolidated-discussion/939
**Category:** ZIPs
**Created:** [July 11, 2026, 10:02pm UTC](https://forum.hypercore.one/t/zip-0001-purpose-process-and-guidelines-consolidated-discussion/939 "2026-07-11T22:02:00Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@0x3639](https://forum.hypercore.one/u/0x3639)
#### Post date: [July 11, 2026, 10:02pm UTC](https://forum.hypercore.one/t/zip-0001-purpose-process-and-guidelines-consolidated-discussion/939/1 "2026-07-11T22:02:00Z")
## Background
ZIP-0001 (the ZIP process itself) has been discussed across a few threads over time. This post is meant to bring that discussion back into one place, get it moving again, and align on next steps.
**ZIP-0001:** [https://zenon.zip/1](https://zenon.zip/1)
## Prior discussion
- [Proposal: Zenon Improvement Proposals (ZIP) Framework Development](https://forum.zenon.org/t/proposal-zenon-improvement-proposals-zip-framework-development/592)
- [Zenon Improvement Proposals (ZIPs) — Community Decisions](https://forum.zenon.org/t/zenon-improvement-proposals-zips-community-decisions/869)
## Inspiration
ZIP-0001 is modeled on Bitcoin’s [BIP-1](https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki), which defines the BIP process itself. We’re adapting that same structure for Zenon.
## What we’re looking for
- Feedback on the current draft at zenon.zip/1
- Points from the prior threads that still need resolving
- Anyone willing to help move this to Final status
Let’s use this thread going forward to keep the discussion in one place.
---
### Author:  [@0x3639](https://forum.hypercore.one/u/0x3639)
#### Post date: [July 12, 2026, 1:19am UTC](https://forum.hypercore.one/t/zip-0001-purpose-process-and-guidelines-consolidated-discussion/939/2 "2026-07-12T01:19:19Z")
I compared ZIP-0001 draft against [BIP-1](https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki). There are a few gaps worth noting:
- **No implementation requirement.** BIP-1 requires a working reference implementation before a Standards Track BIP reaches Final. ZIP-1 has no equivalent gate for Official status.
- **No “vet before drafting” step.** BIP-1 has authors informally float an idea publicly before writing the full draft, to avoid wasted effort. ZIP-1 goes straight from draft to formal NIP-34 submission with no pre-check step.
- **No explicit rejection criteria.** BIP-1 lists concrete reasons an editor can reject a proposal (duplication, unfocused, technically unsound, missing motivation/backwards-compat). ZIP-1 only says maintainers judge “completeness, well-specified, rough consensus” — vaguer, likely to cause disputes later.
- **No single-idea-per-proposal guidance.** BIP-1 recommends splitting unfocused proposals into separate ones. Not addressed in ZIP-1.
- **No ownership transfer process.** BIP-1 covers what happens when an author goes inactive and someone else wants to take over. ZIP-1 has no equivalent, worth having given Nostr-key authorship.
- **No “Deferred” status.** BIP-1 has a status for stalled proposals. ZIP-1’s status list (Draft/Proposed/Official/Rejected/Withdrawn/Superseded) has no way to flag “stalled, not dead.”
- **Recommended sections listed but not defined.** BIP-1 explains what belongs in each section (Motivation, Rationale, Backwards Compatibility, etc.). ZIP-1 just names them.
- **No title length limit or asset file-naming convention.** Minor, but BIP-1 specifies both.
Maybe some of these items will be more important if and when people starting looking at ZIPs. Until then some of these could be overkill.
---
### Author:  [@0x3639](https://forum.hypercore.one/u/0x3639)
#### Post date: [July 12, 2026, 10:25am UTC](https://forum.hypercore.one/t/zip-0001-purpose-process-and-guidelines-consolidated-discussion/939/3 "2026-07-12T10:25:30Z")
ZIP Framework .pdf associated with the AZ that Romeo pursued.
[ZIP\_Framework\_v0.1.pdf](https://forum.hypercore.one/uploads/short-url/mNNCbgzZvUFSsUCiBWtfvDd4P55.pdf) (561.9 KB)