Before you begin
You need:- A chain with IBC deployed, and a light client tracking it. This guide continues from the tutorial.
- Your signing address already in that client’s attestation set.
- Your signing key.
- The chain’s RPC endpoint and router address. General configuration validation permits a missing router address, but attestor startup requires it.
- Go 1.26.10 or later and a build of the binary.
Warning: Stop the tutorial’s relayer with Ctrl+C in its terminal. It hosts the attestor that this guide moves into a separate process.
1. Attestor config
Create a second configuration file alongside the tutorial’s:2. Write its configuration
Write the attestor’s configuration file, reading the router address from the deployment:attestor-<chain it watches>. Names must be unique within the serving process.
Warning: The attestor’s name has to match the name the relayer uses for it. A relayer sends that name in every query, and the process serves its attestors by name, so a mismatch makes every lookup fail.A finality offset of
1 signs one block behind the chain head. Zero waits for the chain’s own finalized block instead.
3. Start it and verify
- Validate the configuration:
- Start the process in a new terminal, and leave it running:
- Back in your first terminal, ask the process what its address is:
- Ask how far it can attest:
Connect a relayer
A relayer references your attestor by name and network address:https://host, which uses port 443 unless you add one, and add a tls block for a private CA or mTLS, as described in TLS for remote services.
Next steps
- Run a standalone relayer brings up a relayer that queries this attestor instead of hosting its own.
- Plan a production deployment covers quorum, finality, key custody, permissions, and service configuration.