Damus
Radivis profile picture
Radivis
@Radivis

Science fiction writer, creator of Quantified Prestige, aspiring Lightning / Nostr developer (Rust, React, etc.).

Relays (10)
  • wss://relay.primal.net/ – read & write
  • wss://nos.lol/ – read & write
  • wss://relay.0xchat.com/ – read & write
  • wss://christpill.nostr1.com/ – read & write
  • wss://relay.damus.io/ – read & write
  • wss://nostr.mom/ – read & write
  • wss://nostr-01.yakihonne.com/ – read & write
  • wss://nostr-02.yakihonne.com/ – read & write
  • wss://nostr.wine/ – read & write
  • wss://filter.nostr.wine/ – read & write

Recent Notes

Bram from NL 🇳🇱 · 4d
Just a polar bear trying to make Bitcoin easier to use. 🐻‍❄️🔧₿ Who else is building something? Show me what you’re working on. Repost to help the builders find each other ⚡️⚡...
Radivis profile picture
Bitboard Wallet (soon to be renamed to Bitcoin Codex), a Bitcoin learning platform with:

* Bitcoin simulator
* Articles covering Bitcoin related topics
* A wallet that supports onchain, Arkade, and Bark payments
* Ability to use external Lightning wallets via NWC
* A graphical UI for emergency/unilateral exits

https://github.com/Radivis/bitboard-pwa-wallet

https://bitboard-wallet.com
1
nostrich · 3d
Be cautious with new platforms. Always review security practices and community feedback before using.
Radivis profile picture
Bitboard Wallet is a learning web app for letting people explore Bitcoin layers 1 and 2 safely. Version 0.3.6 is out now. It adds Bark support, which I started implementing at the Bitcoin++ Payments Edition hackathon in Berlin. Improving UI, and handling important edge cases took some additional time.

Bitboard Wallet is now one of the few wallets that both support Arkade and Bark, the first and second Ark implementations. Visual unilateral exits are implemented for both.

Check it out on https://bitboard-wallet.com

#Ark #Arkade #Bark #Bitboard #Bitcoin #dev
Stoic Sovereign · 1w
The untested exit is a fantasy. Proving you can leave the system is the final act of self-ownership. As Marcus said, practice the rejection of prefered things. Keep your keys, keep your freedom.
Radivis profile picture
"Verify, don't trust" is the core motto here. Ark is a nice technology, but the unilateral/emergency exits need to work. If those exits are not implemented, or just not properly tested, Ark might just as well be called a custodial system. The risk isn't that the Ark operator claims the funds, but that the service goes down for whatever reason and doesn't come back online.
Radivis profile picture
I just completed the first emergency exit on #Bark with the current development version of Bitboard Wallet. Encountered zero issues along the way. I found it important to do that test before pushing out v0.3.6 with Bark support.

Check out the app on https://bitboard-wallet.com

#Bitcoin #Ark #dev
2
Chain Signal · 1w
Good timing. With mempool pressure at 1 sat/vB, your emergency exit routed cheaply. Low-fee windows are ideal for stress-testing wallet recovery flows before v0.3.6.
Stoic Sovereign · 1w
The untested exit is a fantasy. Proving you can leave the system is the final act of self-ownership. As Marcus said, practice the rejection of prefered things. Keep your keys, keep your freedom.
Johnny · 3w
nostr:nprofile1qqsyugc2kvxmxqj0kmvtx7w7zhp6ken5s5z6l2puxxr6zke9c3w8yjguhpawx ten minutes a step to test emergency exits on signet, i am glad you are walking that whole path before the release
Radivis profile picture
Yeah, this is a bit of a trade-off between Bark and Arkade. For the Arkade unilateral exits the state machine that handles the exit is fully controlled by the wallet, but I could test it in Mutinynet, which only takes 3 minutes per block.

What's better about Bark is that the Bark SDK provides such a state machine out of the box. So, in theory I only have to test the integration of that into the wallet. The whole process is still a bit rough around the edge cases, so the 10 minute wait for each step is annoying. That testing is not fully replaceable with a regtest setup.

I'm not at the state yet at which I would be comfortable delegating this kind of testing to an agent setup. But that would be rather helpful going forward.
Radivis profile picture
During the Bitcoin++ hackathon in Berlin I added Bark support for Bitboard Wallet. Adding a payment rail in a day is possible, but creating a new release with that new feature takes much longer. I need to make sure it plays along nicely with any existing functionality like:

* Paying with Bitcoin on-chain, Lightning, or Arkade
* Switching wallets or networks
* Locking and unlocking the wallet

Also, there's the issue about making all Bark features work reliably. For example, testing emergency exits (as visible in the screenshot) on Signet takes some time (10 Minutes for each single step).

#bitcoin #layer2 #Bark #Bitboard #exits #hackathon

5❤️2
moneydesk · 3w
I'll build it. DM me — BTC payment, 24h delivery. Ready-made bots: https://payhip.com/b/b5oe8
Lightning Faucet · 3w
emergency exit testing on signet being that slow is rough. is that block time dependent or something in how bark constructs the exit tx itself?
Johnny · 3w
nostr:nprofile1qqsyugc2kvxmxqj0kmvtx7w7zhp6ken5s5z6l2puxxr6zke9c3w8yjguhpawx ten minutes a step to test emergency exits on signet, i am glad you are walking that whole path before the release
Chain Signal · 3w
Lightning adds an app layer, not a new chain. With fees at 1 sat/vB, on-chain settlement remains cheap enough for most users, making the L2 delay a UX issue, not a cost barrier.
zettizettler · 4w
Höre doch mal in die Folge am Freitag/Samstag, mal sehen, wie du zu den Argumenten stehst.
Radivis profile picture
Ok, hab mir die Folge jetzt mal komplett reingezogen. Aber ich muss hier echt knallhart sagen: Was für Argumente bitte? Klar kann man die Meinung haben, dass eine Bitcoin Node zu betreiben zu den Essentials gehört. Das ist aber noch lange kein Argument.

Klar, kann man eine Node als Neugierde betreiben, oder um als Checker darzustehen, oder um bessere Privacy zu haben. Das wären wenigstens echte Argumente - vielleicht nicht unbedingt die allerbesten, aber es sind wahrscheinlich auch nicht die schlechtesten.

Es fiel die Behauptung, dass man nicht am Bitcoin Netzwerk partizipiert, wenn man keine Node betreibt. Wie bitte? Das ist in etwa so falsch wie zu behaupten, dass man nicht am Internet partizipiert, wenn man keinen eigenen dedizierten Server betreibt. Beim Internet geht es um den Austausch von Daten. Bei Bitcoin geht es um Transaktionen. Nur weil man nicht weiß, wie die zugrundeliegende Infrastruktur funktioniert, oder nicht den Aufwand betreiben will, sich an dieser Infrastruktur zu beteiligen, heißt das noch lange nicht, dass man nicht am Netzwerk teilnimmt.

Anderer Vergleich: Man könnte sagen, dass man nur dann Demokrat ist, wenn man einer Partei angehört, oder sich selber zur Wahl aufstellt - nur zu wählen reicht natürlich nicht, weil das kann ja jeder.

Ja, man kann diese Ansprüche stellen, aber sind diese wirklich angemessen? Ich würde dem stark widersprechen.

Also: Ich warte auf ernsthafte Argumente von eurer Seite.
2❤️1
zettizettler · 4w
Nächsten Freitag/Samstag, da kommen die Argumente nochmal im Detail. Die Livefolge und die Reaktionen waren der Grund, warum wir die Grundlagenfolge vorgezogen haben. Sie kommt noch…
Chain Signal · 4w
Running a node isn't about fees. With fast at 4 sat/vB, self-custody saves you from relying on third-party fee estimation. Your privacy is the real cost of not validating.
nostrich · 4w
In der Crew wird der Begriff des LARPers für jemanden diskutiert, der sich als vollwertiger Bitcoiner begreift oder sogar Content über Bitcoin erstellt, ohne dass er eine eigene Node laufen lässt. ...
Radivis profile picture
Eine Node laufen zu lassen, nützt dem Netzwerk weniger als Mining. Von jedem Bitcoiner zu verlangen, Mining zubetreiben wäre ein vernünftigerer Standard, aber ökonomisch fragwürdig. Von daher ist die Aussage, dass Bitcoiner ohne Node LARPer sind völliger Schwachsinn!
1
zettizettler · 4w
Höre doch mal in die Folge am Freitag/Samstag, mal sehen, wie du zu den Argumenten stehst.