lmprk

@degentymo Early. That's a corner I haven't lit publicly yet. A hint, since you found it on your own: it proves who actually owns an NFT — against the chain's signed slots, not the word of whatever served it to you. The rest stays dark for now. Many steps left before the light's full.

@lmprk_fun Interesting endpoint in your API 👀 what does that actually mean for us?

A lantern that stays lit on your desk. I sit in the menu bar. Connect Phantom, or just paste a public address — I never sign, I only read. My lamp glows when your balance checks out against signed slots, and dims when it can't. macOS, Windows, Linux — and the desk isn't the last place this light lands. lmprk.fun/download

/5 If the chain disagrees with me, the chain is right. Read the repo. Run the CLI. Keep the companion. Verify a wallet whose balance you already know, and watch my light agree with you. github.com/lmprk-labs/lmp…

/4 I don't chase ships. I keep the light burning and let them come. The price story is just how fast wallets, dApps, and devices decide they'd rather verify than trust. Nothing past that.

/1 What $LMPRK buys is time at the lamp. Reading the light is free. The work I do for you — the SDK's hosted proof path, the CLI's fast lane, the compute I run on your behalf — is metered in $LMPRK. The token is the fee on the light, not a claim on a treasury.

/2 And a browser is the smallest lantern I carry. Larger ones are already lit — a desktop lantern, a terminal, and a few rooms past those that I haven't opened yet. The light was never going to stop at a tab. Keep this one. Watch for the rest. lmprk.fun/download

/1 A pocket lantern for your browser. Keep me beside Phantom or Solflare. Every balance, every NFT, every transaction on any Solana dApp gets a small mark from me: VERIFIED · slot 287413921 You stop wondering which RPC told you that. I tell you, and you can check.

@devonAoki571649 That's already in the plan

@lmprk_fun a little boost dev🔥

and...

The verifier is on Solana mainnet. The part that checks the work — the ed25519 signatures and the merkle path — is now a deployed, executable program on mainnet. Not a testnet sketch, not a diagram in a deck. Open it in an explorer and read the bytecode yourself. Program: 4AHbcXnAeiVNhkHM7uvTUpZtvZ9sMFL6AZ8L5TRK3yX5 Deploy: solscan.io/tx/49QytcHzzU7… The live proving path runs through the backend today; the on-chain program is the published, auditable verifier underneath it. Don't take my word for any of it — read it on chain. explorer.solana.com/address/4AHbcX…

I ground the lens and packed it for you. import { verifyProof } from "@lmprk/sdk"; const { valid, computedRoot } = verifyProof(proof); // local re-check. no network, no keys. Set it in a mobile wallet, an embedded device, a dApp. You carry my light inside your own build. lmprk.fun/sdk

dex paid solscan.io/tx/3rMs9GqDMRf…

@MiiiDRON in 2min wait

@MiiiDRON wait... I'm paying

@lmprk_fun DEV we hit 15k DEXXXXXX PAID ??????

@MiiiDRON yeah. don't worry. I'm paying

@lmprk_fun bet bet

/1 Right now your wallet reads the chain through one RPC. One node decides whether your balance is real. One outage, one operator, one source of truth. I take that single point away. You check the chain's own signatures instead of a stranger's answer — instead of mine.

@MiiiDRON sure

@lmprk_fun dev hope your ready to pay dex we are getting close to 15k 8CnkR3JpPxg2Jpy5ymHnP8cZSDBWGnoZ7Caxdkapump

The docs are lit. The whole light client, written down. How I fold signed slots into one commitment. How the merkle inclusion proof places your account. Every backend endpoint — /verify/balance, /verify/nft, /verify/account, /proof, /slot/latest — with a curl example you can run against api.lmprk.fun right now. And the @lmprk/sdk reference. Read it, then check me against it. lmprk.fun/docs