cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Application / CT-GTC-001

Gitcoin (GTC)

Ethereum · Token contract · Documentation reviewed

Documentary contract0xde30da39c46104798bb5aa3fe8b9e0e1f348163f

The verdict

Unrated · 0% Evidence coverage

Operational strength remains unproven; unrated with 0% scoring coverage.

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.

Inspect the evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

Promise

This dossier examines the documented purpose and mechanisms of Gitcoin (GTC) on the Ethereum network. The goal is to explain the stated aims of the token as recorded in community-maintained registries, without verifying live network operation or investment outcomes.

Established facts

The pinned Trust Wallet Ethereum integration record identifies Gitcoin with the symbol GTC and contract address 0xde30da39c46104798bb5aa3fe8b9e0e1f348163f. This entry specifies 18 decimal places for amount representation. Decimal places concern how numbers are displayed and do not measure supply or value. The registry labels the entry ERC20 and active. ERC-20 refers to a standard interface for fungible tokens in smart contracts. It defines functions for reading total supply and balances, executing transfers, and managing allowances. An allowance is the amount a named spender may use from an account; repeated approval overwrites that amount. The specification requires handling false transfer results and describes Transfer and Approval events. Name, symbol, and decimal metadata are optional in the standard. The general ERC-20 specification is separate from this specific token implementation. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply, or security. No token transaction was performed in this review. The community-maintained description states: GTC is the governance token we’re using to decentralize Gitcoin into a DAO ecosystem, collectively working to fund the next generation of public goods. Every project, economic, partnership, performance, supply, date, and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements. The active status is a metadata label, with no live-network validation. The Trust Wallet Assets README describes a community-maintained registry used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The scripts and documentation use the MIT license. The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation.

Unknowns

Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. No deployed bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness, or investment return has been established. The scoring coverage is 0% and the status is unrated. No public admission of these gaps exists beyond this editorial scope.

Consequences

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The registry serves as a catalog of claimed attributes rather than proof of operational reality. Users relying solely on this documentation face uncertainty regarding who controls the contract, whether the code matches the description, and if the token functions as intended.

Verdict

Operational strength remains unproven. The dossier provides a documentary explanation of stated aims but confirms no independent verification. The asset is unrated with 0% scoring coverage. This is not an independent operational verification. Missing evidence does not make the project fraudulent or unsafe, but it prevents any assessment of reliability or performance.

What would change it

Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required. These must be followed by calibration and editorial review to move from an unrated status to a scored assessment. Until such evidence is provided, the conclusion remains based solely on community-submitted registry claims.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Observable usage, token necessity and dependencies.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Trust Wallet: captured Ethereum record for Gitcoin

The pinned Trust Wallet Ethereum integration record names Gitcoin with symbol GTC, contract 0xde30da39c46104798bb5aa3fe8b9e0e1f348163f and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ERC20 and active. Its community-maintained description states: "GTC is the governance token we’re using to decentralize Gitcoin into a DAO (GitcoinDAO) ecosystem, collectively working to fund the next generation of public goods." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. This dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. Treat the generic application family as a documentary contract subject; its economic niche and scoring criteria remain unclassified and unknown.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: f28183f86c52fbfec8ab7adf229d6c5170a03fce9b9a6b09bdc46a0e0e836ff7

Trust Wallet Assets: blockchains/ethereum/info/info.json (bbe582d25a22)

The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 5bf228bbcd577440dc00e5b783b680b0cfdf14504dc9d8b89340ba88d9e95502

Trust Wallet Assets: README.md (bbe582d25a22)

The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 51fc8f690972c850271ca0a6086516eae5ed411e94982fcae6534a4d08fccd73

Ethereum ERC-20: pinned token interface specification

The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 50d0bdc535ed8987ac5c124cb5f9c39606806c97e909aae66ef4b747dd9c93dd

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation