Elgato_dark/datahaven
1
0
Fork 0
mirror of https://github.com/datahaven-xyz/datahaven synced 2026-05-24 01:38:32 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
datahaven/CLAUDE.md
undercover-cactus 863250d555
misc: remove slasher middleware solidity contracts (#366) 
## Summary

This PR remove the middlewares contracts from eigen layer. Instead we
are planning to use the eigne layer contract directly. It also removes
the tests related to the middleware slasher code and the mock contract
used in it.

## Motivation

When slashing an operator in the Dathaven we are going through the
substrate slashing pallet already implemented. It already allow to
configure a slashing window and/or to cancel a slashing. In the future
it will also be compatible with a government pallet. This part of code
is therefore redundant. For the same reason we remove the tests because
we are not using the slashing middleware contracts.

## What changed

* Remove the slasher middleware files
* Remove the tests related to the middleware slasher file
2025-12-29 14:55:21 +01:00

5.6 KiB
Raw Permalink Blame History

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

DataHaven is an EVM-compatible Substrate blockchain secured by EigenLayer. It bridges Ethereum and Substrate ecosystems through:

  • EigenLayer AVS integration for security
  • Snowbridge for cross-chain communication
  • Frontier pallets for EVM compatibility
  • External validators with rewards system

Pre-requisites

  • Kurtosis: For launching test networks
  • Bun v1.2+: TypeScript runtime and package manager
  • Docker: For container management
  • Foundry: For smart contract compilation/deployment
  • Helm: Kubernetes package manager
  • Zig (macOS only): For crossbuilding the node

Critical Development Commands

E2E Testing Environment (from /test directory)

# Setup
bun i                               # Install dependencies
bun cli                            # Interactive CLI for test environment

# Code Quality
bun fmt:fix                        # Fix TypeScript formatting (Biome)
bun typecheck                      # TypeScript type checking

# Code Generation (run after contract/runtime changes)
bun generate:wagmi                 # Generate TypeScript contract bindings
bun generate:types                 # Generate Polkadot-API types from runtime
bun generate:types:fast            # Generate types with fast-runtime feature

# Local Development - Quick Start
bun cli launch                     # Interactive launcher (recommended)
bun start:e2e:local               # Launch full local test network
bun start:e2e:verified            # Launch with Blockscout + contract verification
bun start:e2e:ci                  # CI-optimized network launch

# Stopping Services
bun stop:e2e                      # Stop all test services (interactive)
bun stop:dh                       # Stop DataHaven only
bun stop:sb                       # Stop Snowbridge relayers only
bun stop:eth                      # Stop Ethereum network only

# Testing
bun test:e2e                      # Run all E2E test suites
bun test:e2e:parallel             # Run tests with limited

Rust/Operator Development

cd operator
cargo build --release --features fast-runtime    # Development build (faster)
cargo build --release                           # Production build
cargo test                                      # Run all tests
cargo fmt                                       # Format Rust code
cargo clippy                                    # Lint Rust code

Smart Contracts (from /contracts directory)

forge clean                        # Clean build artifacts
forge build                        # Build contracts
forge test                         # Run tests
forge test -vvv                    # Run tests with stack traces
forge fmt                          # Format Solidity code

Architecture Essentials

Repository Structure

datahaven/
├── contracts/      # EigenLayer AVS smart contracts
├── operator/       # Substrate-based DataHaven node
│   ├── node/      # Node implementation
│   ├── pallets/   # Custom pallets (validators, rewards, transfers)
│   └── runtime/   # Runtime configurations (mainnet/stagenet/testnet)
├── test/          # E2E testing framework
│   ├── suites/    # Test scenarios
│   ├── framework/ # Test utilities
│   └── launcher/  # Network deployment tools
└── deploy/        # Kubernetes deployment charts

Cross-Component Dependencies

  • Contracts → Operator: AVS contracts register/slash operators via DataHavenServiceManager
  • Operator → Contracts: Reads validator registry, submits performance data
  • Test → Both: Deploys contracts, launches nodes, runs cross-chain scenarios
  • Snowbridge: Bidirectional bridge for tokens/messages between Ethereum↔DataHaven

Key Components

  1. DataHavenServiceManager: Core AVS contract managing operator lifecycle
  2. RewardsRegistry: Tracks validator performance and reward distribution
  3. External Validators Pallet: Manages validator set on Substrate side
  4. Native Transfer Pallet: Handles cross-chain token transfers via Snowbridge

Testing Strategy

  • Unit Tests: Component-specific (cargo test, forge test)
  • Integration Tests: Full network scenarios in /test/suites
  • Kurtosis: Orchestrates multi-container test environments
  • Parallel Testing: Use test:e2e:parallel for faster CI runs

Development Workflow

  1. Make changes to relevant component
  2. Run component-specific tests and linters
  3. Regenerate bindings if contracts/runtime changed:
    • bun generate:wagmi for contract changes
    • bun generate:types for runtime changes
  4. Build Docker image for operator changes: bun build:docker:operator
  5. Run E2E tests to verify integration: bun test:e2e
  6. Use bun cli launch --verified --blockscout for manual testing

Common Pitfalls & Solutions

  • Types mismatch: Regenerate with bun generate:types after runtime changes
  • Kurtosis not running: Ensure Docker is running and Kurtosis engine is started
  • Contract changes not reflected: Run bun generate:wagmi after modifications
  • Forge build errors: Try forge clean then rebuild
  • Slow development cycle: Use --features fast-runtime for faster block times
  • Network launch halts: Check Blockscout - forge output can appear frozen
  • macOS crossbuild fails: Ensure Zig is installed for cross-compilation