datahaven/contracts

DataHaven AVS Smart Contracts

Implements the Actively Validated Service (AVS) logic for DataHaven, secured by EigenLayer. These contracts manage operator registration, handle cross-chain rewards via Snowbridge, and enforce slashing with a veto period.

Project Structure

contracts/
├── src/
│   ├── DataHavenServiceManager.sol   # Core AVS service manager
│   ├── middleware/                   # RewardsRegistry, Snowbridge helpers
│   ├── interfaces/                   # Contract interfaces
│   └── libraries/                    # Utility libraries
├── script/                           # Deployment & setup scripts
├── lib/                              # External dependencies (EigenLayer, Snowbridge, OpenZeppelin)
└── test/                             # Foundry test suites

Key Components

• DataHavenServiceManager (src/DataHavenServiceManager.sol): Core contract for operator lifecycle; inherits ServiceManagerBase.
• RewardsRegistry (src/middleware/RewardsRegistry.sol): Tracks validator performance and distributes rewards via Snowbridge.

Development

Requires Foundry.

# Build and Test
forge build
forge test

# Regenerate TS bindings (after contract changes)
cd ../test && bun generate:wagmi

Configuration

Deployment parameters (EigenLayer addresses, initial validators, owners) are defined in contracts/config/<network>.json.

• Do not edit Config.sol or DeployParams.s.sol directly; they only load the JSON.
• Ensure contracts/config/hoodi.json matches your target environment before deploying.

Deployment

Two deployment paths exist: Local (Anvil) and Testnet (Hoodi). Both install the DataHaven AVS contracts (ServiceManager, RewardsRegistry) and Snowbridge (BeefyClient, Gateway, Agent). They differ in EigenLayer setup:

Local (Anvil)

DeployLocal.s.sol bootstraps a full EigenLayer core deployment (DelegationManager, StrategyManager, AVSDirectory, etc.) alongside DataHaven AVS and Snowbridge.

anvil
forge script script/deploy/DeployLocal.s.sol --rpc-url anvil --broadcast

Testnet (Hoodi)

DeployTestnet.s.sol references existing EigenLayer contracts (addresses from contracts/config/<network>.json) and only deploys DataHaven AVS + Snowbridge.

NETWORK=hoodi forge script script/deploy/DeployTestnet.s.sol \
  --rpc-url hoodi \
  --private-key $PRIVATE_KEY \
  --broadcast

Supported networks: hoodi (no mainnet config yet). Artifacts → contracts/deployments/<network>.json.

Contract versioning (version)

DataHaven uses a changeset-based versioning system with centralized tracking:

• contracts/VERSION is the single source of truth for the code version.
• contracts/versions-matrix.json tracks the code version and per-chain deployments.
• contracts/deployments/<network>.json contains addresses only (no version field).
• Version is passed as a parameter during contract deployment (not hardcoded by chain ID).
• Version management is changeset-driven:
  • bun cli contracts bump --type [major|minor|patch] creates a changeset
  • CI applies changesets and updates VERSION + versions-matrix.json
• Multiple environments can share the same deployment file:
  • stagenet-hoodi and testnet-hoodi both write to hoodi.json (chainId: 560048)
• For validation, run bun cli contracts version-check --chain <chain> and bun cli contracts validate-changesets.

How It Works

1. Registration: Validators register with EigenLayer via DataHavenServiceManager.
2. Performance Tracking: DataHaven computes reward points and sends a Merkle root to RewardsRegistry on Ethereum via Snowbridge.
3. Rewards Claims: Validators claim rewards on Ethereum from RewardsRegistry using Merkle proofs.
4. Slashing: Misbehavior triggers slashing (subject to veto period).

See test/README.md for full network integration tests.