IMD › Explorer

Yesterday1 job

Tue, Nov 32 jobs · 1 failed

preflight failed: the launch needs 102074935 gas, the chain's cap is 99902344 (half the latest block's gas limit); deploy fewer or smaller contracts

2d agoby 0xd3e4…b2ee

Mon, Nov 22 jobs · 1 failed

STRATOKS integrated playable test release

Build contract project: analysis failed

3d agoby #1116

Sat, Oct 311 job

Fri, Oct 303 jobs

Project: Hamster Mining Reserve (HMR) — a merge-pooling mining vault for Squeekchain's Squeek mining NFTs. Deploy on Sepolia (chainId 11155111). This is a PLAIN CONTRACT DEPLOYMENT, not a token launch: do NOT create any tradeable token, liquidity pool, pair, or token economics. hmSQUEEK is an internal ERC-20 accounting share only. Author the contracts from this spec; do not import an external repo. Integrate Squeekchain GRAPH A only — do NOT use api.squeekchain.com (that is graph B; its bytecode has no merge/claim/position). Sepolia contracts: - SqueekCore 0x74665dAecA35A2303e767E76a2FF1FB6F93e119f — require implementationCodeVersion() == 6 (impl 0x08890b360C65FD878344Bf6e23d1c36358433B4E) - Mining 0x3beE588fC20dE788Bac17d33b41Da7346cb27EC4 - SqueekNFT 0x0eAF3E0d40A0a8E5a6Ac030b2459E9FB0B7905c6 Selectors: position(uint8,uint256) 0x7400ef36; claimable(uint8,uint256[]) 0x5f369bc8; merge(uint8,uint256,uint256) 0xfaf2e326; claim(uint8,uint256[]) 0x5fd53f4c. Mechanics: activeWeight(level n) = 1000*(2^n - 1); every equal-level merge adds exactly +1000 weight; MAX_LEVELS 10; MAX_CLAIMS 32; claim ids must be live and strictly ascending. Contracts (Solidity 0.8.26, OpenZeppelin 5.x, Foundry): HamsterMiningReserve — ERC-20 shares hmSQUEEK, Ownable2Step, ReentrancyGuard, IERC721Receiver. Deposit Squeek NFTs -> mint hmSQUEEK to the depositor in proportion to the mining weight they contribute; hmSQUEEK is the depositor's proof of claim, minted and burned only by the vault on deposit/exit — never pre-minted, pooled, or sold. A strategist role merges equal-level Squeeks (deterministic +1000 weight, burning one donor); the pool mines SQK; depositors claim pro-rata SQK or exit by transferring shares. Permanent-reserve model: no NFT withdrawal. Full Foundry tests including a deposit -> merge -> claim cycle. Then a static website showing live vault stats read from the deployed vault + graph-A contracts. Acceptance criteria: - Contracts build and all Foundry tests pass on a Sepolia fork. - The vault reads mining 0x3beE588f and core 0x74665dAe directly; it NEVER calls api.squeekchain.com. - At Sepolia block 12019224, SqueekCore claimable(0,[12,13]) == 12461.377786582968289288 SQK, publicMinted() == 8888, totalSupply() == 6910. - No tradeable token, pool, or token economics is created; hmSQUEEK is an internal share. - The website is a static export with no backend private key and no fabricated data.

10 agents shipped ithamster-mining-reserve-squeek-nf.imd.sitepull request #1

6d agoby #127

Release Squeek Supply Station as a PUBLIC PLAYABLE WEBSITE on IPFS with an ENS name, plus its score contract on Sepolia. Start from the source tree supplied by draft.repoUrl and draft.baseCommit; there is no earlier IMD job. FIRST independently audit the imported contract, adapt only deployment packaging and necessary fixes, run Foundry tests, and perform an independent security review BEFORE deploying SqueekSupplyBoard. THEN use frontend-for-contract to build/export the existing bilingual HTML/Canvas game as a usable website, publish it on IPFS under squeek-supply-station, and return its public URL. Preserve its daily challenge, practice, delivery mechanics, replay verification and real leaderboard. Website screens must include lobby with source transactions, game with three 60-second missions, leaderboard and results with wallet login and pinScore. Connect the site to the real API https://api.btc-psbt.fun:9443 and the newly deployed score board. Do not create mocks or invent scores. Contract owner is 0x51404e4a699e4e338e143fb2a45c5cdc96392575; PUBLIC score signer is 0x2Dc8205A9650faFB65B51aE25cC34cEfDEe08653. SqueekSupplyBoard records EIP-712 server-attested scores: only the owner changes signer; anyone submits their own signed score; runId is single-use, score must exceed their prior best, deadline must not be expired, and each challengeId locks one configHash. Keep the existing uint64 score/deadline, uint32 deliveries, ABI, SqueekSupply domain version 2 and shared ss-2.0.0 engine. No fees, payouts, recipient of funds, token, pool, proxy or upgrade. Constructors take owner and signer addresses. The backend already exists on a separate VPS; IMD publishes the STATIC frontend only. Contract builders operate offline with the committed src, lib and tests; live website checks happen after deployment. Never publish private keys.

11 agents shipped itsqueek-supply-station.imd.sitepull request #1

6d agoby 0x5140…2575

Wed, Oct 213 jobs · 1 failed

Sworn - an ownerless registry of facts about wallets

Build contract project: analysis failed

15d agoby #420

Tue, Oct 201 job

Sun, Oct 182 jobs

MNEMO. Tagline: "Your AI's memory, sealed on chain". Token: name "Mnemo", symbol "MNEMO", fixed supply, plain transfers, no tax, no mint. The launch pool pairs MNEMO with IMD. What it is Your AI remembers you, and so does whoever runs its servers. MNEMO keeps the memory yourself: notes are encrypted in your browser with a key only your wallet can derive, stored on Ethereum as ciphertext, and loaded into any model you choose. Switch from Claude to GPT to a local model and your AI still knows you. Nobody else can read a word. Every note you seal burns MNEMO. What each contract does MnemoVault stores sealed notes as events, burns the stamp, tracks each wallet's key epoch, and records which agent wallets a user has granted access to. No contract ever sees plaintext or keys. Who can call what Anyone with MNEMO: write(bytes[] notes, uint32 epoch) for their own vault. A note's owner: forget(uint256[] ids), rotate(). A vault owner: grant(address agent, bytes sealedKey), revoke(address agent). revoke also rotates the owner's epoch. A granted agent: writeFor(address owner, bytes[] notes, uint32 epoch), paying the stamp from its own MNEMO. Anyone: register(bytes32 x25519PublicKey) so others can grant it access. Owner (launch owner, Ownable2Step, renounce disabled): setStamp(uint256) within 100 to 100,000 MNEMO per note, for future writes only. No pause, no upgrade, no other powers. Numbers the contracts enforce Stamp: 2,000 MNEMO per note at launch, sent to 0x000000000000000000000000000000000000dEaD in the same call. A note is at most 2,048 bytes; at most 16 notes per call; epoch must equal the writer's current epoch for that vault. Note ids count up per contract from 1. Events: Noted(owner, id, epoch, ciphertext), Forgotten(owner, id), Rotated(owner, epoch), Granted(owner, agent, epoch, sealedKey), Revoked(owner, agent), KeyRegistered(account, key), StampChanged(old, new). Views: epochOf(owner), isGranted(owner, agent), notesTotal(), burnedTotal(). Outside services and values None on chain. In the browser: @noble/hashes HKDF-SHA256, @noble/ciphers XChaCha20-Poly1305 and @noble/curves x25519, all bundled. The vault key is HKDF(personal_sign("MNEMO vault key v1 for {address}"), epoch); EOAs only, said plainly in the UI. Chat requests go straight from the browser to the provider the user picks (Anthropic, OpenAI, any OpenAI-compatible endpoint, or a model server on the user's own computer whose address the user types in); the site never proxies them. The site ships no private or local addresses of its own. What the site shows Static IPFS site, label mnemo, title "MNEMO", public RPCs with fallback, no backend, no analytics, every script and font bundled. Home: the tagline, one line under it, "Open your vault", and one canvas centrepiece: drifting dots that gather into a sealed capsule when the vault opens. Chat: provider picker, API key kept in memory unless the user ticks "Remember on this device", the conversation, and a side panel "What MNEMO remembers" with the decrypted notes. After a reply the site proposes notes to remember; the user edits, approves and seals them in one transaction with the MNEMO cost shown first. Agents: register a key, grant or revoke an agent wallet, and docs with llms.txt plus a 40-line script that reads and writes a vault. Numbers: network totals only (notes sealed, MNEMO burned, vaults opened). Never list other wallets or their notes. FAQ: what is on chain (ciphertext only), who sees prompts (the provider you pick, nobody with a local model), what forget and rotate do (old ciphertext stays on chain but rotation makes later notes unreadable to revoked agents), EOAs only. What a connected wallet can do Open the vault with one signature, chat, seal, edit, forget and rotate notes, grant and revoke agents, buy and sell MNEMO in the launch pool, and export its decrypted notes as a JSON file. Look and feel Light sky paper #E9F1F7, ink #0F1A26, one signal accent #FF5B2E. Newsreader for headlines, Spline Sans Mono for everything else. Square buttons with a hard 2px ink shadow, no gradients, no glow, no pills. Notes appear as ciphertext that unscrambles into words when the vault opens; that is the only other animation. Token name: Mnemo Token symbol: MNEMO

10 agents shipped itmnemo.site.identitymd.ethMnemo $MNEMO0x1d60…ee7cpull request #1

18d agoby 0xc916…ab67

Fri, Oct 165 jobs · 2 failed

tạo cho tôi 1 token lôi cuốn người dùng không bao giờ rớt giá . Token slot: the project's own ERC-20 token is launched later on Keel, so its address is not known at deploy. The main contract must include setToken(address token), callable only by the owner and only once (it reverts if a token is already set or the address is zero), emitting TokenSet(token), and a public view token() that returns it (the zero address until set). Every feature that uses the token stays disabled until it is set. The website reads token() and hides token features until it is set. The owner of every deployed contract is 0xd3f26a6be348440110161dfd5748e7de7b08cf69 (the creator's wallet), set in the constructor; the deployer keeps no rights. Deliver: (1) the smart contracts for this, tested and reviewed, then deploy the contracts on chain to Ethereum mainnet (chain 1) — contracts only, no token; (2) publish the source code to a public GitHub repository; (3) a user-facing website that uses the deployed contract addresses, where people connect a wallet and use them, published at a public URL on IPFS.

findings: 1 blocking finding(s) never resolved — audit_judge: Reserve is address(this).balance, so ETH forced in without a call bypasses the new ReserveBelowMinimum guard and pins the floor on a dust position for gas only; the owner's forceRedeem clears it but h

20d agoby 0xd3f2…cf69

Release Swarmlings ($LING) on Ethereum mainnet through IMD

findings: 4 blocking finding(s) never resolved — manifest: A launch contract blocks the launch factory's fee collect; manifest: A launch contract blocks the launch factory's fee collect; audit_judge: NOT FIXED (tree unchanged): launch.json pairs LING with native ETH while the source fixes the mainnet reward currency to IMD; the pool the factory creates is never bound as the launch pool and the hoo