Updated Nov 1, 2026
Contact support
Where to go
| Route | Use it for |
|---|---|
| These docs | How markets, funding, resolution, payouts and rewards work |
| Discord, linked in the site footer | Product questions and help from the community |
| legal@ultramint.xyz | Data requests and questions about the policies |
| engineering@fermah.xyz | Security issues |
What to include
The more you send, the faster we can help:
- Your wallet address. It identifies your account and is public anyway.
- The transaction hash, if money moved or didn't. Look it up on a Base block explorer.
- The market link, if your question is about a market.
- The exact error message, and roughly when you saw it.
- Your IP address, if you were refused access. See Who can use Ultramint.
What we'll never ask for
Anyone who asks for these isn't us:
- Your private key or a sign-in code. Never.
- An approval on something we sent you. You only approve things in the app, on a screen you opened.
- A transfer to an address we give you. We never ask you to move funds, "verify" a wallet or "unlock" a payout.
- A fee to release a payout. Payouts come from the market's contract. There's nothing to pay.
We only email you at the address on your account.
What support can't do
- Reverse a transaction. Anything confirmed on-chain is permanent, including a withdrawal to the wrong address or a deposit on the wrong network.
- Get you out of a position early. There's no selling.
- Change a market's result. A public market's result changes only through a challenge. A Members only market's result is up to its creator.
- Sign for you or move your money. Only you can sign for your account.
- Make exceptions to the eligibility rules, or to taking your money out before closing your account.
Reporting a problem
- A market that breaks the rules, or one you think is being resolved in bad faith: use Report on the market page, or email legal@ultramint.xyz and say so in the subject. See What you can't mint.
- A security issue: email engineering@fermah.xyz. Please don't post it publicly before we've fixed it.
Did this not answer it? Contact support.