Aura Repertoire on Base
Deployments
| Name | Address |
|---|---|
BalancerVault | 0xBA12222222228d8Ba445958a75a0704d566BF2C8 (opens in a new tab) |
Action: unstake
Parameters
| Name | Type | Description |
|---|---|---|
rewarder | string (required) | Address rewarder |
Withdraw funds from Aura.
Permissions:
REWARDER below refers to the auraBaseRewardPool contract address for the
corresponding Aura pool.
REWARDER · withdrawAndUnwrap
Redeem REWARDER tokens, then withdraw and unwrap BPT tokens.
-
Contract:
REWARDER -
Function:
withdrawAndUnwrap(uint256,bool)Parameter Constraint amount- claim-
Action: unstake_withdraw_proportional
Parameters
| Name | Type | Description |
|---|---|---|
rewarder | string (required) | Address rewarder |
Withdraw funds from Aura, then from the Balancer pool, withdrawing all assets proportionally.
Permissions:
REWARDER below refers to the auraBaseRewardPool contract address for the
corresponding Aura pool.
TOKEN below refers to the ERC-20 token address of the corresponding pool.
PID below refers to the Balancer pool ID.REWARDER · withdrawAndUnwrap
Redeem REWARDER tokens, then withdraw and unwrap BPT tokens.
-
Contract:
REWARDER -
Function:
withdrawAndUnwrap(uint256,bool)Parameter Constraint amount- claim-
BalancerVault · exitPool
Redeem BPT tokens from the corresponding Balancer pool and receive proportional amounts of TOKEN tokens in exchange.
-
Contract:
BalancerVault -
Function:
exitPool(bytes32,address,address,(address[],uint256[],bytes,bool))Parameter Constraint poolIdequal to PIDsenderequal to AVATARrecipientequal to AVATARrequest.assets- request.minAmountsOut- request.userDataSee the note below for details. request.toInternalBalance-
Note on userData:
userDatais a bytes-like parameter that must be ABI-encoded.- Scoping details:
- For
ComposableStablePools:userDatais scoped as [2], encoded as ["uint256"]. - For all other pool types:
userDatais scoped as [1], encoded as ["uint256"].
- For
Additional Resources:
- Balancer subgraphs (opens in a new tab) for obtaining
PoolType. - Balancer documentation (opens in a new tab) for
userDatastructure.
Action: unstake_withdraw_single_token
Parameters
| Name | Type | Description |
|---|---|---|
rewarder | string (required) | Address rewarder |
exitTokenAddress | string (required) | Address exitTokenAddress |
Withdraw funds from Aura, then from the Balancer pool, receiving a single asset specified by the exitTokenAddress.
Permissions:
REWARDER below refers to the auraBaseRewardPool contract address for the
corresponding Aura pool.
PID below refers to the Balancer pool ID.REWARDER · withdrawAndUnwrap
Redeem REWARDER tokens, then withdraw and unwrap BPT tokens.
-
Contract:
REWARDER -
Function:
withdrawAndUnwrap(uint256,bool)Parameter Constraint amount- claim-
BalancerVault · exitPool
Redeem BPT tokens from the corresponding Balancer pool and receive exitTokenAddress tokens in exchange.
-
Contract:
BalancerVault -
Function:
exitPool(bytes32,address,address,(address[],uint256[],bytes,bool))Parameter Constraint poolIdequal to PIDsenderequal to AVATARrecipientequal to AVATARrequest.assets- request.minAmountsOut- request.userDataSee the note below for details. request.toInternalBalance-
Note on userData:
userDatais a bytes-like parameter that must be ABI-encoded.- Scoping details:
- For all pool types,
userDatais scoped as[0, undefined, exitTokenIndex], encoded as["uint256", "uint256", "uint256"]. - Where
exitTokenIndexis determined by the position ofexitTokenAddresswithin the pool's tokens.
- For all pool types,
Additional Resources:
- Balancer subgraphs (opens in a new tab) for obtaining
PoolType. - Balancer documentation (opens in a new tab) for
userDatastructure.