more than I thought.

Right now, this is just connected to the coinbase advanced trade API since I had that info handy and it was easy to plug into. It's just taking an order book snapshot every 5 seconds and saving a row of calculated data that I think is interesting from it. Good feedback on the colors :)

perhaps you forget that half of people have an IQ lower than 100.

I support this. The code refers to bitcoins as a sum of the base unit, so that would mean that the original intent satoshi had with the first code was to think of the smallest unit as bitcoins.

just throw it all into bitcoin and keep working.

I should have posted earlier :)

these days, vibe coding.

I hate this idea. lol.

For real though, lost keys are a treasure hunt for future compute development and innovation. If we just allow that to happen, we will all be better off as it creates a bounty for Quantum development. The bitcoin bounty is a force that moves humans toward the future.

Static HTLC max is good. The dynamic HTLC setting has proven to be a bad idea with current tech--as balances in flight mess with liquidity observation--a solvable problem but not one that is currently solved.

Currently, it's better to leave HTLC max static. Using inbound fee discounts and setting fee buckets has proven to be a nice way to not need to manually rebalance and allow flow to be more natural.

^ This. Everyone could benefit from running a signet test node as a dev environment and to learn more about bitcoin/lightning. And almost nobody (as a percentage of the population) should run a production lightning node on mainnet :)

I also see uneconomical forwards that seem incomprehensible. It seems that fees don't matter so much to real traffic. Only rebalancers seem to set fee limits in routing consistently. Many wallets like Alby appear to blindly send traffic, accepting whatever fees get the transaction to the destination with the most certainty according to their liveness metrics--but real traffic is fine paying higher fees.

This makes some sense, as Joe-Bob buying alligator jerky from Tom's Apocalypse Shack doesn't really care if he's paying 2-3% in lightning fees for the purchase.

Yes. Zap-O-Matic is connected and it's been working well :)

Are these two your lightning nodes?

Zaprite (01): https://amboss.space/node/03d7582343e179601979ba7e8ca61e35668992ac89326da1b53bfa60537f935957

and

zaprite-lnd: https://amboss.space/node/025ee809529b1e929007d91fb0a7eeeb5f9954e5939b647ab517d8d69c231d4f6c

Asking because that second one doesn't have any owner info and might be someone else pretending to be you for the connections.

Interested in opening a channel to Zap-O-Matic for more routing connections? :)

postgreSQL db replication can be done across machines and data-centers--that's more of a cloud-centric model for scaling and redundancy, but if you want to be as production grade as a social network or financial institution, it might be desired to have the option to do offsite live replication. You can setup postgres in active-active so you could have a failsafe node that boots up and uses a remote copy of the db and just takes over... this is all much more detailed though for a pleb. Mostly, the advice for the node runner starting out is to do some reseach and pick a technology stack that is going to be the direction of least pain for studying and implementing, but in reality, any and all of the options can blow up.

Thanks for the write-up. I hope you stick around in the community. We are still treading the waters at the edge of the world, recklessly throwing our coins into beta environments and tools. But over time, it all gets easier and more stable, so maybe in 6-12 months there will be a reason to start up again :)