Migration to Liquidity Pools v2 about pools-subql HOT 7 CLOSED

@hieronx Here shall we just add the new pool managers to the indexer and these will listen to the new DeployTrancheToken events and therefore attach the new ERC-20 listeners, or did something change there in the implementation of the PoolManager?

from pools-subql.

@filo87 the ABI slightly changed I'm afraid. Here is the v2 version:

PoolManagerV2.abi.json

from pools-subql.

@hieronx is there a new poolManager contract also for sepolia?

from pools-subql.

Yes: 0x5aB7b672dAf72715A58cf0880F840abe0de4dC39

But we didn't do the migration there, so old tranche tokens are now unused and only new ones should be tracked. I think you should just remove the old v1 pool manager for sepolia for simplicity.

from pools-subql.

@hieronx other quick question... escrow and userescrow addresses stay the same across chains?

from pools-subql.

My bad, forgot this in the list of the changes.

There is actually no router escrow anymore.

For the escrow, in most cases this should be the same across chains, but we can't always guarantee it. Here's the list:

• Ethereum, Arbitrum, Base: 0x0000000005F458Fd6ba9EEb5f365D83b7dA913dD
• Celo: 0x9EDf9FC14DDBEE68CE1a69827b09794367180717

from pools-subql.

Just additional context: all addresses can always be found in https://github.com/centrifuge/liquidity-pools/tree/main/deployments

from pools-subql.