S3N Core is an AVS built on EigenLayer through the Othentic stack, designed to notarise and commit to credentials, replacing the need for data signing by issuers.
To set up the environment, create a .env
file with the usual Othentic
configurations (see the .env.example
).
Installing Othentic CLI with npm
:
npm i -g @othentic/othentic-cli
Verify installation by the command:
othentic-cli -h
You need to register 3 self-deploy Operators with a minimum of 0.01 stETH.
- Deployer account:
- A minimum of 1.5 holETH (Faucet)
- A minimum of 5 Amoy MATIC (Faucet)
- Operator account x 3 (Script):
- A minimum of 0.02 holETH on Holesky
- ERC-20 token address
To deploy the AVS’s on-chain components, run the following command:
othentic-cli network deploy \\
--erc20 0x73967c6a0904aA032C103b4104747E88c566B1A2 \\
--l1-initial-deposit 1000000000000000000 \\
--l2-initial-deposit 2000000000000000000 \\
--name test-avs-name
Register as an operator for both EigenLayer and the AVS
othentic-cli operator register
This command converts 0.012 ETH into stETH before depositing it into EigenLayer pool:
othentic-cli operator deposit --strategy stETH --shares 0.01 --convert 0.012
Activate your Operator by depositing into EigenLayer Deposit 0.01 stETH into EigenLayer pool.
othentic-cli operator deposit --strategy stETH --shares 0.01
✅ Your internal Operators are now ready to opt-in to your AVS.
We provide a sample docker-compose configuration which sets up the following services:
- Aggregator node
- 3 Attester nodes
- Validation Service endpoint
- Execution Service endpoint
- Sync Shares of operators across layers
run:
docker-compose up --build
Note
This might take a few minutes when building the images
To execute a task we send a POST request to the Task Performer service:
curl -X POST <http://localhost:4003/task/execute>
✅ Your demo AVS is functional!
To update the othentic-cli
inside the docker images to the latest version, you
need to rebuild the images using the following command:
docker-compose build --no-cache
The Othentic Attester nodes communicate with an AVS WebAPI endpoint which validates tasks on behalf of the nodes. The attesters then sign the tasks based on the AVS WebAPI response.
Attester nodes can either all communicate with a centralized endpoint or each implement their own validation logic.
POST task/validate returns (bool) {"proofOfTask": "{proofOfTask}"};
sync the shares of operators between L1 and L2 at a fixed interval. The default interval is 12h and can be modified inside the docker-compose file