cryptosnif
Filecoin (FIL)
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
The Promise
Filecoin is described as a distributed storage network, with Lotus providing a software implementation. This dossier examines the deployment and build boundaries documented by Lotus. Storage proofs, completed deals and retrieval reliability remain separate questions for independent verification.
Established Facts
The primary source of information is the pinned README for Lotus, an implementation of the Filecoin protocol. This document identifies the Lotus suite components, including lotus, lotus-miner, and lotus-worker, alongside integrated markets and actor repositories. It explicitly states that the master branch is a development branch and advises using stable releases for production mainnet operations. The documentation distinguishes between mainnet builds and the calibration test network, noting that switching networks may require separate procedures. It also outlines a build guide that defaults to prebuilt proof binaries, with an alternative procedure for compiling them from source. These facts are derived solely from the provided summary of the repository content.
Unknowns
No storage proof was independently verified, no storage deal was executed and no retrieval test was performed in this dossier. The linked markets and built-in-actor repositories were not reviewed. The build instructions also supply no successful reproducible build here.
Current storage economics, actor powers, provider concentration and governance remain unknown within the gathered evidence. Actual use, native FIL supply, beneficial ownership, liquidity and the complete incident history also require dated observations.
Consequences
The development-branch warning gives a concrete boundary for examining deployed software: identify the stable release actually being used before interpreting its behavior. Mainnet and calibration-network observations also require separate scopes.
The guide's use of prebuilt proof binaries identifies another step to examine when assessing a build. A documented source-compilation procedure would need to be executed and its result checked before establishing reproducibility. Neither a build guide nor repository availability supplies a storage-reliability measurement or an investment-return forecast.
Verdict
Unrated, with 0% coverage of the scoring criteria. Lotus documents an implementation and its build procedures. Storage service behavior and economic strength remain unproven within this review, while the percentage describes the verified evidence available for rating FIL.
Evidence That Would Change It
A reproduced identity and deployment check would establish the software and network under examination. Independent storage-proof verification, a scoped deal and retrieval test, and a reproducible build would address the relevant mechanism questions. Provider participation, economic and incident evidence would then need calibration and editorial review before a score.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Validator independence, upgrades, execution and fees.
Inspect the evidence
Sources behind this analysis
Filecoin: pinned filecoin-project/lotus overview (99e2be23818e)
The pinned Lotus README identifies Lotus as an implementation of Filecoin's distributed storage network. It describes the Lotus suite as including lotus, lotus-miner and lotus-worker and names separate reusable markets and built-in-actor repositories integrated with Lotus. Those linked repositories were not reviewed in this capture. Its master branch is explicitly a development branch, and production mainnet operation should use an appropriate stable release. It distinguishes mainnet builds from the calibration test network and warns that switching networks can require a separate procedure. The build guide uses prebuilt proof binaries by default and points to another procedure for compiling those proof binaries from source. That documentation supplies no independent storage-proof verification, no storage deal, retrieval test or measure of service reliability. Source availability and a documented build procedure do not establish a successful reproducible build. Native FIL is this documentary subject, excluding provider-reported representations on other networks. Current storage economics, governance, actor powers, provider concentration, usage, supply, beneficial ownership, liquidity and full incident history remain unverified.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.