Support and contact.
Email admin@hoodlock.tech for anything that needs an answer from the team. Most questions about a lock, a fee or a failed transaction are answered faster by the pages linked below, so start there if you can.
How to reach us#
| Channel | Best for |
|---|---|
| Email: admin@hoodlock.tech | Support requests, partnerships, press and integrations. Anything that needs a written answer. |
| X: @HoodLockRH | Announcements, quick questions, and reporting an airdrop or page. |
| Discord: discord.gg/ku2mW7BShh | Community questions and help from other users. |
What to include#
A lock is a public record, so we can usually answer in one reply if you send the details that identify it. Include as many of these as apply:
- The wallet address you used. The public address only.
- The transaction hash, if a transaction failed or did something unexpected.
- The lock, burn or vesting id, or the link to its proof page.
- The token address involved.
- What you expected and what happened instead, with the exact error text or a screenshot.
We will never ask for your seed phrase or private key, and we will never DM you first. Anyone who does is not HoodLock. Our email address is admin@hoodlock.tech and nothing else.
What support cannot do#
HoodLock is non-custodial. We hold no key that overrides a contract, so nobody on the team can unlock tokens early, reverse a burn, cancel a vesting schedule or recover tokens sent directly to a contract address. The security model explains why that limit is the guarantee itself.
Answers that are already written#
- A transaction failed or the app will not connect: troubleshooting.
- What something costs: fees.
- What happens at the unlock date: when a lock expires.
- Everything else people ask: the FAQ.
Security reports#
If you believe you have found a vulnerability in the contracts or the site, email admin@hoodlock.tech or message @HoodLockRH privately before disclosing it publicly. A private report gives us time to protect the people using the contracts.