The following steps were tested on a M1 Macbook Air. However, it might work for other Macbooks with different processor architectures.

Sniffers are only active for a relatively short time so as not to create accidental leaks. Sniffers should be open when testing is started, and only for legitimate reasons like debugging, development, or security analysis, and should be closed when testing is done.

Since the HTTP sniffer is HTTP-based, it can be used to create a loop if several individuals look at the same page or if there is some unsynchronization, thus enabling HTTP or web-socket traffic sniffing. This should only be used in a development environment.

Beyond the web sniffers.

In addition to web sniffers, various alternative tools are available for troubleshooting. Logs and communications are stored in distinct directories and subdirectories (under the IoT Gateway directory) for a limited duration, depending upon the configuration in the Gateway.config file. Access to the Neuron® server is necessary to review these records retrospectively. The following directories hold significance in this context and can be highlighted with brief descriptions:

1. Events
2. Exceptions (comprising both text files (logs) and XML files (statistics))
3. HTTP
4. SMTP
5. UPnP
6. XMPP (about neuron communication with the parent neuron)
7. XMPP_C2S (denoting client<->server communication)
8. XMPP-S2S (referring to server<->server communication)

Importantly, XML-based logs remain open until explicitly closed. These logs are assigned new filenames every hour, including an embedded XSLT file. This embedded file facilitates the conversion of XML content into HTML, making it viewable in web browsers. When reviewing unclosed XML logs, the process involves copying the file, manually adding the end tag using a text editor, and then opening the copied file in a browser to view its content.

Example:

(TODO)

Database Export

Moreover, a practical utility under the Backup section in the Admin dashboard permits users to export database content (or parts of it) or Neuro-Ledger® to a designated file. This export can be in the form of an XML file, which users can navigate through. It’s worth noting that the file size can be substantial if the entire content is exported, but the utility is handy for exporting targeted portions to facilitate troubleshooting.

Chat Admin & Script-Promt

Furthermore, the Chat Admin and Script-Prompt tools are important and can be very helpful in debugging. It’s essential to delve into the concepts of “Collections & Labels” and “Namespaces & Types.” (TODO)

For those who require debugging capabilities for script and Markdown pages, the “Lab” section in the Admin dashboard of the Neuron® offers several relevant options, including:

1. GraphViz
2. Markdown
3. PlantUML
4. Script (Prompt)

• It is crucial to check the integrity between the human and machine-readable content of the contract. The auditor is responsible for assuring the rest of the network that these are consistent. This is what Trust means, and this is the basis for the responsibility a Trust Provider takes. Users should be able to trust that a real Trust Provider’s contract templates are correct and have integrity.
• Furthermore, contracts can be multilingual; therefore, it is essential to check all published languages so integrity is preserved in every language.