PoolTogether V5 is the newest version of the prize savings protocol; where yield on deposits is awarded as random prizes to depositors. This version is designed to be a hyperstructure; an autonomous, immutable protocol that can be permissionlessly extended by anyone.
A prize savings protocol gives users a chance at a large upside without risking their deposit. Each day, the yield from deposits is awarded randomly as prizes. Users have a chance to win everyone else's yield!
What's New in V5
This version of the protocol brings some major improvements:
- Users can swap into prize tokens; there is no need to "activate" your tokens. This enables distribution through AMMs and other swap interfaces.
- Users automatically receive their prizes. No claim needed! The tokens will be transferred to their wallets.
- Supports multiple tokens, and all tokens share one big pool of prizes so that prizes are as large as possible!
This version is also our first "hyperstructure", in that:
- The core protocol is fully autonomous. There is no administrator or parameters than can be adjusted.
- The core protocol is immutable; no code can be changed.
- Anyone can add new tokens or yield sources to the protocol; it can be extended permissionlessly
- All "maintenance" functions can be triggered by anyone and are incentivized
In this way, anyone can build on the protocol and know that it will never change and cannot be stopped. It becomes a solid foundation on which prize savings can be built.
PoolTogether V5 will be deployed on Ethereum and every L2 (eventually). Each deployment will include the core contracts and a set of factories that allow anyone to easily extend the protocol with new tokens or yield sources.
The core contract is the Prize Pool; this is the contract that holds prize liquidity and disburses prizes. Each chain will be an island of prize liquidity; prizes won't be shared across chains.
Flow of Funds
Let's take a closer look at how funds would flow through a V5 deployment. Below is a simplified diagram:
- Users deposit tokens into Vaults.
- Vault yield is liquidated for POOL and sent to the Prize Pool contract.
- POOL Prizes are claimed and sent to the user
We can see that there are three main stages in the process: deposit, liquidation, and prize distribution.
When users "deposit into PoolTogether" they are really depositing into an ERC4626 vault that contributes its yield to the Prize Pool and tracks deposits using the Twab Controller.
The vault can be created by anyone; and PoolTogether V5 has a Vault Factory that makes deploying new vaults a snap. The default factory Vault is an ERC4626 Vault that uses another ERC4626 Vault to generate yield. When a user creates a new Vault they must pass the address of the ERC4626 yield vault. A Prize Pool can support any number of vaults.
In order for users to be eligible to win prizes, their balances must be tracked in the Twab Controller. The default PoolTogether vault doesn't actually store any balances internally; all balances are stored in the Twab Controller.
Yield accrued by the underlying 4626 vault is exposed to an external liquidator, which liquidates the yield and contributes the resulting POOL to the Prize Pool.
Interaction Diagram for a Deposit
The Twab Controller
The Twab Controller tracks a users historic balance, so that the protocol can determine how much liquidity they held between two timestamps. There is one controller per deployment. The "Twab" in the name stands for time-weighted average balance, which is the algorithm used to track balances. Any contract may use the Twab Controller to track balances.
The Twab Controller is really tracking two balances: the "owned" balance for a user and the "delegated" balance for a user:
- The "owned" balance is like their token balance; it's the amount of tokens that the user actually controls.
- The "delegated" balance is the total balance that has been delegated to the user. By default users delegate to themselves, but it may also include any balances that have been delegated to them by others.
Historic balance tracking is based on the delegate balance for the user. When querying
getTwabBetween it will return the balance that had been delegated to them.
Time-Weighted Average Balance
The Twab allows one to calculate the average balance that a user held between two timestamps. Whenever a user's delegate balance changes, the Twab Controller adds a new Twab "observation" to the ring buffer of observations for that user.
A twab observation includes:
- Timestamp: the current timestamp
- Balance: the current delegate balance
- Cumulative Balance: the cumulative twab
The cumulative balance is calculated using the formula:
Then we can compute the average balance held between observations by computing:
Yield from all the vaults is liquidated for POOL and contributed to the Prize Pool. This allows chance to be distributed proportionally to all vaults, and for there to be a single deep pool of prize liquidity. No oracles needed.
Each Vault has a corresponding Liquidation Pair that auctions yield for POOL tokens. Users interact with the Liquidation Pair in order to liquidate vault yield. The pair is responsible for pricing the yield and does so using a periodic continuous gradual dutch auction.
Externally-Owned Accounts should interact with the Liquidation Router, as it provides additional checks that ensure the swap occurs correctly.
Iteraction Diagram for a Liquidation
Periodic Continuous Gradual Dutch Auction
The Continuous Gradual Dutch Auction is an auction algorithm that prices tokens according to an emissions rate. The periodic variant periodically updates the emission rate to account for newly accrued yield.
In a nutshell, a CGDA releases a certain number of tokens per second for sale. It is trying to sell all of these tokens. The price decays if the available tokens increase, because that means sales are falling behind. As tokens are purchased, sales catch up to the emission schedule and so the price increases, as on a bonding curve. This ensures that the auction is as efficient as possible.
For our application, as yield accrues we need to adjust the emission rate for the CGDA. The Periodic CGDA divides time into periods, and updates the emission rate when it enters a new period; the emission rate is the available balance over the period duration. We configure the period duration and offset to match the draw period of the Prize Pool in order to ensure that there are liquidations for a vault for every draw.
Contributing to Prize Pool
When yield is liquidated, the POOL is transferred to the Prize Pool and the Vault tells the Prize Pool that it contributed. The Prize Pool recognizes the balance increase, and updates that vault's contribution.
The Prize Pool tracks contributions using an exponential weighted average. This means that contributions are "smoothed", in the sense that they are spread out over future draws. In the event that liquidations are sporadic, this ensures that a vault always has a chance to win.
Computes the contribution amount for draw with smoothing factor with total contribution :
For example, if a vault contributes 50 tokens before draw 1 and :
Even if liquidations are sporadic, each draw will have liquidity and the vault will have a chance to win.
The Prize Pool releases prizes in periodic Draws. Each Draw is allocated a portion of the prize liquidity, and the prize structure is determined by the number of prize claims from the previous draw. Prize claims for a Draw begin after the completion of a random number generation auction. Prize claims are incentivized by variable-rate gradual dutch auction so that users don't need to claim for themselves.
Draws are like a numbered timeframe; the Prize Pool is initialized with a draw period in seconds, and the first draw start time. Draw 1 is the first period of time, Draw 2 is the second period of time, etc. Each Draw goes through a lifecycle of states:
- Open: the open Draw is the one that is currently receiving contributions from vaults. It is the next draw to close.
- Closed: once the Draw end has elapsed, the draw is considered closed. It will no longer receive new contributions.
- Awarded: when the random number is submitted, the most recent closed draw becomes awarded and prizes can be claimed.
- Finalized: draws become finalized after one draw period has elapsed after they close. After this time no prizes can be claimed.
Each draw is allocated a portion of the contributed liquidity (according to the exponential weighted average above). This liquidity is then distributed across a number of prize tiers and a reserve. Each prize tier has a different prize count and odds of occurring. The reserve is used to fund the RNG auction and backstop prize claims in the event a prize tier runs out of liquidity. When a draw is awarded it computes the number of prize tiers based on the number of claims for the previous awarded draw.
Prize liquidity is distributed into prize tiers and the reserve.
The amount of liquidity that is allocated to a tier per draw is determined by the Prize Pool's configured number of tier shares and reserve shares. If the number of tiers is then the portion of liquidity allocated to a tier is:
Prize Counts and Odds
Each prize tier has a different prize count and odds of occurring. This enables liquidity to build up for prizes and to provide a spectrum of sizes and odds.
The prize count is computed based on the tier :
You can see how tier 0 is the grand prize, as it is the whole tier's liquidity. The highest tier has the highest number of prizes.
The tier odds are also tuned, such that the highest tier has a 100% chance of occurring every draw and the lowest tier (tier 0) occurs every draws. We call the grand prize period.
The formula is:
Where is the number of tiers. Play with it the Tier Odds in Desmos.
The combination of the count and odds results in a broad spectrum of large infrequent prizes and lots of small frequent prizes. Below is a visualization of the prize size over time for a simulation with 4 tiers:
You can see how the highest tier has many small, frequent prizes. While the grand prize builds up to become large and is awarded less frequently.
Adaptive Prize Count
When a draw is awarded, it adjusts the number of prize tiers based on how many prizes were claimed for the previous awarded draw.
We do this quite simply: by using a lookup table of estimated prize counts. When the Prize Pool is constructed it is configured with the grand prize period. The number of tiers must be 3 or greater, and less than or equal to 10. This means we just need to compute the estimated counts for the 8 unique number of tiers.
To compute the number of tiers, we lookup the number of tiers given the last prize claim count then add one. We add one to give room for the number of tiers to expand. It's expected that the highest tier is unclaimed; it's there as a "canary" to see if we need to expand the number of tiers. Unused liquidity is recycled back into prizes.
The Prize Pool sources the random number for the awarded draw from an RNG on Ethereum via a sequence of auctions. These auctions are paid out from the reserve that has accrued in the Prize Pool.
Each time a Draw is to be awarded, two auctions must be completed in sequence:
- RNG Auction: this is the auction to incentivize the RNG request. Some RNG sources, such as the Chainlink VRF, charge per use.
- RNG Relay Auction: this is the auction that incentivizes the bridging of the RNG results to the Prize Pool. It uses ERC-5164 so that bridge transport layers can be swapped easily.
The RNG auction lives on L1 (Ethereum) and the RNG Relay Auction lives on L2.
Interaction Diagram for RNG Auction
Interaction Diagram for the RNG Relay Auction
Since the RNG Auction lives on Ethereum and the Prize Pool lives on L2, there is no way that the auction can be priced according to the available reserve. Instead, we auction a fraction: the auction begins at zero, and increases until it reaches 1. This fraction is the portion of the reserve that the winner will capture. It is a percentage. The RNG Relay Auction also employs a fraction; in that it is a fraction of the reserve less the RNG auction, so that they don't allocate more than the reserve.
Additionally, since the RNG auction does not know when the draw closes, we tune the auction sequence period and offset to match the prize pool on L2. This means that they don't need to exchange any information. It also means that we can re-use the RNG auction for other prize pools, if they are correctly synchronized.
To encourage rapid and consistent price discovery, we use a Parabolic Fractional Dutch Auction. This auction has two phases, both of fixed length of time.
- The first phase is an inverted parabola, and it's origin places it at the last auction price.
- The second phase is a parabola whose origin begins at the auction price, and finishes at 1 at the end of the auction.
In this way, the system will rapidly settle to the previous auction prices.
Parabolic Fractional Dutch Auction
The auctions have an expiry period which, combined, is half of the draw period. This means that the draw must be awarded within the first half of the next open draw, otherwise it won't be awarded at all. This puts a lower limit on the remaining time to claim prizes during a draw.
After a draw has been awarded prizes can be claimed. Prizes can be claimed until the next Draw closes. Vaults claim on behalf of their users, which gives Vaults flexibility in how they want to handle prizes. The default PoolTogether Vault has a separate "Claimer" contract through which users claim prizes for others. Users call the claimer, which calls the Vault, which calls the Prize Pool.
Interaction Diagram for Prize Claiming
Once a draw is awarded, the last auction begins: the auction for prize claims. A variable-rate gradual dutch auction is used to reward anyone who claims a prize on a winner's behalf. The reward is taken from the prize itself. The Prize Pool allows Vaults to claim prizes on behalf of their users, so the claim behaviour can be customized by the vault. PoolTogether V5 provides a default VRGDA Claimer that works very well.
A VRGDA is a generalization of the continuous dutch auction, in that it raises prices when sales are ahead of schedule and lowers prices when sales are behind schedule.
For PoolTogether V5 we are using the VRGDA as a reverse dutch auction to claim prizes, so it lowers fees when claims are ahead of schedule and raises fees when claims are behind schedule. This allows us to ensure that all prizes are claimed before the next draw is awarded, at which point the prizes can no longer be claimed.
The "schedule" of claims is based on a count and timeframe. Recall the estimated claim count from the adaptive number of tiers? We use that same number to compute the schedule. The schedule starts immediately after the draw is awarded, and is set to take one quarter of the draw period. This provides plenty of leeway in the event that there are more prizes, statistically, for a given draw. It's highly unlikely that a draw will see a variance of double the expected prizes, so we believe a quarter of the draw period is sufficient.
The Prize Pool determines whether a user has won a prize by checking if a pseudo-random number is within a certain range. The PRN is generated such that it is unique per draw, tier, vault and user. The number range is used to tune the odds based on the prize frequency and the user's eligiblity.
There are three steps we take:
- Calculate the pseudo-random number
- Calculate the winning zone
- Check if the PRN is less than the winning zone
First we calculate a pseudo-random number is a keccak256 hash of the abi-encoded params:
uint256 pseudoRandomNumber = uint256(keccak256(abi.encode(drawId, vault, user, tier, prizeIndex, drawRandomNumber)))
We include the following params to ensure the PRN is unique:
drawId: the id for the awarded Draw
vault: the address of the vault that is claiming the prize
user: the address that won the prize
tier: the prize tier that was won
prizeIndex: the prize index within the tier that was won. E.g. if a tier 2 has prizes, then prize indices between 0 and 15 (inclusive) can be submitted.
drawRandomNumber: the Draw's random number
Next we calculate the winning zone. The winning zone is a multiple of three fractions: the user's time-weighted average balance, the tier odds, and the vault portion:
uint256 winningZone = tierOdds * userTwab * vaultPortion
- The tier odds is a function that determines the prize tier frequency
- The user's time-weighted average balance is the average balance they held for the duration of the prize tier accrual.
- The vault portion is the fraction of prize liquidity that was contributed by the vault for the duration of prize tier accrual.
The tier odds function creates a spectrum of prize frequencies between the yearly grand prize and the daily prizes. For more details see the Prize Pool.
The prize tier accrual duration is computed based on the tier odds. Essentially it's time periods based on the prize frequency function above; which means that accrual durations will range between one year and one day.
The user's time-weighted average balance is measured between the timestamps
drawClosedAt - duration and
drawClosedAt. E.g. for the yearly grand prize it will be their average balance for the preceding year, and for the daily prize it will be their balance for the preceding day.
The vault portion is the portion of prize liquidity that was contributed by the vault. It is also measured between two timestamps:
vaultPortion = vaultContributedPrizeLiquidityBetween(drawClosedAt - duration, drawClosedAt) / totalContributePrizeLiquidityBetween(drawClosedAt - duration, drawClosedAt)
Check if PRN in Winning Zone
Now that we have our PRN and Winning Zone, we can determine whether the user won a prize from a certain tier.
We first squeeze the PRN into a smaller PRN within the vault's total average supply for the prize tier accrual duration. Then, we check to see if that number is less than the winning zone.
bool userWon = PRN % vaultTotalAverageSupply(drawClosedAt - duration, drawClosedAt) < winningZone
Note that the above is simplified; we use a custom modulo function that handles modulo bias.
Claim Your Prize!
When a prize claim is submitted successfully, the Prize Pool transfers tokens to the winner and increases the claim rewards for the claimer (if any).