Hi everyone, I hope everything is going well as Cycle 2 approaches! 👋 I have a question about when the miniapps will be graded: Are they graded based on their status as of July 31 (i.e., the final submission deadline), or are they graded based on their status up until the results are announced (August 15)? In other words, let’s say I add a feature now—will it be taken into account? If I make a change tomorrow, will that be taken into account? I think this is an important question because it means an extra two weeks to fine-tune a product that has a fixed deadline. Thanks for your answers! 😉

Please i submitted my project on the last day and I didnt know I was to add MIT license to my github, so when I checked my submission later, a competition member asked me to add it which i did, but somethig is still unconfirmed on the git due to that missing fil which i have added. i have tried to reach out since yesterday, got approved today. I want the team to check out my submission, I have already commented on GIT. I also guess my project hasn.t ben listed on the site due to thatgit error from missing MIT file, please rectify. my project is called PREDTUBE

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 🙂

I'm trying to figure out how to get my Nimiq Pay to connect to testnet. Is there a hidden setting somewhere?

I try to use Codex for developing an artellerie game. In landscape mode, the Nimiq Pay status bar and URL ribbon take up a significant part of the available screen. This makes it difficult to provide a comfortable game layout, especially when touch controls and the battlefield need to remain visible simultaneously. I tested the standard browser Fullscreen API on a Samsung Galaxy S22: - In Samsung Chrome, requestFullscreen({ navigationUI: "hide" }) works correctly. - Inside Nimiq Pay, the same page reports that fullscreen is unavailable, so the Mini App cannot request it. - The game still provides a compact fallback layout, but true fullscreen would offer a much better landscape experience. Would it be possible for Nimiq Pay Mini Apps to support user-initiated fullscreen mode? The desired behavior would be: - Fullscreen can only be entered after an explicit user tap. - The Nimiq Pay URL ribbon and Android system bars are hidden while fullscreen is active. - Physical rotation between landscape and portrait remains possible. - The Android Back action or an in-app button can safely exit fullscreen. - Mini Apps without fullscreen support continue working normally. This would be useful not only for games, but also for videos, presentations, maps, and other immersive Mini Apps. Is this already planned, or is there a recommended Nimiq Pay integration that Mini Apps should use?