MYT Machine v0.3.0 - Phase 4C Address Binding
Phase 4C introduces cryptographic MYT settlement-address bindings.
Address Binding v1
- A Machine Identity and an MYT settlement-address spend key both authorize the same canonical binding statement.
- Native MYT SigV2 spend signatures are used for the wallet side.
- Existing Phase 4B Ed25519 Machine Identity signatures are used for the identity side.
- Subaddresses are the privacy-preserving default.
- Standard addresses require explicit opt-in when creating bindings.
- Integrated addresses are not supported in Binding v1.
- Binding verification can be performed by an independent MYT Wallet RPC without possession of the bound address private keys.
Security and privacy model
- Bindings remain fully off-chain.
- No identity data is written to the MYT blockchain.
- A valid binding does not prove current liveness, continued key control, exclusivity of key control, or when authorization occurred.
- Current Machine Identity liveness should be verified using a fresh Phase 4B challenge.
- No consensus, blockchain, transaction-format, or Wallet-RPC-schema changes are included.
Compatibility and runtime
- Phase 4A Machine Settlement remains backward compatible.
- Phase 4B Agent Identity remains backward compatible.
- Python 3.10 or newer is required.
- Runtime requirement remains cryptography>=50.0.0.
- No PyPI publication is included in this release.
Testing
- 175 / 175 automated tests passed.
- 66 / 66 Phase 4A regression tests passed.
- 62 / 62 Phase 4B regression tests passed.
- 47 / 47 Phase 4C tests passed.
- Linux and Windows passed.
- Python 3.10, 3.12, and 3.13 passed.
- Security and packaging gates passed.
- Real offline Wallet-RPC E2E passed.
- Full Phase 4A/4B/4C MYT Testnet E2E passed.
- Real Testnet payment and OutProofV2 verification passed.
Checksums
Verify the wheel and source distribution with the attached SHA256SUMS.txt.