Damus
openoms profile picture
openoms
@openoms

Bitcoin | Lightning | Blink | RaspiBlitz on RPi and more | Self-hosting | Enjoyer of Linux Desktops and GrapheneOS | building hardware at diynodes.com

Relays (4)
  • wss://multiplexer.huszonegy.world/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://nostr.huszonegy.world/ – read & write
  • wss://relay.nostr.hu/ – read & write

Recent Notes

openoms profile picture
Google Pay is the only significant thing which does not work with GrapheneOS, but you can use a smartwatch.
Tested Garmin Pay so far, no problems.
openoms profile picture
This is awesome!
Also please let us set a gap limit or specify the number of monitored addresses for both the deposit and change accounts.
Some well used wallets will thank you!
openoms profile picture
Wrote a quick guide about using an initialized Satochip smart card with Sparrow Wallet: https://github.com/openoms/bitcoin-tutorials/tree/master/satochip#get-started-with-satochip

As these javacards are essentially $5 hardware wallets (with no screen, but using a Secure Element) are great to give bitcoin in a physical form.

This short guide is for the ones receiving them.

To initialize the cards one could use TailsOS offline with Sparrow Wallet or Electrum or a modded version of Seedsigner: @nevent1qvz...
openoms profile picture
Planning to show this setup tonight:


Truely FOSS Satochip javacards https://github.com/Toporin/SatochipApplet initialized with an airgapped, stateless @npub17tyke... .
The cards act as a hardware wallet without a display, but with a PIN protected secure element. Mess up the PIN 10 times and the card is bricked. Blanks cost ~2 dollars with chip, ~5 dollars with NFC support. Can compare with #TapSigner, #BitKey and alike.

Find the modded images supporting the smartcard readers here: https://github.com/3rdIteration/seedsigner/releases

Parts:
- a generic smartcard reader (here ACR39U https://a.aliexpress.com/_EzkLWc9 + microUSB adapter)
- can use the same cards as the SpecterDIY

Notes: https://gist.github.com/openoms/510b2876cab19e15c4190456ea8aad82

@note1hatua...
openoms profile picture
Exercise: you got to send someone money, but the payee didn't publish a bitcoin or LN address you trust. The onchain fees are high anyway for the price of a dinner.
Nostr solves this often, but let's say you just got some other social media contacts.

Solutions:
1. LNURLw
generate an LNURLwithdraw voucher and share the link or QRcode so the recepient can withdraw with most lightning wallets any time. This needs a LNURL server. Some ways to it:
- run BTCPayServer - create a Pull Payment, share the link or QRcode
- run LNbits - create a voucher with the LNURLw extension

Custodial solutions:
- https://lightsats.com - top up in the browser and create vouchers
- hope to have this streamlined in the Blink Wallet - the PoC could be extended here https://github.com/GaloyMoney/galoy-voucher
- there is of course the BTCPay / LNbits of someone else

2. Ecash
Use ecash (that will be Cashu for now) - send the token as text and when the recipient downloaded an Cashu wallet will be able to convert the token to a lightning payment or trade it within the mint for free.

- run LNbits with the Cashu extension, connect it to your eNuts or Minibits wallet
- run a mint directly with https://github.com/cashubtc/nutshell

Custodial solutions:
- download eNuts https://www.enuts.cash/ or Minibits https://www.minibits.cash/ and use the default (or some other) mint
- looking forward to the fedimint instances in the wild

Does anyone has any other practical solution working now for async payments?
I'd like to pay bitcoiners more often, but sometimes not when I can just ask for a lightning invoice.