ZIP 318 §Network-layer privacy: "MUST offer Tor and (if available) Nym" — is Tor required, or is Tor-or-Nym sufficient?
The normative sentence in **§ Network-layer privacy** of ZIP 318 (Orchard to Ironwood Migration, Draft) reads: > The wallet MUST offer Tor and (if available) Nym network options. When enabled, all migration transaction broadcasts MUST be routed through the selected network. Taken
Radar summary of the original source
An open proposal—not a live product.
Radar found activity on the original proposal source. Open means the source still lists it as open; it does not mean the proposal is approved, merged, or implemented.
- Status
- Open proposal
- Source
- Zcash Improvement Proposals
- Source activity
- Confidence
- Source-linked record
ZIPs
Zcash Improvement Proposal updates and their original source links.
Radar summary of the original source
Related activity
- Original source
[ZIP 312] Specify key generation, change randomizer handling
Changes to randomizer handling after I realized that it couldn't possibly be generated using the message as an input. It does simplify things too. Some additional fixes (using "Re-Randomized FROST" consistently; updating Owners) fixes #1051
- Original source
Bulk synchronization: v2 protocol primitives and Block Chain Synchronization ZIP
Recommends how nodes synchronize over the version 2 P2P protocol. The v2 protocol draft (#1344) now defines the primitives (`get-headers`/`get-blocks`/`get-hashes`) and the normative synchronization rules for both headers-first and checkpointed synchronization; this ZIP recommend
- Original source
Add draft-aphelionz-marginal-fee: Reduce Marginal Fee to 1000 Zatoshis
The source is a GitHub pull request that adds a draft ZIP proposing to reduce the marginal fee in ZIP 317 from 5,000 to 1,000 zatoshis per logical action. This change lowers the conventional fee for a minimal 2-action transaction from 10,000 to 2,000 zatoshis, with no other ZIP 3