# Security & Transparency

<figure><img src="/files/sVTjcROcAg6xZIHh52t2" alt=""><figcaption></figcaption></figure>

## **Security & Transparency**

Bitcoin Everlight places a strong emphasis on **security, accountability, and open verification**. To ensure the protocol’s code quality and team integrity, the project has engaged multiple reputable third-party firms for **independent smart contract audits and identity verification**. All reviews are conducted by external security specialists with no affiliation to the project’s development team.

### **Smart Contract Audits**

The core smart contracts powering Bitcoin Everlight have been independently reviewed to detect potential vulnerabilities, validate logic correctness, and confirm alignment with security best practices. These audits encompass token contracts, treasury mechanisms, and key protocol functions.

#### Completed / Available Audits

• **SolidProof Audit** — Independent assessment of Bitcoin Everlight’s contract logic, risk surfaces, and architectural soundness.\
🔗 **Link:** <https://app.solidproof.io/projects/bitcoin-everlight>

• **SpyWolf Audit** — Detailed security analysis covering ERC-20 implementation, deployment assumptions, and contract behavior under edge conditions.\
🔗 **Link:** <https://spywolf.co/audits/Bitcoin_Everlight_0xD3D9dA6345120822B7066B4263fD70F8d8612FFd.pdf>

> *Where possible, readers should refer to each firm’s published report for full methodology, findings, and recommendations.*

### **Team Identity Verification**

To reinforce accountability and transparency, Bitcoin Everlight’s core contributors have completed **third-party identity verification** with trusted compliance providers. This verification process includes jurisdictional checks, identity documentation verification, and anti-fraud validation, ensuring that the project’s leadership is identifiable and verifiable.

#### Certificates

• **VitalBlock Certificate** — Verified team identity certification.\
🔗 **Link:** <https://github.com/VBS-Labs/KYC-Validation-Certificate/blob/main/BTC%20Everlight%20KYC%20CERTIFICATE.pdf>

• **SpyWolf Certificate** — Independent confirmation of contributor identities.\
🔗 **Link:** <https://spywolf.co/kyc-verification/KYC_Bitcoin_Everlight_0xD3D9dA6345120822B7066B4263fD70F8d8612FFd.pdf>

### **Security Philosophy**

Bitcoin Everlight combines **independent technical audits** with **verified team identity checks** to maximize trustworthiness and operational clarity. By partnering with established third-party auditors and verification firms, the protocol demonstrates a commitment to **industry-standard security practices** and **transparent ecosystem participation**.

#### BTC Fee Handling and Distribution Security

BTC-denominated network fees are collected as part of Everlight transaction routing and optional anchoring workflows. These BTC fees are aggregated into protocol-controlled reward pools prior to distribution to eligible node operators.

BTC reward pools are handled using deterministic, auditable processes designed to minimize trust assumptions and reduce attack surface. Distribution calculations are based on verifiable performance metrics recorded by the protocol.

Bitcoin Everlight does not custody user BTC beyond what is required for fee aggregation and scheduled distribution. BTC payouts to node operators are executed according to protocol-defined rules and distribution epochs.

Risks associated with BTC handling include transaction delays, fee volatility, and external Bitcoin network conditions. These risks do not affect Bitcoin’s base protocol and are isolated to Everlight’s fee handling and distribution processes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bitcoin-everlight.gitbook.io/bitcoin-everlight-docs/security-and-transparency.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
