Lookup of the intstruction of a specific wiring

Statebox provides a ‘built-in’ wiring viewer explorer.

For example:

https://stbx-tx-explorer.netlify.com/#!/tx/zFsGM27o59f9Lu8bWjNHBG7Wbq5iftQA6uDt14zRdjCrH

Deep-dive: Event wirings with Statebox Cloud

The Statebox studio is a web tool that allows those that are want to explore the wiring of certain contracts a visual way to do so.

In the box to enter the contractHash of the event wiring you want to explore. If you have no contractHash by hand, I suggest you use the following resource: Statebox Cloud.

Step 1. Enter the wiring address you want to explore

Go to https://browse.statebox.cloud/. Paste the wiring hash of an event configuration you would like to explore.

Example wiring to enter into the transaction hash box: zFsGM28HZcicx8uHpBseng9SFbM4YmYTGBEoNoUPQGp9Z

After entering the wiring you want to explore, click on the chain icon that appears on the left side of the page after plugging the wiring hash.

Step 2. Create executions and move them around

Fire the create_init firing by doubling clicking the green enabled firing

By clicking on the green highlighted boxes (firings) one executes a certain state stange. This will show up in the dynamic wiring as a black dot(that are located in a certain place). These dots are called executions (or tokens).

The black dots in the wiring represent executions (of a ticket in this case). Anything could be tracked with the execution of course. Including, spots in the waiting line for ticket sale, drink tokens or any other asset that would benefit from registration.

Step 3. Play around

In order to get a feel of how a wiring works go wild! In particular, note the one-way nature of firings and how some firings are immutable (meaning that there is no route back to its previous state).

Wiring bug (23/1/2020)

Over the course of 5 months we have discovered that in some cases, the Lambda instance has been repeating the storage of certain wiring firings to IPFS. Causing some wiring receipts to be stored several times in IPFS batches (same hashes).

The counter on the website is unaffected by this issue as it feeds of a different data feed. No ticket execution data has been corrupted as data isn’t deformed or lost. Merely stored several times to much. The bug will be fixed in the next deployment of Stoolbox.