Security & wallet safety

Voiddeeds | 2026-10-19.2 | https://voiddeeds.xyz/security

Current security boundaries, safe testing and wallet requests.

Testing boundaries

Use local forks or an isolated environment to investigate defects. Do not test third-party apps without authorization, disrupt public services, exploit real users or disclose an unpatched issue publicly.

Match observations to the affected release, chain and contract or endpoint. Distinguish behavior of the website, common protocol and independent applications. Redact credentials, personal information and unneeded RPC query strings from logs and screenshots.

Prefer a local chain, fork or generated test accounts. Limit any authorized checks to the minimum needed to demonstrate impact. Do not take funds, persist access, run denial-of-service traffic, alter another person's public profile or use a vulnerability to force a payout. A publicly callable endpoint is not blanket authorization for intrusive testing.

Limits of security evidence

Source publication, a transaction receipt or a resolved issue is not a security certification. Local tests establish only the behavior exercised against the tested code and environment.

Publication of these documents grants no authorization to attack a deployment and no immunity from applicable law. Independent applications have their own code, dependencies and asset-handling risks.

Wallet requests and incident response

The website does not ask for a separate terms signature. A profile or activation request is a message for that specific action; a transaction has its own wallet confirmation. Review the network, account, contract and requested action. Never disclose a seed phrase or private key.

If you suspect a malicious request, cancel it and preserve the public transaction or message details. Review your wallet's documented recovery procedures and the affected application's permissions. The website operator cannot reverse blockchain execution or reset your wallet key. Never disclose recovery material.