pull down to refresh
It seems that your node get mixed with the biggest one, two option for me:
- Testing an attack vector to biggest nodes
- Just "cleaning" (there is no dirty sats) quick a big amount
Do you see some traffic or it was just open/close to your node?
A software to manage my bitaxes, to easily change the power consumption (winter/summer), possible base on electricity cost too.
Bitaxes is super simple, but you still need to know about pool configuration, url, port, password, etc...
Some common recomendation for any hardware like these:
- Use wire to connect to the network if you can
- Start with the lowest hashrate configuration and then increase
We are far away from a Plug and play product without loosing something in the middle.
They need to look into Argentine, this is the same storytelling to put the state in the middle.
- Someone (the state) need to put a max price
- The situation is this because some external actor (bad people, funds, the rich) are buying to rent and it is because of "them" that you can't rent
- We need someone (the state) to build more house at cheaper price
See the pattern? They want to robe you one more time, stop watching the news, use bitcoin, there is NO issue, just the state making noise between private.
Just to add more info, this strategy get my attention: https://github.com/zapomatic/zap_lnd_tools?tab=readme-ov-file#cooperative-fee-strategy by @zapomatic
With time you can identify this type of node and act accordingly:
- Blacklist
- Only open big channels so you can close the channel without losing sats once the liquidity is in the other side (capital intensive).
- Set max_htlc so low that the drain take a lot of time an effort
Repository to collaborate if you know python https://github.com/andreasgriffin/bitcoin-safe