Skip to content
Doefin
Browse documentationCurrent: Smart contracts and technical review

Reference

Smart contracts and technical review

Which actions are signatures and which are contract transactions, and the deployment evidence to request before funding.

Reviewed

Signatures and contract transactions

The app uses a Smart Contract Wallet for account funds. Order submission and cancellation use signed requests; transfers, split/merge and redemption involve contract transactions. A signature prompt and a transaction confirmation therefore do not mean the same thing.

Shares are the position tokens; each represents one outcome for a particular market and collateral. Market resolution and redemption determine which tokens can be redeemed for collateral. Review the deployed contracts behind the exact market you intend to use.

What to verify

  1. Obtain the network and deployed contract addresses for the current environment.
  2. Inspect verified contract code and identify the implementation and any upgrade authority.
  3. Ask for audit reports, including the commit or version reviewed, the scope, unresolved findings and evidence of fixes.
  4. Check account permissions, token approvals, dependencies involved in resolution and the process for handling interruptions.

Evidence must match the deployment

A source repository, a verified explorer page or an audit of another version does not prove that the current deployment behaves the same way. This guide does not certify contract security or list verified deployments. Ask the team for current evidence before relying on an address or audit claim.