-
### What is the issue?
On a NAT64 network, the network exposes a special route (generally 64:ff9b::/96) which will be translated to IPv4 addresses as it leaves the network. This is complemented by DN…
-
We need to start investigating and hardening Iroha against malicious network inputs. The consensus is robust against malicious peers but is not robust against many peers being successfully targeted by…
-
### Current State
LibraNet was originally written for the validator network use-case, while other use-cases such as the validator-internal network and Public FullNode network were engineered in aft…
-
In https://github.com/fedimint/fedimint/pull/4278 I'm disabling random peer errors because they expose some consensus problem that is causing severe flakiness which can be reproduced clearly with: htt…
-
### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [X] My issue happened while using mods.
### What happened?
when the campaign runs, …
-
## Goal
For protocol changes where we know that old peers will not be able to process the data from the new protocol version we are considering introducing a fork in the peer network. Effectively t…
-
## Motivation
To avoid Zcash peer connection storms, we want to start disconnecting from outdated peers before network upgrade activation.
### Specifications
Here is what `zcashd` does:
http…
-
**Describe the bug**
We're running NanoMQ in a bridged setup where topics prefixed with `cloud/` are forwarded to our cloud MQTT broker (managed EMQX cloud instance). In case the network connection…
-
We have two bootnodes running at polkadot-v0.9.38. Upgrading one of these to our new client, which is at polkadot-v1.1.0 raises the following two error messages:
```
[🔮 Zeitgeist Parachain] Report…
-
Commit 09c4b066e25104be8b066e8f7530ff0c6df4ccd5 seems to have broken the JSON serialization logic for `BurnchainHeaderHash`:
```diff
-#[derive(Serialize, Deserialize)]
pub struct BurnchainHeader…