- Add setup for package - Add docs - Add balancer implementation and test - Add CI: - Add setup action - Add test and format CI - Add CD: Publish python package to AWS
3.0 KiB
3.0 KiB
Implementing a SwapExecutor for a Protocol
Overview
The SwapStructEncoder interface is designed to encode the necessary data for a swap, which will be used by the SwapExecutor to interact with a liquidity pool. The encoder is responsible for structuring the swap details, including the input/output tokens, pool addresses, and any additional protocol-specific parameters.
Each protocol must implement its own SwapStructEncoder and ensure that the swap data is correctly encoded for the SwapExecutor.
Dev environment
- Run
aws codeartifact login --tool pip --repository protosim --domain propellerso you can access the propeller packages. - Create the dev environment
conda env create -f propeller-swap-encoders/environment_dev.yaml - Activate it with
conda activate propeller-swap-encoders - Install dependencies with
pip install -r propeller-swap-encoders/requirements.txt - Should you get a pyyaml installation error execute the following command:
pip install "cython<3.0.0" && pip install --no-build-isolation pyyaml==5.4.1
You can import the abstract class SwapStructEncoder from propeller-solver-core in your python code like:
from core.encoding.interface import SwapStructEncoder
Key Methods
This is the SwapStructEncoder interface:
class SwapStructEncoder(ABC):
"""Encodes a PercentageSwap of a certain protocol to be used in our SwapRouterV2
Should be subclassed for each protocol that we support.
"""
@abstractmethod
def encode_swap_struct(
self, swap: dict[str, Any], receiver: Address, **kwargs
) -> bytes:
pass
- encode_swap_struct
- Purpose: To encode the swap details into a bytes object that the SwapExecutor can use to execute the swap.
- Parameters:
swap: A dictionary containing the swap details, such as input/output token addresses, amounts, and pool information.receiver: The address that will receive the output tokens from the swap.**kwargs: Any additional protocol-specific parameters that need to be included in the encoding.
- Returns: A bytes object containing the encoded swap data.
Implementation Steps
- Define Protocol-Specific Encoding Logic: Implement the
encode_swap_structfunction to encode the swap details specific to the protocol. This may include encoding token addresses, pool addresses, and other necessary parameters into a bytes format. - Compatibility with SwapExecutor: Ensure that the encoded data is compatible with the
SwapExecutorimplementation for the protocol. TheSwapExecutorwill rely on this data to perform the swap accurately. - Testing: Thoroughly test the encoding process with various swap scenarios to ensure that the encoded data is correct and that the
SwapExecutorcan process it without errors.
Example Implementation
See the example implementation of a SwapExecutor for Balancer here and test here.