Repository navigation
Add one-shot typed Heartwood rendezvous handoff - #35
Draft
TheCryptoDonkey wants to merge 1 commit into
Draft
TheCryptoDonkey wants to merge 1 commit into
TheCryptoDonkey wants to merge 1 commit into
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
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.
NIP-55 apps can request Heartwood's existing scoped rendezvous child handoff through Cambium without switching to a direct bunker. The new native Activity-only type accepts one strict v1 request: expected persona, app-owned target public key, uint32 index, canonical nonce and expiry bounded to 600 seconds. It forwards exact numeric Heartwood parameters and returns only the unchanged, fully bound encrypted envelope.
Provisioning always shows fresh one-shot approval with the complete persona/target/index/nonce/expiry bindings. It cannot use silent provider authority, remembered approval, batch requests, a website callback or clipboard delivery. The original caller, request sequence/job, identity, pairing and expiry stay checked through queue dispatch, actual relay send and result release. Its CEREMONY registry path has no automatic retry or result cache; existing noncancellable native FFI handling is retained. No generic RPC, secret getter, root key or Cambium client-key export is added. Provider authorities and manifest are unchanged.
Validation at e82a247: 63 focused JVM cases passed with zero failures/errors/skips (19 IntentGate, 13 NIP55 parser, 5 typed request/approval and 26 registry); actual Activity and SDK source compilation passed. Source review checked dispatch/completion currentness and the no-silent/no-remembered boundary. App consumer: forgesworn/kithmoot-android#329; browser equivalent: forgesworn/bark#63 and forgesworn/kithmoot#575.
Keep draft. Actual Android Activity/UI through Cambium and physical Heartwood, native mixed-client Link/Bothy traffic and measured relay metadata remain unexecuted. No installation, production enablement, deployment or independent security acceptance is included.