This website is read-only
MultichainAPI.com does not request wallet connections, collect recovery phrases, or execute blockchain calls from its on-page examples. Copy controls copy displayed text. The downloadable helper runs only in your own configured environment.
Protect credentials in your application
Keep private API credentials outside public HTML and client-side bundles. Use the provider’s documented access restrictions, separate development and production credentials, and define how to rotate or revoke access. Do not place secrets in screenshots or support messages.
Validate at every boundary
Use HTTPS for remote endpoints, validate inputs and response shapes, and avoid treating one API key as a complete authorization design. Keep permitted methods narrow in small utilities and avoid exposing administrative node interfaces.
Primary reference: OWASP REST security guidance. Check the upstream documentation for current method and integration details.
Do not confuse connection with consent to sign
Explain each wallet interaction, keep the network visible, and allow users to decline. Treat account changes, disconnections, and rejected requests as ordinary states that deserve a usable recovery path.
Report a concern responsibly
Email [email protected] with the public URL and a brief description. Do not include private keys or recovery phrases, and do not access another person’s data to demonstrate an issue.
These notes are a review starting point, not a certification or a guarantee about the security of an application you build. Continue with the wallet checklist and provider evaluation guide.