Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Record proposals for live rhododendron sessions in the DB #115

@rphmeier

Description

@rphmeier

To prevent accidental double-propose when going offline for a short period.

DB holds a mapping equivalent to a HashMap<parent_hash, Vec<(round number, proposal)>>.

When proposing at a round k on top of a given parent hash, check if we already proposed at this round and don't create a new one. Otherwise, place the new proposal in the mapping and commit to disk.

When importing a block on top of parent_hash, clear all recorded proposals based on it as they are no longer relevant.

Metadata

Metadata

Assignees

No one assigned

    Labels

    I4-annoyanceThe client behaves within expectations, however this “expected behaviour” itself is at issue.Z1-easyCan be fixed primarily by duplicating and adapting code by an intermediate coder

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions