Public GFC Evidence Layer
Transparency Portal
Development / Testnet
This portal shows what is currently publicly traceable around development of the GFC Token / Economic Layer: project status, published test contracts, source code, on-chain values, control structures, future production references and the limits of each type of evidence.
Current role of the portal:
The Transparency Portal is currently a read-only information and evidence layer supporting development of the GFC Token / Economic Layer. It does not execute blockchain transactions, manage treasury assets, or hold governance or control authority.
Core principle:
A claim is not evidence. For every reference, ask three questions:
What is visible? What does it prove? What remains unproven?
A visible blockchain record can prove a technical execution or contract state, but it does not automatically prove security, economic value, legal permissibility or real-world social impact.
Base Sepolia test contracts published
No official mainnet token
No active public mainnet presale
No external audit report yet
System Status
Current Project Status
Status distinction:
Testnet deployments create development evidence. They are not a production product and must not be confused with the final GFC token, a mainnet deployment or an active public presale.
Smart Contract Registry
Official Contract References
The registry below is generated from the published Base Sepolia registry file. Each GFC deployment is linked to its own manifest, explorer references, documented purpose, control structure, limitations, live-read configuration and local Solidity source code whose SHA-256 integrity is checked against the relevant manifest. The external source-code verification status is tracked separately from the documented explorer reference. Contract details are intended to answer four control questions directly: What can this contract do? What can it not do? Which roles or permissions exist? Which upgrade, pause or emergency mechanisms are disclosed?
Current testnet scope:
The registry lists the currently published GFC test deployments on Base Sepolia. Each entry is a technical testnet reference. It is not the production GFC token, has no official mainnet value and is neither a public fundraising address nor evidence of an active mainnet presale.
The interactive contract registry is built from the published Base Sepolia registry file.
Registry Entry
Interactive contract registry
The underlying registry file remains directly available. The interactive presentation loads after JavaScript initializes successfully.
The contract registry could not be loaded. No registry data is being presented as verified until the published source is available again.
Explorer fallbacks open the Base Sepolia network explorers only. They do not replace the official GFC registry or establish which address belongs to GFC.
Verification Overview
What is currently verifiable?
Each status is classified according to whether it is publicly verifiable, only planned or not yet available. Testnet, mainnet, audit and real-world impact are deliberately treated separately.
Verification method:
What is visible? What does it prove? What remains unproven? The current portal can substantiate development evidence mainly at the testnet and contract-reference level; it does not convert that evidence into production, audit or impact claims.
Current Evidence Scope
Only what can be substantiated is verifiable
Currently publicly verifiable
- published Base Sepolia contract addresses and chain ID;
- associated explorer and source-code references;
- deployment and verification data from the official registry;
- selected public on-chain values through read-only RPC queries;
- documented testnet relationships, dependencies, permissions and limitations.
Quick Verification
How to verify an official reference
- Obtain the contract address exclusively from the contract registry on this page.
- Verify the network and chain ID: Base Sepolia uses 84532, Base Mainnet uses 8453.
- Open the associated BaseScan or Blockscout link from the same registry entry.
- Compare the address, network, contract name, source code and stated verification status.
- Open the contract details and review documented permissions, capabilities, limitations and any upgrade, pause or emergency mechanisms that are disclosed for that deployment.
- Check the audit status separately. Verified source code does not mean that the contract has been externally audited.
- Finish by asking: What is visible? What does it prove? What remains unproven?
System Context
Dependencies and Contract Relationships
A verified contract address alone does not explain the complete system. This section shows external assets, GFC-controlled test contracts, payment paths, distribution relationships and the immutable test treasury reference documented in the registry.
External Dependencies
External dependencies are documented in the published registry; the interactive presentation requires JavaScript.
Published System Relationships
System relationships are documented in the published registry; the interactive presentation requires JavaScript.
The registry notice is shown from the published registry after JavaScript initializes successfully.
Governance & Control
Who can actually control what?
Transparency is not only about visible code. What matters is which address or role can change parameters, move assets, administer contracts or trigger emergency functions. For test contracts, this information is disclosed per contract in the registry and contract details.
Classification rule:
The portal should not use terms such as “decentralized,” “immutable” or “community-controlled” as blanket attributes. Concrete permissions, limitations and published production mechanisms are what matter. A multisig can distribute approvals, but it does not by itself prove that the signers are organizationally independent. The same disclosure standard must ultimately apply to GFC itself.
Financial Transparency
Wallets, Reserves and Fund Flows
Status: not yet applicable — no production treasury published. Production wallets, treasury addresses and reserve addresses have not yet been published. Therefore, there is currently no production treasury or charity transaction history that this portal could present as GFC mainnet evidence.
Base Sepolia movements are development and testing evidence only. They must not be presented as production treasury activity, charity distributions or mainnet financial execution.
Once production references exist, every official financial address should be published with its purpose, network, control model, current status and traceable movements.
Tokenomics
Current Allocation Structure
Status: current production model, not yet enforced on mainnet. The planned model uses a total supply of 1,000,000,000 GFC, no inflation or discretionary post-deployment mint authority, a 0% buy fee and a 1% sell fee. These rules become technically authoritative only when the final Base Mainnet contract is published, source-verified and its actual permission structure has been reviewed. Allocation is also a governance decision: percentages alone do not show who controls the assigned wallets, whether restrictions are technically enforceable or whether those rules can later be changed.
Impact Vault
250,000,000 GFC • 50-year lock planned • intended for charity and impact purposes under the final vault rules. Lock duration alone does not prove purpose restriction or immutability; the technical mechanism, permissions and change rights are the relevant evidence.
Guardian Growth Fund
200,000,000 GFC • Guardian rewards, community growth, ambassadors, governance and campaigns.
Presale Allocation
150,000,000 GFC • planned presale allocation, currently not active.
Treasury Reserve
150,000,000 GFC • development, audits, infrastructure, security, partnerships and expansion.
Liquidity Reserve
150,000,000 GFC • future liquidity measures and market access.
Ecosystem Growth Fund
50,000,000 GFC • ecosystem development, integrations and project development.
Core Team Allocation
50,000,000 GFC • linear vesting over 19 years from a formally defined start date. Vesting duration alone does not prove that the schedule cannot be changed; the final contract and control rights must establish that.
Impact Verification
A visible payment is only the beginning
The long-term transparency model should disclose financial movement, governance evidence and actual real-world impact separately. A blockchain transaction alone does not prove that the stated social purpose was achieved.
Current status:
GFC currently publishes no production charity distributions or verified real-world impact datasets. This section describes the intended evidence standard, not impact that has already occurred. A visible transaction is the beginning of an evidence chain — not its end.
Verification Limits
What Blockchain Can Prove
- that a specific transaction occurred on a specific network;
- which addresses were involved and what on-chain value was transferred;
- which bytecode is deployed at a contract address;
- certain publicly readable contract states and technical rules.
Verification rule:
Visible ≠ verified ≠ fully proven. Ask: What is visible? What does it prove? What remains unproven?
A visible transaction is the beginning of an evidence chain — not its end.
Future Mainnet Scope
Planned Production Components
Status: intended / planned. The following components remain planned and are not represented by the current Base Sepolia test registry unless a separate deployment is published later. A testnet reference does not automatically carry over as production evidence: each mainnet component must be re-published with its own address, network, code, permissions, control model, verification status and applicable evidence limits.
Audit Status
No external audit report yet
No independent audit report has yet been published for any of the Base Sepolia test contracts currently listed. Source-code verification through the explorer identified in the relevant registry entry documents the association between published source code and the deployed contract code; it is not a security assurance and does not replace an independent audit.
An audit should only be treated as complete once the report, the audited code version and the audit scope can be publicly matched and verified. Source-code verification does not replace an independent security audit.
Presale Status
No active public mainnet presale
GFC has published a Base Sepolia test presale contract for technical validation. It accepts Base Sepolia ETH, Circle-listed test USDC for Base Sepolia and GFC Mock DAI and distributes tGFC immediately after a successful test payment. The listed test USDC was not deployed or controlled by GFC and has no real financial value.
This test deployment is neither an official mainnet presale nor a public fundraising address or investment product. The configured test window is read directly from the published test contract in the contract details. The test contract contains neither a soft cap nor a refund mechanism.
Current planning state: The current plan provides for €0.05 per GFC, eight weeks, a €250,000 soft cap, up to 150,000,000 GFC from the presale allocation and a refund if the soft cap is not reached; no separate monetary hard cap is currently planned. These parameters are not live, are not currently enforced by any mainnet sale contract, and there is no publicly confirmed start date.
Binding production parameters and the associated production references will only be presented on the separate presale page and here as live or technically enforced after legal, technical, security and operational clearance has been completed and the final mainnet references have been published.
Only addresses and links published on the official GFC website and in this Transparency Portal should be treated as authoritative. Testnet addresses must never be treated as mainnet purchase or deposit addresses.
Risk Notice
Transparency reduces risk — it does not eliminate it
Blockchain, token and presale structures involve significant technical, regulatory, operational and market-related risks.
- There are no profit promises and no guarantee of value appreciation.
- There is no guarantee of tradability, liquidity or demand.
- Verified contracts are not automatically externally audited.
- Even an audit cannot completely rule out errors or security risks.
- Legal, technical or operational changes may affect implementation.
- This website does not provide individualized investment, financial, legal, tax or purchase advice.
Documentation
Context for the Public Evidence
The Transparency Portal shows status and evidence. The related GFC pages provide architecture, fundamentals, frequently asked questions and the separate presale status. Material changes to the portal are dated so that status changes, new contracts and new evidence can be distinguished from earlier versions.
Versioning
Changelog
- August 26, 2026: The role of the Transparency Portal was aligned with the current GFC product state: through Q1 2027 the primary focus is the GFC Token / Economic Layer; the portal remains a read-only information and evidence layer without execution or control authority. Base remains the operational blockchain focus; Base Sepolia remains the public test/PoC reference, while no mainnet token or public presale is live. Verification freshness, evidence boundaries, presale/token planning status, no-JavaScript initial states and mobile evidence navigation were clarified.
- August 23, 2026: Portal markup prepared for explicit recovery states: separate retry interfaces added for the contract reference, live on-chain values and source code, together with a central non-visual status output for accessible interaction feedback. The English portal version was structurally and substantively synchronized to the same state, and the security configuration was prepared for an equivalent restrictive CSP.
- August 22, 2026: Deployment hardening prepared: the registry bootstrap watchdog was moved from inline code into a standalone, immediately started fallback file so a stalled deferred script cannot delay failure protection. Canonical routes for the Transparency Portal were standardized and the current page state prepared for a restrictive Content Security Policy.
- August 21, 2026: Evidence access prioritized: official contract references moved directly behind project status and a direct evidence navigation added. Status and update information were semantically separated, registry error presentation consolidated, contract-modal loading states clarified, and technical mobile typography and touch targets improved. The Transparency Portal intentionally remains dark-only.
- August 18, 2026: Footer and modals statically integrated into the portal page; runtime partial loader removed. Explorer links restricted to the officially configured BaseScan/Blockscout origins, registry and manifest size checks hardened against the bytes actually loaded, Solidity source-code integrity and loading limits tightened, and modal and no-JavaScript accessibility improved.
- August 16, 2026: Audit wording aligned with the site-wide audit standard. Registry error handling strengthened with a bounded loading state, explicit unavailable states, retry support and Base Sepolia explorer fallbacks. The page update date and registry update date intentionally remain separate.
- August 13, 2026: Portal verification language sharpened: current evidence layers, testnet/mainnet separation, governance disclosure principles, financial-transparency status, verification questions, criteria for audit completion and evidence-chain limits clarified.
- August 8, 2026: Transparency Portal comprehensively restructured around evidence: verification overview, current evidence scope, governance and control status, financial transparency, impact verification and explicit limits of blockchain evidence added.
- August 2, 2026: Central Base Sepolia registry added for the GFC Test Token, GFC Mock DAI and GFC Test Presale, including deployment classifications, explorer references, dependencies and system relationships.
- August 2, 2026: Dynamic architecture prepared for contract details, including manifest data, direct JSON-RPC queries, permissions, limitations and complete verified Solidity source code.
- August 2, 2026: Presale communication updated to clearly distinguish the published Base Sepolia test presale from a future public mainnet presale.
- July 28, 2026: GFC Test Token on Base Sepolia (0x7262Cca91938ede6bB6560F81104Aa410848e7f3) added as the first public development reference.
- July 12, 2026: Status communication standardized for presale, mainnet contracts, refunds and audit.
- July 5, 2026: Transparency page aligned with the current GFC master plan.
Material changes are dated and are intended to become additionally traceable through official repositories or documentation channels.
Contact
Report a Discrepancy
Have you found an incorrect address, a possible scam attempt or a conflicting contract reference?
Please include the explorer link, network, chain ID, transaction hash, URL or specific source. Screenshots alone are not sufficient evidence.