50/100 — Audited by Token Verdict
WeaveDB is the "Layer-0 zkDatabase for the AI-Driven Verifiable Internet" — a decentralized database protocol built on Arweave/AO that delivers cloud-grade performance via LSM rollup architecture, with zkJSON proofs enabling smart contracts on Ethereum, Solana, and other chains to query off-chain data with cryptographic guarantees. The two hard stops: the team is completely anonymous with no publicly identifiable founders, and a $DB token launch featuring complex dual-token bonding curve mechanics has zero smart contract audits on record — a dangerous gap for anything touching on-chain value. The technical foundation is genuinely substantive: open-source repos totaling 325 GitHub stars, a protocol formally verified in Lean theorem prover, and a live zkJSON library that stands independently as real ZK engineering — this is not whitepaper vapor. Score: 47/100 — technically credible infrastructure play, but uninvestable until founders surface and an audit is published.
How well-structured is the token supply, allocation, and distribution?
Tokenomics page exists but supply details unclear.
Allocation mentioned but no specific percentages found.
Vesting mentioned but specifics unclear.
5 distinct token utilities identified.
No burn or deflationary mechanism found.
How is the TGE structured? Is it fair and transparent?
No launch platform details found.
Fair price discovery mechanism found.
Liquidity mentioned but no lock details.
Vesting may provide indirect dump protection.
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.
10 repos found on GitHub.
Does this project have real market demand and competitive positioning?
Project description found. Problem-solution fit needs manual review.
Targets large markets: ai, storage.
Project has description but competitive edge needs manual review.
Traction signals: 325 GitHub stars, Twitter: @weave_db, community channels found.
How engaged is the community and how is governance structured?
Community presence: Twitter: @weave_db, Discord.
Governance model mentioned.
Communication: whitepaper available, Medium blog, detailed website.