Integrate IFR Benefits — Without a Server

Partners and communities connect to IFR benefits without running any server. Everything below works with the existing IFR Benefits shop, the public blockchain and services you may already use.

1. Discounts at Checkout: IFR Benefits (no server)

Register your business in IFR Benefits and create benefit rules: a discount percentage, the IFR a customer must have locked and, optionally, IFR they must hold. At checkout the shop verifies every rule on-chain at one Ethereum block and records the redemption. Your rules are the single source of truth for every surface below. See Business Onboarding.

2. Show Benefits on Your Website: Display Widget

The widget reads the visitor's IFRLock balance directly from Ethereum Mainnet through a public RPC and shows for which of your IFR Benefits rules the visitor's visible lock and hold thresholds are met. Meeting a threshold is not a granted benefit: checkout confirms it and also applies redemption limits and final checks. It loads your active rules from IFR Benefits; without a business it shows the IFRLock tier ladder (Bronze 1,000 · Silver 2,500 · Gold 5,000 · Platinum 10,000 IFR locked), the same presets the shop uses. It never invents a discount.

<div data-ifr-benefits data-business="your-shop-slug"></div>
<script src="https://ifrunit.tech/widget/ifr-benefits-widget.js"
        integrity="sha384-TcQue2NkvC0mRfTTUBHgOwWUxmhF6ZBuLN7ez5XaCBMlRh7QbN72g8Pf9iBcYyyY"
        crossorigin="anonymous" defer></script>

• Display only. A browser check is not access control and grants nothing. The discount is granted at checkout through IFR Benefits, which re-verifies on-chain.
• Fail closed. If the RPC or your rules cannot be read, the widget says so and shows no benefit.
• Only what a browser can prove. Rules met through IFRLock are shown as met. Rules that also accept CommitmentVault time locks are shown as “checked at checkout” unless IFRLock already meets them.
• Data flows. No cookies and no tracking. The widget sends the connected wallet address to the configured RPC and loads your public rules from IFR Benefits (data-api); both providers can see connection metadata such as IP address. Remote text is never rendered as HTML.
• Options: data-rpc (your own RPC URL), data-api (defaults to https://shop.ifrunit.tech).
• Integrity hash: sha384-TcQue2NkvC0mRfTTUBHgOwWUxmhF6ZBuLN7ez5XaCBMlRh7QbN72g8Pf9iBcYyyY

3. Communities and Discord: Guild.xyz or Collab.Land

Use an existing token-gating service with a custom contract-read requirement on Ethereum Mainnet. No IFR server is involved.

Guild.xyz: add a requirement “Contract query” (custom contract call) with the values above and the condition “greater or equal”. Collab.Land: create a token gating rule with a custom contract call using the values above. Name the role after the tier, for example “IFR Silver (2,500 locked)”. The alternative isLocked(address user, uint256 minAmount) returns true when at least minAmount is locked.

4. Optional: Self-Hosted Creator Gateway

The Creator Gateway remains available for creators who want to run their own instance (for example to combine an IFR lock with a YouTube membership). It is optional; the project does not operate a central gateway and does not store personal data.

What This Does Not Do

• No IFR rewards for partners: partner rewards are disabled until a pilot partner is approved (Lane 4).
• No custody: users keep their own wallets; there is no embedded wallet.
• No secret-content protection from the browser widget alone; use IFR Benefits checkout or a token-gating service.