Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SBliFF v1: Semi-Blind Faith Finality V1 #242

Closed
brenzi opened this issue Jan 7, 2024 · 2 comments · Fixed by #255
Closed

SBliFF v1: Semi-Blind Faith Finality V1 #242

brenzi opened this issue Jan 7, 2024 · 2 comments · Fixed by #255
Assignees

Comments

@brenzi
Copy link
Contributor

brenzi commented Jan 7, 2024

The most simple finality for Integritee TEE-validated sidechains only guarantees the following:

  1. next finalized block is a lineal descendant of previous finalized block
  2. block number is monotonically increasing
  3. ShardConfig is respected
    • only authenticated TEE's within a potentially limited set are authorized to propose finality candidate blocks

from the chain's perspective, the validateers are trusted to only supply legit blocks. They are, however, not trusted to be up to date with either the chain state nor its peers

Therefore, there is no need to know intermediate block hashes to accept new blocks. We can relax (1) and just make sure the validateer knows all blocks between our last finalized block and his proposed candidate block

SBliFF specification

storage:

  • last_finalized_block: (BlockNumber, BlockHash)

dispatchables:

confirm_imported_sidechain_block(
  shard,
  latest_finalized_ancestor: (BlockNumber, BlockHash),
  finalization_candidate: (BlockNumber, BlockHash),
)

ensure(authorized for shard)
if finalization_candidate.number <= last_finalized_block.number: fail
if latest_finalized_ancestor.number != last_finalized_block.number: fail
if latest_finalized_ancestor.hash != last_finalized_block.hash: fail

last_finalized_block = finalization_candidate
@clangenb
Copy link
Contributor

clangenb commented Jan 8, 2024

From what you told me about the finality before, I have thought about the finality conditions of BliFF, and I came up with the same conditions and I think they are sufficient for finalizing sidechain blocks.

I am uncertain about the naming though, which part of this is 'faith'? There is no faith involved IMO, we know that a registered sidechain validateer knows by design all blocks between latest_finalized_ancestor and finalization_candidate. I am saying this because I am a bit wary of the word faith, which might foster the misconception that we indeed have to believe instead of knowing something at some point, which is not really trust creating.

@brenzi
Copy link
Contributor Author

brenzi commented Jan 8, 2024

yeah, definitely not a marketing term ;-) I was just tempted to refer to https://en.wikipedia.org/wiki/Blind_Faith not meant to be serious ;-)
still: the faith remains from a chain perspective in the guarantees of SGX and our design to ensure integrity of sidechain blocks

@brenzi brenzi self-assigned this Jan 17, 2024
@brenzi brenzi changed the title BliFF v1: Blind Faith Finality V1 SBliFF v1: Semi-Blind Faith Finality V1 Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants