SatLayer Contracts

The SatLayer core system is comprised of the following contracts: BVS Library: A standalone library for the BVS project which provides shared functionality for all BVS Contracts. The library contains utilities for asserting ownershipof contracts, for working with addresses, and for testing.

BVS Pauser: A centralized contract which manages the operational state of the entire ecosystem. It enables emergency pausing of the entire system in response to critical issues

BVS Registry: The BVS registry is the central record-keeping contract for all Operators and Services within the SatLayer ecosystem. It acts as a directory for all Operators and Services to register themselves and establish relationships with each other. Operators and Services are registered in the registry contract, and their metadata is emitted as events.

This contract provides the bookkeeping registry for vault-router to query delegations to determine if the Operator is validating a Service. This allows the vault-router to make vault management decisions based on the delegations (queue funds withdrawal from the Vault if delegated).

An Operator/Service (sender) can register a Service/Operator to run and vice versa. However, both the Operator and Service must register to each other to establish a relationship.

• As an Operator, by registering a Service, you are indicating that you are willing to run the Service.

• As a Service, by registering an Operator, you are indicating that you are willing to be run by the Operator.

BVS Vault Base: Provides base utilities for the BVS vault contracts, bvs-vault-cw20 and bvs-vault-bank.

BVS-Vault-CW20: Depository vault which supportscw20tokens as deposit assets. Operators which want to accept cw20 tokens as restaked collateral must deploy a vault of this type through the SatLayer front end (available in Phase II).

BVS-Vault-Bank: Depository Vault which supports bankmodule tokens as deposit assets. Operators which want to accept bank tokens as restaked collateral must deploy a vault of this type through the SatLayer front end (available in Phase II).

BVS-Vault-Factory: This contract serves as an entry point to allow operators to deploy new vaults on SatLayer.

BVS-Vault-Router: Serves as the central hub for sending messages to/from vaults in the SatLayer ecosystem. Vaultsare tracked and whitelisted through the router, and protocol-wide parameters such as the withdrawal period from delegated vaults can be set through the router.

BVS-Rewards: This contract is responsible for holding and dispersing rewards that re distributed to stakers and operators on behalf of BVSs.