1. Inside a mini app, is the address returned by window.ethereum (eth_requestAccounts) the same address that holds the user's USDT in Nimiq Pay? 2. Is that USDT the Polygon contract 0xc2132D05D31c914a87C6611C10748AEb04B58e8F (USDT0)? 3. Do mini app contract calls (e.g. approve + supply on Aave) need POL from the user, or is there any gas sponsorship available to mini apps? Thanks in advance !

I am I'm testing my mini app but unfortunately I can't log in to nimiq pay. When I click login, the app doesn't respond at all. It really makes it difficult for me to test my mini app. I've tried using another device but the device only displays a white blank when opening Nimiq Pay. Has anyone experienced the same problem?

Hi nimiq team, I can't withdraw usdt from the nimiq wallet on Polygon chain. It gives an error. Would appreciate your help in fixing this.

Hey everyone Me and my teammates was running into a TESTNET issue while testing our Mini App with Nimiq Pay 2.19.1 and wanted to check if this is known or if there’s a workaround. The flow works correctly up to the native transaction approval screen. We approve the transaction in Nimiq Pay, but immediately afterwards we get: “Something went wrong syncing your account.” We reproduced it twice. What I’ve verified: - Nimiq Pay version: 2.19.1 - TESTNET - provider initializes correctly - listAccounts() works - isConsensusEstablished() → true - getBlockNumber() works - transaction amount: 1 NIM / 100000 Luna - requested fee: 0 - recipient is valid - transaction data is 49 UTF-8 bytes, under the 64-byte limit - sendBasicTransactionWithData() reaches the native Nimiq Pay approval UI - after approval, no transaction hash is returned - independent TESTNET explorer check confirms the transaction was never broadcast I also saw another report where even a plain TESTNET wallet-to-wallet transaction on Nimiq Pay 2.19.1 appears to fail after approval, so I’m wondering if this could be a current TESTNET submission issue rather than Mini App-specific. Has anyone found: - a known fix or workaround? - a specific parameter required for TESTNET transactions? - whether validityStartHeight should currently be passed explicitly? - whether this is a known Nimiq Pay 2.19.1 / TESTNET regression? Happy to provide sanitized logs or help reproduce it. I’m avoiding MAINNET testing for now because I don’t want to use real funds just to diagnose a TESTNET issue.

Hi! I have a question regarding the Nimiq Pay / NIM integration requirement. NimiCurl is a multiplayer curling game fully integrated into Nimiq Pay. It uses the Nimiq Pay Mini Apps SDK for wallet connection and uses the connected wallet to power player profiles, identicons, match history and League features. However, the game currently does not use NIM or USDT for gameplay or player transactions. NIM payments are planned for the Partnership area, where sponsors will be able to pay in NIM to support competitions and in-game events. But playing Nimcurl is FREE today ! Would this satisfy the Nimiq Pay / NIM integration requirement, or does the Mini App need to support an actual NIM or USDT transaction to qualify? Thanks!