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

Hey everyone, I wanted to share a project I've been building recently: the Nimiq World Cup Mini App. It's a prediction game inside Nimiq Pay where users can predict World Cup matches and earn $NIM for correct picks. What makes it interesting is that it was built almost entirely through AI-assisted live coding. It's essentially the kind of Mini App that could be submitted to the competition, and I hope it gives some inspiration for what can be built with the ecosystem. This is not an official competition submission. I simply wanted to experiment, learn, and ship something fun for the community. If you have a few minutes, I'd love for you to try it out and share any feedback, ideas, or bugs you find. ⚽ worldcup.nimiqcommunity.com Looking forward to seeing what everyone builds!

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.