Getting help

Product questions (what something means, how to do something): start with the product’s documentation from the product catalog. If the documentation does not answer you, that is a documentation bug; open an issue on the matching repository saying what you were trying to learn.

Availability questions (is something down, why is a flow gated): How to read our status explains the states, and each product’s documentation links its live status sources so you can check yourself.

Developer questions (APIs, schemas, protocol rules): the developer overview maps where each contract lives. If a contract and its documentation disagree, open an issue; the contract wins until the fix lands.

Lost or stuck assets: read the recovery page of the product you used before anything else. Chain-level outcomes cannot be reversed by support, and nobody who claims otherwise is telling the truth.

Security problems: use GitHub private vulnerability reporting on the affected repository, never a public issue. Full policy: SECURITY.md.

Documentation feedback: every page has an edit link; small fixes as pull requests are welcome. For anything larger, the content request template asks the three questions we need answered.