Skip to main content
Events represent state changes, like a new message or contract event. Snapchain nodes emit events whenever they observe a state change. Clients can subscribe to a node using the Events API to get a live stream of changes. Snapchain keeps events around for 3 days after which they are deleted to save space. To get older data, use the GRPC or HTTP APIs.

HubEvent

Event ID Construction

Event IDs are constructed to ensure chronological ordering by block. The ID combines:
  • The block height (when the event was created)
  • A sequence number within that block
This design allows clients to determine which events occurred in the same block and their relative order, which is useful for processing events in chronological sequence.

HubEventType

MergeMessageBody

MergeUserNameProofBody

PruneMessageBody

RevokeMessageBody

MergeOnChainEventBody

OnChainEvent

OnChainEventType

SignerEventBody

SignerEventType

SignerMigratedEventBody

IdRegisterEventBody

IdRegisterEventType

StorageRentEventBody

TierPurchaseBody

MergeFailureBody

BlockConfirmedBody