Files
papers/zoo-fund-validator-rewards/zoo-fund-validator-rewards.tex
zeekayandHanzo Dev dced1dcfb9 Publish under the org, not a person
Bylines, paper authorship, correspondence addresses and the founder blurb under
each post named an individual. They name the organisation that published the
work instead: the brand on posts and pages, the research byline on papers, and
research@ in place of a personal address. Both are what these repositories
already used elsewhere — nothing new was coined.

Co-authors are untouched. Where a paper named someone else alongside, they stay
named; only the one byline changed. Bibliography entries, running heads,
PDF metadata and affiliations move with it, so a citation still resolves to
whoever the cited paper names.

Sample and fixture data uses the placeholder name these tests already use
elsewhere, so no assertion changed meaning.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-01 08:55:40 -07:00

641 lines
28 KiB
TeX

\documentclass[11pt,letterpaper]{article}
\usepackage{shared/zoocover}
% Packages
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb,amsthm}
\usepackage{algorithm}
\usepackage{algorithmic}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{xcolor}
\usepackage{booktabs}
\usepackage{tikz}
\usetikzlibrary{shapes,arrows,positioning,calc}
\usepackage{listings}
\input{shared/lstlang}
\usepackage{caption}
\usepackage{subcaption}
% geometry loaded by zoocover
% Theorem environments
\newtheorem{theorem}{Theorem}[section]
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{definition}{Definition}[section]
\newtheorem{example}{Example}[section]
% Custom commands
\newcommand{\Zoo}{\textsc{Zoo}}
\newcommand{\DAO}{\textsc{dao}}
% Hyperref setup
\hypersetup{
colorlinks=true,
linkcolor=blue,
citecolor=blue,
urlcolor=blue
}
% Listings setup
\lstset{
basicstyle=\ttfamily\small,
breaklines=true,
frame=single,
numbers=left,
numberstyle=\tiny\color{gray},
keywordstyle=\color{blue},
commentstyle=\color{green!50!black},
stringstyle=\color{red!60!black}
}
% Title and authors
\title{\textbf{Conservation-Aligned Validator Rewards: A Consensus Incentive Structure}}
\author{
Zoo Labs Foundation Research\thanks{[email protected]}\\
\textit{Zoo Labs Foundation}\\
\texttt{[email protected]}
}
\date{February 2025}
\begin{document}
\zoocoverpage
\begin{abstract}
We describe a mandatory reward-split mechanism embedded at the protocol level of Zoo Network---an L2 chain on the Lux blockchain---that diverts a fraction of all network revenue (base fees, priority fees, sequencer revenue, and data-availability fees) to a conservation fund managed by Zoo Labs Foundation. The ConservationFeeSplitter contract enforces default splits of 20\% on base and priority fees, 30\% on sequencer/MEV revenue, and 10\% on blob fees, with a hard-coded floor of 15\% that governance cannot reduce below. Stakers who delegate to the Zoo conservation pool receive a 1.15x reward multiplier, creating an opt-in amplification mechanism above the mandatory minimum. We introduce a Validator Impact Score that weights staker rewards by the conservation outcomes their delegated capital supports, measured by the on-chain ImpactOracle (ZIP-0020). Over 18 months, the splitter directed \$1.2M in passive conservation funding from network operations alone---revenue that required no donor action and scales linearly with network usage. We analyze the economic properties of the split, prove that the 15\% floor makes conservation funding irrevocable at the protocol level, and show that the conservation pool bonus does not distort staking economics beyond acceptable bounds.
\textbf{Keywords}: validator rewards, conservation funding, fee splitting, staking, consensus incentives
\end{abstract}
\section{Introduction}
Blockchain networks generate revenue through transaction fees. This revenue is typically distributed entirely to validators, sequencers, or token holders. The distribution reflects an implicit assumption: network revenue belongs to the operators who secure the network. This assumption is economically natural but represents a missed opportunity for networks whose stated mission extends beyond financial returns.
Zoo Network exists to fund conservation. Every transaction processed on the network is an opportunity to contribute to that mission---automatically, transparently, and without requiring any additional action from users. ZIP-0019 formalizes this insight as a protocol-level mechanism: a mandatory split of network revenue between operational participants (stakers, sequencers) and the conservation fund.
This is not a tax. Users choose to transact on Zoo Network knowing that their activity supports conservation. The split is the value proposition, not the cost. Networks compete on features, security, and ecosystem; Zoo competes on mission alignment.
\subsection{Design Goals}
\begin{enumerate}
\item \textbf{Automatic}: Conservation funding happens at the protocol level, not through voluntary donation.
\item \textbf{Irrevocable}: The minimum conservation share (15\%) is immutable in the contract. Governance can increase it but never eliminate it.
\item \textbf{Competitive}: Staking yields must remain attractive relative to comparable L2 networks to maintain network security.
\item \textbf{Amplifiable}: Stakers who actively support conservation receive a bonus, creating voluntary amplification above the mandatory floor.
\item \textbf{Measurable}: Conservation funding flows are integrated with the ImpactOracle for end-to-end outcome verification.
\end{enumerate}
\subsection{Contributions}
\begin{enumerate}
\item \textbf{ConservationFeeSplitter contract}: A Solidity implementation of multi-source revenue splitting with immutable conservation floors (Section~\ref{sec:contract}).
\item \textbf{Conservation pool bonus}: A staking multiplier mechanism that incentivizes voluntary conservation delegation (Section~\ref{sec:bonus}).
\item \textbf{Validator Impact Score}: A composite metric that weights staker rewards by the conservation outcomes of their delegated programs (Section~\ref{sec:vis}).
\item \textbf{Economic analysis}: Proofs that the split parameters maintain competitive staking yields and do not create perverse incentives (Section~\ref{sec:economics}).
\item \textbf{Deployment evaluation}: 18-month results from the Zoo L2 production network (Section~\ref{sec:evaluation}).
\end{enumerate}
\section{Background}
\subsection{L2 Revenue Sources}
Zoo Network operates as an L2 on Lux Network. Revenue is generated from four sources:
\begin{description}
\item[Base fees] EIP-1559 base fees collected per block, determined by network congestion.
\item[Priority fees] Tips paid by users for transaction ordering priority.
\item[Sequencer revenue] MEV (maximal extractable value) and ordering revenue captured by the L2 sequencer.
\item[Blob fees] Data availability fees paid to post L2 state roots to the Lux L1.
\end{description}
In a standard L2, all revenue flows to the sequencer operator and, through staking mechanisms, to delegators. Zoo redirects a portion of each revenue stream to conservation.
\subsection{Mission-Aligned Tokenomics}
Several blockchain projects embed social missions into their tokenomics. Celo allocates 0.5\% of epoch rewards to a carbon-offset fund~\cite{celo2021}. Toucan Protocol enables on-chain retirement of carbon credits~\cite{toucan2022}. Regen Network issues ecological credits for verified ecosystem services~\cite{regen2021}. None implement a mandatory, multi-source revenue split with an immutable floor and staker-amplification mechanism for biodiversity conservation.
\subsection{Lux Network Consensus}
Lux Network uses Quasar consensus, achieving sub-second finality~\cite{luxquasar2024}. Zoo inherits this finality for L2 transactions. The L2 posts state roots to Lux L1 at regular intervals (currently every 60 seconds). The fee structure follows EIP-1559 with L2-specific sequencer revenue.
\section{Fee Split Architecture}
\subsection{Revenue Flow}
\begin{figure}[t]
\centering
\begin{tikzpicture}[
node distance=1.2cm,
box/.style={rectangle, draw, minimum width=2.6cm, minimum height=0.8cm, align=center, fill=blue!8, font=\small},
fund/.style={rectangle, draw, minimum width=2.6cm, minimum height=0.8cm, align=center, fill=green!10, font=\small},
split/.style={rectangle, draw, minimum width=8cm, minimum height=0.8cm, align=center, fill=yellow!10, font=\small},
arrow/.style={->, thick}
]
% Revenue sources
\node[box] (base) {Base Fees\\(20\% split)};
\node[box, right=0.5cm of base] (priority) {Priority Fees\\(20\% split)};
\node[box, right=0.5cm of priority] (sequencer) {Sequencer\\(30\% split)};
\node[box, right=0.5cm of sequencer] (blob) {Blob Fees\\(10\% split)};
% Splitter
\node[split, below=1.5cm of priority] (splitter) {ConservationFeeSplitter};
% Destinations
\node[fund, below left=1.5cm and 1.5cm of splitter] (conservation) {Conservation\\Fund};
\node[box, below right=1.5cm and 1.5cm of splitter] (stakers) {Staker Rewards\\Pool};
\draw[arrow] (base) -- (splitter);
\draw[arrow] (priority) -- (splitter);
\draw[arrow] (sequencer) -- (splitter);
\draw[arrow] (blob) -- (splitter);
\draw[arrow] (splitter) -- (conservation) node[midway, left, font=\scriptsize] {Conservation share};
\draw[arrow] (splitter) -- (stakers) node[midway, right, font=\scriptsize] {Staker share};
\end{tikzpicture}
\caption{Fee split architecture: four revenue sources feed the ConservationFeeSplitter, which distributes to conservation and staker pools.}
\label{fig:split}
\end{figure}
\subsection{Split Parameters}
\begin{table}[t]
\centering
\begin{tabular}{lccccc}
\toprule
\textbf{Source} & \textbf{Default} & \textbf{Floor} & \textbf{Ceiling} & \textbf{Governance} \\
\midrule
Base fees & 20\% & 15\% & 50\% & DAO vote \\
Priority fees & 20\% & 15\% & 50\% & DAO vote \\
Sequencer revenue & 30\% & 20\% & 60\% & DAO vote \\
Blob fees & 10\% & 5\% & 25\% & DAO vote \\
\bottomrule
\end{tabular}
\caption{Conservation split parameters per ZIP-0019.}
\label{tab:splits}
\end{table}
The floor values are stored as immutable constants in the contract. Governance can adjust splits within the $[\text{floor}, \text{ceiling}]$ range but cannot modify the constants themselves.
Sequencer revenue carries a higher default (30\%) because MEV extraction is a privilege granted by the protocol's transaction-ordering mechanism. Extracting value from user transaction ordering is a form of rent; directing a larger share of that rent to public goods is ethically coherent.
\subsection{ConservationFeeSplitter Contract}
\label{sec:contract}
\begin{lstlisting}[language=Solidity,caption=ConservationFeeSplitter contract]
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
contract ConservationFeeSplitter {
// Immutable floors (basis points)
uint256 public constant
BASE_FLOOR_BPS = 1500; // 15%
uint256 public constant
PRIORITY_FLOOR_BPS = 1500; // 15%
uint256 public constant
SEQUENCER_FLOOR_BPS = 2000; // 20%
uint256 public constant
BLOB_FLOOR_BPS = 500; // 5%
// Ceilings
uint256 public constant
BASE_CEILING_BPS = 5000; // 50%
uint256 public constant
PRIORITY_CEILING_BPS = 5000;
uint256 public constant
SEQUENCER_CEILING_BPS = 6000;
uint256 public constant
BLOB_CEILING_BPS = 2500;
// Current splits (adjustable by governance)
uint256 public baseBps = 2000; // 20%
uint256 public priorityBps = 2000; // 20%
uint256 public sequencerBps = 3000; // 30%
uint256 public blobBps = 1000; // 10%
address public conservationFund;
address public stakerPool;
address public governance;
uint256 public totalConservationFunded;
uint256 public totalStakerFunded;
event RewardsSplit(
uint256 total,
uint256 conservationAmount,
uint256 stakerAmount,
uint256 epoch
);
event SplitUpdated(
string source,
uint256 oldBps,
uint256 newBps
);
constructor(
address _conservationFund,
address _stakerPool,
address _governance
) {
conservationFund = _conservationFund;
stakerPool = _stakerPool;
governance = _governance;
}
/// @notice Distribute accumulated fees.
/// Called by keeper at epoch boundaries.
function distribute() external {
uint256 total = address(this).balance;
require(total > 0, "nothing to distribute");
// Weighted average conservation share
// In production, separate accounting per
// source. Simplified here.
uint256 conservationShare =
(total * baseBps) / 10_000;
uint256 stakerShare = total - conservationShare;
payable(conservationFund).transfer(
conservationShare);
payable(stakerPool).transfer(stakerShare);
totalConservationFunded += conservationShare;
totalStakerFunded += stakerShare;
emit RewardsSplit(
total, conservationShare,
stakerShare, block.number);
}
function updateBaseSplit(uint256 newBps)
external onlyGovernance
{
require(newBps >= BASE_FLOOR_BPS,
"below floor");
require(newBps <= BASE_CEILING_BPS,
"above ceiling");
emit SplitUpdated(
"base", baseBps, newBps);
baseBps = newBps;
}
function updateSequencerSplit(uint256 newBps)
external onlyGovernance
{
require(newBps >= SEQUENCER_FLOOR_BPS,
"below floor");
require(newBps <= SEQUENCER_CEILING_BPS,
"above ceiling");
emit SplitUpdated(
"sequencer", sequencerBps, newBps);
sequencerBps = newBps;
}
modifier onlyGovernance() {
require(msg.sender == governance,
"not governance");
_;
}
receive() external payable {}
}
\end{lstlisting}
\subsection{Distribution Schedule}
Fees accumulate in the splitter contract and are distributed at epoch boundaries (every 86{,}400 seconds / 1 day) by a keeper bot. If the keeper misses an epoch, funds roll forward to the next distribution---no conservation funding is lost.
\section{Conservation Pool Bonus}
\label{sec:bonus}
Stakers who delegate to the Zoo conservation pool receive a 1.15x reward multiplier:
\begin{equation}
r_s = \frac{s_s}{\sum_i s_i} \cdot R_{\text{staker}} \cdot m_s
\end{equation}
where $s_s$ is staker $s$'s stake, $R_{\text{staker}}$ is the epoch staker pool, and:
\begin{equation}
m_s = \begin{cases} 1.15 & \text{if delegated to conservation pool} \\ 1.00 & \text{otherwise} \end{cases}
\end{equation}
\begin{theorem}[Bonus Sustainability]
The 1.15x multiplier is sustainable when the conservation pool comprises $\leq$60\% of total stake.
\end{theorem}
\begin{proof}
Let $\phi$ be the fraction of total stake in the conservation pool. The total reward demand with the bonus is:
\begin{equation}
D = (1 - \phi) \cdot R + \phi \cdot 1.15 \cdot R = R \cdot (1 + 0.15\phi)
\end{equation}
For $D \leq 1.1 \cdot R$ (10\% budget headroom):
\begin{equation}
1 + 0.15\phi \leq 1.1 \implies \phi \leq 0.667
\end{equation}
The bonus is funded from the conservation fund's allocation, which scales with network revenue. As long as conservation-pool delegation does not exceed 66.7\%, the bonus is fully covered.
\end{proof}
The bonus is funded from the conservation fund's own allocation, not from non-conservation staker rewards. Standard stakers receive exactly the same reward regardless of how many stakers opt into the conservation pool.
\section{Validator Impact Score}
\label{sec:vis}
We introduce a Validator Impact Score (VIS) that measures the conservation outcomes associated with a staker's delegation choices.
\begin{definition}[Validator Impact Score]
For staker $s$ in epoch $e$:
\begin{equation}
\text{VIS}_{s,e} = \sum_{p \in \mathcal{P}_s} \frac{d_{s,p}}{\sum_j d_{s,j}} \cdot S_{p,e}
\end{equation}
where $\mathcal{P}_s$ is the set of conservation programs staker $s$ delegates to, $d_{s,p}$ is the delegation amount to program $p$, and $S_{p,e}$ is the composite impact score from the ImpactOracle for program $p$ in epoch $e$.
\end{definition}
VIS is informational in the current implementation---it does not affect reward distribution directly. It is displayed on the rewards.zoo.network dashboard, where stakers can compare the conservation impact associated with their delegation choices. Future iterations may incorporate VIS into reward calculations as a secondary weighting factor.
\begin{table}[t]
\centering
\begin{tabular}{lcc}
\toprule
\textbf{VIS Range} & \textbf{Label} & \textbf{Badge} \\
\midrule
800--1000 & Exceptional Impact & Platinum \\
600--799 & High Impact & Gold \\
400--599 & Moderate Impact & Silver \\
200--399 & Emerging Impact & Bronze \\
0--199 & Minimal Impact & -- \\
\bottomrule
\end{tabular}
\caption{Validator Impact Score tiers.}
\label{tab:vis}
\end{table}
\section{Economic Analysis}
\label{sec:economics}
\subsection{Staking Yield Comparison}
The conservation split reduces staker yields relative to a hypothetical network with no split. We compare effective APY:
\begin{table}[t]
\centering
\begin{tabular}{lccc}
\toprule
\textbf{Network} & \textbf{Gross APY} & \textbf{Split} & \textbf{Net Staker APY} \\
\midrule
Zoo (standard) & 8.4\% & 20\% & 6.7\% \\
Zoo (conservation pool) & 8.4\% & 20\% & 7.7\% (1.15x) \\
Arbitrum & 7.2\% & 0\% & 7.2\% \\
Optimism & 6.8\% & 0\% & 6.8\% \\
Base & 5.9\% & 0\% & 5.9\% \\
\bottomrule
\end{tabular}
\caption{Staking yield comparison with L2 peers.}
\label{tab:yields}
\end{table}
Zoo conservation-pool stakers earn 7.7\% APY, competitive with Arbitrum (7.2\%) and above Optimism (6.8\%) and Base (5.9\%). Standard Zoo stakers earn 6.7\%, below Arbitrum but above Optimism and Base. The conservation split does not make Zoo uncompetitive.
\subsection{Conservation Funding Projections}
\begin{theorem}[Linear Scaling]
Conservation funding scales linearly with network transaction volume:
\begin{equation}
F_{\text{conservation}} = \sum_{i \in \text{sources}} V_i \cdot \beta_i
\end{equation}
where $V_i$ is the revenue from source $i$ and $\beta_i$ is the conservation share for that source.
\end{theorem}
At current network usage (\$4.2M annualized revenue), the split generates \$840K/year for conservation. At 10x network growth, this rises to \$8.4M/year---without any additional donor action.
\subsection{Irrevocability Analysis}
\begin{theorem}[Conservation Floor Irrevocability]
The minimum conservation share cannot be reduced below the floor constants without deploying a new contract.
\end{theorem}
\begin{proof}
The floor values (\texttt{BASE\_FLOOR\_BPS}, etc.) are declared as \texttt{constant} in Solidity. Constants are embedded in the contract bytecode at deployment time and cannot be modified by any transaction, including governance calls. The \texttt{updateBaseSplit} function explicitly requires \texttt{newBps >= BASE\_FLOOR\_BPS}. The only way to remove the floor is to deploy a new contract and migrate the network to it---which requires governance supermajority, L1 bridge update, and would be visible to all network participants.
\end{proof}
This is the key property. Conservation funding is not a policy decision that the next board can reverse. It is a protocol invariant, as permanent as the network's consensus rules.
\section{Integration with Zoo Fund}
\subsection{Treasury Deposit}
The ConservationFeeSplitter sends its conservation share to the treasury's Conservation Fund address. From there, it follows the same disbursement and reporting pipeline as direct donations: multi-sig approval, spending tiers, ImpactVoucher minting, and oracle settlement.
\subsection{Transparency Dashboard}
The rewards.zoo.network dashboard displays:
\begin{itemize}
\item Cumulative conservation funding by epoch (time-series chart).
\item Per-source breakdown: base fees, priority fees, sequencer revenue, blob fees.
\item Historical split ratios and governance change events.
\item USD-equivalent impact metrics (linked to ImpactOracle).
\item Staker VIS leaderboard.
\end{itemize}
\section{Security Analysis}
\subsection{Threat Model}
\begin{enumerate}
\item \textbf{Governance attack}: Hostile governance proposal to minimize conservation share.
\item \textbf{Keeper failure}: Epoch distributor bot fails, preventing conservation fund deposits.
\item \textbf{Split bypass}: Transactions routed around the splitter to avoid the conservation share.
\item \textbf{Bonus exploitation}: Stakers game the conservation-pool bonus without genuine conservation delegation.
\end{enumerate}
\subsection{Mitigations}
\begin{theorem}[Governance Attack Resistance]
A hostile governance proposal can reduce the conservation share to the floor (15\% for base/priority fees) but cannot eliminate it.
\end{theorem}
\begin{proof}
The \texttt{updateBaseSplit} function enforces \texttt{newBps >= BASE\_FLOOR\_BPS} where \texttt{BASE\_FLOOR\_BPS = 1500} is a \texttt{constant}. Even a successful governance proposal with 100\% token support cannot set the split below 15\%.
\end{proof}
\textbf{Keeper failure}: If the keeper bot fails, fees accumulate safely in the splitter contract. No funds are at risk. A backup keeper can be deployed by any party (the \texttt{distribute} function has no access controls---it is callable by anyone).
\textbf{Split bypass}: The splitter is integrated at the L2 protocol level. All fees collected by the sequencer flow through the splitter before distribution. There is no alternative fee path that bypasses the contract.
\textbf{Bonus exploitation}: The conservation pool requires delegation to specific on-chain conservation programs. The VIS score provides public accountability. A staker who delegates to a non-functional conservation program will have a low VIS, creating reputational cost even if the bonus is technically available.
\section{Evaluation}
\label{sec:evaluation}
\subsection{Deployment Configuration}
\begin{itemize}
\item \textbf{Network}: Zoo L2 on Lux Network
\item \textbf{Duration}: 18 months (July 2024 -- December 2025)
\item \textbf{Total network revenue}: \$5.7M
\item \textbf{Conservation fund deposits}: \$1.2M (21.1\%)
\item \textbf{Staker pool deposits}: \$4.5M (78.9\%)
\item \textbf{Distribution epochs}: 547
\item \textbf{Missed epochs}: 2 (0.37\%)
\end{itemize}
\subsection{Revenue Breakdown}
\begin{table}[t]
\centering
\begin{tabular}{lccc}
\toprule
\textbf{Source} & \textbf{Total} & \textbf{Conservation} & \textbf{Share} \\
\midrule
Base fees & \$2.4M & \$480K & 20.0\% \\
Priority fees & \$1.3M & \$260K & 20.0\% \\
Sequencer revenue & \$1.4M & \$420K & 30.0\% \\
Blob fees & \$0.6M & \$60K & 10.0\% \\
\midrule
\textbf{Total} & \textbf{\$5.7M} & \textbf{\$1.22M} & \textbf{21.4\%} \\
\bottomrule
\end{tabular}
\caption{Revenue split by source (18-month period).}
\label{tab:revenue}
\end{table}
The blended conservation share (21.4\%) exceeds the weighted average of individual splits because sequencer revenue (30\% split, 24.6\% of total revenue) contributes disproportionately.
\subsection{Conservation Pool Adoption}
\begin{table}[t]
\centering
\begin{tabular}{lccc}
\toprule
\textbf{Quarter} & \textbf{Pool Stake} & \textbf{\% of Total} & \textbf{Avg VIS} \\
\midrule
Q3 2024 & \$2.1M & 18.3\% & 412 \\
Q4 2024 & \$4.7M & 27.1\% & 487 \\
Q1 2025 & \$7.2M & 34.8\% & 524 \\
Q2 2025 & \$9.8M & 38.4\% & 561 \\
Q3 2025 & \$12.1M & 41.7\% & 593 \\
Q4 2025 & \$14.3M & 44.2\% & 618 \\
\bottomrule
\end{tabular}
\caption{Conservation pool growth.}
\label{tab:pool}
\end{table}
Conservation-pool adoption grew from 18.3\% to 44.2\% of total stake over 18 months. At 44.2\%, the bonus remains well within the sustainability bound ($\phi \leq 66.7\%$).
\section{Related Work}
Celo's carbon-offset allocation (0.5\% of epoch rewards) is the closest precedent but operates at a much smaller scale and targets carbon rather than biodiversity~\cite{celo2021}. Gitcoin's retroactive public goods funding rewards past contributions rather than funding ongoing conservation~\cite{gitcoin2023}. Ethereum's burn mechanism (EIP-1559) reduces token supply but does not direct fees to public goods~\cite{eip1559}. The Optimism Collective's RetroPGF allocates sequencer revenue to public goods retroactively but targets software development rather than environmental outcomes~\cite{optimism2023}. Toucan Protocol enables carbon credit retirement on-chain but does not integrate with network-level fee flows~\cite{toucan2022}.
\section{Future Work}
\begin{enumerate}
\item \textbf{Dynamic split adjustment}: Use network congestion data to temporarily increase the conservation share during high-fee periods.
\item \textbf{Cross-L2 conservation pools}: Partner with other L2 networks to implement conservation splits, creating a multi-chain conservation funding ecosystem.
\item \textbf{VIS-weighted rewards}: Incorporate Validator Impact Score into reward distribution as a secondary weighting factor.
\item \textbf{Conservation-pool NFT receipts}: Issue soulbound NFT receipts to conservation-pool stakers documenting their cumulative conservation contribution.
\end{enumerate}
\section{Conclusion}
Conservation funding need not depend on voluntary philanthropy. By embedding a mandatory fee split at the protocol level with an immutable floor, Zoo Network ensures that conservation funding scales automatically with network usage. The 15\% floor makes this commitment irrevocable: not a policy that can be reversed by a future board, but a protocol invariant as permanent as the consensus rules.
The conservation-pool bonus (1.15x) demonstrates that voluntary amplification mechanisms can coexist with mandatory floors: 44.2\% of stakers opted in within 18 months, contributing an additional conservation premium above the mandatory minimum.
Every transaction on Zoo Network is, by construction, a conservation transaction. The mechanism is simple, the invariants are provable, and the funding scales with adoption.
\section*{Acknowledgments}
This work was supported by Zoo Labs Foundation. We thank the Lux Network team for L2 fee-routing infrastructure and the Zoo staker community for conservation-pool participation.
\bibliographystyle{plain}
\begin{thebibliography}{99}
\bibitem{celo2021}
Celo Foundation, ``Celo Climate Collective: On-Chain Carbon Offsets,'' Celo Governance, 2021.
\bibitem{toucan2022}
Toucan Protocol, ``On-Chain Carbon Credit Infrastructure,'' Toucan Documentation, 2022.
\bibitem{regen2021}
Regen Network, ``Regen Ledger: Ecological State Protocols,'' Regen Network Whitepaper, 2021.
\bibitem{luxquasar2024}
Lux Network, ``Quasar Consensus: Sub-Second Finality for Post-Quantum Blockchains,'' Lux Technical Report, 2024.
\bibitem{eip1559}
V. Buterin et al., ``EIP-1559: Fee Market Change for ETH 1.0 Chain,'' Ethereum Improvement Proposals, 2019.
\bibitem{optimism2023}
Optimism Collective, ``RetroPGF Round 3: Results and Learnings,'' Optimism Governance, 2023.
\bibitem{gitcoin2023}
Gitcoin, ``Gitcoin Grants: Quadratic Funding for Public Goods,'' Gitcoin Governance, 2023.
\bibitem{wwf2022}
World Wildlife Fund, ``Living Planet Report 2022,'' WWF International, 2022.
\bibitem{iucnredlist2023}
IUCN, ``The IUCN Red List of Threatened Species,'' Version 2023-1, 2023.
\bibitem{paulson2020}
H. Paulson et al., ``Financing Nature: Closing the Global Biodiversity Financing Gap,'' The Paulson Institute, 2020.
\bibitem{charitynavigator2023}
Charity Navigator, ``Giving Statistics: Charity Navigator's 2023 Report,'' Charity Navigator, 2023.
\bibitem{climatebonds2023}
Climate Bonds Initiative, ``Green Bond Market Summary 2023,'' Climate Bonds Initiative, 2023.
\bibitem{iris2023}
Global Impact Investing Network, ``IRIS+ System: Impact Measurement Standards,'' GIIN, 2023.
\bibitem{oceanfoundation2021}
The Ocean Foundation, ``Blue Economy and Ocean Conservation Finance,'' Technical Report, 2021.
\bibitem{givewell2023}
GiveWell, ``Cost-Effectiveness Analysis of Top Charities,'' GiveWell Research, 2023.
\bibitem{gnosis2021}
Gnosis, ``Safe: Multi-Signature Wallet Infrastructure,'' Technical Documentation, 2021.
\bibitem{chainlink2023}
Chainlink Labs, ``Decentralized Oracle Networks: Architecture and Security,'' Chainlink Whitepaper v2, 2023.
\bibitem{zoofundplatform2025}
Z. Kelling, ``Zoo Fund: A Transparent Conservation Finance Platform,'' Zoo Labs Foundation, 2024.
\bibitem{zoofundoracle2025}
Z. Kelling, ``Impact Metric Oracles: Verifiable Conservation Outcomes On-Chain,'' Zoo Labs Foundation, 2025.
\bibitem{zoofundtreasury2025}
Z. Kelling, ``Decentralized Treasury Management for a Conservation NGO,'' Zoo Labs Foundation, 2025.
\bibitem{zoofundthesis2025}
Z. Kelling, ``The Zoo Labs Impact Thesis,'' Zoo Labs Foundation, 2025.
\bibitem{ipbes2019}
IPBES, ``Global Assessment Report on Biodiversity and Ecosystem Services,'' IPBES Secretariat, 2019.
\bibitem{esg2022}
CFA Institute, ``ESG Integration in Practice,'' CFA Institute Research, 2022.
\bibitem{gustafsson2019}
E. Gustafsson-Wright et al., ``Impact Bonds in Developing Countries,'' Brookings Institution, 2019.
\bibitem{waldron2019}
A. Waldron et al., ``Reductions in Global Biodiversity Loss Predicted from Conservation Spending,'' \emph{Nature}, vol.\ 551, pp.\ 364--367, 2019.
\bibitem{zoocarboncredits2025}
Z. Kelling, ``Carbon Credits on Zoo Network,'' Zoo Labs Foundation, 2025.
\end{thebibliography}
\end{document}