Sigma-hosted onboarding
Users sign in through Sigma while Droplit keeps Bitcoin-native signature authorization in place for API operations.
View auth flow docsComparison
Droplit vs Privy
Both platforms support modern wallet products. This page highlights where each platform is strongest so teams can choose the best fit.
Droplit Is Best For
BSV-native applications, programmable wallet automation, and agent/backend workflows that need request-level signature verification.
Privy Is Best For
Teams prioritizing multichain consumer onboarding and a broader set of built-in policy and governance controls.
At-a-Glance Comparison
Snapshot across 6 capability areas teams evaluate side by side.
| Capability | Droplit + Sigma | Privy | Status |
|---|---|---|---|
| End-user authentication onboarding | Sigma-hosted sign-in with BSV signature-backed API authorization. | Email, SMS, social, and wallet login methods with embedded onboarding. | Improving |
| Request-level cryptographic authorization | Critical operations are authenticated with signed X-Auth-Token request payloads. | Policy engine and delegated wallet controls manage transaction authorization behavior. | Strong |
| Programmatic wallet operations | Tap, push, fund, mint, and status/activity endpoints are available now. | Client and server wallet infrastructure supports broad transaction workflows. | Competitive |
| Operational access controls | Per-droplit API key allowlists and configurable faucet-level behavior. | Fine-grained policy controls, delegated authorization, and advanced governance tooling. | Improving |
| Realtime activity visibility | SSE activity streaming and dashboard-level operation tracking are available. | Operational event tooling and integrations support production monitoring. | Competitive |
| Enterprise trust visibility | Public docs describe signature model and Sigma security approach. | Public compliance and security posture materials are more mature. | Improving |
What You Can Validate During Evaluation
Review practical capabilities available today, with direct links to docs and implementation guides.
Signed X-Auth-Token requests
Critical endpoints rely on signed request payloads, giving verifiable intent for each backend or agent action.
Review request signingCore wallet operation coverage
Tap, fund, mint, push, and status endpoints are available for production wallet workflows.
Browse API surfaceOperational access controls
Per-droplit API key allowlists and faucet-level config provide immediate least-privilege controls for production apps.
Manage controls in dashboardRealtime activity visibility
Activity stream support (SSE) enables monitoring loops, alerting hooks, and autonomous response logic.
Open SSE guideAgent and Backend Quickstart Recipes
Practical snippets for Sigma-hosted signing, tap, push, and realtime monitoring. These cover the most common agent loop integration tasks.
Use Sigma-hosted signing so your app or agent never needs to store a WIF.
import { createAuthClient } from "better-auth/client"
import { sigmaClient } from "@sigma-auth/better-auth-plugin/client"
const sigmaAuthUrl = process.env.NEXT_PUBLIC_SIGMA_AUTH_URL
if (!sigmaAuthUrl) throw new Error("Missing NEXT_PUBLIC_SIGMA_AUTH_URL")
const authClient = createAuthClient({
baseURL: sigmaAuthUrl,
plugins: [sigmaClient()],
})
// Set once after OAuth callback using result.user.bap_id
authClient.sigma.setIdentity(userBapId)
const requestPath = `/faucet/${droplitName}/tap`
const body = {
recipient_address: recipientAddress,
satoshis: 1000,
}
const authToken = await authClient.sigma.sign(requestPath, body, "brc77")Evaluate in Your Own Environment
Start from the API reference, run signed operations in your own backend or agent loop, and verify fit for your production requirements.