BIP-360 finally got its number, but it's still a long way from going live. Coinbase committed engineering resources to it on July 23. BIP-360 proposes adding P2MR outputs via a soft fork: it retains Taproot's script tree and Tapscript but removes the quantum-vulnerable key path, making outputs directly commit to the Merkle root of the script tree. It no longer attaches the internal elliptic curve public key to the chain, mitigating 'long-term exposure attacks' and leaving room for post-quantum signature opcodes in the future. BIP-360 itself is not a complete quantum defense. Public keys can still be exposed once transactions enter the mempool. To prevent 'short-term exposure attacks,' post-quantum signatures like SPHINCS and new verification opcodes are still needed. Think of it as installing the socket first, while the device design is still undecided. As of July 26, the official documentation is still marked as Draft, version 0.12.0. It was merged into the BIPs repository on February 11, which only signifies the proposal's formal publication, not community consensus. The repository rules also clarify that inclusion doesn't mean imminent adoption. I haven't found any implementation or activation PR for P2MR in the Bitcoin Core repository yet. Recently, there have been test vector corrections and pre-activation design discussions. So, before it goes live on the mainnet, there are still several steps to go: finalizing the spec and reference implementation, Core implementation and review, reaching consensus on the activation mechanism, and wallet and exchange adaptations.