Skip to main content

Registration of Gateways

Gateways register on the Common Chain by specifying the following parameters:

  • The Enclave Key along with an attestation
  • The amount of stakes to be deposited
  • The list of supported Request Chains that Gateway is going to serve
  • The address of the operator owning the gateway
  • The signature from the enclave, signing the list of supported Request Chain and owner address, signed using the Enclave Key

They also need to register on Request Chain with the Enclave Key along with an attestation. So that, Request Chain can verify relayed responses from Common Chain.

Gateways must provision native tokens on all supported Request Chains, as well as the Common Chain, to efficiently cover gas fees when relaying requests and responses. Signatures created with the Gateway Enclave Key are used to verify that Gateway assignments are correctly executed, ensuring that only valid requests are relayed and only attested responses, submitted by Executors on the Common Chain, are transmitted back to the Request Chain.

New Gateway registrations as well as any changes to their stake come into effect after the end of the Epoch in which changes are made.

Gateways Draining​

Once a Gateway's draining process is initiated by its owner, the Gateway will no longer be assigned new requests to relay after the start of the next Epoch. A Gateway is considered fully drained only if the draining process has been active for longer than one Epoch. The operator can then deregister the Gateway or withdraw stakes, but only from a fully drained Gateway. This ensures that Gateways always have stakes deposited, making them eligible for slashing if necessary. Gateways can be revived after being drained and resume participation in gateway assignments for relaying Requests and Responses.