serai/processor/messages
Luke Parker bccdabb53d
Use a single Substrate signer, per intentions in #227
Removes key from Update as well, since it's no longer variable.
2023-08-24 20:30:50 -04:00
..
src Use a single Substrate signer, per intentions in #227 2023-08-24 20:30:50 -04:00
Cargo.toml Correct depends for processor-messages 2023-07-03 12:40:56 -04:00
LICENSE Processor (#259) 2023-03-16 22:59:40 -04:00
README.md Processor (#259) 2023-03-16 22:59:40 -04:00

Processor

The Serai processor scans a specified chain, communicating with the coordinator.

Key Generation

The coordinator will tell the processor if it's been included in managing a coin. If so, the processor is to begin the key generation protocol, relying on the coordinator to provided authenticated communication with the remote parties.

When the key generation protocol successfully completes, the processor is expected to inform the coordinator so it may vote on it on the Substrate chain. Once the key is voted in, it'll become active.

Scanning

The processor is expected to scan all sufficiently confirmed blocks from a given coin. This will create a list of outputs, considered pending.

Reporting

These outputs are to be placed in a Batch, identified by the block containing them. Batches are provided in an Update to Serai, paired by an agreed upon block number.

The processor will also produce an Update if there have been no batches within the confirmation window.

Confirmed Outputs

Once outputs have been acknowledged by Serai, they are considered confirmed. With their confirmation, the validators are ready to create actions based on them.

Actions are triggered by passing the outputs to the scheduler. The scheduler will do one of two things:

  1. Use the output
  2. Accumulate it for later usage

Burn Events

When the Serai chain issues a Burn event, the processor should send coins accordingly. This is done by scheduling the payments out.