Islamic Finance Principles Assessment
Riba — Does io.net involve interest?
io.net's core business is transaction-fee revenue from GPU rental, not interest-based lending or borrowing. Staking rewards are drawn from a disinflationary emission schedule plus usage-linked burns rather than a fixed guaranteed yield. On balance, the protocol's design avoids explicit riba, though undisclosed staking mechanics warrant a cautious final take.
Assessment: Moderate Riba
Score: 62.1/100
Our methodology examines 10 criteria to evaluate how well io.net avoids interest-based mechanisms.
io.net's revenue derives from a 0.25% reservation fee on both renters and suppliers, plus a 2% fee when renters pay in USDC (waived when paying in IO). This is a service fee for real compute usage, not an interest-bearing loan arrangement. At least 50% of post-payout network revenue in IO is permanently burned, funded by actual usage rather than new debt issuance. No sources describe io.net's treasury holding interest-bearing instruments, money-market funds, or lending out user deposits, so the revenue model itself does not appear riba-based.
Rewards to "Suppliers and their Stakers" are paid hourly under a fixed, disinflationary emission schedule (starting at 8% annual inflation, declining ~1.02%/month toward the 800M cap), layered with demand-linked burns. Because a portion of the schedule is pre-set rather than purely tied to performance, it carries a resemblance to fixed-return structures, though it is funded by protocol emissions and real usage-based burns rather than debt or interest. Without confirmed slashing/performance conditions specific to io.net, stakers should treat this as a reward-sharing arrangement tied to network activity rather than a guaranteed interest payment, though the fixed-schedule component merits some caution.
Gharar — How much uncertainty does io.net involve?
io.net carries moderate uncertainty: the team and backers are named and traceable, which reduces gharar, but missing audit confirmation and incomplete staking disclosures increase it. Real operating metrics (revenue, contracts, GPU supply) provide grounding absent in purely speculative tokens. The final take is cautious: legitimate project, but disclosure gaps remain unresolved.
Assessment: Excessive Gharar (High Uncertainty)
Score: 48.4/100
Our methodology examines 15 criteria including team transparency, audit quality, and governance.
io.net's leadership is fully named and verifiable: founder Ahmad Shadid, current leadership under Gaurav Sharma (ex-Binance VP Engineering) and COO Basem Oubah, with public backers including Anatoly Yakovenko, Mo Shaikh, and Yat Siu. This transparency substantially reduces gharar compared to anonymous teams. Documentation is public via io.net's docs site and litepapers, describing tokenomics, fee structure, and the Incentive Dynamic Engine. However, explicit open-source licensing status and formal on-chain governance structures are not clearly described in available sources, leaving some disclosure gaps around code verifiability and decision-making authority.
No named audit of io.net's own smart contracts or protocol could be found in the sources reviewed; the security audits located (Halborn, Neodyme) concern unrelated projects, not io.net. This is a notable gharar concern that should be stated plainly rather than downplayed: an unaudited protocol carries elevated smart-contract and operational risk regardless of team legitimacy. Staking terms — custodial status, lock-up periods, unlock schedules, slashing conditions — are also not clearly documented for IO specifically, compounding uncertainty for anyone considering participation beyond simple holding.
Maysir — Does io.net involve gambling or speculation?
io.net is not designed as a gambling instrument; it functions as a marketplace token settling payments for genuine GPU compute rental. Real enterprise contracts and on-chain revenue distinguish it from purely speculative vehicles. Secondary-market price volatility exists, as with most tokens, but this is incidental to the protocol's design rather than its purpose.
Assessment: Moderate Maysir (High Risk)
Score: 68.5/100
Our methodology examines 11 criteria to determine whether io.net is a gambling instrument or a genuine economic tool.
io.net connects AI/ML developers needing compute with GPU suppliers, undercutting centralized cloud pricing through a decentralized marketplace. This is documented by real usage metrics: Total Network Earnings rising from $11.8M to $15.6M, roughly $84K/day, over $20M in annualized on-chain revenue, and an $8M enterprise contract. Fees are earned from actual service delivery, not wagering on outcomes. This productive, demand-driven utility is precisely what separates io.net from maysir-style instruments whose value derives solely from zero-sum speculation among participants.
Weighing genuine utility against speculative behavior, io.net's underlying protocol generates measurable revenue tied to real compute demand, and its burn mechanism is explicitly funded by usage rather than hype-driven issuance. That said, circulating supply figures vary across trackers (roughly 340-380M of an 800M max), and like most listed tokens, IO trades actively in secondary markets where short-term speculation can dominate price action. This trading behavior reflects broader market dynamics rather than a flaw in io.net's own design, and should not by itself be treated as determinative of the coin's Shariah standing.
The Full 27-Point Screening
1. Legitimacy (4 criteria)
| Criterion | Score | Analysis |
|---|
| Team Transparency | 78/100 | Team members and leadership transitions are named and traceable, with credentialed backers publicly listed. |
| Fraud & Scam Risk | 65/100 | No fraud, hack or regulatory action naming io.net appears in these sources, but this is an absence of adverse findings rather than a confirmed clean audit trail. |
| Use Case Legitimacy | 85/100 | The sources document a functioning decentralized GPU compute marketplace with real enterprise revenue and adoption. |
| Ethical Practices | 88/100 | The protocol's own design is a compute-rental marketplace, not built for or targeted at a prohibited industry. |
Summary: io.net has a named, credentialed team with leadership transitions and notable industry backers, and no fraud or regulatory action against the project itself appears in the sources.
2. Project Operations (9 criteria)
| Criterion | Score | Analysis |
|---|
| Core Protocol Business | 88/100 | Core business is GPU/CPU compute rental for AI/ML, a permissible sector. |
| Transaction Fees | 78/100 | Fees are transparent reservation/payment charges used to fund supplier payouts and token burns, not interest extraction. |
| Treasury Assets | 35/100 (low evidence) | Treasury asset composition (e.g., whether holdings are interest-bearing) is not disclosed in these sources. |
| Revenue Model | 82/100 | Revenue is generated from compute transaction fees rather than lending/interest activity. |
| Transparency | 58/100 | Public docs and litepapers exist, but open-source status of the codebase and full financial disclosure are not clearly confirmed. |
| Governance | 30/100 | No formal token-holder governance process is described; decision-making appears centralized in the corporate team. |
| Launch Fairness | 48/100 | Seed/Series A investors and core contributors received roughly a third of genesis supply with vesting, typical of a VC-backed rather than fully fair launch. |
| Token Distribution | 52/100 | Distribution spans community, investors, team and ecosystem categories, but a substantial insider/investor share exists alongside long emission schedules. |
| Speculation/Utility Ratio | 68/100 | The token's burn mechanism is explicitly tied to real network usage/revenue rather than pure speculation, per disclosed IDE design. |
Summary: The protocol runs a decentralized GPU compute marketplace with disclosed fee mechanics and a revenue-funded burn system, though governance and open-source status are not fully detailed.
3. Financial Health (4 criteria)
| Criterion | Score | Analysis |
|---|
| Protocol Revenue | 82/100 | Disclosed revenue streams are transaction-fee based, not riba-based. |
| Financial Status | 58/100 | Growing on-chain revenue and enterprise contracts are documented, but overall financial stability and reserves are not fully detailed. |
| Interest Assessment | 88/100 | The base protocol's documented functions are compute booking/payment/settlement, with no lending or borrowing feature described. |
| Audit Quality | 15/100 | No audit of io.net's own protocol or smart contracts appears in these sources; retrieved audit reports belong to unrelated projects. |
Summary: Reported revenue is fee-based and growing, the base protocol shows no lending/interest features, but no audit of io.net's own contracts could be located in these sources.
4. Token Economics (5 criteria)
| Criterion | Score | Analysis |
|---|
| Token Purpose | 78/100 | IO is used operationally to pay for and settle compute transactions, indicating genuine utility rather than meme status. |
| Governance Rights | 28/100 (low evidence) | No token-holder governance rights are described in these sources. |
| Rewards Distribution | 45/100 | Rewards follow a fixed, pre-set disinflationary emission schedule rather than being purely performance/variable-based, partially offset by usage-linked burns. |
| Speculation Controls | 62/100 | The Incentive Dynamic Engine explicitly links burns to real revenue to reduce speculative/inflationary dynamics. |
| Asset Backing | 68/100 | Token value is tied to real compute-service demand and revenue rather than a passive reserve asset. |
Summary: IO is used as an operational utility token for compute payments with a burn mechanism linked to real usage, though its emission-based reward schedule is largely fixed rather than fully variable.
5. Staking Mechanism (5 criteria)
| Criterion | Score | Analysis |
|---|
| Mechanism Type | 38/100 | A staking allocation and "Stakers" reward split are documented, but delegation mechanics, custody model and flexibility are not detailed. |
| Islamic Contract Classification | 25/100 | The reward comes from a scheduled token emission rather than a clearly documented profit-sharing (Mudarabah/Wakalah) arrangement, leaving the contract classification unresolved. |
| Rewards Structure | 30/100 | Rewards are paid on a fixed disinflationary schedule tied to time rather than being demonstrably variable with real staking performance. |
| Documentation | 20/100 (low evidence) | No dedicated documentation of staking lock-up terms, slashing conditions or risk disclosures for IO was found. |
| Shariah Alignment | 32/100 | The mixture of fixed scheduled emissions and undocumented mechanics leaves a core Shariah question about the staking reward's nature unresolved. |
Summary: A staking mechanism tied to "Suppliers and their Stakers" exists, but its custody, lock-up, slashing and Islamic contract classification are not clearly documented in the sources.
Overall Assessment: io.net presents as a genuine, revenue-generating decentralized compute project with reasonable operational transparency, but gaps remain around audits, treasury composition, governance rights and staking-reward documentation that limit full Shariah verification.
Written by ThanvirFounder, Ex Director S&P Global Energy
Reviewed by Imam Omar SiddiqiShariah Scholar