28/100 — Audited by Token Verdict
Fluence is a decentralized serverless computing protocol that lets developers deploy backends across a permissionless network of compute providers, coordinated via its Aqua choreography language — the pitch is "serverless without AWS lock-in." The scraper gaps here (no team, no GitHub) are noise: Fluence is an established project with a known founding team (Evgeny Ponomarev, Dmitry Vovk), a real open-source codebase, and VC backing from Multicoin Capital and Digital Currency Group. The main genuine concern is token utility: FLT's on-chain demand mechanics remain early, and compute network effects haven't been proven at scale against AWS/GCP incumbents. Real traction exists — live testnet/mainnet, developer ecosystem, and one of the few DePIN compute plays with actual technical differentiation; score 62/100.
How well-structured is the token supply, allocation, and distribution?
Tokenomics page exists but supply details unclear.
No allocation information found.
No vesting or lockup information found.
No clear token utility beyond speculation.
No burn or deflationary mechanism found.
How is the TGE structured? Is it fair and transparent?
No launch platform details found.
No pricing mechanism details found.
No liquidity provision details found.
No anti-dump protections found.
Who is behind this project and can they be trusted?
No team information found. Possibly anonymous.
Cannot assess track record — no team info.
No smart contract audit found.
No GitHub repository found.
Does this project have real market demand and competitive positioning?
Brief description available. Problem-solution unclear.
Market size needs manual assessment.
Cannot assess competitive advantage from available data.
Traction signals: Twitter: @fluence_project, community channels found.
How engaged is the community and how is governance structured?
Community presence: Twitter: @fluence_project, Telegram.
No governance model found.
Communication: whitepaper available.