circuitbreaker VS i2pd

Circuit Breaker v0.3.1 (Released: 25th July 2022) - https://github.com/lightningequipment/circuitbreaker/tags

A lightning 'firewall' to avoid griefing attacks (see Github repo, and Bitcoin Magazine article). Alpha quality so should be as an option, not in main guide yet.

In the case depicted in Fig-2, our routing node is directly connected to the custodial service. This is ideal to optimize the attack: the deposits have no cost, HTLCs will settle quickly, and we avoid the limitations set by other routing nodes using CircuitBreaker (payments fail when a few HTLCs are pending). If the attack is successful, having a lot of inbound liquidity from other nodes is key. The channel to the custodial service will quickly become unusable as we have stolen the liquidity to our side. Therefore, you want to desuturate it by circular rebalancing. Once we free up inbound liquidity from the custodial service, the channels to our liquidity providers will be saturated, we can chose to close those and move the profits on-chain or we could loop out (not sure which process is less costly: we are making free BTC, does it even matter?)

That's old news from last year. Already been addressed: https://github.com/lightningnetwork/lnd/pull/4527 https://github.com/lightningequipment/circuitbreaker

The nano shiller proceeds with more FUD: "Ya but LN has many security issues, there is the famous flood & loot attack, you should google it". What the nano shillers either don't know, or as I would expect from them, consciously omit is that we already have a sort of "firewall" for this attack and this problem has been fixed. I suspect consciously because they always claim bitcoin is not scalable when this is obviously false and they know that too.

Ah ok I misunderstood your question then. The third option is what i use also. For your 4th option take a look at https://github.com/lightningequipment/circuitbreaker where an hold fee for an htlc was discussed. The base fee part could probably be used as you suggest as fourth option but I do not think something like this is implemented anywhere yet.

1) Flood & Loot attacks have been fixed. Source 1 & Source 2.

And here https://github.com/lightningequipment/circuitbreaker

I'm running a tor bridge on my home proxmox box, and I'm interested in running an i2p node as well but I have no experience with this. From what I was able to gather the easiest way is to install the i2pd .deb (https://github.com/PurpleI2P/i2pd/releases).

need someone to find me c++ developers who are very familiar with the i2pd codebase and link me up with them for the price of $25 USD (I can do payments in crypto or cashapp).

If you really dislike Java that much, there are other I2P implementations like this:

https://github.com/PurpleI2P/i2pd

I created an ansible role for i2pd. Basically, this allows system administrators who want to take part in the I2P network to automate i2pd deployment.

Check this: https://i2pd.website/

there may be instructions in the github i think? https://github.com/PurpleI2P/i2pd

> We are building network which helps people to communicate and share information without restrictions.

> Free from censorship. Free from privacy violations.

https://i2pd.website/

I2P is neither “for” nor “not for” piracy. I2P is for protecting communications and data from any kind of censorship.

Filtering copyright violating content is a type of censorship. To some it is justified. To others it is not.

To a network protocol like I2P the point is that no kind of censorship should be possible. Regardless of reason.