Streamlock Integration

DAEMON integrates Streamlock as a server-side Operator API workflow for locked streams, entitlement ledgers, zero-sum sessions, and settlement helpers.

What the integration adds#

Streamlock gives DAEMON a locked-asset operator path. The integration scaffolds a project-local readiness check, adds the expected environment placeholders, and keeps the operator key on the server side while the product moves toward guarded session and settlement flows.

Environment setup#

The Streamlock starter uses environment variables so projects can keep secrets out of browser code and source control. DAEMON writes placeholders to the project env example, then the builder adds real values to a local env file.

# Streamlock Operator API key.
# Keep this server-side only. Never expose it to browser code.
STREAMLOCK_OPERATOR_KEY=sk_replace_with_operator_key

# Chain target. Use soldev/devnet while developing and mainnet for production.
STREAMLOCK_CHAIN=soldev

# Hosted Streamlock API base URL. Override only for local or custom deployments.
STREAMLOCK_API_BASE_URL=https://streamlock.fun

# RPC used by future write-flow broadcast and confirmation helpers.
SOLANA_RPC_URL=https://api.devnet.solana.com

# Optional mint for the read-only stream discovery check.
STREAMLOCK_TOKEN_MINT=replace_with_streamlock_token_mint

DAEMON workflow#

The Integration Command Center exposes Streamlock as an infrastructure integration. The first workflow creates a project-local readiness script and lets the builder run it before enabling higher-impact operator actions.

• Open a project in DAEMON and select the Streamlock integration.
• Create the starter file at src/streamlock/operator-readiness.mjs.
• Add the generated streamlock:operator-check package script.
• Move real secrets into a local env file and keep STREAMLOCK_OPERATOR_KEY server-side.
• Run pnpm run streamlock:operator-check or the matching package-manager command.

Read-only starter#

The generated starter is intentionally narrow. It confirms the Operator API shape, proves the key and chain headers are wired, and optionally lists streams for a mint. It does not create operator sessions or sign transactions.

GET /v1/operator/tokens/:mint/streams
Authorization: Bearer $STREAMLOCK_OPERATOR_KEY
Content-Type: application/json
X-Streamlock-Chain: $STREAMLOCK_CHAIN

• Masks the operator key in terminal output.
• Skips stream discovery if STREAMLOCK_TOKEN_MINT is missing or still a placeholder.
• Prints response chain, request id, stream count, and the first stream id when a mint is configured.
• Exits after read-only verification.
• Creates no session, submits no delta, signs no transaction, and settles no claim.

Safety model#

Streamlock is treated as a high-impact primitive because locked assets, ledgers, operator sessions, and settlement helpers can affect real user funds. DAEMON keeps that surface separated from renderer code and staged behind confirmation gates.

• Operator keys are server-side secrets and should not be shipped to browser bundles.
• The default DAEMON starter is read-only and safe to run before signing flows exist.
• Session, delta, settle, and claim paths remain behind explicit wallet or operator-signing review.
• Write flows should require clear user acknowledgement, fresh confirmation, and transaction inspection.
• Hosted token launch flow opens Streamlock externally while DAEMON keeps wallet, token, and post-launch tools nearby.

Launch center#

DAEMON currently uses Streamlock as the primary external launch path for hosted token launches. Builders can open https://app.streamlock.fun/ from DAEMON, complete the launch in Streamlock, then return to DAEMON for wallet context, token feeds, launch history, and post-launch workflows.

Current status#