RAVENContact
Raven is built and operated by Raven Attest. Pick the route that matches your purpose — each address is read for that purpose only. Whatever you send: describe the decision or the system, not your secrets. We never need API keys, passwords, private keys, seed phrases, or wallet secrets to answer you.
Security — report a vulnerability privately
security@ravenattest.com
For vulnerability disclosure, security flaws, trust/verification weaknesses, credential exposure, and signature or trust-root issues. Reports are reviewed privately. Do not open public issues for unpublished vulnerabilities.
Never include API keys, passwords, private keys, seed phrases, wallet secrets, or other credentials in the initial message — we will never ask for them. A description, the affected component, and a reproduction shape are enough to start.
Full policy and the machine-readable reporting route (RFC 9116): security page · /.well-known/security.txt.
Developer / API access
access@ravenattest.com
For Raven API access, your first integration, receipt API onboarding, and developer access questions. The structured request is the faster path: request access — tell us what you're building and the call volume you expect, and we reply with a signed receipt for your token.
Partnerships
partners@ravenattest.com
For integration partnerships, Solana infrastructure collaboration, design-partner discussions, and ecosystem or business partnerships.
General
raven@ravenattest.com
Anything that doesn't fit the routes above. If your message is about security, API access, or a partnership, the purpose-specific address gets it to the right place sooner.