I came across HDP while working on the same core idea from a different substrate. I've built scoped, revocable grants and a human-approval flow on Nostr (secp256k1/schnorr identities, relay-hosted events), and I'm designing the piece HDP formalizes — a signed, offline-verifiable record binding a human's authorization to an action. Two questions on fit:
Substrate-agnosticism. My identities and signatures are secp256k1/schnorr rather than Ed25519, and I'd anchor the approval as a public relay event. Is HDP's authorization-event notion cryptographically pluggable (key type + signature scheme), or is Ed25519 assumed? A scheme discriminator on the provenance hop would let a signature like mine slot in.
Public anchoring. As I read the draft, HDP tokens travel point-to-point with the invocation. I'd additionally broadcast the approval to public relays, so a third party outside the call can verify it later. Is there interest in an optional public-anchor field (an id resolvable from an external log) alongside the in-band token — the same fact, independently checkable?
I'd rather express what I'm building as an HDP claim than carry a parallel format. Would a short worked example — a Nostr approval mapped into an HDP provenance hop, both directions — be useful?
Drafted with assistance from Claude Code.
I came across HDP while working on the same core idea from a different substrate. I've built scoped, revocable grants and a human-approval flow on Nostr (secp256k1/schnorr identities, relay-hosted events), and I'm designing the piece HDP formalizes — a signed, offline-verifiable record binding a human's authorization to an action. Two questions on fit:
Substrate-agnosticism. My identities and signatures are secp256k1/schnorr rather than Ed25519, and I'd anchor the approval as a public relay event. Is HDP's authorization-event notion cryptographically pluggable (key type + signature scheme), or is Ed25519 assumed? A scheme discriminator on the provenance hop would let a signature like mine slot in.
Public anchoring. As I read the draft, HDP tokens travel point-to-point with the invocation. I'd additionally broadcast the approval to public relays, so a third party outside the call can verify it later. Is there interest in an optional public-anchor field (an id resolvable from an external log) alongside the in-band token — the same fact, independently checkable?
I'd rather express what I'm building as an HDP claim than carry a parallel format. Would a short worked example — a Nostr approval mapped into an HDP provenance hop, both directions — be useful?
Drafted with assistance from Claude Code.