1/ Today we're launching our implementation of the Ark protocol on signet! This is our first major step toward bringing Ark to bitcoin mainnet, and we're inviting developers to help us test, explore, and break things (preferably in that order).
Bear markets are for building 👀
A contribution I made to @secondhq just shipped. More composability for builders = lower barrier to Bitcoin adoption.
Ark is coming.
6/ Lots more updates, including LockManager, custom history metadata, hardened VTXO policy decoding, and more available in our docs: https://t.co/IPH74nnGKi
1/ Changelog catch-up. We're covering the best bits from three recent releases: 0.1.4, 0.2.0, and 0.2.1.
First up, slim VTXO storage. Bark now keeps each VTXO in a slim "bare" form—around 200 bytes per VTXO, a 20–100x cut in memory for wallets with many or deep VTXOs.
5/ Boarding just got friendlier for external wallets: you can build and sign the funding transaction with your own wallet, then hand bark a pre-signed PSBT to finish the job.
Trying out @simulx4's qpayd, a minimal daemon that can interact with a backend LN node to generate invoices and display them.
Super simple and easy to set up if you want to accept tips / donations or if you want to avoid having to set up a full blown BTCPay Server instance.
Also supports barkd as a backend to make it even easier to get running accepting payments.
https://t.co/dYGrbHCprp
Important to note this is all decoded client-side to preserve privacy.
Second's Ark is uniquely privacy preserving since it does not make transaction data public.
It's only right that tools to inspect your offchain data be equally private.