Wow 450+ members! Amazing to see builders from around the world coming together to build open-source Mini Apps. Can’t wait to see which Mini Apps get shipped. Promote your work below. Explain your Mini App in one sentence.👇

You deserve a better way to communicate with your users — in real time, right inside the MiniApp experience. Try create your own group on Knock Chat, or use the general Nimiq Community group, Join the group here 👇 https://knockchat.org/?group=568e48c7-68de-4997-ae1b-49f207cc0605 Open the link with Nimiq Pay, scan the QR code, or use it directly in your browser.

The idea is simple: you can set a small cost for people who want to connect with you. For example, you could require someone to pay 1 NIM to become your contact. or set it to 0 NIM if you want anyone to be able to connect for free. The same concept works for community chats. Group owners can set a cost to join their community, keep spam and unwanted users out. Knock Chat also lets you: 💬 Send encrypted direct messages 👥 Join public community chats 💸 Send and receive NIM directly in chat 🎁 Gift NIM to other community members ❤️ Reply to messages and react with emojis 🤖 Talk with AI bots

Following up on the network request from this week — here's a second small gap, with a real bug story attached. What happened: I added a pre-flight check to Nimble so a payer sees "not enough NIM" on the approval screen instead of tapping through to the wallet only to be refused. My backend read the balance from the embedded Nimiq client… and every payment got blocked. Turns out the web client runs Pico sync: no accounts tree, so getAccount() returns balance: 0 for any address it doesn't own. A wallet holding 200k NIM reported zero — before and after subscribing the address. I ripped the feature out. Then I looked for the obvious source instead — the wallet itself. It's the connected wallet, it's the user's own account, and Nimiq Pay clearly knows the number (it's on the home screen). But window.nimiq exposes: listAccounts, sign, isConsensusEstablished, getBlockNumber, sendBasicTransaction(WithData) + staking. No balance anywhere, and nothing on window.nimiqPay either (language + device id only). The ask: nimiq.getBalance() (or balance on the accounts returned by listAccounts) for the connected accounts only — no privacy expansion, the user already granted access to that account. Why it's worth it: any Mini App handling payments wants to answer "can this user afford this?" before the wallet sheet opens. Right now the alternatives are all bad: run a full node just to read one balance, depend on a third-party RPC/explorer, or let people hit a refusal they could have been warned about. It's a UX papercut in every payment app on the platform, not just mine. Happy to test a beta build against Nimble, and to open an issue/PR if you point me at the right repo. If you've hit the same wall, a +1 below probably helps 🙂

Time to come off mute and show the community what you’ve been building! 🔨 Sip & Show is a live demo session held as part of our weekly Sip & Ship community call, where builders come off mute, share their screen, and get 3-5 minutes to demo their Mini App. You'll get real-time feedback from the community and the Nimiq team, free visibility before the deadline hits, and a shot at getting featured across our channels. 🗓️ Wed, 11:00 AM ET (15:00 UTC) 📹 Join us on Zoom (🔑 MiniApps) 🎙️ Listen along on X Want a spot? Drop your Mini App name and one line about what it does in the comments below. ⭐ Reminder: Participation in our weekly community calls is also part of the competition scoring, so it’s worth joining even if you’re not demoing.