What Droplit does
Droplit is a turn-key wallet SaaS on Bitcoin SV. Each droplit is a named hosted wallet: you create it over HTTP, fund it with BSV, and then tap, push, fund, or mint from your application backend. The public site at droplit.dev publishes documentation and discovery. Wallet writes run on api.droplit.dev, not through this Next.js host. There is no unauthenticated create or deposit shortcut; protected routes use BRC-103/104 mutual authentication.
Typical jobs are sponsoring user transactions so people never buy coin, paying agents or users from a faucet wallet, writing OP_RETURN attestations, receiving deposits at {name}@droplit.dev, and running multi-tenant wallets on subdomains. Droplit is not an exchange, not a custodial fiat on-ramp, and not an Ethereum paymaster. If you need those, this product will not help.
How agents use it
An autonomous service signs with a ProtoWallet from @bsv/sdk and wraps it in AuthFetch. A human-approved agent can complete Sigma device authorization (RFC 8628) at auth.sigmaidentity.com, then use the same mutual-auth client. After POST /auth/register and POST /faucets, the agent deposits via paymail or a deposit address and operates through POST /faucet/{name}/actions.
Identity keys for dashboard users stay in the Sigma domain. This frontend never holds WIFs. The playbook for signup, create, and deposit is in the Agents guide.
Who builds it
Droplit is published by bOpen / Open Protocol Labs, the same group behind Sigma identity. Sigma is the hosted identity and signing layer: OAuth, device authorization, and iframe wallets whose private keys never leave sigmaidentity.com. Droplit is the hosted wallet that those identities (and service-to-service keys) operate. Source for this app lives on GitHub. Product docs start at /docs.