EcoChain proposes a BOT Chain-native contribution protocol. Under this model, a finalized BOT transfer can be linked to treasury allocation, evidence, independent attestation, and portable impact identity.
One wallet. One BOT receipt. One traceable path to impact.EcoChain proposes a BOT Chain-native contribution protocol for environmental action. Under the proposed model, participants support a registered project with BOT, the network's native asset, while the protocol links the public transfer to project allocation, outcome evidence, and independent attestation without collecting wallet keys or publishing personal information.
A BOT transaction hash can prove that value moved from a wallet to an address, but it does not explain which project version received it, how the project treasury used it, which methodology measured the outcome, or who authorized the final impact claim. EcoChain connects those events into one reviewable provenance record.
The EcoChain specification treats each native BOT contribution as a stateful impact record, not a decorative transaction hash. Under the model, the donation principal would move from a participant wallet to a registered project treasury on BOT Chain; the BOT-denominated network Gas fee remains separate from the amount supporting the project.
Bind the project, registered treasury, purpose, BOT amount, and Chain ID 677 before wallet authorization.
INTENT_ID + PROJECT_IDSend the donation principal in BOT from the participant wallet to the project's registered treasury address.
TX_HASH + BLOCK_NUMBERRecord the BOT donation separately from Gas, then map the received value to a budget line, reporting period, and milestone.
ALLOCATION_STATEBind methodology, metric scope, geographic reference, and supporting files to the finalized BOT receipt.
EVIDENCE_DIGESTLet an authorized verifier attest, dispute, supersede, or revoke the evidence-linked impact claim.
IMPACT_ATTESTATIONintent → wallet_submitted → chain_finalized → allocated → evidence_pending → attested / disputed / revokedsender · project treasury · BOT value · Gas fee · tx hash · block · finality · evidenceDigest · attestation stateprivate keys never collected · optional donor PII · raw reports · photos · sensor data · treasury accountingBOT Chain can establish the sender, recipient, value, Gas paid, transaction hash, block reference, and finality. Correct treasury use and environmental outcomes still depend on accountable operators, project reconciliation, credible methodology, supporting evidence, and independent review.
The protocol architecture is specified around BOT Chain Mainnet: a participant would fund a registered project treasury with native BOT, the chain would provide transaction receipt and finality, and EcoChain would connect that receipt to allocation, evidence, attestation, and governance controls.
Project discovery · BOT amount selection · Chain ID 677 check · receipt explorer
Donation principal · Gas estimate · tx hash · finality · treasury allocation
Versioned reports · methodology · evidence digests · verifier signatures · disputes
Chain 677 · project state · BOT receipt · allocation state · attestation status
Role policy · protocol upgrades · partner applications · portable impact identity
{
"recordType": "EcoChainBOTContribution",
"network": {
"chainId": "uint256; required=677",
"nativeAsset": "string; required=BOT"
},
"contribution": {
"receiptId": "bytes32; required",
"projectId": "bytes32; required",
"sender": "address; required",
"treasury": "address; registered",
"amountBot": "uint256; donation principal"
},
"networkFee": {
"amountBot": "uint256; separate from principal"
},
"settlement": {
"transactionHash": "bytes32; BOT Chain receipt",
"blockNumber": "uint256",
"finality": "enum<pending|finalized|reverted>"
},
"evidence": {
"digest": "bytes32",
"attestation": "enum<pending|attested|disputed|revoked>"
}
}EcoProjectRegistryProject review authorityProject version digest + eligibility stateTARGET: ON-CHAINBOTContributionRegistryAuthorized recorderBOT value + tx hash + finality stateTARGET: ON-CHAINAllocationStateRegistryProject treasury controllerTreasury, budget, milestone, and BOT allocationTARGET: ON-CHAINImpactAttestationRegistryIndependent verifierBOT receipt + evidence digest + signed claim stateTARGET: ON-CHAINEvidence StoreProject operatorReports, media, methodology, and operational dataPRIVATE / OFF-CHAINA trustworthy impact record keeps two BOT amounts explicit: the donation principal transferred to the project treasury and the network Gas fee paid separately to execute the transaction. EcoChain then follows the finalized receipt through allocation, utilization, evidence, and attestation.
intent.createdParticipantProject, registered treasury, purpose, and intended BOT amount are selected.
bot.transfer.submittedParticipant walletRecords submission of BOT donation value on Chain ID 677; Gas authorization remains separate.
bot.transfer.finalizedBOT ChainRecords the transaction hash, block reference, transferred BOT, and finality state.
allocation.declaredTreasury controllerReceived BOT is mapped to a budget line and project milestone.
evidence.submittedProject operatorUtilization details and supporting evidence are bound to the receipt.
impact.attestedIndependent verifierA specific outcome claim is signed, disputed, or revoked.
Preserve Chain ID 677, sender, registered treasury, donation value, Gas paid separately, tx hash, block reference, timestamp, and finality.
Use stable receipt and project identifiers to reconcile each wallet-to-treasury BOT transfer with project accounting and audit exports.
Treat refunds as new BOT transactions and preserve disputes, superseded reports, and revoked attestations as explicit states—not deleted history.
Participants retain wallet custody until signing; project treasuries and protocol records use scoped roles, multisig policy, and separation of duties.
BOT transaction boundary. EcoChain is non-custodial: wallet private keys remain with participants, and every BOT transfer requires explicit wallet authorization. EcoChain does not promise returns or represent a BOT contribution as ownership of an environmental asset. Production deployment requires registered treasury addresses, contract security review, governance controls, monitoring, and applicable legal review.
EcoChain's long-term identity layer is a consent-based participation passport spanning projects, communities, and institutions. It records verifiable environmental action without turning personal identity or reputation into a financial asset.
Participants choose what to present. Wallet private keys, raw identity documents, and donor PII never enter the public ledger or EcoChain systems.
A signed receipt establishes that a specific contribution or verified activity entered the protocol lifecycle.
Eco Points become non-transferable participation history that can travel across projects without becoming a tradeable asset.
Credentials, roles, and attestations carry issuer scope, expiry, supersession, dispute, and revocation state.
verified participation · signed receipts · project history · contribution continuity · earned reputationWHAT IT DOES NOT CLAIMhuman uniqueness · legal identity · creditworthiness · investment eligibility · biometric verificationEcoChain is the first application surface. The larger ambition is a BOT Chain-native network connecting contributors, project treasuries, operators, verifiers, researchers, public institutions, and third-party applications through shared trust primitives.
IndividualsLocal communitiesInstitutionsProject operatorsBOT holdersParticipant walletsProject treasuriesCommunity matching vaultsIndependent verifiersResearch institutionsData providersDispute panelsEcoChainPartner portalsEnterprise reportingCivic programsOpen schemas and APIs connect BOT wallets, registered project treasuries, evidence systems, and reporting tools.
BOT contributors, treasury controllers, operators, scientists, verifiers, and communities remain separately accountable.
More reviewed projects and credible evidence make the network more useful without converting impact into speculation.
The roadmap sequences protocol capabilities from wallet-to-treasury settlement through evidence, identity, interoperability, and governance. Each stage must earn the right to expand through treasury validation, contract security review, BOT reconciliation controls, and credible evidence standards.
P0SPECIFICATIONBOT contribution intents, Chain ID 677 validation, registered treasury records, receipt schemas, and impact account interfaces.
P1SECURITY GATEWallet authorization, evidence ingestion, treasury reconciliation, exception handling, and independent security review.
P2NETWORK GATEBOT Chain registry anchors, verifier framework, audit APIs, treasury allocation reporting, and dispute procedures.
P3IDENTITY GATEEco Passport, cross-project reputation, selective disclosure, partner SDKs, and interoperable credentials.
P4GOVERNANCE GATEMulti-stakeholder governance and a global coordination layer for evidence-based environmental finance.
The ambition is not to create another donation website. It is to establish a shared accountability layer through which BOT contributions, project treasury decisions, environmental evidence, and verified outcomes can become traceable, interoperable, and governable.
At global scale, EcoChain could help transform billions of disconnected actions into a coordinated system for planetary stewardship—giving every participant a clearer way to contribute, verify, learn, and build lasting environmental reputation.
Protocol scope. BOT is BOT Chain's native contribution and Gas asset. EcoChain does not custody wallet keys, assert human uniqueness, or grant ownership, investment, or governance rights through a contribution receipt. Identity and governance modules require treasury validation, scientific standards, independent security review, and applicable legal review before deployment.