diff --git a/README.rst b/README.rst index 2725e4e5..b64cba68 100644 --- a/README.rst +++ b/README.rst @@ -149,6 +149,7 @@ written. 402 New Wallet Database Format Reserved 403 Verification Behaviour of zcashd Reserved 416 Support for Unified Addresses in zcashd Reserved + 2001 Lockbox Funding Streams Draft guide-markdown {Something Short and To the Point} Draft guide {Something Short and To the Point} Draft @@ -168,7 +169,6 @@ be deleted. Blocks should balance exactly Manufacturing Consent; Re-Establishing a Dev Fund for ECC, ZF, ZCG, Qedit, FPF, and ZecHub Block Reward Allocation for Non-Direct Development Funding - Lockbox Funding Streams Establishing a Hybrid Dev Fund for ZF, ZCG and a Dev Fund Reserve @@ -301,6 +301,7 @@ Index of ZIPs 1012 Dev Fund to ECC + ZF + Major Grants Obsolete 1013 Keep It Simple, Zcashers: 10% to ECC, 10% to ZF Obsolete 1014 Establishing a Dev Fund for ECC, ZF, and Major Grants Active + 2001 Lockbox Funding Streams Draft guide-markdown {Something Short and To the Point} Draft guide {Something Short and To the Point} Draft diff --git a/_config.yml b/rendered/_config.yml similarity index 69% rename from _config.yml rename to rendered/_config.yml index 0bacc557..bf43952e 100644 --- a/_config.yml +++ b/rendered/_config.yml @@ -1,3 +1,5 @@ theme: jekyll-theme-tactile url: "https://zips.z.cash" markdown: GFM +gems: + - jekyll-redirect-from diff --git a/rendered/draft-nuttycom-funding-allocation.html b/rendered/draft-nuttycom-funding-allocation.html index a71b7227..873d3046 100644 --- a/rendered/draft-nuttycom-funding-allocation.html +++ b/rendered/draft-nuttycom-funding-allocation.html @@ -23,7 +23,7 @@ Pull-Request: <https://githu

The key words "MUST", "REQUIRED", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

Abstract

-

This ZIP proposes several options for the allocation of a percentage of the Zcash block subsidy, post-November 2024 halving, to an in-protocol "lockbox." The "lockbox" will be a separate pool of issued funds tracked by the protocol, as described in ZIP <TBD>: Lockbox Funding Streams 4. No disbursement mechanism is currently defined for this "lockbox"; the Zcash community will need to decide upon and specify a suitable decentralized mechanism for permitting withdrawals from this lockbox in a future ZIP in order to make these funds available for funding grants to ecosystem participants.

+

This ZIP proposes several options for the allocation of a percentage of the Zcash block subsidy, post-November 2024 halving, to an in-protocol "lockbox." The "lockbox" will be a separate pool of issued funds tracked by the protocol, as described in ZIP 2001: Lockbox Funding Streams 4. No disbursement mechanism is currently defined for this "lockbox"; the Zcash community will need to decide upon and specify a suitable decentralized mechanism for permitting withdrawals from this lockbox in a future ZIP in order to make these funds available for funding grants to ecosystem participants.

The proposed lockbox addresses significant issues observed with ZIP 1014 3, such as regulatory risks, inefficiencies due to funding of organizations instead of projects, and centralization. While the exact disbursement mechanism for the lockbox funds is yet to be determined and will be addressed in a future ZIP, the goal is to employ a decentralized mechanism that ensures community involvement and efficient, project-specific funding. This approach is intended to potentially improve regulatory compliance, reduce inefficiencies, and enhance the decentralization of Zcash's funding structure.

Motivation

@@ -41,7 +41,7 @@ Pull-Request: <https://githu

Requirements

    -
  1. In-Protocol Lockbox: The alternatives presented in this ZIP depend upon the Lockbox Funding Streams proposal 4.
    2. +
  2. In-Protocol Lockbox: The alternatives presented in this ZIP depend upon the Lockbox Funding Streams proposal 4.
  3. Regulatory Considerations: The allocation of funds should minimize regulatory risks by avoiding direct funding of specific organizations. The design should enable and encourage compliance with applicable laws and regulations to support the long-term sustainability of the funding model.
@@ -54,7 +54,7 @@ Pull-Request: <https://githu

Specification

-

The following alternatives all depend upon the Lockbox Funding Streams proposal 4 for storage of funds into a deferred value pool.

+

The following alternatives all depend upon the Lockbox Funding Streams proposal 4 for storage of funds into a deferred value pool.

Some of the alternatives described below do not specify a termination height for the funding streams they propose. In these cases, the termination height is set to u32::MAX_VALUE. A future network upgrade that alters the maximum possible block height MUST also alter these termination heights.

Alternatives

@@ -314,11 +314,11 @@ Pull-Request: <https://githu - +
- +
4Draft ZIP: Lockbox Funding StreamsZIP 2001: Lockbox Funding Streams
diff --git a/rendered/draft-nuttycom-lockbox-streams.html b/rendered/draft-nuttycom-lockbox-streams.html index f49dedae..bdcb74e5 100644 --- a/rendered/draft-nuttycom-lockbox-streams.html +++ b/rendered/draft-nuttycom-lockbox-streams.html @@ -1,113 +1,3 @@ - - - - Draft nuttycom-lockbox-streams: Lockbox Funding Streams - - - - -
- 
ZIP: Unassigned
-Title: Lockbox Funding Streams
-Owners: Kris Nuttycombe <kris@nutty.land>
-Credits: Daira-Emma Hopwood <daira-emma@electriccoin.co>
-         Jack Grigg <jack@electriccoin.co>
-Status: Draft
-Category: Consensus
-Created: 2024-07-02
-License: MIT
-Pull-Request: <https://github.com/zcash/zips/pull/>
-

Terminology

-

The key words "MUST", "REQUIRED", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

-
-

Abstract

-

This ZIP specifies a change to the Zcash consensus protocol to define a pool of issued Zcash value to be used to fund future development efforts within the Zcash ecosystem.

-

This ZIP builds upon the funding stream mechanism defined in ZIP 207 3. It defines a new "DEFERRED_POOL" funding stream type such that portions of the block reward sent to a stream of this type are deposited directly into the deferred funding pool instead of being sent to a recipient address. Other ways of adding to the pool, such as allowing for direct deposits or fee value currently allocated to miners may be defined in the future.

-
-

Motivation

-

In accordance with ZIP 1014, 2 the Zcash block reward is allocated with 80% going to miners, and the remaining 20% distributed among the Major Grants Fund (8%), Electric Coin Company (ECC) (7%), and the Zcash Foundation (ZF) (5%). This funding structure supports various essential activities such as protocol development, security, marketing, and legal expenses. However, this model will expire in November 2024, leading to the entire block reward being allocated to miners if no changes are made.

-

Several draft ZIPs under consideration for replacing the existing direct allocation of block rewards suggest that part of the block reward be directed to a reserve, the distribution of which is to be determined via a future ZIP. This ZIP is intended to provide a common mechanism that can be used to implement these various proposals.

-
-

Requirements

-

The Zcash protocol will maintain a new Deferred chain pool value balance - \(\mathsf{PoolValue}_{Deferred}\) - for the deferred funding pool, in much the same fashion as it maintains chain pool value balances for the transparent, Sprout, Sapling, and Orchard pools.

-

The funding stream mechanism defined in ZIP 207 3 is modified such that a funding stream may deposit funds into the deferred pool.

-
-

Specification

-

Deferred Development Fund Chain Value Pool Balance

-

Full node implementations MUST track an additional - \(\mathsf{PoolValue}_{Deferred}\) - chain value pool balance, in addition to the Sprout, Sapling, and Orchard chain value pool balances. This balance is set to zero prior to the activation of Network Upgrade 6.

-

ZIP 207 3 is modified as follows:

-

In the section Funding streams 4, instead of:

-
-

Each funding stream has an associated sequence of recipient addresses, each of which MUST be either a transparent P2SH address or a Sapling address.

-
-

it will be modified to read:

-
-

Each funding stream has an associated sequence of recipients, each of which MUST be either a transparent P2SH address, a Sapling address, or the identifier DEFERRED_POOL.

-
-

In the section Consensus rules 5, the following will be added:

-
-

The "prescribed way" to pay to the DEFERRED_POOL is to add - \(\mathsf{FundingStream[FUND].Value}(\mathsf{height})\) - to - \(\mathsf{PoolValue}_{Deferred}\) - .

-
-

The protocol specification is modified to define the "total issued supply" such that the total issued supply as of a given height is given by the function:

-
\(\begin{array}{ll} -\mathsf{IssuedSupply}(\mathsf{height}) := &\!\!\!\!\mathsf{PoolValue}_{Transparent}(\mathsf{height}) \\ -&+\;\; \mathsf{PoolValue}_{Sprout}(\mathsf{height}) \\ -&+\,\; \mathsf{PoolValue}_{Sapling}(\mathsf{height}) \\ -&+\,\; \mathsf{PoolValue}_{Orchard}(\mathsf{height}) \\ -&+\,\; \mathsf{PoolValue}_{Deferred}(\mathsf{height}) -\end{array}\)
-
-
-

References

- - - - - - - -
1Information on BCP 14 — "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels" and "RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"
- - - - - - - -
2ZIP 1014: Establishing a Dev Fund for ECC, ZF, and Major Grants
- - - - - - - -
3ZIP 207: Funding Streams
- - - - - - - -
4ZIP 207: Funding Streams. Section: Funding streams
- - - - - - - -
5ZIP 207: Funding Streams. Section: Consensus rules
-
-
- - \ No newline at end of file +--- +redirect_to: "https://zips.z.cash/zip-2001" +--- diff --git a/rendered/draft-zf-community-dev-fund-2-proposal.html b/rendered/draft-zf-community-dev-fund-2-proposal.html index d20c5e91..4fdd60ea 100644 --- a/rendered/draft-zf-community-dev-fund-2-proposal.html +++ b/rendered/draft-zf-community-dev-fund-2-proposal.html @@ -28,7 +28,7 @@ Pull-Request:

"Section 501(c)(3)" refers to that section of the U.S. Internal Revenue Code (Title 26 of the U.S. Code). 14

"Zcash Community Advisory Panel", also called "ZCAP", refers to the panel of community members assembled by the Zcash Foundation and described at 13.

The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 3.

-

“Lockbox” refers to a deferred funding pool of issued Zcash value as described in 12.

+

“Lockbox” refers to a deferred funding pool of issued Zcash value as described in ZIP 2001 12.

“Dev Fund Reserve”, also called “DFR”, refers to the funds that are to be stored in the Lockbox as a result of the changes described in this ZIP.

Abstract

@@ -250,11 +250,11 @@ Pull-Request: - +
- +
12Draft ZIP: Lockbox for Decentralized Grants AllocationZIP 2001: Lockbox Funding Streams
diff --git a/rendered/index.html b/rendered/index.html index dfdadc94..fe6a43b2 100644 --- a/rendered/index.html +++ b/rendered/index.html @@ -114,6 +114,7 @@ 402 New Wallet Database Format Reserved 403 Verification Behaviour of zcashd Reserved 416 Support for Unified Addresses in zcashd Reserved + 2001 Lockbox Funding Streams Draft guide-markdown {Something Short and To the Point} Draft guide {Something Short and To the Point} Draft
@@ -124,7 +125,6 @@ Blocks should balance exactly Manufacturing Consent; Re-Establishing a Dev Fund for ECC, ZF, ZCG, Qedit, FPF, and ZecHub Block Reward Allocation for Non-Direct Development Funding - Lockbox Funding Streams Establishing a Hybrid Dev Fund for ZF, ZCG and a Dev Fund Reserve

Withdrawn, Rejected, or Obsolete ZIPs

@@ -247,6 +247,7 @@ 1012 Dev Fund to ECC + ZF + Major Grants Obsolete 1013 Keep It Simple, Zcashers: 10% to ECC, 10% to ZF Obsolete 1014 Establishing a Dev Fund for ECC, ZF, and Major Grants Active + 2001 Lockbox Funding Streams Draft guide-markdown {Something Short and To the Point} Draft guide {Something Short and To the Point} Draft
diff --git a/rendered/zip-2001.html b/rendered/zip-2001.html new file mode 100644 index 00000000..4677832e --- /dev/null +++ b/rendered/zip-2001.html @@ -0,0 +1,113 @@ + + + + ZIP 2001: Lockbox Funding Streams + + + + +
+ 
ZIP: 2001
+Title: Lockbox Funding Streams
+Owners: Kris Nuttycombe <kris@nutty.land>
+Credits: Daira-Emma Hopwood <daira-emma@electriccoin.co>
+         Jack Grigg <jack@electriccoin.co>
+Status: Draft
+Category: Consensus
+Created: 2024-07-02
+License: MIT
+Pull-Request: <https://github.com/zcash/zips/pull/>
+

Terminology

+

The key words "MUST", "REQUIRED", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

+
+

Abstract

+

This ZIP specifies a change to the Zcash consensus protocol to define a pool of issued Zcash value to be used to fund future development efforts within the Zcash ecosystem.

+

This ZIP builds upon the funding stream mechanism defined in ZIP 207 3. It defines a new "DEFERRED_POOL" funding stream type such that portions of the block reward sent to a stream of this type are deposited directly into the deferred funding pool instead of being sent to a recipient address. Other ways of adding to the pool, such as allowing for direct deposits or fee value currently allocated to miners may be defined in the future.

+
+

Motivation

+

In accordance with ZIP 1014, 2 the Zcash block reward is allocated with 80% going to miners, and the remaining 20% distributed among the Major Grants Fund (8%), Electric Coin Company (ECC) (7%), and the Zcash Foundation (ZF) (5%). This funding structure supports various essential activities such as protocol development, security, marketing, and legal expenses. However, this model will expire in November 2024, leading to the entire block reward being allocated to miners if no changes are made.

+

Several draft ZIPs under consideration for replacing the existing direct allocation of block rewards suggest that part of the block reward be directed to a reserve, the distribution of which is to be determined via a future ZIP. This ZIP is intended to provide a common mechanism that can be used to implement these various proposals.

+
+

Requirements

+

The Zcash protocol will maintain a new Deferred chain pool value balance + \(\mathsf{PoolValue}_{Deferred}\) + for the deferred funding pool, in much the same fashion as it maintains chain pool value balances for the transparent, Sprout, Sapling, and Orchard pools.

+

The funding stream mechanism defined in ZIP 207 3 is modified such that a funding stream may deposit funds into the deferred pool.

+
+

Specification

+

Deferred Development Fund Chain Value Pool Balance

+

Full node implementations MUST track an additional + \(\mathsf{PoolValue}_{Deferred}\) + chain value pool balance, in addition to the Sprout, Sapling, and Orchard chain value pool balances. This balance is set to zero prior to the activation of Network Upgrade 6.

+

ZIP 207 3 is modified as follows:

+

In the section Funding streams 4, instead of:

+
+

Each funding stream has an associated sequence of recipient addresses, each of which MUST be either a transparent P2SH address or a Sapling address.

+
+

it will be modified to read:

+
+

Each funding stream has an associated sequence of recipients, each of which MUST be either a transparent P2SH address, a Sapling address, or the identifier DEFERRED_POOL.

+
+

In the section Consensus rules 5, the following will be added:

+
+

The "prescribed way" to pay to the DEFERRED_POOL is to add + \(\mathsf{FundingStream[FUND].Value}(\mathsf{height})\) + to + \(\mathsf{PoolValue}_{Deferred}\) + .

+
+

The protocol specification is modified to define the "total issued supply" such that the total issued supply as of a given height is given by the function:

+
\(\begin{array}{ll} +\mathsf{IssuedSupply}(\mathsf{height}) := &\!\!\!\!\mathsf{PoolValue}_{Transparent}(\mathsf{height}) \\ +&+\;\; \mathsf{PoolValue}_{Sprout}(\mathsf{height}) \\ +&+\,\; \mathsf{PoolValue}_{Sapling}(\mathsf{height}) \\ +&+\,\; \mathsf{PoolValue}_{Orchard}(\mathsf{height}) \\ +&+\,\; \mathsf{PoolValue}_{Deferred}(\mathsf{height}) +\end{array}\)
+
+
+

References

+ + + + + + + +
1Information on BCP 14 — "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels" and "RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"
+ + + + + + + +
2ZIP 1014: Establishing a Dev Fund for ECC, ZF, and Major Grants
+ + + + + + + +
3ZIP 207: Funding Streams
+ + + + + + + +
4ZIP 207: Funding Streams. Section: Funding streams
+ + + + + + + +
5ZIP 207: Funding Streams. Section: Consensus rules
+
+
+ + \ No newline at end of file diff --git a/zips/draft-nuttycom-funding-allocation.rst b/zips/draft-nuttycom-funding-allocation.rst index d6d9fbf8..15b2bd51 100644 --- a/zips/draft-nuttycom-funding-allocation.rst +++ b/zips/draft-nuttycom-funding-allocation.rst @@ -27,8 +27,8 @@ Abstract This ZIP proposes several options for the allocation of a percentage of the Zcash block subsidy, post-November 2024 halving, to an in-protocol "lockbox." The "lockbox" will be a separate pool of issued funds tracked by the protocol, -as described in ZIP : Lockbox Funding Streams -[#draft-nuttycom-lockbox-streams]_. No disbursement mechanism is currently defined +as described in ZIP 2001: Lockbox Funding Streams +[#zip-2001]_. No disbursement mechanism is currently defined for this "lockbox"; the Zcash community will need to decide upon and specify a suitable decentralized mechanism for permitting withdrawals from this lockbox in a future ZIP in order to make these funds available for funding grants to @@ -105,7 +105,7 @@ Requirements ============ 1. **In-Protocol Lockbox**: The alternatives presented in this ZIP depend upon - the Lockbox Funding Streams proposal [#draft-nuttycom-lockbox-streams]_. + the Lockbox Funding Streams proposal [#zip-2001]_. 2. **Regulatory Considerations**: The allocation of funds should minimize regulatory risks by avoiding direct funding of specific organizations. The @@ -141,7 +141,7 @@ Specification ============= The following alternatives all depend upon the Lockbox Funding Streams proposal -[#draft-nuttycom-lockbox-streams]_ for storage of funds into a deferred value +[#zip-2001]_ for storage of funds into a deferred value pool. Some of the alternatives described below do not specify a termination height @@ -608,4 +608,4 @@ References Lowercase in RFC 2119 Key Words" `_ .. [#osd] `The Open Source Definition `_ .. [#zip-1014] `ZIP 1014: Dev Fund Proposal and Governance `_ -.. [#draft-nuttycom-lockbox-streams] `Draft ZIP: Lockbox Funding Streams `_ +.. [#zip-2001] `ZIP 2001: Lockbox Funding Streams `_ diff --git a/zips/draft-zf-community-dev-fund-2-proposal.rst b/zips/draft-zf-community-dev-fund-2-proposal.rst index c55c65fd..30182c7f 100644 --- a/zips/draft-zf-community-dev-fund-2-proposal.rst +++ b/zips/draft-zf-community-dev-fund-2-proposal.rst @@ -54,7 +54,7 @@ The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification [#protocol-networks]_. “Lockbox” refers to a deferred funding pool of issued Zcash value as described -in [#draft-nuttycom-lockbox-streams]_. +in ZIP 2001 [#zip-2001]_. “Dev Fund Reserve”, also called “DFR”, refers to the funds that are to be stored in the Lockbox as a result of the changes described in this ZIP. @@ -493,7 +493,7 @@ References .. [#zip-1011] `ZIP 1011: Decentralize the Dev Fee `_ .. [#zip-1012] `ZIP 1012: Dev Fund to ECC + ZF + Major Grants `_ .. [#zip-1014] `ZIP 1014: Establishing a Dev Fund for ECC, ZF, and Major Grants `_ -.. [#draft-nuttycom-lockbox-streams] `Draft ZIP: Lockbox for Decentralized Grants Allocation `_ +.. [#zip-2001] `ZIP 2001: Lockbox Funding Streams `_ .. [#zcap] `Zcash Community Advisory Panel `_ .. [#section501c3] `U.S. Code, Title 26, Section 501(c)(3) `_ diff --git a/zips/draft-nuttycom-lockbox-streams.rst b/zips/zip-2001.rst similarity index 99% rename from zips/draft-nuttycom-lockbox-streams.rst rename to zips/zip-2001.rst index 65a130a0..9be3855c 100644 --- a/zips/draft-nuttycom-lockbox-streams.rst +++ b/zips/zip-2001.rst @@ -1,6 +1,6 @@ :: - ZIP: Unassigned + ZIP: 2001 Title: Lockbox Funding Streams Owners: Kris Nuttycombe Credits: Daira-Emma Hopwood