Avatar
tee8z
8ae75ae2d75a7da1ed11572059cbae2674eebc7fb2cbea60b83d98f1c162214d
@voltage.cloud - a pleb, doing my best.

https://github.com/BitcoinCoderBob/Satogram Lightning spam is good for the network, change my mind

(This is just for generating a timeseries data set to test a system in case anyone is curious, nothing serious)

So much of the world runs on people NOT flipping a switch I bet

Does anyone know why it’s “bad” for a bitcoin miner to also be a lightning routing node? ie. Are there possible exploits a miner is able to do to its peers/channel partners that are not possible for regular routing nodes? I feel like I’ve heard “don’t just a miner that’s also a routing node” but don’t quite remember why, will sling some sats around to whoever has a solid answer

Hell of an opener:

Ahh memory leaks, the gift that keeps on giving

Replying to Avatar Voltage

🌟 Exciting Announcement! Surge: Empowering Lightning Network Node Management ⚡️

We are thrilled to share with you the game-changing tool that is set to revolutionize Lightning Network node management. Introducing Surge, a powerful solution designed to bring transparency, efficiency, and actionable insights to your node operations like never before. 🚀

🔗 In the world of Lightning Network, managing nodes effectively is paramount. Surge is here to empower businesses by providing unprecedented access to time series data and invaluable insights. No more labor-intensive efforts or manual data gathering – Surge brings this information to you in a visually intuitive format, enabling swift decision-making and enhancing overall operational efficiency.

Here's what Surge brings to the table:

✨ Separate observability from actions: Grant read-only access to support agents, accountants, and key stakeholders, allowing them to gain deep insights into node performance without compromising operational integrity. Empower your team with actionable data for customer support and financial accounting.

✨ Identify top peers: Surge enables node runners to pinpoint the peers that are most active in sending and receiving funds. Make informed decisions on channel allocation, rebalancing, and gain valuable insights for routing yield optimization.

✨ Optimize channel uptime: Gain visibility into historical uptime of nodes and channels. Troubleshoot payment failures with ease and identify peers that may impact your node's performance. Keep your payment flows seamless and efficient.

✨ Streamline channel management: Surge simplifies channel states, categorizing them as active, inactive, or active but not utilized. Optimize capital utilization by reallocating funds effectively and ensure that your channels are actively contributing to your node's success.

✨ Visualize balances over time: Monitor the performance of your channels and node by visualizing balance trends over time. Detect anomalies and make data-driven decisions to optimize your node's efficiency and performance.

Join the surge of innovation in Lightning Network node management with Surge! Unlock the true potential of your node and stay ahead of the curve in this dynamic landscape. ⚡️

Voltage customers can now install Surge on their node, we will be releasing an update for all Lightning Network users in the future.

Hopefully my time-series headaches working on this keep from others having them

Time is a human construct, never does that hit me more than dealing with timeseries data, absolute headache every time

Man, I can’t seem to get this verification to work with nostrnest damn haha

Verifying my Nostr Nests identity: s0XionG_c16CGQs4OZo3-lGfzt82whk4-rXq6VYraWI

https://nostrnests.com

Verifying my Nostr Nests identity: tVn6C9a3sM9K_RKq8V2zyKSi3O0W1821mxRvHIJnf9E

https://nostrnests.com

Setting up zaps through voltage is extremely easy, works even with a node on being hosted by them

Oh, there’s probably simpler ways to do this now, I was just trying to find a setup that would allow me to hold the keys of the wallet my zaps interact with, mostly people are using custodial wallets for that right now

Finally figure out a non-custodial zap setup:

1) voltage node running lnbits

2) vida account associated to custom nip-05 id

3) connect vida account to an lnbits wallet via their integration page

4) paste the @vida.live into your nostr account for the lnurl address

5) zap away

I’m sure someone better at lnbits & it’s extensions knows how to skip Vida altogether, but this at least worked for me. The node and lnbits could also be self-hosted of course. This is very much a “good enough” solution to me.