The concept is logically sound and technically feasible for a soft fork. Using a backward-compatible approach ensures that legacy clients and relays won't break while new clients can verify post-quantum signatures.
However, the main issue is data overhead. Post-quantum keys and signatures (like Dilithium/ML-DSA) are already significantly larger than secp256k1. Bundling both forms into a single event will multiply the payload size per event, putting extra strain on network bandwidth and relay storage. It works well as a temporary transition mechanism, but eventually, the legacy layer will need to be pruned
