corver

Results 23 issues of corver

## Problem to be solved Consensus on info_sync duty is triggered every epoch (32 slots). That means that any cluster size that is a divisor of 32 will have a...

protocol
next-sprint-candidate

# 🎯 Problem to be solved go v1.20 added support for "integration test coverage", we should report this as part of our compose/smoke tests. # 🛠️ Proposed solution See [blog...

protocol

## Problem to be solved VCs do not support our proposed aggregation endpoint yet. They do however request and submit aggregations "incorrectly and randomly". This causes weird errors that may...

protocol

## Problem to be solved We currently require nodes to be publicly accessible via a static IP address (determined at startup), otherwise nodes must connect via a bootnode relay (using...

enhancement
protocol

## Problem to be solved We currently track the number of duty exit partial signatures in parsigdb by pubkey. This has a few problems: - Cannot distinguish between exits submitted...

enhancement
protocol

## Problem to be solved QBFT current requires every peer to call `Propose` for that peer to participate in a consensus round. This has negative effect on over latency, since...

enhancement

# 🎯 Problem to be solved The current configuration is not optimal for users behind a NAT that want to advertise a public address instead of relying on automatic peer...

protocol

# 🎯 Problem to be solved A user on discord reported that refactoring the docker-compose command syntax for geth and lighthouse and others to an array improves developer experience especially...

protocol

# 🚀 Feature Request ## Problem to be solved This repo only support teku VC, but we want to add support for multiple VCs. So add opt-in compose files for...

protocol
next-sprint-candidate

# 🚀 Feature Request ## Problem to be solved The `node-exporter` container doesn't have any mounted volumes, so it doesn't seem to have access to proper host metrics 🤷 See...

protocol