NimJump A Server-Verified Endless Runner, Built for the Nimiq Pay Ecosystem Built with Godot 4.7 GitHub: github.com/nimjump/game (Source is open to nimiq moderators just write me) Play now: nimjump.zetashare.com - Sign In With Your Nimiq Pay Wallet — Playing in Under a Minute - Fully Playable Offline - Deterministic Server Verification - Public, Shareable Replay System - Daily Quests, Daily & Weekly Leaderboards - Highly Compressed Input-Only Replays - Real NIM Rewards, Paid Directly to Your Wallet The Problem We Set Out to Solve The moment a game rewards players with real cryptocurrency, every vulnerability — a modified client, a memory editor, a cheat engine — stops being a nuisance and becomes a profitable attack. Most games try to detect cheaters after the fact. We asked a different question instead: what if the client never had enough authority to cheat in the first place? That question became NimJump. The client only renders graphics, reads your inputs, and records them — it never decides your score, coins, rewards, quests, or leaderboard position. All of that is verified independently, on the server. Built Around Nimiq Pay Your Nimiq Pay wallet is how you sign in, how your stats are tracked, and how every reward reaches you. Connect your wallet, and you're playing in under a minute. Rewards — quest completions, leaderboard prizes, your own gameplay — are paid in real NIM, directly to that wallet. Deterministic Simulation Every level is generated from a deterministic seed, so every obstacle, collectible, and event can always be reproduced exactly. When you finish a run, the client doesn't upload your score, coins, or rewards — it uploads only a compressed replay of your inputs. Nothing else. The server replays that input log against the same seed, at the same 60Hz tick rate, and recalculates everything itself: every jump, collision, kill, pickup, and score. If it can't reproduce your run exactly, the run is rejected. No manual review, no guessing — just deterministic verification, which is also why a modified client trying to fake a score, complete a quest instantly, or inject impossible gameplay simply doesn't matter: none of those values are ever trusted in the first place.

The moment that stuck with me: someone asking “is this the same file?” and nobody being 100% sure. You email a rental agreement back and forth. Everyone signs. Months later, someone asks again: is this the real version? Did anyone change it after we signed? You’re digging through inboxes, comparing file names, and hoping everyone has the same copy. Most e-sign tools want your document uploaded to their servers... fine for some things, but not when it’s an NDA, or anything you’d rather keep on your own device. I wanted something simpler and more honest: your PDF never leaves your computer, but everyone can still prove what was agreed to, and prove it later, without trusting me or any third party. Nimiq works well for this, because I needed a timestamped, tamper-evident notary anyone can check independently. Nimiq’s mini app framework and wallet integration let me ship a real workflow inside Nimiq Pay: connect, sign, and seal without the usual web3 friction. Your wallet is your identity; the chain is the proof. No 3rd-party to go through to access the network. That’s VeriLock. Fingerprint your PDF locally, get wallet-backed signatures from everyone involved, then seal the hash on-chain when you’re ready. Anyone with a copy can verify it later. no account, no upload, no “trust us.” Just your Nimiq wallet. Give it a spin at verilock.online (https://verilock.online/). If you hit a bug, tell me. I’m a solo dev and I want to fix things fast. And if you actually seal an agreement with it, I’d love to hear about it. Success stories help more than you’d think. Cheers, Sam

SafePay ZK is a Nimiq Pay Mini App concept focused on one simple idea: Verify before you pay. The current version is now working as a testnet prototype using a blockchain-only flow. SafePay ZK runs inside Nimiq Pay as a Mini App. You can open Nimiq Pay, add/search a Mini App by URL, and use: https://safepayzk.com What works today: Request Payment flow: A business connects with Nimiq Pay, creates a SafePay payment request, adds order details, generates a QR code, and waits for payment. Verify Payment flow: A user scans the QR code, reviews the payment request, verifies it, and pays through Nimiq Pay on testnet. Payment confirmation: The payment is sent through Nimiq Pay with SafePay data attached to the transaction. Business can detect the payment on-chain and show the order as Paid. If the order expires without payment, it can be marked as Expired. Current architecture: SafePay ZK currently uses a testnet + blockchain-only approach. There is no backend yet. The app checks the Nimiq testnet while Business is open and updates order status based on what it finds on-chain. Current status: - Runs inside Nimiq Pay as a Mini App - Can be opened by URL: https://safepayzk.com - Create payment requests - Generate QR codes - Scan SafePay requests - Review order details before payment - Verify before enabling payment - Pay through Nimiq Pay on testnet - Attach SafePay intent data to the payment transaction - Detect Paid / Expired status from the blockchain - Show receipts in Business and Personal flows Why this matters: SafePay ZK is not trying to replace Nimiq Pay. Nimiq Pay still handles the wallet, user confirmation, and transaction. SafePay adds a verification layer before payment, helping users confirm that the request they are about to pay matches the intended recipient, amount, network, and order data. Roadmap: Phase 1 — Competition prototype polish Keep the app stable on testnet, polish the Request Payment and Verify Payment flows, improve receipts, add anti-self-payment checks, and clearly present the app as a working testnet prototype.

I have an early concept demo live: https://kmiru.github.io/nimiq-safepay-zk/app/ This is not the final competition demo yet, just a first look at the general flow: Review → Verify → Pay The demo link can also be opened inside Nimiq Pay to see how the Mini App experience feels in context. SafePay does not replace Nimiq Pay. Nimiq Pay still handles the wallet, final confirmation, and transaction. The core verification flow is already working at a single-request level: the user reviews a payment request, verifies it, and the Pay button only becomes available after successful verification. Based on community feedback, I’m also refining how SafePay is presented as its own request workspace: a place where users can load, create, manage, review, approve, reject, and verify payment requests before continuing to Nimiq Pay. Feedback is welcome, especially on whether the flow feels clear and useful.

As a fun experiment for the Nimiq Mini App Competition, I built NimDoom a version of DOOM running inside Nimiq Pay. It's based on the awesome nimiq-doom project, which stores the entire DOS cartridge on the Nimiq blockchain using ~48,000 transactions. Huge credit to the original project for making this possible! For NimDoom, I focused on bringing that experience into the Nimiq Pay Mini App ecosystem by adding: - 🎮 DOOM playable inside Nimiq Pay - 👛 Nimiq Pay wallet integration - 💰 Buy NIM directly from the app to "continue your adventure" 😉 - 📱 Mobile-friendly Mini App experience I don't expect this to be the winning competition entry I mostly wanted to answer one important question: Can Nimiq Pay run DOOM? Turns out... yes. Try it out and let me know what you think! 🌐 Play: https://nimminiapps.github.io/NimDoom/ 💻 NimDoom: https://github.com/NimMiniApps/NimDoom 💻 Original nimiq-doom: https://maestroi.github.io/nimiq-doom/