ZIP: 207
Title: Split Founders' Reward
Owners: Jack Grigg <>
Category: Consensus
Status: Withdrawn
Created: 2019-01-04
License: MIT


The key words "MUST", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 1


This Withdrawn proposal would have altered consensus rules to split the original Founders' Reward across several recipient addresses per block instead of one, corresponding to the several funding streams contained within it.


Since the launch of the Zcash network, the consensus rules have required that until the first block reward halving (at block 850,000), each block must send 20% of the block subsidy to a hard-coded transparent address. 2 This funding stream is referred to as the Founders' Reward.

This stream of 2.5-ZEC outputs (the value after the mining slow-start was completed) can be split into several logical funding streams (for background, see 3). Modifying the consensus rules to allocate the 2.5 ZEC across separate recipient addresses decouples these funding streams organizationally, legally, and operationally. It further reinforces transparency as to the structure of the original Founders' Reward.



We use the following constants and functions defined in 4:

  • BlossomActivationHeight
  • PostBlossomHalvingInterval
  • Halving(height)

We also define the following constants and functions:

  • SlowStartShift as-defined in 2.
  • HeightForHalving(halving): Smallest height such that Halving(height) = halving

Funding streams

A funding stream is defined by a block reward fraction (represented as a numerator and a denominator), a start height (inclusive), and an end height (exclusive).

By defining the issuance as a proportion of the total block issuance, rather than absolute zatoshis, this ZIP dovetails with any changes to both block target times and issuance-per-block rates while maintaining an unchanged target-time-based issuance schedule. We anticipate such target-time / issuance rate changes in other ZIPs (for example, 4).

The value of a funding stream at a given block height is defined as:

FundingStream[FUND].Value(height) =
        BlockReward(height) * FundingStream[FUND].ValueNumerator
    ) / FundingStream[FUND].ValueDenominator)

An active funding stream at a given block height is defined as a funding stream for which the block height is less than its end height, but not less than its start height.

Each funding stream has an associated set of recipient addresses. Each address is used for at most 1/48th of a halving interval, creating a roughly-monthly sequence of funding periods. The address to be used for a given block height is defined as follows:

AddressChangeInterval = PostBlossomHalvingInterval / 48
AddressPeriod(height) =
        height + PostBlossomHalvingInterval - HeightForHalving(1)
    ) / AddressChangeInterval)
FundingStream[FUND].AddressIndex(height) =
    AddressPeriod(height) - AddressPeriod(FundingStream[FUND].StartHeight)
Address(height) = FundingStream[FUND].Addresses[FundingStream[FUND].AddressIndex(height)]

This has the property that all active funding streams change the address they are using on the same block height schedule, aligned to the height of the first halving so that 48 funding periods fit cleanly within a halving interval. This can be leveraged to simplify implementations, by batching the necessary outputs for each funding period.

Below is a visual representation of how stream addresses align with funding periods:

Example height Stream A Stream B Stream C
AddressChangeInterval - 2 A0
AddressChangeInterval - 1 A0
AddressChangeInterval A1 B0 C0
AddressChangeInterval + 1 A1 B0 C0
2*AddressChangeInterval - 2 A1 B0 C0
2*AddressChangeInterval - 1 A1 B0 C0
2*AddressChangeInterval A2 C1
2*AddressChangeInterval + 1 A2 C1
PostBlossomHalvingInterval - 2 A2 C1
PostBlossomHalvingInterval - 1 A2 C1
PostBlossomHalvingInterval C2
PostBlossomHalvingInterval + 1 C2

Note that this is not intended to align with the end of a pre-Blossom Founders' Reward address period (as defined by FounderAddressChangeInterval in 5). There will be a shortened Founders' Reward address period prior to Blossom activation.

Consensus rules

Prior to activation of the Blossom network upgrade, the existing consensus rule for payment of the original Founders' Reward is enforced. 5

Once the Blossom network upgrade activates:

  • The existing consensus rule 5 is no longer active.
  • The coinbase transaction in each block MUST contain at least one output per active funding stream that pays the stream's value to the stream's recipient address for the block's height.

Stream definitions

The consensus-defined funding streams described above each start at the Blossom activation height, and end at the first block reward halving. They are defined as follows:

Stream Value numerator Value denominator Start height End height
FS 1 3 40 BlossomActivationHeight HeightForHalving(1)
FS 2 1 25 BlossomActivationHeight HeightForHalving(1)
FS 3 1 40 BlossomActivationHeight HeightForHalving(1)
FS 4 1 50 BlossomActivationHeight HeightForHalving(1)
FS 5 1 80 BlossomActivationHeight HeightForHalving(1)
FS 6 1 80 BlossomActivationHeight HeightForHalving(1)
FS 7 1 100 BlossomActivationHeight HeightForHalving(1)
FS 8 1 200 BlossomActivationHeight HeightForHalving(1)
  • To-do: specify the correct values.

The sum of the block reward fractions for the above funding streams is 1/5, equal to the original Founders' Reward (as-defined by FoundersFraction in 6).

The sets of recipient addresses are defined as follows:

std::vector<std::string> FS_1_ADDRESSES = [

std::vector<std::string> FS_2_ADDRESSES = [

std::vector<std::string> FS_3_ADDRESSES = [

std::vector<std::string> FS_4_ADDRESSES = [

std::vector<std::string> FS_5_ADDRESSES = [

std::vector<std::string> FS_6_ADDRESSES = [

std::vector<std::string> FS_7_ADDRESSES = [

std::vector<std::string> FS_8_ADDRESSES = [
  • To-do: specify the correct sets of FR addresses.
  • To-do: require that the FR address sets are PGP-signed with appropriate keys.

Example implementation

struct FundingPeriod {
    std::vector<std::string> addresses,
    uint64_t valueNumerator,
    uint64_t valueDenominator,
    int startHeight,
    int endHeight,

enum FundingStream {

struct Params {
    int nFundingPeriodLength;
    FundingPeriod vFundingPeriods[MAX_FUNDING_STREAMS];

void AddZIP207FundingStream(
    Consensus::Params& params,
    Consensus::FundingStream idx,
    std::vector<std::string> addresses,
    uint64_t valueNumerator,
    uint64_t valueDenominator)
    assert(valueNumerator < valueDenominator);
    params.vFundingPeriods[idx].addresses = addresses;
    params.vFundingPeriods[idx].valueNumerator = valueNumerator;
    params.vFundingPeriods[idx].valueDenominator = valueDenominator;
    params.vFundingPeriods[idx].startHeight =
    params.vFundingPeriods[idx].endHeight = HeightForHalving(params, 1);
    assert(params.vFundingPeriods[idx].startHeight < params.vFundingPeriods[idx].endHeight);

CMainParams() {

    consensus.nFundingPeriodLength = consensus.nSubsidyPostBlossomHalvingInterval / 48;

    AddZIP207FundingStream(consensus, Consensus::FS_1, FS_1_ADDRESSES, 3, 40);
    AddZIP207FundingStream(consensus, Consensus::FS_2, FS_2_ADDRESSES, 1, 25);
    AddZIP207FundingStream(consensus, Consensus::FS_3, FS_3_ADDRESSES, 1, 40);
    AddZIP207FundingStream(consensus, Consensus::FS_4, FS_4_ADDRESSES, 1, 50);
    AddZIP207FundingStream(consensus, Consensus::FS_5, FS_5_ADDRESSES, 1, 80);
    AddZIP207FundingStream(consensus, Consensus::FS_6, FS_6_ADDRESSES, 1, 80);
    AddZIP207FundingStream(consensus, Consensus::FS_7, FS_7_ADDRESSES, 1, 100);
    AddZIP207FundingStream(consensus, Consensus::FS_8, FS_8_ADDRESSES, 1, 200);


CScript FundingStreamRecipientAddress(
    int nHeight,
    const Consensus::Params& params,
    Consensus::FundingStream idx)
    // Integer division is floor division in C++
    auto curPeriod = (
        nHeight + params.nSubsidyPostBlossomHalvingInterval - HeightForHalving(params, 1)
    ) / params.nFundingPeriodLength;
    auto startPeriod = (
            + params.nSubsidyPostBlossomHalvingInterval
            - HeightForHalving(params, 1)
    ) / params.nFundingPeriodLength;
    auto addressIndex = curPeriod - startPeriod;
    return params.vFundingPeriods[idx].addresses[addressIndex];

CAmount FundingStreamValue(
    int nHeight,
    const Consensus::Params& params,
    Consensus::FundingStream idx)
    // Integer division is floor division in C++
    return CAmount((
        GetBlockSubsidy(nHeight, params) * params.vFundingPeriods[idx].valueNumerator
    ) / params.vFundingPeriods[idx].valueDenominator);

std::set<std::pair<CScript, CAmount>> GetActiveFundingStreams(
    int nHeight,
    const Consensus::Params& params)
    std::set<std::pair<CScript, CAmount>> requiredStreams;
    for (int idx = Consensus::FS_ZECC_EF; idx < Consensus::MAX_FUNDING_STREAMS; idx++) {
        // Funding period is [startHeight, endHeight)
        if (nHeight >= params.vFundingPeriods[idx].startHeight &&
            nHeight < params.vFundingPeriods[idx].endHeight)
                FundingStreamRecipientAddress(nHeight, params, idx),
                FundingStreamValue(nHeight, params, idx));
    return requiredStreams;

bool ContextualCheckBlock(...)

    if (NetworkUpgradeActive(nHeight, consensusParams, Consensus::UPGRADE_BLOSSOM)) {
        // Coinbase transaction must include outputs corresponding to the consensus
        // funding streams active at the current block height.
        auto requiredStreams = GetActiveFundingStreams(nHeight, consensusParams);

        for (const CTxOut& output : block.vtx[0].vout) {
            for (auto it = requiredStreams.begin(); it != requiredStreams.end(); ++it) {
                if (output.scriptPubKey == it->first && output.nValue == it->second) {

        if (!requiredStreams.empty()) {
            return state.DoS(100, error("%s: funding stream missing", __func__), REJECT_INVALID, "cb-funding-stream-missing");
    } else {
        // Coinbase transaction must include an output sending 20% of
        // the block reward to a founders reward script, until the last founders
        // reward block is reached, with exception of the genesis block.
        // The last founders reward block is defined as the block just before the
        // first subsidy halving block, which occurs at halving_interval + slow_start_shift
        if ((nHeight > 0) && (nHeight <= consensusParams.GetLastFoundersRewardBlockHeight())) {
            bool found = false;

            for (const CTxOut& output : block.vtx[0].vout) {
                if (output.scriptPubKey == Params().GetFoundersRewardScriptAtHeight(nHeight)) {
                    if (output.nValue == (GetBlockSubsidy(nHeight, consensusParams) / 5)) {
                        found = true;

            if (!found) {
                return state.DoS(100, error("%s: founders reward missing", __func__), REJECT_INVALID, "cb-no-founders-reward");



This proposal was originally intended to be deployed with the Blossom network upgrade. 7

Backward compatibility

This proposal intentionally creates what is known as a "bilateral consensus rule change". Use of this mechanism requires that all network participants upgrade their software to a compatible version within the upgrade window. Older software will treat post-upgrade blocks as invalid, and will follow any pre-upgrade branch that persists.

This proposal is designed with the explicit requirement of not altering the overall issuance schedule (based on time), nor does it alter the proportion or timeline of the overall Founders' Reward. As a result, no users outside of the Zerocoin Electric Coin Company and Zcash Foundation should experience any UX or economic change outside of the upgrade due to this proposal itself.

Interactions with other ZIPs

4 (Shorter Block Target Spacing) specifies a change to the block target spacing. It is planned to take effect in the Blossom network upgrade 7. This ZIP was originally written to take effect at the same time, but was Withdrawn from consideration for Blossom.

ZIP 208 modifies the payment of the original Founders' Reward to take account of the block target spacing change. It does this by specifying a FounderAddressAdjustedHeight function and related changes, which would need to be revisited to take into account funding streams.

Reference Implementation



1 Key words for use in RFCs to Indicate Requirement Levels
2 Section 7.7: Calculation of Block Subsidy and Founders' Reward. Zcash Protocol Specification, Version 2018.0-beta-33 or later [Overwinter+Sapling]
3 Continued Funding and Transparency
4 ZIP 208: Shorter Block Target Spacing
5 Section 7.8: Payment of Founders' Reward. Zcash Protocol Specification, Version 2018.0-beta-33 or later [Overwinter+Sapling]
6 Section 5.3: Constants. Zcash Protocol Specification, Version 2018.0-beta-33 or later [Overwinter+Sapling]
7 ZIP 206: Blossom Network Upgrade