Introduction

Every time a transaction is executed in Evmos, different messages with the transaction’s information are created and registered. The goal of this documentation is to allow users and developers to understand these messages and the elements that compose them. The actual data from existing transactions can be accessed through Numia’s open databases or through their Data Analytics services.

Transactions, messages, events, attributes…

What are these messages that are stored? Well, they are nothing more than key-value documents that gather all the relevant information regarding the transaction. While most of the transactions derive in the creation of a single message, there are occasions where multiple messages are generated in a single transaction. This is why, no matter if there is one or more, all the messages related to a transaction are saved together in a list. With this list we can understand everything that happened within that transaction.

Deepening in the structure

The structure of the messages is quite simple. They are documents composed by two key-value pairs. The first one, “msg_index”, contains the value used to identify each message that exists inside a transaction. The second one, “events”, saves a list of the different events that were triggered in relation to the message.

The structure of these events is quite similar to that of the messages. They are also documents formed by two key-value pairs: “type”, which indicates the type of event that was triggered, and “attributes” that saves a list of the different attributes related to the event.

I suppose you won’t be surprised if I tell you that attributes are, once again, documents that include two key-value pairs. In this case the first one, “key”, sets the attribute identifier, and “value” the value of that attribute.

With this structure we can easily define transactions that are described by one or more messages, each of which can register one or more events that were triggered, each of which includes one or more relevant attributes.

This may seem complex but, hopefully, the image shown in the right helped you follow what we were trying to explain. Below you can find another image that shows a schematized version of the structure, which may also help you to have a clearer view of the matter.

     Raw log of a transaction and its messages

Using the tool

As said previously, the goal of this tool is to help users and developers to understand better the messages and underlying elements that register the transactions that have been done in Evmos. To do so, in the tool you’ll be able to find all the different types of transactions that have been executed in Evmos so far. For each of them we have included the following information:

• Name → the name of the transactions as it is shown in Mintscan.
• Topic → the topic the transactions relate to. This value has been set by us with the aim of grouping different transactions that have related objectives/goals in the blockchain.
• Domain → the module of the blockchain in charge of managing them.
• Message → the name of the message that identifies the transaction type.
• Linked Action Messages → the name of other messages usually sent together with the previous one.
• Deprecated messages → the previous message name the particular transaction had.
• Event types → all the different event types that are launched in the transaction and recorded in the message.

<aside> 📌

</aside>

This main set of information, and its organization in columns, allows the filtering of information through the six toggles that appear right above the column names. With this, you’ll be able to select only the transactions or elements you are looking for in a easy manner. However, there are still more utilities included in the tool.

By clicking on any transaction name, a side window with more information about that particular transaction will appear. In it, you’ll be able to find:

• A low level description about what does the transaction do.
• Other transactions that are related to the selected one.
• A complete explanation about all the different event types that are launched in the transaction, together with descriptions of the attributes included in each of them.
• And a parsed and structured example of a real transaction of that kind, so that you can compare it with the descriptions mentioned in the previous point and clear possible doubts that may come up. The example also includes a link to Mintscan, in case you’d also like to check what other information is stored for every transaction. The message-related information can be found in either the raw-logs or the logs.

With this, we believe you already have the sufficient knowledge to start using the tool. We’ve tried to make it as user-firendly as possible, so the more you use it the easier you’ll find its usage. You may even come up with ways of using it we didn’t think of!