Independent guide, not an official HedgerX site. Official site: www.hedgerx.com/en

HEX smart contract audit: where things stand

HedgerX's company deck lists the HEX smart contract audit for August to September 2026. No published audit report is available yet, and the whitepaper treats audits as something HedgerX will establish.

Checked 2026-10-17. Based on the HedgerX company deck (roadmap slide) and the HEX whitepaper (security section).

What HedgerX said

  • The company deck’s roadmap lists “Complete the HEX smart contract audit” under August to September 2026.
  • The whitepaper says HedgerX will establish a security framework that includes smart-contract audits, multi-signature controls and treasury security.

What we found

The documents we reviewed contain no audit report, no auditor name and no link to either. The planned period has passed. The whitepaper publishes the contract address and the supply split, but no burn addresses, reserve addresses or audit.

What a useful audit report shows

  • The auditor’s name and track record.
  • The exact contract address and the version or commit that was reviewed.
  • The date, the scope and the findings, with their severity and whether each was fixed.
  • Whether the owner can mint tokens, pause transfers or change fees.

An audit lowers the risk of code bugs. It says nothing about the team’s behaviour, the token’s price or how the project is run.

How we will update this

When HedgerX publishes a report, or says the audit is delayed, we will check it against the points above and add the date here. The roadmap tracks the other dated items.

Frequently asked questions

Has the HEX contract been audited?

HedgerX lists an audit as planned for August to September 2026. No published report is available yet. If one exists, it should name the auditor, the contract address and the date.

How do I check the HEX contract myself?

Compare the address from the whitepaper, 0x37BbE10B6C403dE2e84FC36D134Da858d28d9901, with its page on BscScan. Look at the creation date, holders, liquidity and whether the source code is verified.