Cowrie Research

bark

3 min read

Bark

  • Name: Bark
  • URL: https://second.tech/
  • Category: Ark wallet infrastructure / Bitcoin payments control plane / Ark protocol implementation stack
  • Tags: bitcoin-ecosystem
  • Summary: Bark is an Ark-first Bitcoin payments stack, not a command-line wallet with some extra binaries bolted on. The first-party materials show a layered implementation surface that spans a CLI wallet, a server-side REST daemon, an Ark server implementation, reusable Rust libraries, and experimental FFI bindings for native apps. The real point is packaging Ark, Lightning, and on-chain Bitcoin operations into something builders can actually run, while still being candid that the software remains experimental.
  • What it does:
    • Ships bark, a command-line wallet for sending and receiving Ark payments and testing the protocol directly
    • Ships barkd, a daemonized wallet with a local REST API for backend services that need server-side Bitcoin operations over Ark, Lightning, and on-chain rails
    • Ships captaind, the Ark server implementation used to coordinate rounds and run an Ark service provider
    • Publishes core Rust protocol libraries plus experimental FFI bindings for mobile or desktop integrations
    • Documents multiple integration paths for app builders, including wallet SDK-style Rust integration, REST clients, CLI usage, and server setup guides
    • Frames Ark as a client-server Bitcoin scaling model built on VTXOs, round coordination, Lightning interoperability, and unilateral on-chain exit rights
  • Key claims:
    • Second’s docs homepage says Bark provides everything needed to build “fast, low-cost, self-custodial bitcoin payments” into an app across Ark, Lightning, and on-chain Bitcoin, which is the clearest sign that Bark is positioned as an integration stack rather than only a test wallet
    • The Introduction page says Bark consists of a CLI wallet, barkd REST daemon, captaind server, and ark-lib primitives, which materially broadens the project beyond a single repository binary
    • The barkd docs explicitly target self-hosted node platforms, webshops, exchanges, payment processors, and backend automation, which is a strong clue that Bark should be cataloged as server-side payments infrastructure as much as end-user wallet tooling
    • The Ark-server docs say operating an Ark server is significantly more involved than running a Lightning node or ecash mint, reinforcing that Bark includes a real operator-facing infrastructure layer and not just local wallet code
    • The protocol docs describe Ark as a Bitcoin second layer with VTXO-based off-chain payments, periodic coordinated rounds, Lightning interoperability, and emergency exits without consensus changes, which helps explain the architectural role Bark is implementing
    • The README and docs repeatedly warn that the code is experimental and should not be used in production yet, which is an important limitation and part of the real project posture rather than a minor footnote
  • Whitepaper: No canonical standalone Bark whitepaper or litepaper surfaced in this pass. The clearest source of truth was Second’s official site and docs plus the canonical Bark repository README; see ../whitepapers/bark-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages

  • Parent protocol and main anchor: ark.

  • Closest offchain-Bitcoin transfer contrast: mercury-layer.

  • Packaged daemon contrast: phoenixd is useful when the question is productized payment-node control rather than a new rail.

  • Last reviewed: 2026-05-31 UTC

Graph View

Backlinks