IUEC@SORA PQC - Satoshi is SHA-256

1,079 posts
Opens profile photo
IUEC@SORA PQC - Satoshi is SHA-256
@DataRescueCoin
Crypto Apocalypse: Satoshi. Gather 1.44B tokens to unveil the SHA-256 imprint — myth or truth? 暗号黙示録:Satoshi。 14億4000万枚を揃えよ──SHA-256の刻印は神話か真実か?
Kita-ku, Tokyoiuec.co.jpJoined December 2012

IUEC@SORA PQC - Satoshi is SHA-256’s posts

🙃The SORA L2 Blockchain implements features related to HDD/SSD. 🙂 - While sending coins, it allows for a thorough inspection of drives(HDD/SSD) based on SORA.💪 - While sending coins, you can embed encrypted personal notes into the SORA blockchain.📝 - Also, while sending
Image
Key aggregation is amazing. Aggregating 75 ECDSA keys into a Schnorr signature. To target this, a hacker would need to obtain all 75 private keys. They might use various techniques like side-channel attacks, but getting 75 keys is extremely difficult. Missing even one key would
Image
🙃First, we have completed the SORA server update on xeggex. We have confirmed normal deposits and withdrawal.😄 Now, let's communicate information using the crypto memo feature of the SORA L2 Blockchain. - Decide on a 16-seed phrase and send the network fee to be used when
Image
The verification of Schnorr signatures is now complete. In addition to the method that validates the X coordinates and ensures that R_y is even, we have also confirmed the operation of another method that validates the complete match of both X and Y coordinates. With the
Image
Regarding Schnorr signatures, we have fully grasped the details through reproduction (sign and verify) with OpenSSL. The next step is to integrate the Schnorr part into libsecp256k1 and get it running. Since the initial values of the hash have been changed, we will focus on that
Image
We have completed the verification of Schnorr signatures. Now, any signature can be successfully verified regardless of the parity of the public key’s Y-coordinate. In traditional ECDSA, the parity of the public key’s Y-coordinate did not affect the verification process. However,
Image
In a recent post, we introduced a secret encryption memo feature that can be securely recovered anytime using a 16-seed phrase. We mentioned that deleting this data(wallet.dat and walletsql.dat) after use would enhance its security. However, it's important to note that there
Today, I'm excited to introduce the "SORA L2 Statistical Scan" feature, which allows for a detailed inspection of SSDs using blockchain technology in a single pass. Firstly, Recently SSDs are becoming more affordable and offering higher capacities. Many have already switched
Image
Thank you for your patience. We have completed all the time-consuming verifications on the blockchain. Such verifications need to be done beforehand as they cannot be changed once implemented, which takes time. However, it is infinitely better to spend this time now than to
Image
SORA L2 Blockchain - The "FromHDDtoSSD" Feature: Encrypted Memo. You can store secret encrypted memos on the SORA Blockchain that only you can see. These are encrypted with a quantum-resistant key built into the SORA Integrated Wallet (HD Wallet). The SORA Integrated Wallet
Image
Regarding the research on Schnorr signatures, we confirmed that the operation of signature and verification is problem-free with full X and Y coordinate matching during verification against the recovery point (R), regardless of the parity of the public key Y coordinate (which was
Image
For Schnorr signatures, we are starting the implementation with some parts using OpenSSL as a TODO (we will definitely replace it with libsecp256k1 later). The issue seems to be that the values don't match when changing k + e * priv to k + invert(e) * priv. The logic is correct
We have managed to get the Schnorr signature working with OpenSSL for now, so we will proceed with the implementation. By stacking signatures and keys, introducing OP_CHECKSIGADD will allow for easy multi-signature processes with multiple keys. The wallet will need to be modified
With some persistence, it worked! I found the reason why it wasn't working with libsecp256k1, and was able to come up with a workaround. After investigating this library, I discovered that it seemed like the order-const (0xFFFFFFFF ... 141) were overflowing. Then, and since
Image
⚙️ Today, we will have Alice and Bob work hard again. Alice: Hey, are you properly checking it? Bob: Checking? Alice: The drive check. Especially the SSD. Bob: That's not necessary. They don't break! Alice: True, the possibility of SSDs failing these days is low. However, if
Image
Development is progressing smoothly.😊 We are about to release a feature that allows transactions with Ethereum addresses currently in testing. To handle this without the need for a Hard Fork , we have also incorporated the traditional SORA addresses (public key hash), and set
Image
The mainnet release of Quantum & AI-resistant technology is coming soon. Before that, we will prepare a lightweight version for mining pools and exchanges. It seems that the latest version became heavier due to the increase in verification functions, etc., and there may have
Image
Continuing from yesterday, what does exploring "low probabilities" with AI and blockchain entail, specifically in terms of phenomena? One example is already implemented in SORA L2. Yes, it's the feature that detects minor malfunctions in the drive early on. In this method,
We are implementing the KECCAK256 hash and progressing with preparations for SORA-erc20 and SORA-bep20.😉 With this hash, the same address (a public key in 0x format) will be generated from the same secret key, making it usable in SORA. This allows us to introduce a bridge
Image