Sequence (SQNC) architecture has two variations depending on the use case:
- In most cases, an external API creates, reads and burns tokens via HTTP using
sqnc-api
, which then handles communication withsqnc-node
andsqnc-ipfs
. - When it's necessary to monitor on-chain state directly within an external API service (e.g.
sqnc-matchmaker-api
), the service subscribes tosqnc-node
via WebSocket. This means it must also communicate withsqnc-ipfs
via HTTP to upload/download files in tokens.