We're hiring. Like tinkering on bitcoin software? We need someone to help us build app prototypes and POCs on Bark. Non-stop "hackathons", publishing open-source, and posting your progress publicly. Normally bitcoin companies need to be cautious with vibe coding. For this role, we want you to go nuts with it. More details and application link at @Bitcoiner Jobs:
If you're in Mauritius for @`Btrust`'s Dev Day tomorrow, don't miss @`dunxen`'s session on how Bark makes adding self-custodial Lightning to your apps simple. image
Another new project building on Bark. image
Some really neat send payment UX going into @Christoph Ono ArkΓ© wallet, based on some patterns established in @Bitcoin Design. By integrating with Bark, a wide range of payment formats are available immediately across Lightning, Ark, and on-chain. Video demo of ArkΓ©'s send page dynamically reacting to what's held in the clipboardβ€”fewer clicks and less to think about for the user:
Why Rust? Memory safety isn't optional when you're handling people's bitcoin. Type safety catches bugs at compile-time that would be runtime disasters in other languages. Performance matters too when you're processing hundreds of signatures per round.
Self custody is going to get a lot easier.
Our goal isn't replacing Lightning. It's ensuring every bitcoin user can access Lightning without needing to become a node operator. Ark is the gatewayβ€”you hold a self-custodial balance, pay Lightning invoices when needed, no channel management required.
During a round, the Ark server + users construct a tx tree. Each leaf of the tree is controlled by a single user. The root of the tree is broadcast on-chain (the round tx). Once confirmed, each user has verifiable assurance they can unilaterally retrieve their bitcoin on-chain. image
We've released bark 0.1.0-beta.2β€”our second beta release. This update simplifies VTXO state management, enhances UX with immediate VTXO availability, and makes wallet integration easier with non-mutable API methods. Note: The VTXO state simplification and BlockRef representation changes may require code updates if you're building on the bark API or CLI. Highlights: VTXOs are now usable within the same round they're created (no more waiting!), VTXO states reduced from many to just three (Spendable, Locked, Spent), nearly all Wallet methods are now non-mutable for easier integration, Lightning receives are faster and more secure, and on-chain spends automatically refresh VTXOs by default. Full changelog: docs.second.tech/changelog/changelog
Kept you waiting, huh? (We're finally on Nostr) image