Node

Node copied to clipboard

czarte

Improve Stability in the Payment Process

2

I and Bert identified a couple of problems which are likely responsible for frequent delinquency bans in the network. The current mechanism doesn't seem reliable enough because of rather a...

utkarshg6

Currently, when a Node is delinquency-banned, it remains a fully-connected part of the network, but the Nodes that have delinquency-banned it simply drop its data and Gossip CORES packages and...

dnwiebe

Heartbeat Message

1

Why We Need This? - Consider this situation: an exit node is unaware that a node, which is a member of the route back, has died. As a result, the...

utkarshg6

Header Names Are Not Case-Sensitive!

1

The HTTP standard states that HTTP header names are not case-sensitive. Therefore, `Host`, `host`, and `HOST` all mean the same thing. However, in `HttpProtocolPack`, in the `find_header_host()` function, only `Host`...

dnwiebe

Add RatePack limits

2

1. Let user establish price limits beyond which he will not pay. 2. Make these limits part of the Gossip, so that other Nodes will be able to use that...

dnwiebe

Add routing logic for Ping

3

This card depends on GH-585. Calculating the route for a Ping is not trivial. First, if we're wondering about the latency of a link, we don't want to Ping the...

dnwiebe

FinsaasGH

This card depends on GH-586. We don't have time for a complete description of the problem here, but this card should be about modifying the existing latency-measurement logic to: 1....

dnwiebe

Introduce CORES packages for Ping and PingResponse

2

As of the writing of this card, there are five structures that can inhabit a CORES package: `Gossip_0v1` `NodeRecordInner_0v1` (this is cheating, kind of; see below) `DnsResolveFailure_0v1` `ClientRequestPayload_0v1` `ClientResponsePayload_0v1` `NodeRecordInner_0v1`...

dnwiebe