Technical claims
These should resolve to an on-chain record, protocol document, or named data provider.
This policy explains the evidence hierarchy, automated assistance, correction process, market-data handling, and limits applied across GOAT.CX.

These should resolve to an on-chain record, protocol document, or named data provider.
These should resolve to a dated archive, direct project material, or attributable reporting.
These are labeled as analysis. They are not presented as ledger facts.
Current GOAT observations name the provider and freshness state. Price uses the deepest-liquidity pool returned by the live feed; aggregates may span multiple discovered pools. Historical charts identify their provider and period. A displayed observation is not an executable quote. Review the live-data methodology
Automation may assist with data retrieval, drafting, internal consistency tests, structured-data generation, and original visual production. It does not create first-hand experience, professional credentials, or a basis for unsourced certainty. Material factual claims remain attached to named evidence, and original AI-assisted illustrations are labeled.
An automated import cannot publish itself into search. Each scheduled dispatch must carry explicit approval from a named reviewer, a review date, at least one inspectable external source, and a specific explanation of what the page adds beyond existing coverage. The publication gate checks developed sections, internal context, heading structure, unnatural repetition, and overlap with earlier dispatches. A page that fails stays outside the index and sitemap until it is reviewed.
GOAT.CX does not pad a page to an arbitrary word count. A short answer can be complete, while a complex claim may need a longer source trail. A date changes only after a substantive public update; a new publication date is never used to make unchanged material appear fresh.
Substantive updates change the visible modified date and sitemap signal. Corrections should preserve the page URL when the subject remains the same. Source challenges, rights concerns, and factual corrections can be sent to [email protected].
GOAT.CX does not sell coverage, paid placement, sponsored articles, press-release republication, or ranking positions in any list. No entity pays to appear in the evidence ledger, the research library, or the market pages, and no external party reviews a draft before publication.
The publication does not issue, market, or hold a position it promotes to readers. External links support verification and never carry affiliate or referral tracking. If a commercial relationship ever changes that rule, it must be disclosed on the page carrying it rather than hidden in a site-wide notice.
The dispatch pipeline is a production tool controlled by the GOAT.CX Editorial Desk, not an open publishing platform. Outside businesses cannot place unrelated pages on this domain to inherit its search signals. Every indexable page remains within the stated editorial scope and under the same sourcing, review, correction, and removal standards.
Outbound links serve verification. A source is chosen for evidentiary weight, not for authority by reputation: an on-chain record outranks a market directory, a directory outranks a news summary, and a news summary outranks a social post. When the strongest available source is weak, the page says so instead of borrowing credibility from a better-known name that does not actually support the claim.
GOAT.CX does not control external destinations, and their content can change after a page is published. Market data providers are named wherever their figures appear, because their methodologies differ and a value quoted without a provider and a timestamp is not verifiable. The evidence ledger records which source carries each claim.
On-chain observations show what a node reported at a moment in time. They cannot prove a person's identity, a custody agreement, or an asset's safety. Holder figures list addresses, not beneficial owners. One address may represent an exchange, pool, program, or many customers.
Market values can be delayed or wrong when a provider fails. Historical ranges only cover the period a provider returns. If the public record cannot settle deployer identity or key custody, the answer stays unproven until better evidence appears. See the desk's stated limits.
GOAT.CX does not present attention, market capitalization, or past highs as a valuation floor. GOAT can lose most or all of its value. Readers are expected to verify the mint, understand the transaction, and make their own decisions. Use the GOAT risk guide
The organizational GOAT.CX Editorial Desk applies this policy. The broader mission and domain-preservation position are available on About GOAT.CX