Core Concepts
CRP Tutorial
CRP Tutorial
Similar to Core Pools, Configurable Rights Pools are created from a public factory. Refer to Addresses to find the contract on your network of choice.
To deploy a new Configurable Rights Pool, call newCRP on the CRPFactory. This function takes three parameters (cheating a bit, since two of them are big structs):
1
function newCrp(
2
address factoryAddress,
3
ConfigurableRightsPool.PoolParams calldata poolParams,
4
RightsManager.Rights calldata rights
5
)
6
external
7
returns (ConfigurableRightsPool)
Copied!
The factoryAddress is that of the BFactory (see Core Concepts). The Configurable Rights Pool is the Smart Pool "wrapper" around the underlying Core Pool (BPool). You (caller of newCRP) are the controller of the Smart Pool. The Smart Pool is the controller of the Core Pool. So the Smart Pool needs to deploy a Core Pool - and requires the BFactory to do that.
The next argument is PoolParams - this is where you define the structure and basic parameters of the pool, such as the tokens it will hold, their initial weights and balances, and the swap fee.
1
struct PoolParams {
2
// Balancer Pool Token (representing shares of the pool)
3
string poolTokenSymbol;
4
string poolTokenName;
5
// Tokens inside the Pool
6
address[] constituentTokens;
7
uint[] tokenBalances;
8
uint[] tokenWeights;
9
uint swapFee;
10
}
Copied!
Since the Balancer Pool Tokens are themselves ERC20 tokens, they have symbols and names. You can set both when creating your pool.
The tokens must be addresses of conforming ERC20 tokens. Balances and weights are expressed in Wei - and the weights are denormalized, not percentages. Valid denormalized weights range from 1 to 49, since the maximum total denormalized weight is 50. (This corresponds to a percentage range from 2% to 98%: 1/(1+49) = 2%; 49/(1+49) = 98%)
Note that balances must be "normalized" for the number of decimals in the token. For instance, USDC has 6 decimals, so "10" is "10000000" - not "10000000000000000000"!
Note that if you're going to be doing gradual weight updates, using denorm totals near the maximum 50 can be problematic! It is possible for
pokeWeightsto fail if the weights are 45/5, since the contract will never allow the total to go over 50 - even temporarily during an intermediate step. Unless you truly need the full range, best practice is to use a lower total, like 40; e.g.; for 90/10, use 36/4. (If you need to use extreme weights, put tokens whose weights should go down first in the array; that way the weight reductions will be processed before the increases.)Also note that adding new tokens (to pools with the addRemoveTokens right), and direct calls to updateWeight have stricter decimal limits. Core pools support tokens from 6-18 decimals. Smart pools can hold the full range of tokens - but only support addToken/updateWeight operations on 12-18 decimal tokens.
The swap fee is also expressed in Wei, as a percentage. For instance, toWei("0.01") means a 1% fee.
Finally, the Rights struct defines the permissions.
1
struct Rights {
2
bool canPauseSwapping;
3
bool canChangeSwapFee;
4
bool canChangeWeights;
5
bool canAddRemoveTokens;
6
bool canWhitelistLPs;
7
bool canChangeCap;
8
}
Copied!
Note that if you are whitelisting LPs, and intend for the whitelisted users to Add Liquidity through the Balancer GUI, you will need to whitelist their DSProxy addresses - not their wallet address. (The DSProxy address can be found at the bottom of the wallet page. New users will need to create a DSProxy before adding liquidity.)
At this point (after calling newCRP), we have a deployed Configurable Rights Object with all its permissions and parameters defined. But we can't do much with it - mainly because there is no Core Pool yet. We need to deploy a new Core Pool, with our Smart Pool as the controller, by calling createPool(initialSupply). (There is also an overloaded version of createPool; more on that later.)
We've already defined the tokens and balances we want the pool to hold. When we call createPool with a value for initialSupply, it will mint initialSupply Balancer Pool Tokens (BPTs) and transfer them to the caller, simultaneously pulling the correct amount of collateral tokens into the contract. (They end up in the Core Pool, passed through the CRP.)
To accomplish this, we need to allow the CRP to spend our collateral tokens, before calling createPool. For an example three-token pool, we might write:
1
const MAX = web3.utils.toTwosComplement(-1);
2
​
3
// crpPool was returned from CRPFactory.newCRP()
4
​
5
await weth.approve(crpPool.address, MAX);
6
await dai.approve(crpPool.address, MAX);
7
await xyz.approve(crpPool.address, MAX);
8
​
9
// consume the collateral; mint and xfer 100 BPTs to caller
10
await crpPool.createPool(toWei('100'));
Copied!
Now we're in business! The pool will already be set up for public swapping, and depending on the permissions settings, possibly public liquidity provision as well. The Core Pool will show up on the Exchange GUI.
Refer to Exchange and Reward Listing for instructions on adding any new tokens you might be introducing to the Exchange GUI, and making them eligible for BAL governance tokens. Earnings are distributed weekly, and are not applied retroactively, so you'll need to have the token approved by 00:00 UTC the Monday before you launch your pool.
If your smart pool is eligible for BAL, earnings will be redirected to LPs - as long as you create the pool through our standard factory. If you create a new pool using a different factory, or deploy a pool contract directly, you will need to apply for a redirect or redistribution. (You will also need a redirect if your CRP controller is a contract that holds BPTs, and doesn't have a way to withdraw them.)
The process for the redirect is to make a pull request to update this file in our script repository with the CRP and your wallet address, along with proof that you own the pool (e.g., the CRP deployment transaction hash). Here's an example request. Similarly, if you have a CRP and want to handle the redistribution differently, you can make a pull request to update this file.
On a related note, while it is possible to send tokens directly to a core pool contract - as long as they are in the pool, you they can be recovered with gulp() - this is not the case for smart pools! Any tokens sent directly to the CRP contract will be unrecoverable. (This can happen in some circumstances even without a direct transfer, such as airdrops to token holders.)
Note that there is also an overloaded version of createPool, where you can specify additional parameters related to updateWeightsGradually.
1
function createPool(
2
uint initialSupply,
3
uint minimumWeightChangeBlockPeriod,
4
uint addTokenTimeLockInBlocks
5
)
Copied!
If the pool you're creating doesn't have permission to change weights, or you accept the default values of the time parameters, you can just use the single-argument version.
initialSupply can be set to a value of your choice - within min/max limits (currently 100 - 1 billion, in ether units).
minimumWeightChangeBlockPeriod enforces a minimum time between the start and end blocks of a gradual update. addTokenTimeLockInBlocks is used when adding a token (if you have the AddRemoveTokens permission), as the minimum wait time between committing a new token, and applying it (i.e., actually adding it to the pool). There is one additional constraint: minimumWeightChangeBlockPeriod >= addTokenTimeLockInBlocks.
These parameters have default values, and can only be changed by overriding them in this version of createPool. The addTokenTimeLock defaults to 500 blocks (~ 2 hours), and the blockPeriod defaults to 90,000 (~ 2 weeks). If you want to use different minimum values, be sure to set them in createPool, since they are immutable thereafter!
Also note that these only apply to gradual updates. The controller can call updateWeight directly at any time, as long as no gradual update is in progress.
The GUI displays the approximate dates for the block numbers you enter. Some protocols (e.g., UMA) use UNIX timestamps for time-related inputs. If you are calling it programmatically, make sure you use block numbers, not timestamps!
Luckily,
updateWeightsGradually is forgiving - even if this happens, you don't have to wait five centuries for the block numbers to catch up to the timestamp (currently ~ 2600 AD); just call it again with the correct values.You can use this simulator to explore how weight changes and updates work, estimate slippage and impermanent loss, etc. There is also a demo video illustrating the simulator functionality.
Complex functionality = lots of simulators! This one helps you calculate single- and multi-asset entry and exit.
Last modified 3mo ago