From 969e3c344808e6806da9e17d1831a8a38936095c Mon Sep 17 00:00:00 2001 From: Stephen Fluin Date: Fri, 22 Mar 2024 16:57:53 -0500 Subject: [PATCH] chore: rename workers to verifiers in onboarding (#320) --- doc/src/overview.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/overview.md b/doc/src/overview.md index a7c7b7ef5..7b67f3b8f 100644 --- a/doc/src/overview.md +++ b/doc/src/overview.md @@ -187,12 +187,12 @@ messages from the gateway, and interacts with the multisig contract to conduct t ### Multisig Contract [`multisig`](contracts/multisig.md) is responsible for signing arbitrary blobs of data. Contracts register with the -multisig contract to generate a key id, and then use that key id to initiate signing sessions. Off chain workers +multisig contract to generate a key id, and then use that key id to initiate signing sessions. Off chain verifiers associated with the key id sign messages when new signing sessions are created. ### Service Registry -[`service-registry`](contracts/service_registry.md) is responsible for tracking workers associated with specific -services. Two example services are voting and signing. Workers must be authorized to join a service via governance -vote. Once authorized, workers must also bond a sufficient amount of stake before becoming active in the service. +[`service-registry`](contracts/service_registry.md) is responsible for tracking verifiers associated with specific +services. Two example services are voting and signing. Verifiers must be authorized to join a service via governance +vote. Once authorized, verifiers must also bond a sufficient amount of stake before becoming active in the service. Services query the service registry to create weighted snapshots of the active worker set.