Code Browser

build(deps): Bump google.golang.org/grpc from 1.82.1 to 1.83.1 in the go_modules group across 1 directory

feat(consensus): add opt-in asynchronous block event publication

FilePV HRS state can roll back after atomic rename, allowing conflicting validator signatures

Committed evidence can be accepted again after restart if the committed marker write fails

rpc/client/http: unbuffered subscription can stall WebSocket event dispatch

build(deps): Bump google.golang.org/grpc from 1.82.1 to 1.83.0

config.toml: bootstrap_peers rendered onto its comment line (trim-marker collapses newline)

fix(blocksync): don't treat already-committed block from slow peer as an error

fix(lp2p): cap per-reactor priority queue to prevent memory-exhaustion DoS

fix(mempool): AppMempool ABCI response handling, callback/cleanup, and lifecycle

test(consensus): fix flaky TestPrepareProposalReceivesVoteExtensions

Offering a free security review — no strings attached

Evidence `Hash` is 1byte off

Local 4-node testnet fails to peer on macOS 26.4.1 — `chacha20poly1305: message authentication failed`

PoI (Proof-of-Information Consensus)

PebbleDB v1.1.5 has 32-bit limitations. PebbleDB v2+ does not

Free Web3 Security Review for Your Repository

Expose WebSocket connection lifecycle events (disconnect/reconnect) in the Go RPC client for reliable event subscriptions

Version string mismatch in v0.37.17, v0.37.18; retry release CI job

Add configuration to disable O_SYNC in PrivValidator file writes for performance tuning

privval: better handling of remote signer errors

types: Protobuf Serialization Is Not Canonical

abci: Feature Request: Allow Application to Set Custom BlockIdFlag When Vote Extension Fails Verification

Peers erroneously removed during playback

Improve testnet command with key-type flag

Proposal: Extend the `privval.Message` interface to support signing arbitrary hashes

Logging websocket connection issues

e2e(main): Tests failing due to validator oscillation

consensus: do we really need `initialHeight` in the consensus reactor?

e2e: application logging is too verbose and not properly formatted