There’s two ways to „get on zero“:
Pro actively: turn Fiat into precious #Bitcoin and move to cold storage.
Passively: leave fiat sitting in your bank account and wait for the banking system to fail.
Up to you.
Godspeed.
https://pbs.twimg.com/media/Fq4vCMoXwAY5n26?format=jpg&name=900x900
If you have a passion for building software, you should seriously consider checking out the Elixir language😉
Wonderful ecosystem and platform to build software suited for the modern era.
Your stack may even get simpler a whole lot!
https://void.cat/9em6r5jZ5EezWWCr6LnNuA
Here’s a video that might get you excited 😊
Careful though, he talks fast and this programming language is another rabbit hole you might fall into.
I‘m a little bit of an Elixir fan myself.
I was looking for a way to integrate it into the Phoenix framework.
I think it might be possible by writing a custom Transport/Socket and map events channels and topics but I don’t know yet if this is even a good idea anyway. I should probably start out simpler and just something up and running.
#[4]
#[5]
#[6]
👀
There’s other people using Elixir! It’s spreading 😁🙌
If the received amount equals to 21, 210, 2100, 21000,… it should be this one IMHO
That’s the point 😃
The first LN invoice represents the „balance“ (if compared to my thoughts) and you send ecash as long as you have any and then get new ecash tokens with the next LN invoice.
Exactly, and the payment is push instead of pull, like in Lighting making it a lot easier to implement.
Pretty sure it could be built very easily using this lib: https://github.com/cashubtc/cashu-js
Jesus Christ!
And you don’t even need to handle the „balance“ in the background as I would have needed to do in my thought exercise.
You already solved this via Cashu itself, right ?! 👀
I thought about using LN for monetizing API access, but this sounds better and achieves the goal to reduce roundtrips (compared to „create invoice for every request“)!
If I understood Cashu correctly, you can „top up“ a balance with the first LN invoice (say, 1000 sats), and then send 10 requests using 10 sats worth of ecash?
https://twitter.com/mrlukelukasson/status/1529192648015331330?s=46&t=8YH8IlzSo8cWrg_G3bi8Xg
There’s this special, almost magical moment on Nostr.
You see an npub.
Your client hasn’t synched its data yet.
You only see „xyza1234:jklc8453“.
You go to the profile, wondering who this might be.
Your client synchs.
„Hey! It’s you! Nice, you‘re here as well. 😃👏🤝“
A magical moment, indeed 😊
🤔 hab mal meine LNUrl geändert. Geht‘s jetzt?
Und schon mal Danke im Voraus 😃🧡🙌
Hyperbitcoinization. Soon.
„Why is Server B always saying Erlang? That’s not Elixir“, you might ask.
Good question!
Elixir compiles to Erlang.
Elixir is built on top of it. It leverages a battle tested history of over 40 years!
Elixir provides an easily approachable syntax (similar to Ruby), but remains a fully functional and immutable programming language.
But not just that.
It offers nice abstractions for common patterns. Patterns that evolved in Erlang to build scalable software are packaged up in Agents, GenServer, GenStage, and other building blocks.
Theses building blocks help to manage state in a functional language.