Second company primary sources — 2026-08-11

Project status in this pass

• Existing projects/ark and projects/bark notes were already useful on protocol and implementation mechanics.
• This pass pulled out the named company/operator boundary into ../companies/second.md so the corpus can answer how does Ark work? separately from which organization currently leads the default server, gateway, docs, and SDK path around Bark?

Primary-source snapshots

1) Second main site

• URL: https://second.tech/
• Key excerpt:
  • The homepage markets the simple way to add bitcoin payments to your app and bundles Ark, Lightning, and on-chain payments into one integration surface.
  • It frames the offering around app builders rather than only around protocol research or a single consumer wallet.
• Why it matters:
  • This is evidence that Second is selling and packaging a company-shaped builder path around Ark, not merely publishing a neutral protocol explainer.

2) Bark docs home

• URL: https://second.tech/docs/index.md
• Key excerpt:
  • The docs say Bark provides everything needed to build fast, low-cost, self-custodial bitcoin payments into an app.
  • The entrypoint splits users into wallet builders, server/backend integrators, and people who want to Run an Ark server.
• Why it matters:
  • This makes the implementation and operator shell explicit: Second is packaging multiple adoption paths around one stack, including the server side.

3) Bark repository README

• URL: https://gitlab.com/ark-bitcoin/bark/-/raw/master/README.md
• Key excerpt:
  • The README says Bark is an implementation of the Ark protocol on bitcoin, led by Second.
  • It defines the project as the Ark wallet (bark), the Ark server (captaind), and protocol libraries.
• Why it matters:
  • This is the cleanest direct source tying the default implementation stack to the named company.

4) Intro to the Ark protocol

• URL: https://second.tech/docs/learn/intro
• Key excerpt:
  • The docs say the protocol centers around an Ark server.
  • Users connect to that server to transact with one another directly over Ark, and the server also exposes a Lightning gateway.
• Why it matters:
  • It shows why the company/operator note belongs beside the protocol note: the self-custodial mechanics still rely on a server role that can become company-shaped in practice.

5) Ark liquidity

• URL: https://second.tech/docs/learn/liquidity
• Key excerpt:
  • The docs say the Ark server must deploy bitcoin upfront for refreshes, offboards, and Lightning payments and therefore maintain a bitcoin treasury.
  • Liquidity costs depend on amount, remaining lifetime, and the server’s bitcoin-denominated opportunity cost of capital.
• Why it matters:
  • This makes the operator boundary concrete: liquidity treasury policy and cost framing are part of the real live control surface around an Ark deployment.

6) Lightning payments

• URL: https://second.tech/docs/learn/payments-lightning
• Key excerpt:
  • The docs say the Ark server operates its own Lightning node(s) and acts as a gateway between Ark users and the Lightning Network.
  • The server handles channel management, inbound liquidity, routing, and rebalancing for users.
• Why it matters:
  • This is one of the clearest statements of why a named operator boundary matters separately from the protocol note.

7) VTXO lifetime

• URL: https://second.tech/docs/learn/lifetime
• Key excerpt:
  • The docs say that when a VTXO reaches expiry, the server gains the ability to sweep any remaining bitcoin to its own wallet.
  • They present expiry and sweep behavior as a core part of the server incentive model.
• Why it matters:
  • Expiry/sweep rights are a distinct practical authority surface that belongs in the company/operator map, not only in the protocol mechanics note.

8) Ark server docs

• URL: https://second.tech/docs/ark-server
• Key excerpt:
  • The docs provide a dedicated guide for running an Ark server and note that operating one can be significantly more involved than running a Lightning node or ecash mint.
• Why it matters:
  • This reinforces that Second is packaging an operator workflow around the implementation rather than only shipping a wallet.

9) llms.txt docs index

• URL: https://second.tech/docs/llms.txt
• Key excerpt:
  • The index exposes Bark SDKs, Barkd docs, Ark-server guides, agent/MCP docs, and multiple builder entrypoints.
• Why it matters:
  • This shows the breadth of the company-shaped documentation and integration shell around the implementation.

Working conclusion

Second clears the bar for a company/entity note because the useful question is not only how does Ark work? or what binaries are in Bark? but which named organization currently leads the default implementation, packages the Ark server, documents the Lightning gateway and liquidity treasury model, and provides the easiest builder/operator path into this stack?