Operator Allowlisting

Overview

Allowlisting is an access control mechanism used to manage Operator participation in the AVS network. AVSs can selectively add Operators to the allowlist based on their requirements, creating a permissioned network.

Key Features

• Access Control: Only Operators on the allowlist can register to the AVS network, ensuring that access is restricted to approved participants.

• Security: Helps protect AVS against unauthorized access and spam by ensuring that only vetted Operators can participate.

---

Usage

You can integrate allowlisting into AVS using either the CLI or custom scripts, depending on the operational needs.

When using the CLI, the allowlisting authentication token is generated internally. If registering via scripts, you'll need to generate the token manually.

Using CLI

1. Enable Allowlisting

   • Use the setIsAllowListed function in the AVS governance contract

   • Set the parameter to true

2. Register Your AVS

   • Visit the allowlister platform: https://allowlister.othentic.xyz/

   • Complete the registration with your email

3. Share Governance Address

   • Share the AVS governance address through Telegram group

   • This links the AVS to the allowlisting system

4. Add Operators

   • Important: Add operators to the allowlist before registration

   • Only approved operators will have registration access once allowlisting is enabled

---

Using scripts

You can generate the AUTH_TOKEN using Operator registration scripts:

1

Generate Signature for Allowlist Service

If registration requires allowlisting, use this script to generate the required signature.

ts-node scripts/allowlist/generateSignature.ts \
<SIGNER_PRIVATE_KEY> <WALLET_ADDRESS> <AVS_GOVERNANCE_ADDRESS>

Parameters:

• SIGNER_PRIVATE_KEY: Operator private key or Private key of the Operator's signer (for smart wallets and multisigs)

• WALLET_ADDRESS: Address of the smart wallet or multisig

• AVS_GOVERNANCE_ADDRESS: Address of the AVS governance contract

Example:

ts-node scripts/allowlist/generateSignature.ts 6212d241a920a6d5d9841af933411d8d6141638c8f7d21a6b32594014ef0006e 0x7F2a575015946D06284E130b00944c5755c351f2 0x02c13D68F7194F9741DBfDdC65e6a58979A9dfcd

Output will be stored in .othentic/othentic-allowlist-request-signature.json.

2

Validate Allowlist Signature (Optional)

Verify that your allowlist signature is valid before submitting to the allowlist service.

ts-node scripts/allowlist/validateSignature.ts <JSON_FILE> <RPC>

Parameters:

• JSON_FILE: Path to the allowlist signature JSON from step 3

• RPC: URL of the Ethereum RPC endpoint

Example:

ts-node scripts/allowlist/validateSignature.ts \
.othentic/othentic-allowlist-request-signature.json \
https://holesky.gateway.tenderly.co

3

Submit Signature to the Allowlist Service

After generating the allowlist signature, submit it to the allowlist service:

http://allowlist-signer.othentic.xyz/signer/sign

Request Payload Format

{
   "wallet": "",
   "avsGovernanceAddress": "",
   "signature": ""
}

Example (Using curl):

curl --location 'http://allowlist-signer.othentic.xyz/signer/sign' \
--header 'Content-Type: application/json' \
--data '.othentic/othentic-allowlist-request-signature.json'

The returned token can be used as the AUTH_TOKEN parameter.