-
Updated
Jul 28, 2020
protocol
Here are 1,377 public repositories matching this topic...
-
Updated
Sep 17, 2020 - JavaScript
-
Updated
Sep 12, 2020 - Swift
Background
When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.
In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the
-
Updated
Sep 18, 2020 - Go
-
Updated
Sep 16, 2020 - Rust
-
Updated
Apr 17, 2019 - Objective-C
-
Updated
Apr 13, 2020 - Swift
-
Updated
Sep 16, 2020 - C++
-
Updated
Sep 9, 2020 - Go
On macOS, it's a fairly standard practice to display a pre-roll if your application needs some form of permissions, before calling the system APIs for the first time that will actually produce the system's requested-permissions window.
For instance, for any given end-user, the following window is likely A) intimidating, and B) possibly encourages insecure habits, such as simply clicking "acce
-
Updated
Jul 6, 2020 - C
-
Updated
Sep 16, 2020 - CSS
-
Updated
Jul 5, 2020 - C
Now that we have code coverage enabled there are a few places we can easily improve test coverage for.
- Get/Set all parameters for all types of objects
- Trigger the Settings updated code path by setting a registry key
- Test out multiple registration execution modes
- Test Server IP load balancing mode
- Packet drops in validating received initial token
- Trace ru
-
Updated
Nov 3, 2019 - Go
-
Updated
Nov 6, 2018 - Swift
Encrypt retry token
When stateless retries are enabled, Quinn embeds some state in the retry token and authenticates it with a HMAC. This information is not secret, so the current approach works, but it would be more in the spirit of QUIC to use strong encryption to prevent other parties from coming to rely on that data, creating a stability hazard.
The stateless nature of retry tokens requires some care if we wan
I have a library that I generate all of my mocks into that is imported in my unit tests. When mocking a protocol, the generated mock object doesn't have an initializer declared. This means is uses the default initializer, which would be fine, except the default init() method is internal. I can get around this by importing my mock library @testable, but I'd suggest that protocol mocks for publi
-
Updated
Sep 18, 2020 - Java
-
Updated
Sep 10, 2020 - Python
-
Updated
Sep 17, 2020
I'd like IPFS companion to use a local gateway without exposing a local IPFS API endpoint. Unfortunately, if I do this, companion will direct all dnslink queries to the public gateway because my local IPFS node "has no peers".
If I configure companion to use a specific IPFS gateway, I expect it to always use that gateway.
-
Updated
Sep 14, 2018 - Swift
Improve this page
Add a description, image, and links to the protocol topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the protocol topic, visit your repo's landing page and select "manage topics."
Right now the docs correspond to what's on
master. We need docs for each daemon release so developers can see what's available in the version they are using.https://github.com/jimporter/mike may be helpful.