Search…
About Bancor Network
Bancor V3
Bancor Basics
Resources
Token Whitelisting Requirements
Security & Audits
Developer Guides
Contracts
Write Functions
Read Functions
Data & Events
Other Guides
Bancor Vortex Burner
Bancor V3 Beta Tutorial
Migration to V3 Tutorial
Migrating V2.1 Protected Positions
Joining Standard Rewards
Marketing
Brand Guide
Powered By GitBook
Migrating V2.1 Protected Positions
This section outlines the process to migrate Bancor V2.1 protected positions to Bancor V3.
This process calculates all your available rewards and might be expensive

1. Identify your protected position(s)

This step explains how to identify your protected position IDs.
  • Visit the LiquidityProtectionStore contract on etherscan​
  • Execute the protectedLiquidityIds function (this is a Read function)
​
​
Input variable
Name
Type
Description
_provider
address
Your wallet address
Output response
Name
Type
Description
id(s)
uint256
1 or more unique IDs that indicate the protected positions for the specified address

2. Identify protected position data

This section explains how to identify the relevant data based on the unique protected position ID.
  • Visit the LiquidityProtectionStore contract on etherscan​
  • Execute the protectedLiquidity function (this is a Read function)
​
​
Input variable
Name
Type
Description
_id
uint256
A unique protected position ID
Output response
Name
Type
Description
provider
address
The wallet address of the position owner
poolToken
token
The pool token address * (i.e. LINK/BNT pool token address)
reserveToken
token
The reserve token address * (i.e. LINK token address)
poolAmount
uint256
Pool token amount *
reserveAmount
uint256
Reserve token amount
reserveRateN
uint256
Rate of 1 protected reserve token in units of the other reserve token (numerator)
reserveRateD
unit256
Rate of 1 protected reserve token in units of the other reserve token (denominator)
timestamp
unit256
Timestamp of the original deposit
* These values are needed for the migratePositions function

3. Migrate your protected positions

Now that you have your V2.1 protected position(s) data available, you can proceed in calling the migration function and move the funds to Bancor V3.
This process will migrate the full position and update the protection to 100% as a bonus
Important:
During Beta, pool deposits are limited and might cause Metamask to show errors. Use at your own discretion.
Visit the LiquidityProtection contract on etherscan​
  • Execute the migratePositions function (this is a Write function)
​
​
Input variable
Name
Type
Description
positionLists
PositionList
Array of data to define the pool, token and positions.
1
Format example:
2
[["poolTokenAddress", "reserveTokenAddress", [ID1, ID2, ..]]]
3
[["0x5B38Da6a701c568545dCfcB03FcB875f56beddC4","0x5B38Da6a701c568545dCfcB03FcB875f56beddC4",[1,2,3]]]
4
​
Copied!
You can group multiple IDs with the same poolToken and reserveToken combination i.e. all IDs for LINK from the LINK/BNT pool
Once executed successfully, the following will happen:
  1. 1.
    The v2.1 protected position(s) will no longer exist
  2. 2.
    The value of the protected tokens will be staked into Bancor V3
  3. 3.
    You would receive bnTokens that represent your migration
If you wish to participate in Standard Rewards, proceed to Joining Standard Rewards guide
​

​

Other Guides - Previous
Migration to V3 Tutorial
Next
Joining Standard Rewards
Last modified 10d ago
Copy link
Contents
1. Identify your protected position(s)
2. Identify protected position data
3. Migrate your protected positions