IFR Holder Discount
Browser-based IFR verification for discounted Stripe checkout.
Current status
$IFR (Inferno) is an ERC-20 token on Ethereum. SecureCall no longer includes WalletConnect or in-app IFR tier unlocking in the current release line.
The previous Android WalletConnect/SIWE flow is kept only as an internal test build. The public model is a web checkout discount: verify an eligible wallet in the browser, receive a 50% Stripe discount, then unlock the app through the normal purchase or activation-code path.
- Token: $IFR (Inferno) — 9 decimals
- Network: Ethereum Mainnet (Chain ID: 1)
- Token Contract:
0x77e99917Eca8539c62F509ED1193ac36580A6e7B - Trade: Open $IFR on Uniswap
- App status: no in-app WalletConnect or IFR unlock in the current SecureCall release
Web checkout flow
- Open web checkout — The user starts from the StealthX website, not from the Android app.
- Verify wallet in browser — MetaMask or another browser wallet signs a read-only ownership challenge.
- Check IFR balance server-side — The backend verifies the wallet and IFR balance on Ethereum Mainnet.
- Apply Stripe discount — Eligible holders receive a checkout discount, 50%.
- Unlock normally — Stripe delivers an activation code or license state. SecureCall stays wallet-free.
Eligibility
| Item | Status | Result |
|---|---|---|
| Current app | Live | No WalletConnect, no in-app IFR unlock |
| IFR holder checkout | Active | Browser verification plus Stripe discount |
| Discount value | Active | 50% off eligible Stripe purchases |
Frequently Asked Questions
Can I move my tokens?
Yes. The planned flow is read-only and does not spend, transfer, or lock IFR. Eligibility will be checked at web checkout time.
What if I add more tokens?
Eligibility is checked in the browser before Stripe checkout. The Android app will not need a wallet connection.
Is it safe?
The planned browser verification never gives SecureCall access to private keys. The server performs a read-only balance check and Stripe handles payment details.
Can I use the same wallet on multiple devices?
The planned discount is checkout-bound, not device-bound. Once a license or activation code is issued, the app uses the normal unlock path.
What happens if the Ethereum network is down?
The discount check would be unavailable until Ethereum RPC access recovers. Existing app purchases and activation codes are not affected.
Why not WalletConnect in the app?
- Android wallet return links are fragile across MetaMask browser, WebView, and app-link policies.
- The app should remain focused on calls, contacts, settings, and normal tier unlocks.
- Stripe checkout is easier to audit and support than wallet state inside the Android app.
- Users still keep their IFR tokens; verification stays read-only and browser-based.
Wallet App Helper
Wallet verification happens in the browser with wallets such as MetaMask. SecureCall itself will not open wallet apps or store wallet state.