Crosslink Workshop: Wednesday, Oct 22nd at 5pm UTC

The way we currently do it is that we store sigma headers inside the BFT payload. The “oldest” of these is the one being finalized. The sigma-1 child blocks to the finalized block are highlighted on mouse hover of the BFT block in question. However, if the PoW system in Zebra is not independently aware of the blocks we don’t visualize them. It is a confusing visualization right now, we are working to revamp it.

The workshop did run with sigma = 3. Although we don’t rigorously implement all of the validations currently.

The new version of the visualizer will implement analytical layouting and will show the “rolled up” bc headers in a more obvious way.

5 Likes

I see. What rules are not currently implemented?

A lot of the content was written by @shielded-nate! And one of the critical ideas (either the Extension rule or the Linearity rule, or possibly both; I’ll have to check) is due to @str4d. The basic idea of “trailing finality”, and also the Last Final Snapshot rule IIRC, are also due to @shielded-nate. The security analysis of these rules’ interaction is primarily by me.

5 Likes