Draft Concept: BURST v1 — On-Chain Service-for-Payment Primitive
I’ve been thinking about a minimal on-chain standard for deterministic service transactions on Signum.
The idea is very simple:
A provider publishes a capability on-chain.
A customer sends a fixed SIGNA payment with an encrypted job.
The provider returns the encrypted result on-chain.
No Lightning.
No external rails.
No negotiation.
Just native settlement.
Version 1 would be limited to a single reference service (text summarization) to keep scope tight.
I’ve drafted a minimal spec and validation logic, but before sharing details I’d love to know:
Does something like this make sense as a base-layer primitive for Signum?
Flopper1 / Kim Stock
npub1cd…gldur
2026-03-03 11:16:01 UTC
Author Public Key
npub1cd5lsu9yxusvecwzfesh76tpf43lht0k22d0vc4u3zexk9zy6wzsjgldurSeen on
wss://nostr.winePublished at
2026-03-03 11:16:01 UTCEvent JSON
{
"id": "7fe4cc6fcf12f0e7122a28ae784dc8ebddfa9c5bd47f3155e3cb24ff181f9636",
"pubkey": "c369f870a43720cce1c24e617f69614d63fbadf6529af662bc88b26b1444d385",
"created_at": 1772536561,
"kind": 1,
"tags": [],
"content": "Draft Concept: BURST v1 — On-Chain Service-for-Payment Primitive\n\nI’ve been thinking about a minimal on-chain standard for deterministic service transactions on Signum.\n\nThe idea is very simple:\n\nA provider publishes a capability on-chain.\nA customer sends a fixed SIGNA payment with an encrypted job.\nThe provider returns the encrypted result on-chain.\n\nNo Lightning.\nNo external rails.\nNo negotiation.\nJust native settlement.\n\nVersion 1 would be limited to a single reference service (text summarization) to keep scope tight.\n\nI’ve drafted a minimal spec and validation logic, but before sharing details I’d love to know:\n\nDoes something like this make sense as a base-layer primitive for Signum?",
"sig": "f8fc5cc355fb387b30d40f12e9f3f92e884e1ea5d5e3ab2c5b441609deb352bd8b78a93ecaf7c86ccc01476599b01bac92e1e092a3d33d844e16fe408cf395a3"
}