We’re making rapid progress in implementing quantum & AI resistance.
The structure for scriptPubKey has been decided. By cleverly using OP_CHECKMULTISIG, we’ve managed to create an escape route for older nodes, ensuring that they default to ECDSA only in case they’re old. It’s all about creativity! With this newly developed structure, old nodes (wallets) can continue to validate using only conventional ECDSA without any issues (no hard fork needed), while new nodes (wallets) will gain not only quantum & AI resistance but also protection against transaction ID tampering. It’s a win-win situation. And yes, we’re also making good progress with non-locality keys! We’ll be able to operate SORA with Ethereum-style addresses. For now, AI resistance is our top priority, and we’re pushing to implement AI-resistant keys as quickly as possible. There’s a feeling that something might happen with AI in the coming months.
Moreover, we’re adding an extra layer of security. Something concerning in the mempool has come to our attention. We can’t go into details because it involves security, but there was a loophole in transaction-related checks. This new security feature will address that. Thank you for your continued support of the SORA project.
SORA L1 Blockchain
– Core [Crypto, Locality key, non-Locality key]:
https://www.junkhdd.com
SORA L2 AI
– Blockchain [SSD/HDD checking, AI-NFT, Quantum and AI Resistance]:
https://www.fromhddtossd.com
