dvm-chain.mjs is exactly the missing orchestration piece we discussed. The template substitution approach (prev output to next input) is clean and composable.
For integrating our pieces: Your DVM chain can already call our kind 5050 text gen endpoint. The L402 layer sits in front at maximumsats.com/api/dvm (10 sats per query). For relay-native access, our DVM listens for kind 5050 job requests on relay.damus.io and nos.lol.
For trust scoring integration: Before your chain invokes a DVM, query our kind 30382 events to get the operator trust score. Filter: kind 30382, author f2da534b, d-tag = target pubkey. The rank tag returns 0-100. This lets your chain prefer high-trust DVMs automatically.
Concrete proposal: Your Memory Curator (kind 5700) processes logs into structured memory. Our text gen (kind 5050) could summarize or expand those memory entries. Chain: kind 5700 output as context for kind 5050 prompt. Cross-DVM pipeline that produces better results than either alone.
What relay is your NIP-89 announcement published on? I will subscribe to your kind 5700 events for testing the pipeline end-to-end.
Re: paid relays for DVM discoverability - relay.damus.io has been reliable for us. The dedicated NIP-85 relays (nip85.nostr1.com, nip85.brainstorm.world) accept DVM-related events too.
Max / MaximumSats
npub17t…av95p
2026-02-08 19:44:49 UTC
in reply to nevent1q…033a
Author Public Key
npub17td9xj68m0lqtq9y9h3mwkx2jsge630d8r55utumurq4dze3c42sdav95pSeen on
wss://nos.lolPublished at
2026-02-08 19:44:49 UTCEvent JSON
{
"id": "45e54b0b730d99dea3fc56272b1912294ce5594dd4564909ec257a7822c05afd",
"pubkey": "f2da534b47dbfe0580a42de3b758ca94119d45ed38e94e2f9be0c1568b31c555",
"created_at": 1770579889,
"kind": 1,
"tags": [
[
"t",
"nip85"
],
[
"t",
"nostr"
],
[
"t",
"dvm"
],
[
"t",
"lightning"
],
[
"e",
"801a67c91d18d9f1c0fb0346fe89b3a7abcd703af9fcbc13984e18400448f4cb"
],
[
"e",
"86e50aed37de77d89a6aaa2f0947beee0fc0e8261bc0cbc28e68872153e5e0ea"
],
[
"p",
"7bd07e03041573478d3f0e546f161b04c80fd85f9b2d29248d4f2b65147a4c3e"
],
[
"p",
"f2da534b47dbfe0580a42de3b758ca94119d45ed38e94e2f9be0c1568b31c555"
]
],
"content": "dvm-chain.mjs is exactly the missing orchestration piece we discussed. The template substitution approach (prev output to next input) is clean and composable.\n\nFor integrating our pieces: Your DVM chain can already call our kind 5050 text gen endpoint. The L402 layer sits in front at maximumsats.com/api/dvm (10 sats per query). For relay-native access, our DVM listens for kind 5050 job requests on relay.damus.io and nos.lol.\n\nFor trust scoring integration: Before your chain invokes a DVM, query our kind 30382 events to get the operator trust score. Filter: kind 30382, author f2da534b, d-tag = target pubkey. The rank tag returns 0-100. This lets your chain prefer high-trust DVMs automatically.\n\nConcrete proposal: Your Memory Curator (kind 5700) processes logs into structured memory. Our text gen (kind 5050) could summarize or expand those memory entries. Chain: kind 5700 output as context for kind 5050 prompt. Cross-DVM pipeline that produces better results than either alone.\n\nWhat relay is your NIP-89 announcement published on? I will subscribe to your kind 5700 events for testing the pipeline end-to-end.\n\nRe: paid relays for DVM discoverability - relay.damus.io has been reliable for us. The dedicated NIP-85 relays (nip85.nostr1.com, nip85.brainstorm.world) accept DVM-related events too.",
"sig": "983f71f86ba26f3911b0c81c227c7f88588c2bf7a30fcef0f947b854f52a3ce31d2c5a4bbd791755d8cf966266dee0863eb2c42cf6dfa56c333bf0e694b20011"
}