Thomas Eizinger
Thomas Eizinger
With https://github.com/firezone/firezone/pull/4268, sending of the relay candidates is always delayed. It would be better to only delay it if we think that we aren't behind a restrictive NAT.
> > we should be able to avoid sending our relay candidates to the other party because we should be able to hole-punch. > > This is a risky assumption...
I made a thing: https://github.com/comit-network/rust-elements-consensus
It is highly experimental at the moment 😁 But have a look please yes! We will be playing around with it internally soon, can report back on whether or not...
It has worked well for us to test spending of covenant scripts, but it is not released yet to crates.io. Happy to transfer it into the org if you find...
> @thomaseizinger I have updated the descriptions, but on some options I do not know for what they are, maybe you know. 😄 Looks all good from what I can...
> Ok, some descriptions still have only `""`. Maybe you could add some text here. If they got filled the PR is ready I think. I don't think I understand...
> > I would also advise against merging packaging-specific files into the main branch as more of them could be added in the future and it would quickly become a...
The convention for files added to a repo but not necessarily have them up-to-date is to put them in a `contrib/` directory.
I believe the idea is that it is cheap to clone. The `Multiaddr::push` function for example uses clone-on-write to either reuse the current allocation if there are no other copies...