Christoph Ono's ArkΓ© wallet keeps getting better. This is what happens when you unleash a designer armed with agents and the Bark SDK.
Christoph Ono's ArkΓ© wallet keeps getting better. This is what happens when you unleash a designer armed with agents and the Bark SDK.
Bark makes it ridiculously easy to build bitcoin wallet apps that supports on-chain, Lightning, and Ark payments. All self-custodial.
Bark bindings now ship with every release, published to package managers automaticallyβpre-built binaries, no cloning repos, no local builds, no Rust toolchain. Just add the dependency the way you already do for everything else.
Luca bringing the fuzz! π
4/ Fuzzer runs 24/7 now, with minimized corpora pushed to our bark-qa repo alongside test vectors used throughout Bark's development. More targets comingβserialization/deserialization expansions, method-level fuzz targets. Full writeup: https://blog.second.tech/fuzzing-bark-for-server-reliability/
3/ The vec allocation bug is a good example of something easy to miss in reviewβstable Rust doesn't yet support try_with_capacity, so the bounds check has to be done manually. Our first fuzz target was a straightforward deserialize/serialize pass, and it surfaced the issue immediately.
2/ Bark's client-server architecture means the server has to gracefully handle anything thrown at itβmalformed VTXOs, malicious client requests, unexpected edge cases. Fuzzing helps make sure the server stays up and keeps serving rounds no matter what comes in.
1/ We caught a capacity overflow bug in Bark before it ever hit a user, thanks to the fuzz testing @luca0x46 has been running around the clock. A malformed VTXO could have requested an arbitrary vec size during deserialization, triggering a panic. Now it's patched.
Hello Bluesky, someone told us there were bitcoiners out here too?