🔁 LOCK Protocol v1.0.1 — Post-Audit Update

🔁 LOCK Protocol v1.0.1 — Post-Audit Update

Following the initial release of v1.0.0, this version finalizes the LOCK Protocol after a full audit and consistency pass.
All files have been cross-reviewed for correctness, logic integrity, naming precision, and implementation clarity.

This is the reference release for any client implementer or security reviewer going forward.

---

✅ What's New in v1.0.1

• 🔄 Audit-Driven Corrections & Alignment

  • Renamed fee_requirement ➝ amount_condition
  • Replaced fee_matches(...) ➝ amount_matches(...)
  • "ANY" removed from recipient_wallet support
  • recipient_wallet now accepts only "self" or a fixed address

• �� Multiple authorized_wallet Support

  • Now accepts a list of wallets (not just a single string)
  • Logic updated to require at least one input signature match
  • Added support for shared access, threshold access, and inheritance scenarios

• 📜 "Sign-to-Decrypt" Flow Finalized

  • Metadata encrypted using ECDH + HKDF
  • Viewers must sign challenge to derive decryption key
  • Fully documented in KEY_DERIVATION.md and whitepaper

• 🧩 Pseudocode & Terminology Cleanup

  • bind(), unseal() updated for accuracy and lifecycle compliance
  • Final naming conventions locked in across all spec files
  • Added comprehensive examples for all vault types

• 📊 Updated Diagrams & Lifecycle Spec

  • New vault lifecycle diagram reflects final process
  • Consistent cross-file logic alignment verified
  • Added detailed rebinding guide with amount condition preservation

---

🚀 Summary

This release makes the protocol implementation-ready and audit-clean.
If you're building on LOCK, this is the version to work from.

---

👉 View the Protocol Repository

🔓 Verifiable access begins here.