As of 19 Nov 2026, Hinkal has 1 audit report on Trustblock, by Quantstamp, dated 28 Aug 2026. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Newest first
| Report | Security firm | Date | Scope | Critical findings | Source |
|---|---|---|---|---|---|
| Hinkal Protocol - 2 | Security firm: Quantstamp | Date: | Scope: —Not recorded; see the report | None open | certificate.quantstamp.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 1 |
| Low | 0 | 1 | 7 |
Marked Informational by the firms. Not counted as findings.
`EmporiumUpgradeable.runAction()` executes the caller-supplied `stack.ops` as arbitrary calls from the Emporium contract. However, its balance checks only protect the caller-supplied `circomData.erc20TokenAddresses`. An attacker can submit a Min0 proof with no token rows and set `signerAddress` to `address(0)`, which requires no signature in `verifyWallet()`. The attacker can then use `stack.ops` to transfer residual ERC20 tokens or native ETH from Emporium. An empty token array prevents the resulting balance decrease from being checked. This allows anyone to steal assets accidentally transferred, donated, or stranded in Emporium. The attacker may also spend third-party assets through allowances previously granted by Emporium.
Open the report`0` as a hash could be problematic and short-cut Merkle tree paths.
Open the reportIn the circom template `ConditionalOverflowPreventer` the signal `enabled` is not constrained to be 0 or 1, despite the intention being that it represents a boolean true or false value. Since this value is later multiplied against a real value, it may change that value in problematic ways. The severity of this issue is lower as within the current architecture the template is only used within `OverflowPreventer.circom` where the value of `enabled` is always hardcoded to 1. It would be safer for future updates to ensure the input is constrained within the template itself rather than assuming it has already been validated outside of the template.
Open the reportPrivileged roles can replace various security-critical helper contracts without delay, potentially introducing unintended changes that apply for already in-flight transactions. 1. The `HINKAL_HELPER_MANAGER` role can replace `hinkalHelper` at will. That contract both assembles the public-input vector fed to the verifier and enforces the `calldataHash` integrity check that binds the proof to the spend data. 2. The `DEFAULT_ADMIN_ROLE` can call the `registerExternalAction()` function to replace external action addresses. 3. The `owner` can register any address as the Groth16 verifier for a proof shape using the `registerVerifiers()` function.
Open the reportImprove input validation in the following locations: 1. Add a reverting 0-address check in `setHinkalHelper()`. 2. In `insertNullifiers()`, require that any slot flagged `onChainCreation` carries only zero-valued `inputNullifiers` instead of just skipping nullifier recording for `onChainCreation` slots. 3. Require `input.length == inputAmount` in the verifier wrapper.
Open the reportThe reports name a repository or files. Open a report to see its scope.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="hinkal-1"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us