Second, a Bitcoin development lab, just pushed Bark to Bitcoin mainnet. Bark is its implementation of the Ark protocol, and it aims at a specific UX sore spot. Most mainstream Bitcoin payment paths still push users toward either custodial services or Lightning Network complexity like channels and liquidity management.
Second says Bark lets developers and everyday users “get started with self-custodial bitcoin, hold it, and spend it” without surprise fees and without managing channels or liquidity. CEO Steven Roose wrote that in a company blog post.
What Ark changes under the hood
Ark is a layer-2 design that tries to keep users self-custodial while smoothing out the fee and flow problems that come with on-chain activity.
Bitcoin UTXOs sit at the center of the model. Ark lets “large numbers of users share on-chain UTXOs via trees of pre-signed, off-chain transactions.” In plain operational terms, the protocol spreads the cost of using those on-chain UTXOs across participants, rather than making each spend act like a standalone on-chain event.
Second contrasts Ark with Lightning by pointing to two practical differences:
- Ark requires no channel management.
- Ark requires no liquidity pre-allocation.
Those are exactly the friction points that have kept many non-crypto users tethered to custodial rails, according to Second’s framing.
Mainnet is live, plus the tooling
The company says its Ark server is now publicly accessible for payments on mainnet.
Second also bundled a developer stack designed to reduce integration overhead. Bark includes:
- Bark SDK, written in Rust
- Bindings for Kotlin, Swift, React Native, Flutter, Go, Python, and WebAssembly
For server deployments, Second ships Barkd, a standalone wallet daemon. Barkd exposes a REST interface with an OpenAPI spec.
This matters because it turns “protocol support” into “something you can wire into apps.” If the API surface behaves as documented, builders get faster iteration than if they need custom wallet logic per integration.
Wallets and merchant rails at launch
Second isn’t launching Bark as a lonely protocol demo. Multiple applications are described as mainnet-enabled.
Here’s what Second listed:
| Product | Type | What Second says it does |
|---|---|---|
| Noah | Mobile wallet | React Native frontend plus Rust backend for Ark |
| Arke | iOS wallet | Design-led native wallet aligned with open-source UX principles from bitcoin.design |
| Satsigner | Mobile wallet | Sparrow-style UTXO management and multisig workflows |
| Bark Wallet | Umbrel app | Supports Ark, Lightning, and on-chain payments |
| BTCPay Server plugin | Merchant integration | Processes self-custodial Lightning payments without opening channels or managing liquidity |
That last item matters if you run a merchant backend. Second is effectively packaging wallet and payment UX decisions into the software layer, rather than pushing it into each operator’s operational playbook.
Why now: a crowded Bitcoin layer-2 race
Second’s launch lands in a busy corner of Bitcoin infrastructure. Bitcoin layer-2 solutions are competing to close the gap between self-custody and everyday usability.
Bitcoin Magazine notes that multiple protocols are vying for that same outcome, including Arkade from Ark Labs and statechain-based solutions.
In this context, Bark’s differentiator is its claim of avoiding channel management and liquidity pre-allocation, while still letting users share on-chain UTXOs through Ark’s off-chain transaction trees.
It also signals something about the direction of the space. Instead of only optimizing throughput or routing, the current battleground is operational ergonomics. Who makes spending feel like a normal app action rather than a protocol lesson?
Next steps for users and builders
Second also announced a live AMA on Stacker News on June 9 at 10:00 AM EST.
On the business side, the lab says it raised $5.1 million from a private investor and has 11 people. Second also references hiring talent from industry, including former Blockstream engineers.
As with any layer-2 approach, the real test will be the specifics: how the off-chain transaction model behaves in edge cases, how failure modes surface to users, and whether fees stay predictable in the scenarios everyday wallets hit.
For now, Bark is live and the integration path is laid out. Developers can build with the SDK and the Barkd API, and wallet teams already have mainnet-enabled targets to iterate against.