Hi! I have a question about the dates. On the website, it says that Pitch Day is on July 30, but in the Skool community I only see a regular call scheduled for July 29, at least from what I understand. I also saw that submissions close on July 31. Could you please clarify the exact dates and schedule for Pitch Day and submissions so we can make sure we don’t miss anything? Thank you!😸

1. What's the exact Cycle-I submission process and hard deadline (date/time/timezone)? Is it a PR to a specific repo or a portal, and where does the ≤250-word write-up go? 2. How do we get our Mini App listed in the in-app library so testers don't hit the "Open this mini app?" warning? What's the process + lead time? 3. Does the GitHub repo need to be public at Early Access start (~20 Jul), or only at final submission (~2 Aug)? 4. Any license-back / IP clause in the T&C to know about before flipping an MIT repo public? 5. How is "unique wallets that transacted" measured for scoring?

I need to broadcast NIM transactions on testnet from a small backend (treasury → user payouts at settlement). My transport is offline-sign + HTTP JSON-RPC: build & sign the tx offline (TransactionBuilder.newBasic → signTransaction → toHex), then POST sendRawTransaction to a node. This works perfectly against the public mainnet RPC https://rpc.nimiqwatch.com — it returns a tx hash and accepts the tx. The blocker: the testnet equivalent https://rpc.nimiq-testnet.com is returning an nginx 500 (not responding), so I can't broadcast on testnet. Questions: 1. Is there a healthy/official public testnet (Albatross) JSON-RPC endpoint I can point at — or is rpc.nimiq-testnet.com expected to come back up? 2. If not, what's the recommended way for a Mini App backend to broadcast testnet transactions? (I'd prefer not to run a local node — @nimiq/core's Node client throws on worker init / never reaches consensus in plain Node.) 3. Otherwise, is mainnet with tiny real amounts the intended path for testing Mini App money flows? Thanks!

Looking for a gut-check on the idea and one design decision. THE IDEA — a social commitment game as a Nimiq Pay mini app. You stake a small amount on a personal goal for a week (run daily, no sugar, meditate, study an hour…) and do it with friends keeping you honest — social proof, not surveillance. Finish the week and you reclaim your stake, plus a share of what the quitters forfeit, plus a small NIM completion bonus. Miss a day and you forfeit that day's slice. Inviting friends to join is the core loop, so it's meant to pull new people into Nimiq Pay. THE FORK — how we hold the stakes: 1) Self-custodial / trustless: stakes go into an on-chain escrow contract (USDT on Polygon). Bulletproof, no-rug, on-brand for a self-custodial wallet — but each user has to approve + interact with the contract at join, and pay POL gas. A brand-new wallet has no POL, so this friction lands at the most conversion- critical moment. 2) Custodial: users send NIM (free, instant, no EVM, no gas) to a transparent, app-controlled wallet; we run the escrow logic off-chain and pay out in NIM. Buttery-smooth onboarding and leans hard into NIM — but we'd be custodying pooled user funds, which raises trust and possibly regulatory questions, and cuts against the self-custody ethos. Questions for the community / Nimiq team: - Does the idea resonate, and does it fit what you want to see on Nimiq Pay? - For this competition and ecosystem, is a low-stakes, transparent custodial model acceptable — or is self-custody the firm expectation? - If self-custodial: how are others making a first-time EVM stake gasless for a zero-POL wallet? Any sanctioned relayer/paymaster or pattern you'd recommend? Thanks — genuinely torn on this one and would value the perspective.

Quick confirmation question before we commit to an architecture. The EVM Tokens docs say that gas abstraction applies only to native Nimiq Pay sends, and that "in a mini app, standard EVM gas rules apply — the user must hold the native token of the chain to cover gas fees" (POL on Polygon, etc.). Reading that literally, it means: 1. A Mini App calling any contract via window.ethereum (e.g. an ERC-20 transfer or a custom contract method) requires the user to already hold POL for gas. 2. A brand-new Nimiq Pay wallet with a 0 POL balance therefore cannot complete a Mini-App-initiated EVM transaction — it would fail. Two things I want to confirm: - Is that understanding correct, with no exceptions? - Is there any officially supported path to sponsor/abstract gas for Mini-App EVM transactions (a relayer, paymaster, ERC-4337, or the Nimiq gas-abstraction relayer exposed to Mini Apps)? Or is a self-run relayer / funding users' gas the only option today? Thanks!