Effective Date: April 22, 2026
This document contains the Terms and Conditions governing use of the Flew Protocol. Please read carefully before using the protocol.

1. Introduction and Acceptance

Welcome to Flew Live (“Flew,” “the Protocol,” “we,” “us,” or “our”), a privacy-preserving prediction market protocol built on the Solana blockchain and powered by Arcium’s confidential computation infrastructure. By accessing, interacting with, or using the Flew Live Protocol — including its smart contracts, interfaces, software development kits (SDKs), application programming interfaces (APIs), or any associated front-end products — you (“User,” “you”) agree to be bound by these Terms and Conditions (“Terms”). If you do not agree to these Terms, you must not use the Protocol. These Terms constitute a legally binding agreement between you and Flew Live. Your use of the Protocol constitutes your ongoing acceptance of any updates or amendments to these Terms, which will be published with a revised effective date.

2. Protocol Overview

Flew is a privacy-preserving prediction market protocol that enables users to:
  • Create permissionless prediction markets
  • Place private bets on market outcomes
  • Participate in policy-controlled market types
  • Claim payouts or refunds following market resolution
The Protocol uses confidential computation powered by Arcium’s Multi-Party Computation (MPC) infrastructure to keep bet positions and pool state encrypted during the live market phase. Settlement occurs verifiably at resolution. This temporal privacy model — private during the live phase, verifiable at settlement — is fundamental to the Protocol’s design.
Flew Protocol is experimental software. Interaction with blockchain protocols carries significant financial risk. You acknowledge that use of this Protocol may result in partial or total loss of digital assets.

3. Eligibility and Access

3.1 General Eligibility

To use the Protocol, you represent and warrant that:
  • You are at least 18 years of age, or the age of legal majority in your jurisdiction, whichever is higher
  • You have full legal capacity to enter into a binding agreement
  • Your use of the Protocol does not violate any applicable laws or regulations in your jurisdiction
  • You are not subject to economic or trade sanctions administered by any government authority
  • You are not a citizen or resident of any jurisdiction where use of the Protocol is prohibited

3.2 Jurisdictional Restrictions

The Protocol is not available to individuals or entities located in, or ordinarily resident in, jurisdictions where prediction markets, digital asset protocols, or related activities are prohibited or require regulatory licensing not held by Flew Protocol, including but not limited to the United States of America, unless applicable exemptions exist. You are solely responsible for determining whether your use of the Protocol is lawful in your jurisdiction. Flew Protocol makes no representation that the Protocol is appropriate or legally permissible in any particular jurisdiction.

3.3 Integrator Access

Developers, organizations, and platforms (“Integrators”) accessing the Protocol through its SDK or API interfaces are additionally bound by any applicable integrator agreement. Integrators accept responsibility for ensuring their own users comply with applicable laws.

4. Protocol Mechanics and User Responsibilities

4.1 Market Creation

Any eligible user may create a prediction market on the Protocol (“permissionless creation”). When creating a market, the creator must:
  • Post a creator bond into the market vault in the amount required by the relevant market policy
  • Define a resolution path consistent with Protocol policy rules
  • Configure market parameters including resolution windows, claim and refund deadlines, and market type designations
The creator bond is distinct from the YES/NO betting pools. It serves as an accountability mechanism and is subject to forfeiture or redistribution in accordance with Protocol policy if the market creator fails to fulfill their obligations.

4.2 Bet Placement

When placing a bet, users provide private inputs that are encrypted and routed through Arcium’s MPC computation pipeline. The Protocol does not expose bet size, side, or identity in plaintext during the live market phase. By placing a bet, you acknowledge:
  • Bet placement is a final, irreversible on-chain action once confirmed
  • Private inputs are processed through third-party MPC infrastructure (Arcium) over which Flew has limited operational control
  • Network congestion, computational delays, or infrastructure issues may affect the timing of computation callbacks
  • You have independently assessed the market and are acting on your own judgment

4.3 Resolution

Markets are resolved by an authorized resolver. Resolution triggers a confidential computation through Arcium that reveals the pool state necessary for fair settlement and computes payout ratios. You acknowledge:
  • Resolution is not automated or trustless in the current protocol version
  • The resolver is an authorized party, not a decentralized oracle network
  • Resolution is subject to the deadlines and fallback paths defined by the applicable market policy
  • If a market is not resolved within the defined window, refund paths become available

4.4 Claims and Refunds

Following resolution, winning users may claim payouts within the claim window defined by market policy. If a market is unresolved within the resolution window, users may claim refunds. Claim and refund rights expire at the deadlines defined in the market policy. Flew Protocol accepts no liability for unclaimed funds resulting from a user’s failure to act within applicable windows.

5. Privacy Architecture and Trust Assumptions

5.1 What the Protocol Protects

During the live market phase, the Protocol uses confidential computation to protect:
  • Bet amounts
  • Bet side (YES or NO)
  • Aggregate YES/NO pool accounting
  • Intermediate computation state
At resolution, the Protocol reveals only the pool state information necessary to compute fair settlement ratios. Post-settlement, aggregate outcome data becomes publicly verifiable on-chain.

5.2 What the Protocol Does Not Protect

The Protocol’s privacy model does not extend to:
  • On-chain transaction metadata, including wallet addresses, transaction hashes, and timestamps, which are inherently public on Solana
  • The identity of market creators or resolvers
  • The existence of a user’s participation in a market (i.e., that a wallet interacted with the market), even if the amount and side remain private
  • Off-chain data, communications, or any information not processed through Arcium’s MPC pipeline
Privacy protection during the live phase does not guarantee anonymity. On-chain transaction metadata is publicly visible. Do not treat use of this Protocol as equivalent to anonymized financial activity.

5.3 Third-Party Computation Dependencies

The Protocol’s confidential computation functionality depends materially on Arcium’s MPC infrastructure. Flew Protocol does not operate or control Arcium’s node network, execution environments, or cryptographic key management. You acknowledge that:
  • Arcium’s X25519 key exchange and Rescue-based encryption are foundational to the privacy model
  • Arcium’s availability, performance, and security assumptions are outside Flew Protocol’s direct control
  • Changes to Arcium’s infrastructure or protocol may affect the Protocol’s privacy guarantees

6. Risks and Disclaimers

6.1 Financial Risk

Prediction markets are speculative instruments. Participation may result in partial or total loss of digital assets. You should never participate with funds you cannot afford to lose. Flew Protocol does not provide investment, financial, or trading advice. Nothing in the Protocol, its documentation, or associated communications constitutes a recommendation to participate in any market.

6.2 Smart Contract Risk

The Protocol’s smart contracts have not been audited by an independent third party as of the effective date of these Terms. Smart contracts may contain bugs, vulnerabilities, or logic errors that could result in loss of funds. By using the Protocol, you accept these risks.

6.3 Blockchain and Network Risk

Solana network congestion, outages, forks, or upgrades may affect the Protocol’s operation. Transaction finality, computational callback timing, and on-chain state transitions depend on the health and performance of the Solana network, which is outside Flew Protocol’s control.

6.4 Regulatory Risk

The regulatory environment for blockchain-based prediction markets is evolving rapidly. Changes in applicable law or regulation may render the Protocol or specific market types non-compliant in certain jurisdictions. You are solely responsible for assessing and complying with applicable legal requirements.

6.5 Resolver Risk

In the current protocol version, market resolution depends on an authorized resolver acting honestly and within defined deadlines. Resolver failure, dishonesty, or unavailability may result in unresolved markets. While the Protocol includes refund paths for unresolved markets, users should assess resolver trust before participating.

6.6 No Warranties

THE PROTOCOL IS PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. FLEW PROTOCOL EXPRESSLY DISCLAIMS ALL WARRANTIES, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND UNINTERRUPTED OR ERROR-FREE OPERATION. WE DO NOT WARRANT THAT THE PROTOCOL WILL BE AVAILABLE AT ALL TIMES OR THAT IT WILL OPERATE WITHOUT ERRORS OR INTERRUPTIONS.

7. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, FLEW PROTOCOL AND ITS CONTRIBUTORS, DEVELOPERS, AFFILIATES, OFFICERS, EMPLOYEES, AND AGENTS SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES, INCLUDING BUT NOT LIMITED TO LOSS OF DIGITAL ASSETS, LOSS OF PROFITS, LOSS OF DATA, OR LOSS OF GOODWILL, ARISING OUT OF OR IN CONNECTION WITH:
  • Your use of or inability to use the Protocol
  • Any smart contract bug, vulnerability, or exploit
  • Failure or unavailability of Arcium’s MPC infrastructure
  • Solana network issues, congestion, or outages
  • Resolver failure, delay, or dishonesty
  • Unauthorized access to your wallet or private keys
  • Any third-party actions or integrations
Where liability cannot be excluded under applicable law, Flew Protocol’s aggregate liability shall not exceed the lesser of: (a) the total fees paid by you to the Protocol in the twelve months preceding the event giving rise to liability, or (b) USD $100.

8. User Conduct and Prohibited Uses

You agree not to use the Protocol to:
  • Violate any applicable law or regulation
  • Engage in market manipulation, wash trading, or coordinated deceptive behavior
  • Exploit smart contract bugs, vulnerabilities, or unintended behaviors for personal gain
  • Circumvent the Protocol’s policy controls, access restrictions, or wallet-gating mechanisms
  • Create markets with outcomes tied to illegal activity, violence, or harm to individuals
  • Facilitate money laundering, sanctions evasion, or other financial crimes
  • Attempt to reverse-engineer, decompile, or tamper with the Protocol’s smart contracts or cryptographic infrastructure in unauthorized ways
  • Use automated systems to interact with the Protocol in ways that degrade performance for other users

9. Intellectual Property

All software, documentation, SDKs, smart contract code, and related materials published by Flew Protocol are subject to their respective open-source licenses where applicable. Use of the Protocol’s code outside the scope of its published license(s) is prohibited without written permission. The Flew name, logo, and branding are proprietary to Flew Protocol. No right to use these marks is granted by these Terms or by use of the Protocol.

10. Protocol Fees

The Protocol may collect fees on market activity, including market creation, bet placement, and payout claims. Fee structures are defined at the protocol level and may vary by market type, integrator, or policy configuration. Current fee parameters are documented in the Protocol’s on-chain configuration and associated documentation. In B2B integrator deployments, fees may be split between the Flew treasury, the integrating platform, and Arcium infrastructure costs pursuant to separate integrator agreements. Flew Protocol reserves the right to modify fee structures with reasonable notice published on its official channels.

11. Modifications to the Protocol and Terms

Flew Protocol reserves the right to modify, upgrade, or deprecate the Protocol at any time, including through smart contract upgrades, parameter changes, or infrastructure changes. We will endeavor to provide reasonable notice of material changes through our official communication channels, including @flewlive_ on X (formerly Twitter). These Terms may be updated from time to time. Continued use of the Protocol after the effective date of any update constitutes acceptance of the revised Terms.

12. Governing Law and Dispute Resolution

These Terms shall be governed by and construed in accordance with applicable laws, without regard to conflict of laws principles. Any disputes arising out of or in connection with these Terms or your use of the Protocol shall be resolved through binding arbitration, except that either party may seek injunctive relief in a court of competent jurisdiction for matters involving intellectual property or irreparable harm. You waive any right to participate in class-action proceedings against Flew Protocol.

13. Severability and Entire Agreement

If any provision of these Terms is found to be unenforceable, the remaining provisions shall continue in full force and effect. These Terms, together with any applicable integrator agreement and the Privacy Policy, constitute the entire agreement between you and Flew Protocol regarding your use of the Protocol.
These Terms and Conditions are provided for informational purposes and do not constitute legal advice. Users are encouraged to seek independent legal counsel regarding their use of the Protocol in their respective jurisdictions.

© Flew Live · April 22, 2026 · flew.live