eeFidocs 2.0 What BeeFi is Market Risks FAQ public · docs 2.0
Product → Verification and transparency

Verification and transparency

Don't trust — replay. BeeFi's answer to "how do I know?" is always the same: check it yourself.

What participants can verify

  • Asset backing. Every asset issued on the venue can be independently audited: anyone can confirm that no share exists without a genuine Bitcoin commitment behind it. This is a public capability, not a request-you-file-with-support.
  • Committed terms. A round's terms, supply, and milestone schedule are committed before investors join. What you evaluated is what exists — later edits cannot quietly rewrite the deal.
  • Settlement. Payments and share deliveries settle in single Bitcoin transactions that both sides can inspect before signing and confirm after the fact on any Bitcoin block explorer.
  • Governance outcomes. Votes produce auditable tallies that members can recompute.

Open source, on purpose

BeeFi's software is open source under the GNU Affero General Public License v3 (AGPL-3.0). Anyone may read, run, and audit the code — and anyone operating it as a service must share their modifications. For a venue whose pitch is "verify, don't trust", keeping the codebase closed would be a contradiction.

What transparency does not mean

  • Your business terms stay private. Contracts, allocations, and negotiations live with the participants; the public chain sees settlement, not your documents.
  • Your identity stays gated. Verification data is handled for compliance purposes under the venue's privacy approach — see trust/privacy.
  • Some engineering detail is pre-launch confidential. The protocol's design is public and the code is open; certain implementation specifics are published at launch rather than before. This is a competitive-timing choice, not a hiding of behaviour — everything the system does remains verifiable by its users.

Status honesty

Transparency includes saying where we are: BeeFi currently operates in Bitcoin testing environments. Claims in these documents describe demonstrated behaviour in those environments, and the move to production networks is a separately gated step — see legal/regulatory-approach.

323 words · 2 min readBeeFi · docs 2.0 · publicno investment advice