This release includes a modification of the old astroport liquid pooler contract which works with cw20-based LP tokens.
The only changes between that contract and this one should be isolated to the way ExecuteMsg::Withdraw is handled.
This contract modifies that handler to work with the native tokenfactory LP tokens. No other changes should be necessary.
The new contract was excluded from the workspace so as to ensure that the build of the original v0.1.0 version contracts, that were audited, is reproducible. That is, the generated contract wasm files for all original contracts will have the exact same checksums as in the v0.1.0 release.
The new astroport-tf-liquid-pooler contract has undergone thorough testing (in both an integration test environment, and on the Neutron mainnet).
Testing
Because of different astroport versions causing conflicts in the same workspace, this contract is currently tested on its dedicated v0.1.1 release branch.
The local-interchaintest directory there contains the existing e2e tests that are modified to use this contract code id instead of the old one.
What's Changed
Full Changelog: v0.1.0...v0.1.1
valence_astroport_liquid_pooler.wasm 1683
valence_astroport_tf_liquid_pooler.wasm 1684
valence_clock.wasm 1685
valence_clock_tester.wasm 1686
valence_covenant_single_party_pol.wasm 1687
valence_covenant_swap.wasm 1688
valence_covenant_two_party_pol.wasm 1689
valence_ibc_forwarder.wasm 1690
valence_interchain_router.wasm 1691
valence_native_router.wasm 1692
valence_native_splitter.wasm 1693
valence_osmo_liquid_pooler.wasm 1694
valence_outpost_osmo_liquid_pooler.wasm 1695
valence_remote_chain_splitter.wasm 1696
valence_single_party_pol_holder.wasm 1697
valence_stride_liquid_staker.wasm 1698
valence_swap_holder.wasm 1699
valence_two_party_pol_holder.wasm 1700
