← Back to portfolio greentrace.twilightvoyager777.com
2024 National Service Outsourcing — Award Winner

GreenTraceChain — turning every gram of CO₂
into auditable, on-chain truth.

A four-role blockchain platform for carbon trading: enterprises submit emissions data, auditors verify, third-party regulators oversee, and a platform admin governs the chain. Each event is committed to ChainMaker — every transaction traceable, immutable, public.

ChainMaker · Vue · Go · MySQL 4 role-based portals Mock-chain backend included

Demo flow — at a glance

01
Enterprise submits
Carbon emissions data + supporting docs
02
Auditor verifies
Cross-checks docs, approves on-chain
03
Regulator oversees
Reads chain, flags anomalies
04
Admin governs
Manages roles, contracts, system state

Pick a role to enter the demo

Each portal opens in a new tab. Click any credential value to copy it to your clipboard.

Enterprise User

用户端 · Type 0

Submit carbon-emission filings, browse the on-chain marketplace, trade carbon credits/coins, and track your transactions across blocks.

UsernameGreenForestTech
Passworddemo123
Enter Enterprise Portal

Data Auditor

数据审核员 · Type 1

Review pending emission filings, validate supporting documents, approve or reject submissions — every decision is committed to the chain.

UsernameDAPAdmin2026
Passwordadmin
Enter Auditor Portal

Third-Party Regulator

第三方监管 · Type 2

Read-only oversight: query historical transactions, audit cross-firm patterns, flag suspicious chains, generate compliance reports.

UsernameTPRP_admin2
Password12345
Enter Regulator Portal

Platform Administrator

平台管理员

Govern the platform: create/revoke roles, monitor smart-contract state, manage block-producer keys, view aggregate analytics across all firms.

UsernameAPadmin_3
Passwordadmin
Enter Admin Portal
Note for reviewers — this demo runs against a mock ChainMaker backend, so transactions commit instantly and ledger state is shared across all four portals in real time. Try the canonical flow: Enterprise submits an emission → Auditor approves → Regulator sees it on-chain → Admin sees the aggregated stats. Source on GitHub ↗.
Copied to clipboard