king @IXKingXl

Just a man with a mysterious income trenches Joined February 2023

Tweets

3K
Followers

303
Following

67
Likes

922

king @IXKingXl

7 days ago

AcLHnjbvYML5geLeT6L33qXcYLszrK466LUqLHPJpump

4 1 4 56 0

View Details

no one noticed that pumpfun gave us a random index in the api ?? wtf is INDEX : XYZ100 is this not them giving us a free coin to run paired to the highest pump coins? frontend-api-v3.pump.fun/coins/perps#:~…

15 1 14 187 0

View Details

king @IXKingXl

a week ago

@MagicalTux Is my ledger clean?

0 0 0 32 0

View Details

king @IXKingXl

2 weeks ago

@momo_mattomo good tech aped

0 0 0 162 0

View Details

Momo @momo_mattomo

2 weeks ago

Been seeing all the quantum-attack talk, so I used AI to explore an idea: what would a memecoin with a post-quantum seal on its origin look like? That experiment became Quantum Seal. The proof starts with a digital birth certificate: the mint address, creator, token name, ticker, initial supply, timestamp and a hash of the metadata URI. These details are encoded in a fixed format so a verifier can reproduce exactly the same bytes. We hash that message with SHA3-512, then sign the resulting commitment using ML-DSA-65, a post-quantum signature algorithm. A separate SHA3-512 fingerprint commits to the proof record, including its public key and signature. That final fingerprint was included in the same Solana transaction that created the token. The full proof stays off-chain; its fingerprint is permanently recorded with the launch. Here’s where to look: solscan.io/tx/4TSGgkvf4cs… The launch transaction Open the launch on Solscan Under Instruction Details, expand #5 — Memo Program v2. You’ll find a string beginning with PQB1:. That is the commitment to the external proof. Solscan may label this instruction “Unknown”; expand it to see the memo data. The external proof record: api.npoint.io/bee368d18e7347… This is the public JSON record used for verification. The included public key lets people check the signature without needing any private key. Keep a copy: the on-chain fingerprint preserves the commitment, but it does not store the complete proof. The token itself solscan.io/token/5RpZVdZm… What does verification actually involve? Reconstruct the message using the protocol’s exact byte format and calculate its SHA3-512 commitment. Verify the ML-DSA-65 signature against that commitment. Calculate the proof record’s fingerprint and compare it with the PQB1: memo. Compare the signed mint, creator, name, ticker, metadata URI hash and supply with the launch transaction. The fingerprint is calculated from the protocol’s encoded record—not simply by hashing the downloaded JSON text. The local proof passed verification and matched the launch memo and displayed launch details. Anyone checking independently should repeat those checks against the published record. That’s the “seal”: a verifiable connection between this token’s launch and a post-quantum-signed origin record. The metadata URI hash commits to the URI string; it does not freeze whatever a website serves at that address. AI-assisted, experimental and unaudited. The post-quantum component authenticates the launch record through external verification; token transactions continue through Solana’s standard authorization system.

Justin Drake @drakefjustin

2 weeks ago

Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large