wayfinder-paths 0.1.7__tar.gz → 0.1.8__tar.gz

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: wayfinder-paths
-Version: 0.1.7
+Version: 0.1.8
 Summary: Wayfinder Path: strategies and adapters
 Author: Wayfinder
 Author-email: dev@wayfinder.ai
@@ -125,6 +125,7 @@ We welcome contributions! This is an open-source project where community members
 ### Contributor Guidelines
 
 #### For Adapters
+
 - **Start from the template**: Copy `wayfinder_paths/templates/adapter/` as a starting point
 - Extend `BaseAdapter` from `wayfinder_paths/core/adapters/BaseAdapter.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/adapter/manifest.yaml`) with:
@@ -138,6 +139,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### For Strategies
+
 - **Start from the template**: Use `just create-strategy "Strategy Name"` to create a new strategy with its own wallet, or copy `wayfinder_paths/templates/strategy/` manually
 - Extend `Strategy` from `wayfinder_paths/core/strategies/Strategy.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/strategy/manifest.yaml`) with:
@@ -151,6 +153,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### General Guidelines
+
 - **Code Quality**: Follow existing patterns and use type hints
 - **Testing**: See [TESTING.md](TESTING.md) - minimum: smoke test for strategies, basic tests for adapters
 - **Documentation**: Update README files and add docstrings
@@ -205,6 +208,7 @@ poetry run python wayfinder_paths/run_strategy.py your_strategy --action status
 ## 🏗️ Architecture
 
 ### Client System
+
 The platform uses a unified client system for all API interactions. Clients are thin wrappers that handle low-level API calls, authentication, and network communication. **Strategies should not call clients directly** - use adapters instead for domain-specific operations.
 
 ### Clients vs Adapters
@@ -231,6 +235,7 @@ Adapter manifests declare the capabilities an adapter provides and the clients i
 **Template:** Copy `wayfinder_paths/templates/adapter/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.my_adapter.adapter.MyAdapter"
@@ -243,12 +248,14 @@ dependencies:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the adapter class (required)
 - `capabilities`: List of abstract capabilities this adapter provides (required, non-empty)
 - `dependencies`: List of client class names from `core.clients` that this adapter requires (required, non-empty)
 
 **Example** (`wayfinder_paths/adapters/pool_adapter/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.pool_adapter.adapter.PoolAdapter"
@@ -269,6 +276,7 @@ Strategy manifests declare permissions and required adapters with their capabili
 **Template:** Copy `wayfinder_paths/templates/strategy/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.my_strategy.strategy.MyStrategy"
@@ -282,6 +290,7 @@ adapters:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the strategy class (required)
 - `name`: Strategy directory name (optional, used for wallet lookup - defaults to directory name)
@@ -291,6 +300,7 @@ adapters:
   - `capabilities`: List of capabilities required from this adapter
 
 **Example** (`wayfinder_paths/strategies/stablecoin_yield_strategy/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.stablecoin_yield_strategy.strategy.StablecoinYieldStrategy"
@@ -308,12 +318,14 @@ adapters:
 #### Manifest Validation
 
 Manifests are automatically validated to ensure:
+
 - Schema compliance (all required fields present, correct types)
 - Entrypoint classes exist and are importable
 - Dependencies are valid client classes
 - Permissions policies are non-empty
 
 **Validate locally:**
+
 ```bash
 # Validate all manifests
 just validate-manifests
@@ -348,6 +360,7 @@ The `validate_manifests.py` script performs multi-stage validation:
    - Policy syntax is not parsed/validated (assumed to be valid at runtime)
 
 **Validation Flow:**
+
 ```
 For each manifest file:
   1. Load YAML → Parse with Pydantic (schema validation)
@@ -357,6 +370,7 @@ For each manifest file:
 ```
 
 The script automatically discovers all manifests by scanning:
+
 - `wayfinder_paths/adapters/*/manifest.yaml` for adapter manifests
 - `wayfinder_paths/strategies/*/manifest.yaml` for strategy manifests
 
@@ -367,12 +381,15 @@ All errors are collected and reported at the end, with the script exiting with c
 Capabilities are abstract operation identifiers (e.g., `"pool.read"`, `"swap.execute"`) declared in manifests. They represent what operations an adapter can perform, not specific method names. The manifest is the **single source of truth** for capabilities—they are not duplicated in code.
 
 When creating an adapter:
+
 1. Declare capabilities in your `manifest.yaml`
 2. Implement methods that fulfill those capabilities
 3. Capabilities are validated at manifest validation time (entrypoint must be importable)
 
 ### Configuration
+
 Configuration is split between:
+
 - **User Config**: Your credentials and preferences
 - **System Config**: Platform settings
 - **Strategy Config**: Strategy-specific parameters
@@ -384,9 +401,11 @@ See [CONFIG_GUIDE.md](wayfinder_paths/CONFIG_GUIDE.md) for details.
 Wayfinder Paths supports two authentication methods:
 
 #### 1. Service Account Authentication (API Key)
+
 For backend services and automated systems with higher rate limits:
 
 **Option A: Pass to Strategy Constructor**
+
 ```python
 from wayfinder_paths.strategies.stablecoin_yield_strategy.strategy import StablecoinYieldStrategy
 
@@ -397,19 +416,21 @@ strategy = StablecoinYieldStrategy(
 ```
 
 **Option B: Set Environment Variable**
+
 ```bash
 export WAYFINDER_API_KEY="sk_live_abc123..."
 # All clients will automatically discover and use this
 ```
 
 **Option C: Add to config.json**
+
 ```json
 {
   "user": {
     "api_key": "sk_live_abc123..."
   },
   "system": {
-    "api_key": "sk_live_abc123..."  // Alternative: system-level API key
+    "api_key": "sk_live_abc123..." // Alternative: system-level API key
   }
 }
 ```
@@ -419,6 +440,7 @@ export WAYFINDER_API_KEY="sk_live_abc123..."
 **Note:** API keys in `config.json` are loaded directly by `WayfinderClient` via `_load_config_credentials()`, not through the `UserConfig` or `SystemConfig` dataclasses. This allows flexible credential loading.
 
 #### 2. Personal Access Authentication (OAuth)
+
 For standalone SDK users with username/password:
 
 ```json
@@ -426,12 +448,13 @@ For standalone SDK users with username/password:
   "user": {
     "username": "your_username",
     "password": "your_password",
-    "refresh_token": null  // Optional: use refresh token instead
+    "refresh_token": null // Optional: use refresh token instead
   }
 }
 ```
 
 **How It Works:**
+
 - API keys are automatically discovered by all clients (no need to pass explicitly)
 - When an API key is available, it's used for all API requests (including public endpoints) for rate limiting
 - If no API key is found, the system falls back to OAuth authentication
@@ -614,6 +637,7 @@ just create-wallets
 ```
 
 This creates:
+
 - `main` wallet - your main wallet for testing (labeled "main" in wallets.json)
 - `wallets.json` - wallet addresses and private keys for local testing
 
@@ -689,12 +713,14 @@ This package follows [Semantic Versioning](https://semver.org/) (SemVer) and is
 3. **Dependent changes**: Only after publishing can dependent changes be merged in other applications
 
 **Why this order matters:**
+
 - Other applications depend on this package from PyPI
 - They cannot merge changes that depend on new versions until those versions are available on PyPI
 - Publishing from `main` ensures the published version matches what's in the repository
 - This prevents dependency resolution failures in downstream applications
 
 **Example workflow:**
+
 ```bash
 # 1. Make changes in a feature branch
 git checkout -b feature/new-adapter
@@ -727,6 +753,7 @@ just publish
 ```
 
 **Important:**
+
 - ⚠️ **Publishing is only allowed from the `main` branch** - the publish command will fail if run from any other branch
 - ⚠️ **Versions must be unique** - ensure the version in `pyproject.toml` has been bumped and is unique
 - ⚠️ **Follow the order of operations** - see [Versioning](#-versioning) section above for the required workflow
@@ -749,6 +776,7 @@ pip install git+https://github.com/wayfinder-ai/wayfinder-paths.git
 ### Managing Package Access
 
 To add collaborators who can publish updates:
+
 1. Go to https://pypi.org/project/wayfinder-paths/
 2. Click "Manage" → "Collaborators"
 3. Add users as "Maintainers" (can publish) or "Owners" (full control)

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/README.md

@@ -102,6 +102,7 @@ We welcome contributions! This is an open-source project where community members
 ### Contributor Guidelines
 
 #### For Adapters
+
 - **Start from the template**: Copy `wayfinder_paths/templates/adapter/` as a starting point
 - Extend `BaseAdapter` from `wayfinder_paths/core/adapters/BaseAdapter.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/adapter/manifest.yaml`) with:
@@ -115,6 +116,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### For Strategies
+
 - **Start from the template**: Use `just create-strategy "Strategy Name"` to create a new strategy with its own wallet, or copy `wayfinder_paths/templates/strategy/` manually
 - Extend `Strategy` from `wayfinder_paths/core/strategies/Strategy.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/strategy/manifest.yaml`) with:
@@ -128,6 +130,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### General Guidelines
+
 - **Code Quality**: Follow existing patterns and use type hints
 - **Testing**: See [TESTING.md](TESTING.md) - minimum: smoke test for strategies, basic tests for adapters
 - **Documentation**: Update README files and add docstrings
@@ -182,6 +185,7 @@ poetry run python wayfinder_paths/run_strategy.py your_strategy --action status
 ## 🏗️ Architecture
 
 ### Client System
+
 The platform uses a unified client system for all API interactions. Clients are thin wrappers that handle low-level API calls, authentication, and network communication. **Strategies should not call clients directly** - use adapters instead for domain-specific operations.
 
 ### Clients vs Adapters
@@ -208,6 +212,7 @@ Adapter manifests declare the capabilities an adapter provides and the clients i
 **Template:** Copy `wayfinder_paths/templates/adapter/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.my_adapter.adapter.MyAdapter"
@@ -220,12 +225,14 @@ dependencies:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the adapter class (required)
 - `capabilities`: List of abstract capabilities this adapter provides (required, non-empty)
 - `dependencies`: List of client class names from `core.clients` that this adapter requires (required, non-empty)
 
 **Example** (`wayfinder_paths/adapters/pool_adapter/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.pool_adapter.adapter.PoolAdapter"
@@ -246,6 +253,7 @@ Strategy manifests declare permissions and required adapters with their capabili
 **Template:** Copy `wayfinder_paths/templates/strategy/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.my_strategy.strategy.MyStrategy"
@@ -259,6 +267,7 @@ adapters:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the strategy class (required)
 - `name`: Strategy directory name (optional, used for wallet lookup - defaults to directory name)
@@ -268,6 +277,7 @@ adapters:
   - `capabilities`: List of capabilities required from this adapter
 
 **Example** (`wayfinder_paths/strategies/stablecoin_yield_strategy/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.stablecoin_yield_strategy.strategy.StablecoinYieldStrategy"
@@ -285,12 +295,14 @@ adapters:
 #### Manifest Validation
 
 Manifests are automatically validated to ensure:
+
 - Schema compliance (all required fields present, correct types)
 - Entrypoint classes exist and are importable
 - Dependencies are valid client classes
 - Permissions policies are non-empty
 
 **Validate locally:**
+
 ```bash
 # Validate all manifests
 just validate-manifests
@@ -325,6 +337,7 @@ The `validate_manifests.py` script performs multi-stage validation:
    - Policy syntax is not parsed/validated (assumed to be valid at runtime)
 
 **Validation Flow:**
+
 ```
 For each manifest file:
   1. Load YAML → Parse with Pydantic (schema validation)
@@ -334,6 +347,7 @@ For each manifest file:
 ```
 
 The script automatically discovers all manifests by scanning:
+
 - `wayfinder_paths/adapters/*/manifest.yaml` for adapter manifests
 - `wayfinder_paths/strategies/*/manifest.yaml` for strategy manifests
 
@@ -344,12 +358,15 @@ All errors are collected and reported at the end, with the script exiting with c
 Capabilities are abstract operation identifiers (e.g., `"pool.read"`, `"swap.execute"`) declared in manifests. They represent what operations an adapter can perform, not specific method names. The manifest is the **single source of truth** for capabilities—they are not duplicated in code.
 
 When creating an adapter:
+
 1. Declare capabilities in your `manifest.yaml`
 2. Implement methods that fulfill those capabilities
 3. Capabilities are validated at manifest validation time (entrypoint must be importable)
 
 ### Configuration
+
 Configuration is split between:
+
 - **User Config**: Your credentials and preferences
 - **System Config**: Platform settings
 - **Strategy Config**: Strategy-specific parameters
@@ -361,9 +378,11 @@ See [CONFIG_GUIDE.md](wayfinder_paths/CONFIG_GUIDE.md) for details.
 Wayfinder Paths supports two authentication methods:
 
 #### 1. Service Account Authentication (API Key)
+
 For backend services and automated systems with higher rate limits:
 
 **Option A: Pass to Strategy Constructor**
+
 ```python
 from wayfinder_paths.strategies.stablecoin_yield_strategy.strategy import StablecoinYieldStrategy
 
@@ -374,19 +393,21 @@ strategy = StablecoinYieldStrategy(
 ```
 
 **Option B: Set Environment Variable**
+
 ```bash
 export WAYFINDER_API_KEY="sk_live_abc123..."
 # All clients will automatically discover and use this
 ```
 
 **Option C: Add to config.json**
+
 ```json
 {
   "user": {
     "api_key": "sk_live_abc123..."
   },
   "system": {
-    "api_key": "sk_live_abc123..."  // Alternative: system-level API key
+    "api_key": "sk_live_abc123..." // Alternative: system-level API key
   }
 }
 ```
@@ -396,6 +417,7 @@ export WAYFINDER_API_KEY="sk_live_abc123..."
 **Note:** API keys in `config.json` are loaded directly by `WayfinderClient` via `_load_config_credentials()`, not through the `UserConfig` or `SystemConfig` dataclasses. This allows flexible credential loading.
 
 #### 2. Personal Access Authentication (OAuth)
+
 For standalone SDK users with username/password:
 
 ```json
@@ -403,12 +425,13 @@ For standalone SDK users with username/password:
   "user": {
     "username": "your_username",
     "password": "your_password",
-    "refresh_token": null  // Optional: use refresh token instead
+    "refresh_token": null // Optional: use refresh token instead
   }
 }
 ```
 
 **How It Works:**
+
 - API keys are automatically discovered by all clients (no need to pass explicitly)
 - When an API key is available, it's used for all API requests (including public endpoints) for rate limiting
 - If no API key is found, the system falls back to OAuth authentication
@@ -591,6 +614,7 @@ just create-wallets
 ```
 
 This creates:
+
 - `main` wallet - your main wallet for testing (labeled "main" in wallets.json)
 - `wallets.json` - wallet addresses and private keys for local testing
 
@@ -666,12 +690,14 @@ This package follows [Semantic Versioning](https://semver.org/) (SemVer) and is
 3. **Dependent changes**: Only after publishing can dependent changes be merged in other applications
 
 **Why this order matters:**
+
 - Other applications depend on this package from PyPI
 - They cannot merge changes that depend on new versions until those versions are available on PyPI
 - Publishing from `main` ensures the published version matches what's in the repository
 - This prevents dependency resolution failures in downstream applications
 
 **Example workflow:**
+
 ```bash
 # 1. Make changes in a feature branch
 git checkout -b feature/new-adapter
@@ -704,6 +730,7 @@ just publish
 ```
 
 **Important:**
+
 - ⚠️ **Publishing is only allowed from the `main` branch** - the publish command will fail if run from any other branch
 - ⚠️ **Versions must be unique** - ensure the version in `pyproject.toml` has been bumped and is unique
 - ⚠️ **Follow the order of operations** - see [Versioning](#-versioning) section above for the required workflow
@@ -726,6 +753,7 @@ pip install git+https://github.com/wayfinder-ai/wayfinder-paths.git
 ### Managing Package Access
 
 To add collaborators who can publish updates:
+
 1. Go to https://pypi.org/project/wayfinder-paths/
 2. Click "Manage" → "Collaborators"
 3. Add users as "Maintainers" (can publish) or "Owners" (full control)

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "wayfinder-paths"
-version = "0.1.7"
+version = "0.1.8"
 description = "Wayfinder Path: strategies and adapters"
 readme = "README.md"
 authors = ["Wayfinder <dev@wayfinder.ai>"]

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/wayfinder_paths/adapters/brap_adapter/adapter.py

@@ -147,8 +147,7 @@ class BRAPAdapter(BaseAdapter):
             )
 
             # Extract best quote from response
-            quotes = data.get("quotes", {})
-            best_quote = quotes.get("best_quote")
+            best_quote = data["best_route"]
 
             if not best_quote:
                 return (False, "No quotes available")

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/wayfinder_paths/adapters/brap_adapter/test_adapter.py

@@ -81,12 +81,10 @@ class TestBRAPAdapter:
     async def test_get_best_quote_success(self, adapter, mock_brap_client):
         """Test successful best quote retrieval"""
         mock_response = {
-            "quotes": {
-                "best_quote": {
-                    "input_amount": "1000000000000000000",
-                    "output_amount": "995000000000000000",
-                    "total_fee": "8000000000000000",
-                }
+            "best_route": {
+                "input_amount": "1000000000000000000",
+                "output_amount": "995000000000000000",
+                "total_fee": "8000000000000000",
             }
         }
         mock_brap_client.get_quote = AsyncMock(return_value=mock_response)
@@ -108,7 +106,7 @@ class TestBRAPAdapter:
     @pytest.mark.asyncio
     async def test_get_best_quote_no_quotes(self, adapter, mock_brap_client):
         """Test best quote retrieval when no quotes available"""
-        mock_response = {"quotes": {}}
+        mock_response = {"best_route": None}
         mock_brap_client.get_quote = AsyncMock(return_value=mock_response)
 
         success, data = await adapter.get_best_quote(

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/wayfinder_paths/adapters/ledger_adapter/test_adapter.py

@@ -159,12 +159,15 @@ class TestLedgerAdapter:
 
         # Test
         operation_data = SWAP(
+            adapter="TestAdapter",
             from_token_id="0xA0b86a33E6441c8C06DdD4D4c4c4c4c4c4c4c4c4c",
             to_token_id="0xB1c97a44F7552d9Dd5e5e5e5e5e5e5e5e5e5e5e5e5e",
             from_amount="1000000000000000000",
             to_amount="995000000000000000",
             from_amount_usd=1000.0,
             to_amount_usd=995.0,
+            transaction_hash="0x123abc",
+            transaction_chain_id=8453,
         )
 
         success, data = await adapter.record_operation(

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/wayfinder_paths/adapters/pool_adapter/README.md

@@ -15,6 +15,7 @@ A Wayfinder adapter that provides high-level operations for DeFi pool data and a
 The adapter uses the PoolClient which automatically handles authentication and API configuration through the Wayfinder settings. No additional configuration is required.
 
 The PoolClient will automatically:
+
 - Use the WAYFINDER_API_URL from settings
 - Handle authentication via environment variables or config.json
 - Manage token refresh and retry logic
@@ -44,17 +45,6 @@ else:
     print(f"Error: {data}")
 ```
 
-### Get All Pools
-
-```python
-success, data = await adapter.get_all_pools(merge_external=False)
-if success:
-    pools = data.get("pools", [])
-    print(f"Total pools available: {len(pools)}")
-else:
-    print(f"Error: {data}")
-```
-
 ### Find High Yield Pools
 
 ```python
@@ -90,22 +80,6 @@ else:
     print(f"Error: {data}")
 ```
 
-### Search Pools
-
-```python
-success, data = await adapter.search_pools(
-    query="USDC",
-    limit=10
-)
-if success:
-    pools = data.get("pools", [])
-    print(f"Found {len(pools)} pools matching 'USDC'")
-    for pool in pools:
-        print(f"Pool: {pool.get('name')} - {pool.get('symbol')}")
-else:
-    print(f"Error: {data}")
-```
-
 ### Get Llama Matches
 
 ```python
@@ -168,7 +142,7 @@ if success:
     for pool_analytics in analytics:
         pool = pool_analytics.get("pool", {})
         llama_data = pool_analytics.get("llama_data", {})
-        
+
         print(f"Pool: {pool.get('name')}")
         print(f"  Combined APY: {pool_analytics.get('combined_apy', 0):.2%}")
         print(f"  TVL: ${pool_analytics.get('tvl_usd', 0):,.0f}")
@@ -189,6 +163,7 @@ The adapter uses the following Wayfinder API endpoints:
 ## Error Handling
 
 All methods return a tuple of `(success: bool, data: Any)` where:
+
 - `success` is `True` if the operation succeeded
 - `data` contains the response data on success or error message on failure
 

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.8}/wayfinder_paths/adapters/pool_adapter/adapter.py

@@ -53,25 +53,6 @@ class PoolAdapter(BaseAdapter):
             self.logger.error(f"Error fetching pools by IDs: {e}")
             return (False, str(e))
 
-    async def get_all_pools(
-        self, merge_external: bool | None = None
-    ) -> tuple[bool, PoolList | str]:
-        """
-        Get all available pools.
-
-        Args:
-            merge_external: Whether to merge external data
-
-        Returns:
-            Tuple of (success, data) where data is all pools or error message
-        """
-        try:
-            data = await self.pool_client.get_all_pools(merge_external=merge_external)
-            return (True, data)
-        except Exception as e:
-            self.logger.error(f"Error fetching all pools: {e}")
-            return (False, str(e))
-
     async def get_llama_matches(self) -> tuple[bool, dict[str, LlamaMatch] | str]:
         """
         Get Llama protocol matches for pools.
@@ -227,56 +208,3 @@ class PoolAdapter(BaseAdapter):
         except Exception as e:
             self.logger.error(f"Error getting pool analytics: {e}")
             return (False, str(e))
-
-    async def search_pools(self, query: str, limit: int = 10) -> tuple[bool, Any]:
-        """
-        Search pools by name, symbol, or other criteria.
-
-        Args:
-            query: Search query string
-            limit: Maximum number of results
-
-        Returns:
-            Tuple of (success, data) where data is search results or error message
-        """
-        try:
-            success, all_pools_data = await self.get_all_pools()
-            if not success:
-                return (False, f"Failed to fetch pools: {all_pools_data}")
-
-            pools = all_pools_data.get("pools", [])
-            query_lower = query.lower()
-
-            # Simple text search
-            matching_pools = []
-            for pool in pools:
-                name = pool.get("name", "").lower()
-                symbol = pool.get("symbol", "").lower()
-                description = pool.get("description", "").lower()
-
-                if (
-                    query_lower in name
-                    or query_lower in symbol
-                    or query_lower in description
-                ):
-                    matching_pools.append(pool)
-
-            # Sort by relevance (exact matches first)
-            matching_pools.sort(
-                key=lambda x: (
-                    query_lower not in x.get("name", "").lower(),
-                    query_lower not in x.get("symbol", "").lower(),
-                )
-            )
-
-            return (
-                True,
-                {
-                    "pools": matching_pools[:limit],
-                    "total_found": len(matching_pools),
-                    "query": query,
-                },
-            )
-        except Exception as e:
-            self.logger.error(f"Error searching pools: {e}")
-            return (False, str(e))