There’s a lot happening within the diagram displayed above. Nonetheless, the processes displayed are repetitive. The diagram proven under zooms in on a single state change receipt and the way it factors to a stateHash in a previous IPFS batch.

What’s the historical past of a ticket execution?

Do not forget that all of the state change receipts are structured in a repeating construction.

A: (stateHash t=n),B: (stateHash t=n-1), C: kind: f=firing , D: 2 

To search out the earlier state of this execution the ticket explorer might want to question the worth present in B: (stateHash t=n-1) on the primary place of a mutation receipt in a previous IPFS batch.

Because the earlier stateHash (B) would be the ‘present stateHash (A)’ of the mutation receipt in a previous IPFS batch. In pseudo-code we’re searching for a mutation receipt with B on the primary place:

IN BATCH FIND * WHERE A = (stateHash & t=n) FOR BATCHES WHERE t<n

Beneath you discover the output of such a question. In daring context is supplied.

27DiJvDmjtAHwHxU5a7s5zzf8MEbBJF9NUu6mvaG,zFsGM27VMNWZne1SSkWnDQTzr6TdjmsKpbxGkJKKaEC8e,w,0  -> Occasion wiring state change receiptzFsGM28J4Vh7ycAHvaHzy4SyyQiZ1nwYjGdZK71VbcQ9A,zFsGM27DiJvDmjtAHwHxU5a7s5zzf8MEbBJF9NUu6mvaG,f,0 -> Preliminary firing of executionzFsGM273hfXgKWXanz3v8UqYzdy8Rc8dRPzqkc2JvnJ5Z,zFsGM28J4Vh7ycAHvaHzy4SyyQiZ1nwYjGdZK71VbcQ9A,f,13 -> State change 2ndzFsGM289462RDKVqkZ8MRDapH2ZWuvqBGgLXieidVN4hy,zFsGM273hfXgKWXanz3v8UqYzdy8Rc8dRPzqkc2JvnJ5Z,f,2 -> State change thirdzFsGM27bm6Ur4v2TgRwX1XHDd3F96kdTDEA2VeJKKcBos,zFsGM289462RDKVqkZ8MRDapH2ZWuvqBGgLXieidVN4hy,f,6 -> State change 4thzFsGM26PgU7eP2uHyB7TsSBxAnXADZDm2bspRL71EvvMN,zFsGM27bm6Ur4v2TgRwX1XHDd3F96kdTDEA2VeJKKcBos,f,3 -> State change fifthzFsGM26FJ3XVFETU3vWtFJP9nQuTgT4HxE6th598zMrty,zFsGM26PgU7eP2uHyB7TsSBxAnXADZDm2bspRL71EvvMN,f,11 -> State change sixth

The end result above reveals 6 state modifications and 1 wiring receipt. If we’d add the timestamp of the IPFS batch that anchors these state modifications we’d have the ability to create a timeline for this ticket.

What do we all know now?

With none further knowledge concerning the occasion or this ticket, we will solely conclude that ‘a’ ticket modified state 6 instances (together with the precise instances of every state change).

If we wish to know extra about what these state modifications precisely entailed, a verifier must know the wiring instruction. That is just like Ethereum/Solidity, a contract name solely makes for an observer after they know what code is being run. With GET all wiring directions are public by default, how this works intimately is defined within the weblog overlaying wiring linked under:

[blog/info not yet public — awaiting the addition of enhanced authentication by Statebox]

transitions = 
0: 'init_create',
1: 'fire_block',
2: 'fire_buy',
3: 'fire_buy_',
4: 'fire_buyBack',
5: 'fire_cancel',
6: 'fire_forSale',
7: 'fire_noShow',
8: 'fire_notResold',
9: 'fire_notSold',
10: 'fire_notSold2',
11: 'fire_scan',
12: 'fire_showOver',
13: 'fire_unblock',
transitions =
0: 'init_create',
1: 'fire_block',
2: 'fire_buy',
3: 'fire_buy_',
4: 'fire_buyBack',
5: 'fire_cancel',
6: 'fire_forSale',
7: 'fire_noShow',
8: 'fire_notResold',
9: 'fire_notSold',
10: 'fire_notSold2',
11: 'fire_scan',
12: 'fire_showOver',
13: 'fire_unblock',

With this mapping, you might have a exact historical past of how ‘a’ ticket modified state over time. So this may depart us with:

zFsGM27DiJvDmjtAHwHxU5a7s5zzf8MEbBJF9NUu6mvaG,zFsGM27VMNWZne1SSkWnDQTzr6TdjmsKpbxGkJKKaEC8e,w,0  -> Occasion wiring state change receiptzFsGM28J4Vh7ycAHvaHzy4SyyQiZ1nwYjGdZK71VbcQ9A,zFsGM27DiJvDmjtAHwHxU5a7s5zzf8MEbBJF9NUu6mvaG,f,0 -> 1st: Ticket Create zFsGM273hfXgKWXanz3v8UqYzdy8Rc8dRPzqkc2JvnJ5Z,zFsGM28J4Vh7ycAHvaHzy4SyyQiZ1nwYjGdZK71VbcQ9A,f,13 -> 2nd: Ticket Unblocked zFsGM289462RDKVqkZ8MRDapH2ZWuvqBGgLXieidVN4hy,zFsGM273hfXgKWXanz3v8UqYzdy8Rc8dRPzqkc2JvnJ5Z,f,2 -> third: Ticket PurchasezFsGM27bm6Ur4v2TgRwX1XHDd3F96kdTDEA2VeJKKcBos,zFsGM289462RDKVqkZ8MRDapH2ZWuvqBGgLXieidVN4hy,f,6 -> 4th: Ticket forSalezFsGM26PgU7eP2uHyB7TsSBxAnXADZDm2bspRL71EvvMN,zFsGM27bm6Ur4v2TgRwX1XHDd3F96kdTDEA2VeJKKcBos,f,3 -> fifth: Ticket Buy_

[blog/info not yet public — awaiting the addition of enhanced authentication by Statebox]

Any questions or wish to know extra about what we do? Be a part of our energetic Telegram group for any questions you might need, learn our whitepaper, go to the web site, be a part of the dialogue on the GET Protocol Reddit. Or get your self a wise occasion ticket in our sandbox atmosphere. Obtain the GUTS Tickets app on iOS or Android.



Supply hyperlink