From bed45694f9d1bbc535e8c7662fa0eb2fe057e7de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nikola=20Risti=C4=87?= Date: Wed, 6 May 2026 11:30:44 +0200 Subject: [PATCH] docs: mention ampd local network requirement --- src/content/docs/validator/amplifier/verifier-onboarding.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/validator/amplifier/verifier-onboarding.mdx b/src/content/docs/validator/amplifier/verifier-onboarding.mdx index 66a509692..2204b4a5f 100644 --- a/src/content/docs/validator/amplifier/verifier-onboarding.mdx +++ b/src/content/docs/validator/amplifier/verifier-onboarding.mdx @@ -45,6 +45,10 @@ Running a verifier requires three components: Handlers are separate processes that connect to ampd's gRPC server. If a handler crashes, it does not affect ampd or other handlers. + + Run `tofnd`, `ampd`, and ampd handlers on the same host, and keep ampd's gRPC server on `127.0.0.1` (the default in the config examples below). The gRPC API has no authentication — exposing it on `0.0.0.0` or a public interface would let anyone on the network trigger signing and broadcast transactions through your verifier. + + There are three ways to set up and run a verifier: - **Option 1: Source** -- Clone and build directly from the GitHub source code.