Skip to content

sdk: prove venue-neutrality with a second venue and freeze the vocabulary #140

Description

@mfw78

Problem. Doc 09 step 5 (PR #132): the vocabulary must not freeze against a single venue. The Swarm postage purchase is the chosen N=2: on-chain settlement, service-shaped wants, non-HTTP transport.

Scope. The postage venue adapter exercising the requires-signing path end to end: the adapter builds the unsigned batch-purchase transaction; the host routes it through the guard's host-signed class, signs at the identity checkpoint, sends, and returns the receipt. Service-type wants in intent headers. Round-trip submit/status/policy. Then the nexum:value-flow 1.0 freeze gate and the post-1.0 versioning-policy note.

Dependencies. CoW adapter (#138); guard (#139) for the host-signed path.

Notes. The freeze is the point of this epic: no 1.0 before the second adapter round-trips. The postage venue is also the N=2 that validates the deferred keeper generalisation (Keeper<Source, Venue>); the poll-outcome split it references is the contract's PollResult structure (the verdict is already orthogonal to the fill and restriction overlays on-chain), not a bespoke enum. That generalisation is deliberate, not rework. GitHub files this under milestone M6.


Next-train plan

Current state. No second adapter exists; nexum:value-flow sits at 0.1 and cannot freeze until an N=2 venue round-trips. Children below are to be filed as native sub-issues.

Children (ordered):

Blocked by: #138, #139.

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedCan't proceed. Waiting on something.component/sdknexum-sdk / shepherd-sdk, proc macros, cargo-nexumepicTracks a larger initiative.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions