The GeoHackers bot can watch an XL1 address and post each new transfer into or out of it in a Discord channel you choose, with links to the Oxyon explorer.
Get started: the bot is in two Discord servers: the UnOfficial XYO Discord and the WinLEW Discord. Join either, and read the GeoHackers guide for what the bot does and how to verify your wallet. Watching an address doesn't need a verified wallet.
Subscribe to an address
| Command | Who can use it | What it does |
|---|---|---|
/watch xl1 add <address> [network] [channel] [label] [mode] | members with Manage Channels | start watching an address |
/watch xl1 remove <address> [network] [channel] | members with Manage Channels | stop watching, in one channel or in every channel of the server |
/watch xl1 list [channel] | anyone | what this server watches |
- Address: the 40-character XL1 address.
- Channel: where posts go. If you leave it out, posts go to the channel you ran the command in.
- Label: an optional name for the address, up to 32 characters of plain text. Mentions, links and formatting are removed.
- Mode: each posts every transfer. Digest posts one summary every 10 minutes.
- Starting point: nothing older than the moment you add an address is posted. The bot replies with the block it starts from.
Mainnet and Sequence
- Network is
mainnet(the default) orsequence, XL1's other public network. - The same address on the two networks is two separate watches, with separate posts. Add both if you want both.
- Every post names its network, and its links open the explorer on that network.
Permissions and limits
- Only members with Manage Channels can add or remove watches. Anyone can list them.
- The bot needs View Channel and Send Messages in the channel it posts to. It says so if it can't.
- Posts never ping anyone, and they show no link previews.
| Limit | Value |
|---|---|
| Addresses watched per server | 10 |
| Channels per address, per server | 3 |
| Posts per channel | 5 a minute, then one summary line |
| Busy addresses (over 20 transfers in 10 minutes) | a warning when you add one, suggesting digest mode |
| How often each address is checked | about once a minute, slower if very many are watched |
What a post means: observed activity, not finality
My wallet received 45.125 XL1 as a block reward · observed in Mainnet block 2,089,325 · [block] · [address]
- "Observed" means the bot saw the transfer in XYO's chain data, read through the Oxyon explorer's API. It is not a finality guarantee.
- A post isn't changed if a block is later reorganised. The address page on the explorer is always the full record.
- Received transfers link to their transaction, or to their block when no transaction is named. Block rewards link to their block.
Delivery: at most once, and every gap announced
The bot never posts the same transfer twice. The price of that guarantee is that a post can occasionally be lost. When that happens, the bot says so in the channel, never silently:
- Discord refused a post: the next post that goes through starts with "⚠️ N earlier notifications could not be delivered here".
- The bot stopped while posting: a note names the block range that may be missing.
- Too much activity to read in one check: a note names the exact blocks that were not checked, then summarises what was.
- The bot was offline for over an hour: one catch-up summary instead of a flood.
When a warning appears, the address page on the explorer has everything.
What it reads
Only the public Oxyon explorer API. The bot doesn't contact XYO's RPC, block producers or Oxyon's observers directly, so watching an address adds no load to them.