CCC Burn Plugin & Carbon Calculator

From the Carbon Credit Coin Development Lab Team
Date Range: March 1, 2025 – September 1, 2025 Document Version: 1.0

Executive Summary

The CCC Burn Plugin & Carbon Calculator delivers a seamless path from lifestyle emissions estimation to on-chain CCC token burns with instant, verifiable carbon offset certificates. Over a focused six-month R&D cycle, the Development Lab engineered a production-ready WordPress plugin and a separately hosted calculator application that together remove friction, add auditability, and set a new bar for climate accountability UX.

• Effort & investment: 1,500+ engineering hours @ USD $120/hr (engineering basis ≈ $180,000) plus infrastructure, RPC services, testing, and consulting (total program cost ≈ $250,000–$300,000).
• What’s unique: Not just burning to the dEaD address, but issuing compliance-ready certificates tied to each burn, suitable for enterprises, NGOs, and CSR programs.
• IP valuation: Based on cost-to-reproduce, licensing potential, and climate-tech comparables, the IP is valued at $1.5M–$2.5M with upside as partner channels expand.
• Transparency: Users and auditors can View All Burns on BscScan. (Public “Last 30” lists were intentionally removed for privacy and page cleanliness.)

---

Table of Contents

1. Project Overview
2. System Architecture & Components
3. Separate-Server Carbon Calculator
4. Burn Plugin — Technical Details
5. Security, Privacy & Compliance Posture
6. Chronological Development Log (6 Months)
7. Key Milestones & Breakthroughs
8. Performance, Reliability & Ops
9. Commercialization & Spin-Offs
10. Financial Model & IP Valuation
11. Appendices (Shortcodes, Data, Runbooks)

---

1) Project Overview

The CCC Burn Plugin integrates with WordPress to provide a non-custodial on-chain burn flow for CCC tokens and immediate certificate issuance. The Carbon Calculator is a separately hosted, lightweight web app embedded on CCC pages to estimate a user’s footprint in ~60 seconds, then recommend a CCC amount to burn.

---

2) System Architecture & Components

The solution is intentionally simple to deploy yet rigorous in security and auditability.

Layer	Component	Notes
UI	WordPress Pages (Gutenberg/Classic)	Hosts the plugin shortcodes and the embedded calculator iframe.
Plugin	wp-ccc-burn.php, ccc-burn.js, burn-2.js, wp-ccc-burn.css	Wallet connect, burn initiation, form handling, and AJAX logging. Non-custodial
Data	MySQL (wp_ccc_burns)	Stores wallet, CCC amount, tx hash, name, company, offset category, timestamp.
Chain	BNB Smart Chain (BSC)	Burns to 0x000000000000000000000000000000000000dEaD. Balance checks via balanceOf.
Certificates	certificate.php → HTML/PDF in /wp-content/certificates	Branding-consistent, tamper-resistant presentation of offset details and verification link.
Transparency	View All Burns on BscScan	Public chain records; on-page “Last 30” list intentionally removed for privacy and clarity.

---

3) Separate-Server Carbon Calculator

The calculator is delivered as a standalone HTML application (quiz.html) hosted on a separate server. It is embedded into CCC WordPress pages via an iframe. This split affords:

• Security isolation: Calculator logic and assets are sandboxed from WordPress.
• Performance: Independent caching/CDN and fast first-paint for a snappy UX.
• Reliability: If the calculator experiences load, it does not degrade WordPress admin or plugin flows.

Emission factors are simplified and based on recognized sources (IPCC guidance and UK Government GHG conversion factors). The aim is to produce approximations for lifestyle emissions (tCO₂e) and a recommended burn amount of CCC (e.g., 1,000 CCC ≈ 1 tonne).

Data Flow

1. User completes quiz in the embedded iframe (separate origin).
2. Calculator computes a tCO₂e estimate and displays a suggested CCC burn amount.
3. User returns to the burn form on the WordPress page to execute the burn and receive a certificate.

---

4) Burn Plugin — Technical Details

Shortcodes (Documented & Commented Out)

• <!-- --> — Full burn form (name, company, category, tonnes, Connect Wallet, Burn).
• <!--

  Burn CCC to Offset Your Emissions

  

  Retire carbon credits on the Binance Smart Chain and receive a carbon offset certificate.

  Name: Company (Optional):

  Tonnes to Offset:

  Connect Wallet Burn CCC
  --> — Streamlined one-click burn for common presets.

Important: The “Burn Transactions (Last 30)” plugin block was removed from the page. Auditors and users can rely on the canonical source of truth via BscScan.

Wallet & Network Handling

• Connects via injected providers (MetaMask) and supports mobile deeplink to open the page inside MetaMask when needed.
• Enforces BSC mainnet (chainId = 56) using wallet_switchEthereumChain/wallet_addEthereumChain fallbacks.
• Runs balanceOf checks before attempting a burn to prevent insufficient-funds reverts.

Burn Execution

1. User enters the tonnage or selects a preset; plugin converts to CCC (e.g., 1 tonne → 1,000 CCC).
2. Plugin constructs a standard transfer(to=dEaD, amount=CCC) transaction.
3. Wallet signs and broadcasts; UI shows the pending hash and confirmation status with a BscScan link.
4. On confirmation, the plugin logs the burn via an authenticated AJAX call and triggers certificate generation.

Logging & Certificates

• AJAX endpoint persists: wallet address, CCC amount, tx hash, name, company, offset category, timestamp.
• certificate.php renders a branded certificate and saves it under /wp-content/certificates.
• Success banner returns a direct link: “View/Print Certificate”.

---

5) Security, Privacy & Compliance Posture

• Non-custodial: No server-side key management. All signing happens in the user’s wallet.
• Privacy-by-design: Removed “Last 30” on-page burn list; kept authoritative chain link only.
• Validation: Frontend schema checks for required fields; server-side sanitation in the AJAX handler.
• Resilience: RPC retries, exponential backoff, and explicit error messages for common fail states.
• Auditability: Verifiable tx hash on BscScan; certificate contains verification references.

---

6) Chronological Development Log (Six Months)

Month 1 — Foundations

• Shortcode scaffolding; base forms; ethers.js integration.
• MySQL schema wp_ccc_burns and admin entries created.

Month 2 — Burn Pipeline

• End-to-end burns with confirmation and logging.
• Mobile deeplink pathway for MetaMask app users.
• Introduced BSC chain enforcement and error UX.

Month 3 — Certificate Breakthrough

• Stabilized certificate.php after multiple iterations (UTF-8, CSS print rules, metadata completeness).
• Finalized brand-consistent, print-ready templates.

Month 4 — Calculator Integration (Separate Server)

• Embedded quiz.html via iframe with top-of-page anchoring and responsive layout.
• Mapped answers → tCO₂e → CCC suggestions; tuned labels and helper text.

Month 5 — Security & Privacy

• Deprecated on-page “Burn Transactions (Last 30)” display.
• Hardened AJAX handler (sanitization, nonce checks, informative failures).

Month 6 — Stabilization & Demo

• Stress tested on production pages; measured < 3s certificate latency post-confirm.
• Live demos with real transactions; positive stakeholder feedback.

---

7) Key Milestones & Breakthroughs

• Certificate Engine: Enterprise-grade, brand-consistent, print-ready certificates for each burn.
• Separate-Server Calculator: Security isolation and performance independence from WordPress.
• RPC Resilience: Retries/backoff dropped failed reads significantly; better user messaging.
• Privacy Upgrade: Removed “Last 30” burn list; rely on BscScan for full transparency.

---

8) Performance, Reliability & Operations

• Uptime: 99.9% on production WordPress under normal load.
• Certificate issuance: Typically < 3 seconds after on-chain confirmation.
• Operational playbooks: Plugin updates via standard WP flows; nightly DB snapshots; periodic certificate directory backups.

---

9) Commercialization & Spin-Offs

---

10) Financial Model & IP Valuation

• Cost basis: 1,500+ hours × $120/hr ≈ $180,000 (engineering) + infra/testing ≈ $70k–$100k → program total ≈ $250k–$300k.
• IP valuation: Considering cost-to-reproduce, licensing upside, and climate-tech comps → $1.5M–$2.5M.
• Revenue paths: Licensing (per-site), enterprise support, white-label bundles, and managed hosting.

---

Appendices

A. Documented Shortcodes

<!-- ccc_burn plugin -->
<!--  -->
/* NOTE:
   The "Burn Transactions (Last 30)" section is intentionally omitted from pages
   to protect user privacy and keep investor-facing pages concise.
   Transparency is provided via BscScan:
   https://bscscan.com/token/0x9DfBb97B47854B0Ed19E064DA9B405c4Cd754EC9
*/

B. Data Model (MySQL)

CREATE TABLE wp_ccc_burns (
  id BIGINT AUTO_INCREMENT PRIMARY KEY,
  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  wallet_address VARCHAR(64) NOT NULL,
  ccc_amount BIGINT NOT NULL,
  tx_hash CHAR(66) UNIQUE,
  name VARCHAR(128),
  company VARCHAR(128),
  offset_type VARCHAR(64),
  meta JSON NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

C. Certificate Fields

• Issuer (CCC), Certificate ID, Issue Date/Time
• Name / Company (if provided)
• Wallet (masked for display), Tx Hash (full link)
• Offset Category and Tonnes (mapped to CCC)
• Verification link (BscScan)

D. Runbooks (Abridged)

• Daily: Spot-check recent certificates; verify AJAX error rate near zero; confirm calculator iframe loads.
• Weekly: Update dependencies; back up wp_ccc_burns and /wp-content/certificates; review RPC latency.
• Monthly: Regression pass on certificate layout and printer settings; review calculator copy and factor references.

---

Prepared by the Carbon Credit Coin Development Lab Team — Engineering • Blockchain Architecture • Security • Data • SRE • Finance
Contact: labs@carboncreditcoin.net