Home ▸ Wiki FAQ ▸ IFR Holder Discount
Classification: Restricted SC-IFR-001 StealthX // Inferno Integration
Classification: Restricted · SC-IFR

IFR Holder Discount

Browser-only IFR ownership verification for the seller-set discount displayed at checkout.

IFR is not used for in-app tier unlocking · Open $IFR on Uniswap

Overview

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 Android app never performs wallet verification. The public sales page contains the browser-only ownership flow; discounted payment remains fail-closed whenever the secure fiscal checkout is unavailable.

How It Works

Web checkout flow

  1. Open web checkout — The user starts from the StealthX website, not from the Android app.
  2. Verify wallet in browser — MetaMask or another browser wallet signs a read-only ownership challenge.
  3. Check IFR balance server-side — The backend verifies the wallet and IFR balance on Ethereum Mainnet.
  4. Apply checkout discount — Eligible holders receive the seller-set discount displayed at checkout.
  5. Unlock normally — Stripe delivers an activation code or license state. SecureCall stays wallet-free.
Discount Plan

Eligibility

Item Status Result
Current app Live No WalletConnect, no in-app IFR unlock
IFR holder checkout Launch-gated Disabled pending payment and accounting approval
Discount value Planned Seller-set discount displayed for eligible purchases
Important: Current SecureCall releases do not unlock Pro or Premium by connecting a wallet inside the app. Use Play billing or activation codes until the web discount flow is released.
FAQ

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.

Is there a minimum IFR amount?

No. Any positive IFR balance qualifies as holder proof. The seller displays the applicable product discount before checkout; the Android app never needs 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 Web Checkout

Why not WalletConnect in the app?

  1. Android wallet return links are fragile across MetaMask browser, WebView, and app-link policies.
  2. The app should remain focused on calls, contacts, settings, and normal tier unlocks.
  3. Stripe checkout is easier to audit and support than wallet state inside the Android app.
  4. Users still keep their IFR tokens; verification stays read-only and browser-based.
Internal test note: the old WalletConnect/SIWE app build is retained only for internal testing and is not the current public release path.
Wallet Apps

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.

Document End // Classification: Restricted