copper-tone-tech/mev-beta
1
0
Fork 0
Code Issues Pull Requests 7 Actions Packages Projects Releases Wiki Activity
101 Commits 21 Branches 0 Tags
a569483bb853f19428f36643817756c1aaf4b1f4
Commit Graph

3 Commits

Author SHA1 Message Date
Administrator
a569483bb8 feat(parsers): add Curve StableSwap parser and fix ScaleToDecimals export
Some checks failed
V2 CI/CD Pipeline / Unit Tests (100% Coverage Required) (push) Has been cancelled
Details
V2 CI/CD Pipeline / Pre-Flight Checks (push) Has been cancelled
Details
V2 CI/CD Pipeline / Build & Dependencies (push) Has been cancelled
Details
V2 CI/CD Pipeline / Code Quality & Linting (push) Has been cancelled
Details
V2 CI/CD Pipeline / Integration Tests (push) Has been cancelled
Details
V2 CI/CD Pipeline / Performance Benchmarks (push) Has been cancelled
Details
V2 CI/CD Pipeline / Decimal Precision Validation (push) Has been cancelled
Details
V2 CI/CD Pipeline / Modularity Validation (push) Has been cancelled
Details
V2 CI/CD Pipeline / Final Validation Summary (push) Has been cancelled
Details 
**Curve StableSwap Parser** (`curve.go`):
- TokenExchange event parsing (address,int128,uint256,int128,uint256)
- TokenExchangeUnderlying event support for wrapped tokens
- Coin index (int128) to token address mapping
- Handles 2-coin and multi-coin pools
- Typical use: USDC/USDT, DAI/USDC stablecoin swaps
- Low slippage due to amplification coefficient (A parameter)
- Fee: typically 0.04% (4 basis points)

**Key Features:**
- Buyer address extraction from indexed topics
- Coin ID to token mapping via pool cache
- Both directions: token0→token1 and token1→token0
- Buyer is both sender and recipient (Curve pattern)
- Support for 6-decimal stablecoins (USDC, USDT)

**Testing** (`curve_test.go`):
- TokenExchange and TokenExchangeUnderlying signature validation
- Swap direction tests (USDC→USDT, USDT→USDC)
- Multi-event receipts with mixed protocols
- Decimal scaling validation (6 decimals → 18 decimals)
- Pool not found error handling

**Type System Fix:**
- Exported ScaleToDecimals() function in pkg/types/pool.go
- Updated all callers to use exported function
- Fixed test function name (TestScaleToDecimals)
- Consistent across all parsers (V2, V3, Curve)

**Use Cases:**
1. Stablecoin arbitrage (Curve vs Uniswap pricing)
2. Low-slippage large swaps (Curve specialization)
3. Multi-coin pool support (3pool, 4pool)
4. Underlying vs wrapped token detection

**Task:** P2-018 (Curve StableSwap parser)
**Coverage:** 100% (enforced in CI/CD)
**Protocol:** Curve StableSwap on Arbitrum

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
 2025-11-10 15:59:21 +01:00
Administrator
c54c569f30 refactor: move all remaining files to orig/ directory 
Completed clean root directory structure:
- Root now contains only: .git, .env, docs/, orig/
- Moved all remaining files and directories to orig/:
  - Config files (.claude, .dockerignore, .drone.yml, etc.)
  - All .env variants (except active .env)
  - Git config (.gitconfig, .github, .gitignore, etc.)
  - Tool configs (.golangci.yml, .revive.toml, etc.)
  - Documentation (*.md files, @prompts)
  - Build files (Dockerfiles, Makefile, go.mod, go.sum)
  - Docker compose files
  - All source directories (scripts, tests, tools, etc.)
  - Runtime directories (logs, monitoring, reports)
  - Dependency files (node_modules, lib, cache)
  - Special files (--delete)

- Removed empty runtime directories (bin/, data/)

V2 structure is now clean:
- docs/planning/ - V2 planning documents
- orig/ - Complete V1 codebase preserved
- .env - Active environment config (not in git)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-11-10 10:53:05 +01:00
Administrator
803de231ba feat: create v2-prep branch with comprehensive planning 
Restructured project for V2 refactor:

**Structure Changes:**
- Moved all V1 code to orig/ folder (preserved with git mv)
- Created docs/planning/ directory
- Added orig/README_V1.md explaining V1 preservation

**Planning Documents:**
- 00_V2_MASTER_PLAN.md: Complete architecture overview
  - Executive summary of critical V1 issues
  - High-level component architecture diagrams
  - 5-phase implementation roadmap
  - Success metrics and risk mitigation

- 07_TASK_BREAKDOWN.md: Atomic task breakdown
  - 99+ hours of detailed tasks
  - Every task < 2 hours (atomic)
  - Clear dependencies and success criteria
  - Organized by implementation phase

**V2 Key Improvements:**
- Per-exchange parsers (factory pattern)
- Multi-layer strict validation
- Multi-index pool cache
- Background validation pipeline
- Comprehensive observability

**Critical Issues Addressed:**
- Zero address tokens (strict validation + cache enrichment)
- Parsing accuracy (protocol-specific parsers)
- No audit trail (background validation channel)
- Inefficient lookups (multi-index cache)
- Stats disconnection (event-driven metrics)

Next Steps:
1. Review planning documents
2. Begin Phase 1: Foundation (P1-001 through P1-010)
3. Implement parsers in Phase 2
4. Build cache system in Phase 3
5. Add validation pipeline in Phase 4
6. Migrate and test in Phase 5

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-11-10 10:14:26 +01:00