A Fund Baby @AFundBaby

Some devs are just legendary. Like Satoshi He never once sold a token. Still holds 5% of Bitcoin supply after 17 years.

Project 42 may be coming soon. Don’t panic and enjoy decentralization.

Since the snapshot was completed 1. I dropped Q/QOM price back to QUSDT/QOM price. 2. I burned $72,000 Q , I cannot control price anymore. Thank you -Herr

The new $QOM snapshot was taken. You can continue to buy,sell, hold as normal. Thank you. The final split share of the 30% airdrop is BABY: 42.19% FUND: 36.45% FATHER: 16.96% QOMX: 4.41%

I’m testing base level consensus for validators in the new $QOM chain. This means validators will be able to sign in traditional Ed25519 or have option to use ML-DSA key. Quantum operating machine won’t be false advertisement anymore.

Example of documentation of PQ tech of new $QOM chain. Quantum-Resistant Account Abstraction A hybrid post-quantum Account Abstraction solution for the **QOM Chain**, supporting both ECDSA and **ML-DSA (Dilithium)** signatures. ## Overview This project enables smart contract accounts on the QOM Chain to verify signatures using either traditional ECDSA or post-quantum **ML-DSA-44 (Dilithium)** through a custom EVM precompile. The goal is to provide quantum-resistant account functionality while maintaining compatibility with existing ECDSA-based workflows. ## Key Components ### 1. Dilithium Precompile - **Address**: `0x0000000000000000000000000000000000000401` - Performs on-chain verification of **ML-DSA-44** signatures. - **Input format**: `keccak256(message) || pubKey (1312 bytes) || signature (2420 bytes)` ### 2. SimpleAccount A smart contract wallet with hybrid signature support. **Main Functions:** | Function | Description | |--------------------------------|--------------------------------------------------| | `execute(target, value, data)` | Execute a call (only by owner) | | `isValidSignature(hash, signature)`| ERC-1271 compatible hybrid signature validation | | `setDilithiumPubKey(pubKey)` | Register a Dilithium public key | | `transferOwnership(newOwner)` | Transfer ownership of the account | ### 3. SimpleAccountFactory A factory contract used to deploy `SimpleAccount` instances using `CREATE2`. ## Current Status | Feature | Status | Notes | |--------------------------------------|------------|-------| | Hybrid signature verification | ✅ Working | Both ECDSA and Dilithium supported | | Dilithium verification via precompile| ✅ Working | Fully functional | | Account deployment via factory | ✅ Working | Basic deployment works | | Deterministic deployment (`getAddress`) | ⚠️ Unstable | Salt-based prediction is unreliable | | Full ERC-4337 compatibility | ❌ No | No EntryPoint or UserOperation support | ## Usage Example ```solidity // 1. Deploy a new account address accountAddr = factory.createAccount(owner, salt); SimpleAccount account = SimpleAccount(accountAddr); // 2. (Optional) Set a Dilithium public key account.setDilithiumPubKey(dilithiumPubKey); // 3. Verify a signature (works with both ECDSA and Dilithium) bytes4 magicValue = account.isValidSignature(messageHash, signature); // 4. Execute a transaction account.execute(target, value, data); Generating Test DataUse the included Go script to generate valid ML-DSA test vectors:bash go run generate_ml_dsa.go The script outputs:Original message keccak256 hash of the message Dilithium public key (1312 bytes) Dilithium signature (2420 bytes) Important: SimpleAccount expects signatures over the keccak256 hash of the message, not the raw message. Security NotesOnly the registered owner can call execute(). Invalid signatures return 0xffffffff (following ERC-1271). The Dilithium precompile uses the cloudflare/circl cryptographic library. Limitations: The Dilithium precompile only exists on the QOM chain. Deterministic account deployment using salt is currently unstable. This is not a full ERC-4337 implementation (no EntryPoint or UserOperations). Future Plans: Improve reliability of salt-based deterministic deployment Add batch execution support Explore integration with a full ERC-4337 EntryPoint Support additional ML-DSA parameter sets (ML-DSA-65 / ML-DSA-87) LicenseMIT License

If you are holding FUND, BABY, FATHER, QOMX tokens in LP or other staking contracts, you should begin to remove them. This is your one warning before the snapshot happens for new $QOM tokens.

I successfully tested real post-quantum signatures on the new $QOM chain. - Verify ML-DSA signatures inside smart contracts -require quantum resistant signatures for proposals -verify off chain messages -hybrid system for transactions -support future proof contracts Next I will need to add account abstraction. There is no reason to create a blockchain if in less than 10 years all will be compromised without this tech.

QOM Chain: A Cosmos EVM with built-in post-quantum capabilities. We’re taking a practical hybrid approach: • Normal users continue using standard secp256k1 transactions with no changes • Developers can optionally use quantum-resistant ML-DSA signatures inside smart contracts Key Specifications: • Cosmos SDK + Full EVM Compatibility • CometBFT Consensus with instant finality • 5-second block times • Native IBC support • Custom ML-DSA (FIPS 204) precompile Building future-proof infrastructure while maintaining ease of adoption and compatibility. THIS IS WHAT HERR IS TRYING TO BUILD.

Just like Qom X - the people’s exchange I am now tasked with creating a new $QOM - the people’s chain We don’t know what God has instore for us, just part of the process and enjoy.

New $QOM supply will be 200,000,000 Top chains can’t have sub penny prices. Tron is an exception.

I’m already in testnet. I got a working $QOM chain in local environment and register EVM token. Making progress Chads.

Ignorance won’t save you. Only you can .

QL1 has died three times. Once before, overlords projects migration Once before Qom x And now again. Part of the process, people come and go.

It took millions of dollars to build Qom X. I have sold zero QOM. And people are fudding because they think I sold $2,000 You NGMI

x.com/cyphernepfish_… I haven’t sold any Qom. In the beginning I borrow 600 billion Qom from investors from qomx to seed the Qom/q pool, afterwards I transferred back to cover users liabilities. I have already repaid about 500-550 billion Qom to the Qom x deposited The community dev who sold on you held 70% of the reserve, so when he withdraw to sell on Q market which caused the panic run, I was forced to send the 550 billion Qom back to Qom x exchange. There is no arb, no sells on my behalf. Thank you for your attention to this matter. -Herr

億ざっぷるん✨InfiniteDrive【g.qom】 @CypherNepFish_G

a week ago

………

keyboard_arrow_left Previous keyboard_arrow_right Next

1 0 5 2K 1

We have the people’s exchange @QomX_io You can buy and sell $QOM on it. When the people’s chain?