Skip to content

Commit

Permalink
observer-signer
Browse files Browse the repository at this point in the history
  • Loading branch information
fadeev committed Jan 19, 2024
1 parent fe26ddd commit fa71ae0
Showing 1 changed file with 27 additions and 15 deletions.
42 changes: 27 additions & 15 deletions docs/architecture/observers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,28 +5,40 @@ sidebar_position: 9
import ObserverList from "@site/src/components/ObserverList/ObserverList";
import ObserverParams from "@site/src/components/ObserverParams/ObserverParams";

# Observers
# Observer-Signer Validators

ZetaChain has two types of validators: core validators and observer validators
(observers).
ZetaChain has two types of validators: core validators and observer-signer
validators (observer-signers).

Observers are tasked with running nodes of connected chains, observing them with
`zetaclient` and writing transactions to connected chains.
:::note

The protocol is designed in a way to allow observers in the future to choose
which chains they want to observe. This allows for a more flexible system where
observers can observe only the subset of chains they are interested in (for
example, their infrastructure is built around running EVM nodes). In the current
version of the protocol, all observers are observing all chains.
ZetaChain is designed to have two types of validators: observers and signers.
Observers monitor activities on connected chains, while signers handle the
signing of transactions from the Threshold Signature Scheme (TSS) address on
behalf of the protocol. However, currently, all observer-signer validators on
ZetaChain perform both roles, acting as both observers and signers. This means
each observer-signer validator simultaneously observes transactions on connected
chains and participates in transaction signing.

A list of [observers](/architecture/modules/observer/overview) on the ZetaChain
testnet:
:::

Observer-signers are tasked with running nodes of connected chains, observing
them with `zetaclient` and writing transactions to connected chains.

The protocol is designed in a way to allow observer-signers in the future to
choose which chains they want to observe. This allows for a more flexible system
where observer-signers can observe only the subset of chains they are interested
in (for example, their infrastructure is built around running EVM nodes). In the
current version of the protocol, all observers-signers are observing all chains.

A list of [observer-signers](/architecture/modules/observer/overview) on the
ZetaChain testnet:

<ObserverList />

As they perform a critical function in the system, the minimum self
delegation/stake required to be an observer is set as a param of the `observer`
module on a per chain basis. This is to ensure that observers are incentivized
to perform their duties and are not malicious.
delegation/stake required to be an observer-signer is set as a param of the
`observer` module on a per chain basis. This is to ensure that observer-signer
validators are incentivized to perform their duties and are not malicious.

<ObserverParams />

0 comments on commit fa71ae0

Please sign in to comment.