Code Browser

Ensure that all vote extensions in the commit info are verified

PBTS: analize the impact of long clock jumps

e2e must be able to test rollback command

mempool: CListMempool.CheckTx misuses read-lock to protect write operations; possible data race

crypto: provide simple way to add new curves

spec: move consensus parameters documentation from abci and data structures specs

e2e: `runner load` cannot be used from the same network as the testnet

evidence: evidence expiration parameters should match the chain's unbounding period

privval: add specification for the remote signer

e2e: pruning related test flakiness

Move to self-hosted github runners to save money

Mempool reactor test should not test transaction ordering

Evidence may not work consistently

spec: update `consensus/signing.md` documentation

golangci-lint: enable more linters

tests: `make test` fails locally while Github CI checks pass

Lightclient: Additional checks in VerifyAdjacent

p2p/pex: gracefully shutdown Reactor (Follow-up)

spec: Revise content of `spec/core/data_structures.md`

types: is a `Proposal` with `Height == 0` valid?

libs/json: decide if we should make cmtjson use Go's standard library encoding/json's incremental parser instead of amino-json based parser for the GenesisDoc, or instead implement an incremental decoder/parser for cmtjson

p2p: Sending a high-priority msg can take a long time due to full `MConnection` queue

consensus: extract block gossiping into its own reactor

Change `BlockSizeBytes` to a histogram

TxSearch silently does not honor a query if a timeout occurs

panic: proto: could not resolve import

In params.go ConsensusParams.ABCI should be ConsensusParams.Abci according to CamelCase rules

New ABCI method to surface to the application that there was a consensus error

TestInspectRun (15m0s) and TestInspectRun/from_config (15m0s) are flaky

design: Why does consumeGas panic & not return an error?