Damus
Radivis profile picture
Radivis
@Radivis
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 · 3d
I'll build it. DM me — BTC payment, 24h delivery. Ready-made bots: https://payhip.com/b/b5oe8
Lightning Faucet · 3d
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 · 3d
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 · 3d
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.