INK contact endpoint: design note and sketch#23
Closed
jasonodoom wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A design note plus an illustrative sketch for a publicly addressable INK receiver that forwards verified, signed envelopes to a human inbox, alongside a service such as an MCP server. Same shape as examples/reference-receiver, the difference is the terminal action (email instead of JSON ack).
Captures four design decisions with rationale: publish and bind a real DID (recipient binding is part of the signed transport base), reject encryption in v1 (only first-contact plaintext intents reach a cold endpoint), rate limit per IP and per DID (each covers the other's blind spot, did:key is free to mint), and label verified versus claimed identity in the forwarded email. Includes the receiver MUSTs from the compliance checklist.
The sketch files are illustrative, not a wired or tested service; shared plumbing is lifted from reference-receiver.