oasisprotocol / oasisprotocol/oasis-core

Consider making deferred InitChain events non consensus-breaking

Open
#4,389 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

c:breaking/consensus c:consensus/cometbft
Dominant language
Go
Stars
369
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
6

Description

Currently events emitted from InitChain handlers are deferred until the first block by serializing them into storage. Even though event changes are otherwise not consensus-breaking, handling them like this makes them so as the initial state root depends on their serialization. It would be great to change this to avoid unexpected breaking changes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the InitChain event handling, deferred serialization into storage, and the initial state-root computation. Determine how event serialization currently affects consensus, then define and test a design where changing those events does not change the initial state root or create unexpected breaking changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.