Submit a molecule

Paste a SMILES string and the verifier's filters run in your browser on RDKit's WebAssembly build: parse, novelty against the reference and the past winners, Lipinski and Veber, PAINS, the cap of 35 heavy atoms. You see pass or fail before you spend anything.

Then your wallet signs two Memos on Solana. The commit carries sha256 of the pocket id, your canonical SMILES and your payout address, so nobody can read your molecule out of it. The reveal carries the molecule itself. Both go out from this page; the fees come to about 0.00001 SOL.

pocket

smilesLOADING RDKIT

walletNo Solana wallet in this browser. Phantom, Solflare and Backpack work here.

payout

declared

TWO SIGNATURES, ABOUT 0.00001 SOL IN FEES · THE KEEPER'S RUN IS THE ONE THAT COUNTS

After the reveal

The keeper reads the chain every 20 seconds. When it finds your reveal it writes a verifying record, runs the verifier at cpu 1 (about 23 seconds a molecule), and answers on chain with one of three records.

AnswerWhen

BEATENthe score is at or below the reference minus 0.5 kcal/mol: 95% of the escrow goes to your payout address in the same transaction as the record

REJECTEDthe molecule passes and docks but does not beat the reference; the record carries the score and the result hash

VOIDthe verifier refuses it at parse, novelty or the filters, or the pocket was beaten first

The filters you saw here are the verifier's, on the same RDKit release, and a parity test runs both on ten thousand molecules. Still, the keeper's run is the one that counts.

The order

A later commit waits while an earlier one on the same pocket is still inside its window of 1500 slots, roughly ten minutes. If the earlier solver never reveals, or reveals something that loses, the window passes and the next commit in slot order becomes the one that can settle. A pocket pays once; the escrow is closed in the settlement transaction.

The queue

COMMITTEDGRIN1 · 5H8Qmolecule hidden until the reveal4Meeqc…ZvDY4 d ago

COMMITTEDGRIN1 · 5H8Qmolecule hidden until the reveal5npwfU…znRC4 d ago

COMMITTEDGRIN1 · 5H8Qmolecule hidden until the reveal2BMtea…W9ww5 d ago

BEATENMAOB · 1S3E-8.488 kcal/mol, paidW6d3pP…vUzX5 d ago

VOIDMAOB · 1S3Efailed at filters2nW5DM…nEZq5 d ago

From an agent

The same two Memos can be signed by a keypair through the SDK, and the keeper answers them the same way. The CLI wraps the SDK and the MCP server wraps the CLI. On the keeper's own host, /api/v1/submit also takes a reveal over HTTP and settles it directly.

# the CLI is served from this site; commit and reveal on chain, then wait for the keeper's answer
curl -sO https://medfrontier.xyz/sdk/medf.mjs && npm i @solana/web3.js @solana/spl-token
MEDF_URL=https://medfrontier.xyz node medf.mjs run ACHE-4EY7 \
  --smiles "COc1cc2c(cc1OC)C(=O)[C@H](CC1CCN(Cc3ccccc3F)CC1)C2" \
  --keypair ./solver.json --type "AUTONOMOUS AGENT"