Protocol schema

Short description about each contract in the protocol workflow

While descriptions are very poor, please pay attentions to connectors section, there are important information.

SingleIdentifierId

Handles emitters, initiates crosschain messages.

Take it if you need to register/update SID.

SingleIdentifierRegistry

Stores project schemas and SIDs.

The only reasons to use this contract are:

  • Registering schema

  • Revoking SID

SingleRouter

Handles connectors and crosschain routing.

You will never use this contract directly.

Connectors

We use connectors for working with different crosschain protocols. For now we support only 2 protocols:

Protocol
Connector id

Hyperlane

1

LayerZero

2

If for some reason neither accidentally or purposefully message would be targeted to the same chain it sent from then any connector id would be ignored and message would be redirected to the destination contract.c

Last updated