You have tried the ERC20 Messaging dApp to see Topos in action and have executed a cross-subnet token transfer. You were presented with a very high-level view of what happened, just like what a user would see.
You can now use the Topos Explorer to see more details. Because Topos subnets are EVM-based, an explorer for Topos can use the standard Ethereum JSON-RPC API. In addition, the Transmission Control Engine (TCE) will expose a GraphQL endpoint available (here).
In addition to the Topos Explorer, you can also access Blockscout instances for the Topos Subnet and Incal. Blockscout is a fully-featured open source blockchain explorer tailored to work with any EVM-based blockchain. Blockscout will provide you with more detailed information about the blockchains themselves while the Topos Explorer will focus on Topos-specific information.
Navigate to the Topos Explorer:
If you look at the Topos Subnet by clicking on the Subnet tab, you will observe multiple pieces of information about the subnet:
- Subnet name
- Subnet ID
- Subnet currency
- Subnet RPC endpoint
- Latest blocks being created
- Latest certificates being created
The Explorer displays live data without an indexer running in the background, meaning that in its current state you do not have access to historical blocks. Nevertheless you can find a link to all certificates above the latest certificates or search old blocks and certificates.
During your tests with the Playground, you created some transactions. Look for the blocks including these transactions:
You can see further details by clicking on a block:
Here you can see that the cross-subnet token transfer you invoked triggered a call on the ERC20 Messaging Contract.
You learned about the ERC20Messaging contract in the first chapter. This optional contract is used in the context of the ERC20 Messaging dApp for cross-subnet token transfers.
Topos guarantees that certificates are delivered with certain conditions fulfilled, like causal ordering. The execution logic of the transactions included in those certificates is not part of the core protocol. The Topos executor service on the other hand is an example implementation for such a logic. You can call the executor service API endpoint in your browser to explore what's on offer. Note that you will need to authenticate your request.
It is nice to have these kinds of tools to get started with a new protocol. Of course, we have glossed over a lot of details. The next section will explain how to run a local network and examine the actions performed during your test.