---
# System prepended metadata

title: Casimir Docs

---

# Casimir

Casimir is a non-custodial Ethereum restaking platform built on EigenLayer’s infrastructure, using Distributed Validator Technology (DVT). As a permissionless platform, Casimir is designed to align with the foundational principles of the Ethereum protocol and the broader Web3.0 ecosystem, focusing on secure, decentralized staking and digital asset management.

## Key Features

### Validator Management

Validators on Casimir are openly registered, collateralized operators utilizing Distributed Validator Technology (DVT), which ensures high performance and reliability.

### Key Security

Keys are managed through a trustless, zero-coordination distributed key generation (DKG) process, enhancing security and reducing the risk of mismanagement.

### Restaking

Casimir leverages the robust EigenLayer infrastructure for restaking, allowing stakers to deposit ETH directly to selected Ethereum operators without the issuance of a Liquid Restaking Token. This method significantly reduces counterparty risks.

### Withdrawal Flexibility

The platform supports full withdrawals, providing stakers with complete control over their assets without compromising on the accessibility of their funds.

By eliminating the need for Liquid Restaking Tokens and focusing on decentralized, secure key management, Casimir minimizes risks for users and strengthens the overall decentralization and efficiency of Ethereum staking.

## Smart Contract Architecture

Casimir’s architecture is built around three core smart contracts: CasimirFactory, CasimirRegistry, and CasimirManager, designed to facilitate flexible and secure staking strategies on the Ethereum blockchain.

### CasimirFactory

This contract acts as the central hub for registering multiple staking strategies. Each strategy defined by CasimirFactory specifies various parameters such as the size of the operator cluster, minimum collateral required from operators, reward fee etc. This modular approach allows for the customization of staking conditions to suit diverse staker needs and risk profiles.

### CasimirRegistry and CasimirManager

For each strategy, a dedicated instance of CasimirManager and CasimirRegistry is deployed. These instances handle specific roles:

- **CasimirRegistry**: Manages the operational aspects of validator nodes. This includes the registration, removal, and resharing of operator responsibilities. It ensures that the network of validators is maintained efficiently and securely.
- **CasimirManager**: Facilitates user interactions such as staking and unstaking. This contract is the point of interface for users who wish to engage with the staking protocols defined by the CasimirFactory.

### Beacon Upgradeability

The protocol utilizes Beacon Upgradeability for managing future upgrades to both the Manager and Registry contracts. This upgradeability feature ensures that the system can evolve with EigenLayer and adapt to new requirements or improvements without sacrificing the integrity of ongoing operations.

### Reporter

A protocol-controlled address, known as the "Reporter," performs critical operational functions. These include creating, activating, syncing, and removing validators on EigenLayer, claiming rewards, and managing reports that update key protocol metrics such as rewards. This role is vital for the continuous and autonomous functioning of the system.

> Note, this role changes (less or no trust) with the [EigenPod redesign](https://hackmd.io/U36dE9lnQha3tbf7D0GtKw#The-Checkpoint-Proof-System).