It's clear that Pawtato has a backend server fetching data from the Sui blockchain — you can confirm this by inspecting network activity in your browser's developer tools when using their website. So let’s take a look at what’s happening under the hood.

How it Works Under the Hood

Getting Data from Sui

From the Sui docs (https://docs.sui.io/guides/developer/getting-started/data-serving), there are two main ways to fetch blockchain data:

• JSON‑RPC: Directly asking a Sui full node for events, transactions, or object updates.
• Custom Indexer: Like a database that continuously listens to every checkpoint (a snapshot of new blocks), extracts relevant actions, and stores them in database like PostgreSQL for fast querying

💡 Sui also offers newer beta/alpha interfaces like gRPC, GraphQL, and future scalable streaming APIs but most production setups still use JSON‑RPC or custom indexers.

Spotting Interesting Actions

Pawtato will implement logic to monitor action like:

• Token transfers (swap, send, receive)
• NFT mints
• …

This filtering happens either in real-time (via indexers) or by polling JSON‑RPC. For example, using sui_queryEvents they can check for specific event types

You can learn more here: https://docs.sui.io/guides/developer/sui-101/using-events

So Why There’s a Delay

Delays happen due to:

1. Indexer or polling lag – custom systems need time to ingest checkpoint data.
2. Message queueing – backend structures may batch notifications to avoid spamming or hitting Telegram API rate limits.

Pawtato likely uses the Sui JSON-RPC API to query for new events on a schedule. For example, the Sui RPC offers suix_queryEvents (or the equivalent SuiClient.queryEvents in ). In practice, Pawtato’s backend would loop (e.g. every few seconds) to fetch events involving tracked wallet addresses or common modules, then push matching events to the Telegram bot.

Alternatively, Pawtato could use a dedicated Sui indexer (Indexer 2.0) or GraphQL service. Sui Labs is building an Indexer+GraphQL RPC stack (currently in alpha) that ingests all transactions into a Postgres DB( Ref from https://docs.sui.io/guides/developer/getting-started/data-serving#:~:text=,level)

There is no built-in “webhook” service on Sui that pushes events. Pawtato might use third-party data APIs if any support Sui (e.g. a blockchain indexer service), but no standard webhook exists. In Ethereum you might use tools like Moralis or Alchemy, but for Sui such services are not mainstream yet.

If you're wondering how Pawtato tracks wallet activity and sends alerts to Telegram, the most likely setup is that they run a backend server connected to an on-chain indexer that listens to blockchain events in near real-time. Instead of directly watching each wallet through constant RPC calls, they probably use services like Subsquid, Suibase, or a custom indexing node to monitor and organize blockchain data efficiently. Your wallet actions—like sending tokens, receiving NFTs, or staking—are detected through these indexers, and when an event matches something you've subscribed to, their server queues it and sends a message to you via the Telegram Bot API. The delay you notice usually comes from a few factors: the time it takes for events to be confirmed and indexed, possible rate-limiting rules on Telegram to avoid spamming users, and internal queuing systems that handle alerts in batches. If they’re using RPC polling (less likely), you might experience longer delays, especially during high-traffic times. So yes, while it may feel like it’s instant, there's always a small buffer between when a transaction happens on-chain and when you get the alert—usually because their system is designed to be efficient and avoid false positives. If you want to dive deeper into how systems like this work, you can explore resources like Subsquid's indexing documentation, the Sui developer docs, or Telegram's Bot API documentation.