simperby

simperby copied to clipboard

I think we have to explicitly remove outdated agendas and blocks after finalization, and have to consider that in the read function so that we don't have to check that...

junha1

It must have `None` as the candidate and should stay the same when progress is requested

junha1

## Background Current impl. of Simperby's repository networking is based on directly fetching and pushing branches using the Git remote protocol. This works nicely, but has some drawbacks 1. Not...

junha1

junha1

fixes #289 Remove on_4f_non_nil_prevote_in_propose_step() in prevote event response.extend() works twice is fine

hataehyeok

I think so. Like `fp` or `dms`. I think it's worth having a doc for those abbreviations _Originally posted by @junha1 in https://github.com/postech-dao/simperby/pull/402#discussion_r1141396756_

fakedev9999

Change `(PublicKey, PrivateKey)` to `PrivateKey`

1

`PublicKey` is always derivable from `PrivateKey`

junha1

Handle `ConsensusEvent::valid`

1

The consensus module would query the validity of the given proposal to the node, instead of just skipping it if it's not currently included in the known verified set.

junha1

junha1

We should allow every operation on an arbitrary branch. See #374 for the background (no local git server)

junha1