User Agreement

1.

Acceptance and updates

By registering, signing in, purchasing capacity or equipment, using APIs or Web interfaces, you enter into a binding agreement with the policies published on flopser.com.

We may update this document; continued use after changes constitutes acceptance. Lack of awareness does not waive compliance.

2.

Official channels

Primary website: flopser.com. Official communication addresses include admin@flopser.com and notify@flopser.com.

3.

Credentials and account safety

Passwords and secrets are not stored in plaintext in our systems; only secure verification artifacts are kept.

We may suspend or terminate accounts linked to suspicious transactions, abusive compute usage or risk signals. Refunds or adjustments are handled at the platform's reasonable discretion on a case-by-case basis.

4.

Cookies and identifiers

We use cookies and similar technologies for sessions, preferences, analytics and abuse prevention. Email and related identifiers may be retained without a fixed expiry where required for operations, legal obligations or fraud prevention.

5.

Nature of the service

Flopser provides computing power infrastructure and orchestration. Participation is voluntary; the platform is not an investment product or deposit-taking institution.

6.

Pricing and capacity valuation

The market values compute capacity; our pricing engine weighs multiple independent signals. Factors may include AI workload demand, implied value of 1 TFLOPS, network reputation and latency, token pricing inside our data-centre economics, overall AI-sector capitalisation, fleet utilisation, hardware depreciation curves and macro volatility.

These inputs are combined statistically; there is no guaranteed one-to-one mapping between any single factor and the price you see.

7.

GFT, GFLOPS anchor and liquidity

GFT pricing references the economic value of 1 GFLOPS using similar macro signals as above; automated rebalancing applies. Web3 swap and custody features co-exist with Web2 balances.

We are not obliged to keep the entire project treasury as on-chain token liquidity. As an indicative ceiling, on-chain token liquidity should not exceed a two-to-one ratio versus the reference valuation that combines replacement cost of deployed hardware and an illustrative six-month forward yield scenario.

8.

Miscellaneous

If any clause is held invalid, the remainder stays enforceable. Governing language follows the English master copy where translations differ.