UXF Inter-Wallet Transfer Protocol v1 — onIntent widening ack
@unicity-sphere/sphere-sdk is landing the UXF Inter-Wallet Transfer Protocol v1. One spec change affects this repo as a sphere-sdk consumer: ConnectHost.onIntent now passes a 4th schemaVersion: 'uxf-1' | 'legacy' argument so wallet hosts can route UXF-shaped intents differently from legacy ones.
Backward-compat: 3-arg onIntent callbacks keep working unchanged — JS drops the extra positional argument. No code change is strictly required if you're happy ignoring the new argument; the upstream defaults to 'legacy' for any payload that doesn't carry UXF-1 signals.
What's needed from this repo
Read the migration note for the full detection rules + before/after callback shapes. The migration note documents:
- Detection rules — when
schemaVersion='uxf-1' fires.
- Before/after callback shape with TypeScript signatures.
- Branching example — how to route by
schemaVersion.
- Auto-approve handler symmetry.
- Compatibility matrix.
If you want UXF-aware behavior (e.g., route NFT intents differently), widen your onIntent type signature to accept the optional 4th arg. If you're happy with legacy behavior, you can close this issue without code changes.
Acknowledgement
Please close this issue when you've reviewed the migration note and decided your repo's stance (widen, or accept default). Closure of this issue with the uxf-transfer-v1-ack label is the ack signal that the external-acks-gate CI workflow checks before allowing the T.8.D production cutover PR to merge.
Refs:
- Spec:
docs/uxf/UXF-TRANSFER-PROTOCOL.md
- Migration note:
docs/uxf/CONNECT-HOST-MIGRATION-NOTE.md
- Plan task:
docs/uxf/UXF-TRANSFER-IMPL-PLAN.md §T.7.C.5
UXF Inter-Wallet Transfer Protocol v1 —
onIntentwidening ack@unicity-sphere/sphere-sdkis landing the UXF Inter-Wallet Transfer Protocol v1. One spec change affects this repo as a sphere-sdk consumer:ConnectHost.onIntentnow passes a 4thschemaVersion: 'uxf-1' | 'legacy'argument so wallet hosts can route UXF-shaped intents differently from legacy ones.Backward-compat: 3-arg
onIntentcallbacks keep working unchanged — JS drops the extra positional argument. No code change is strictly required if you're happy ignoring the new argument; the upstream defaults to'legacy'for any payload that doesn't carry UXF-1 signals.What's needed from this repo
Read the migration note for the full detection rules + before/after callback shapes. The migration note documents:
schemaVersion='uxf-1'fires.schemaVersion.If you want UXF-aware behavior (e.g., route NFT intents differently), widen your
onIntenttype signature to accept the optional 4th arg. If you're happy with legacy behavior, you can close this issue without code changes.Acknowledgement
Please close this issue when you've reviewed the migration note and decided your repo's stance (widen, or accept default). Closure of this issue with the
uxf-transfer-v1-acklabel is the ack signal that the external-acks-gate CI workflow checks before allowing the T.8.D production cutover PR to merge.Refs:
docs/uxf/UXF-TRANSFER-PROTOCOL.mddocs/uxf/CONNECT-HOST-MIGRATION-NOTE.mddocs/uxf/UXF-TRANSFER-IMPL-PLAN.md§T.7.C.5