What we can and cannot do
Most of this category asks you to trust a team. The useful version of this page is the list of things that hold even if you do not.
We cannot move your funds
There is no administrative function in the contract that sweeps or redirects an escrow. Every write returns an unsigned transaction and your wallet signs it. We do not hold end user keys, and holding them is not a setting we could switch on.
We cannot trap your funds
Every state has a path to settlement that does not need us, the resolver, or the other party to cooperate. If we went offline permanently, open escrows would still resolve, because the rules are on chain and anyone can build the transaction.
We cannot change the terms after you fund
Fees and caps are copied into your escrow when it is created and frozen when it is funded. Nothing we change afterwards reaches it.
We publish what breaks
An operational commitment. Incidents, their cause and what changed afterwards go on the status page rather than into a support queue.
Audit
Scope covers the validator, the minting policies, the configuration mechanism and the off chain transaction builder. The builder is in scope deliberately, because published audits of comparable systems keep finding issues in exactly that layer, and leaving it out would make the audit look more complete than it was.
Auditors work against the state transition table and the threat model at a specific commit, both of which are written before the contract rather than reconstructed after it.
Reporting a vulnerability
Report privately to security@usehokan.com rather than opening an issue. We acknowledge within two business days and aim to give an assessment within ten.
We will not take legal action against good faith research that stays in scope, avoids privacy violations and service degradation, and gives us reasonable time before disclosure.
We hold ourselves to the same standard. Where our own research finds a vulnerability in another project, we notify them privately and give them time to respond before we publish anything, including internally circulated documents that describe the issue in reproducible detail.
Questions people actually ask
What happens if Hokan shuts down?
Open escrows resolve without us. The rules live in the contract, the transactions can be built by anyone, and the exit paths do not require our signature. You would lose the API, the webhooks and the support, not the money.
Can you freeze my escrow?
No. We can stop new escrows being created on a version, which exists so we can halt a compromised version without trapping anyone, and that flag has no effect on escrows that already exist.
Who resolves disputes?
Whoever you nominate, which defaults to you rather than to us. Whoever it is can only split the money between the two parties already named in the escrow, and loses the ability to act at all once the window expires.
Is there a token?
No. Nothing to buy, stake or farm. Our revenue is a fee on settled work, which means we only earn when the protocol is actually used.
Do I need to understand Cardano?
To integrate, no. You call an API and hand the returned transaction to a wallet. To evaluate whether the guarantees are real, some, and the contract source and the specification are public so you can check rather than take our word for it.
Can I build my own transactions?
Yes, and the system assumes you will. The contract does not care who assembled a transaction, only whether it satisfies the rules. Anything that only works because we built it would not be a protocol.
What assets are supported?
Ada, USDM and USDCx by default. Other Cardano native assets follow through configuration.
Are you a money transmitter?
No. We do not hold customer funds at any point and are not licensed to hold them. Funds move from the depositor’s wallet into the contract and from the contract to the receiver, and no Hokan wallet is anywhere in that path.