Skip to main content
The managed Token Management API covers the standards and templates that ship with Qustody. When that’s not enough, you can use Path B: bring your own Solidity, compile it yourself, and submit deployment and contract-call transactions directly through Qustody (or through Quantum Chain RPC).

​
When to use which path

You can mix both paths in the same project: deploy a custom contract via Path B, then use Path A for downstream operations once the contract address is registered as a Qustody token (when supported).

​
What Path B keeps

​
What Path B requires from you

  • A Solidity toolchain (e.g. solc or Foundry).
  • ABI encoding for every contract call.
  • Manual mapping between contract events and your reconciliation pipeline.
  • Verification of the deployed contract bytecode against your source.

​
QRC-compatible Solidity

Public docs refer to your custom contracts as QRC-compatible contracts. If your Solidity inherits from libraries whose internal symbol names use ERC*, that is a build-time detail — keep your public-facing template ID, contract name, and operational documentation in the QRC vocabulary.

​
Where to next