Do not open a public issue for a suspected vulnerability. Use GitHub's private security advisory form and include the affected commit, impact, safe reproduction steps, and any suggested mitigation. Do not include real credentials, private keys, customer data, signed authorization material, or raw production output.

Fork operators must replace this destination with a private security channel they monitor. Daski cannot receive or respond to vulnerability reports for an independently operated fork.

Before the first stable release, only the latest commit on develop is supported for testing. After releases begin, supported versions will be listed in their GitHub release notes. Never infer support from a branch name alone.

The provider accepts paid work only through the signed standard Exact-EVM rail. Core verifies the gateway signer, environment, chain, audiences, expiry, service/outcome bindings, request hashes, payer, quote, payment evidence, release evidence, sanctions state, and replay state before invoking a service. The service adapter must not duplicate or bypass that admission decision.

The provider still trusts its own:

• deployed code and runtime secret store;
• PostgreSQL integrity and availability;
• reviewed Base RPC sources and contract coordinates;
• Daski-issued signer and outcome bindings; and
• explicitly configured product API or MCP dependency.

A compromised provider host, database owner, wallet, or upstream product can violate fulfillment. This starter is technical infrastructure, not a provider's legal, compliance, custody, incident-response, or business-continuity program.

• Map each skill to one fixed reviewed operation. Never proxy a buyer-selected URL, method, MCP server, tool name, credential, or arbitrary header.
• Use the reviewed outbound HTTP boundary with HTTPS, DNS/IP checks, timeouts, response-size limits, concurrency limits, and endpoint pinning.
• Strictly parse product responses; do not pass raw upstream errors or payloads into public errors or logs.
• Use stable idempotency keys and journal intent before non-convergent external mutations. Reconcile authoritative product state after ambiguity.
• If an operation cannot reconcile and finish inside the synchronous budget, use provider-full rather than weakening terminal or restart guarantees.
• Store credentials only in an approved runtime secret manager. .env is for local development and must never be committed.

• Use Node 24, the committed lockfile, and the pinned non-root Docker image.
• Use PostgreSQL 16+; production requires verified TLS and separate migration and runtime principals.
• Expose stable HTTPS through a reviewed reverse proxy and edge rate limiter.
• Keep one active application replica for this minimal runtime and route traffic only while /health/ready passes.
• Separate Testnet and Mainnet wallets, databases, origins, product accounts, and Daski-issued artifacts.
• Run the documented type, lint, architecture, docs, skill, test, audit, build, secret, and artifact scans before release.

Mainnet is whitelisted and coordinated. Passing local gates or receiving a signed artifact does not grant Mainnet admission.