bitbox-wallet-app VS circuitbreaker

Here is the app repo that uses it. https://github.com/digitalbitbox/bitbox-wallet-app/. The Android app lives in frontend/android.

Following the link from there, I downloaded the file bitbox_4.37.0_amd64.deb.asc from here and followed the instructions.

Complementary to that, you can also download the official release from https://github.com/digitalbitbox/bitbox02-firmware/releases and install it manually using command line tools, after verifying it is legit by reproducing it. Or build the app yourself after checking that the bundled firmware is correct.

say what?

BitBoxApp v4.35.1 (Released: 06th December 2022) - https://github.com/digitalbitbox/bitbox-wallet-app/releases

It is not present on f-droid. See also this issue: https://github.com/digitalbitbox/bitbox-wallet-app/issues/1171

I downloaded the Ubuntu desktop app and I followed the signature verification instructions from here: https://github.com/digitalbitbox/bitbox-wallet-app/releases/tag/v4.30.0

After Android app is installed, unit began firmware upgrade - NICE! Straight from Github

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