Digital asset control
Connect instructions, effect checks, admission, signing and operation results in one controlled process.
Platform
One control process, from instruction to outcome
TMGT connects business intent to cryptographic execution and external status. Every transition has defined conditions and an auditable basis.
The solution ecosystem
Five product areas share a common control process. Your systems retain their interfaces, accounting and business logic.
- Client applications and accounting systems
- Five TMGT product areas
- Effect checks · policies · T1 · admission
- MPC / HSM · controlled publication
- External networks and systems
Wallet infrastructure
Embed wallets and controlled operations in your application through APIs and SDKs.
Digital depositary technology
Connect an internal instruction to its network operation, confirmations and reconciliation data.
Transaction controls
Add effect checks, policies and risk assessment before operations are signed in your existing system.
Agentic operations
Allow agents to propose operations within a defined mandate, with independent controls before execution.
Evidence across every stageAn auditable record accompanies every critical stage. It includes decision grounds, rejections and stops, as well as successfully executed operations.
The operation lifecycle
Intent
The client system supplies the operation parameters, initiator and context.
Expected effect
Simulation estimates changes using the available network state.
Policy and risk
Policies and approvals set mandatory conditions. T1 adds a risk assessment and its underlying factors.
Formal admission
A single-use authorisation is bound to the operation, key, configuration and cryptographic step.
MPC signing
Participants execute the threshold protocol within the protected cryptographic environment.
Controlled publication
The signed operation passes a separate control stage before it is sent to an external network.
External result
Confirmations, finality, errors and discrepancies are returned to the client system.
Evidence across every stageAn auditable record accompanies every critical stage. It includes decision grounds, rejections and stops, as well as successfully executed operations.
See where the decision is made
These schematic examples illustrate the control logic. They are not live product interfaces or real transactions.
Permitted operation
- Intent
- Expected effect
- Policy and risk
- Formal admission
- MPC signing
- Controlled publication
- External result
- Intent
- Transfer an allowed asset to an approved recipient.
- Policy
- Policies and required approvals are satisfied.
- T1 assessment
- The T1 assessment is acceptable for the configured rules.
- Formal admission
- Admission is bound to this operation and cryptographic step.
The operation may proceed to MPC, followed by a separate publication stage.
Decision recordCheck results and the grounds for each transition are recorded.
Blocked by policy
- Intent
- Expected effect
- Policy and riskStop
- Formal admission
- MPC signing
- Controlled publication
- External result
- Intent
- The proposed transfer exceeds the configured limit.
- Policy
- The limit is breached.
- T1 assessment
- A favourable T1 assessment cannot override the prohibition.
- Formal admission
- Admission is not granted.
The operation stops before MPC.
Decision recordThe rejection reason and check parameters are recorded.
Outside the agent’s mandate
- Intent
- Expected effect
- Policy and riskStop
- Formal admission
- MPC signing
- Controlled publication
- External result
- Intent
- An agent proposes a transfer outside its permitted scope.
- Policy
- The recipient, amount or validity period is outside the mandate.
- T1 assessment
- Risk assessment cannot grant permissions the agent does not hold.
- Formal admission
- Admission is not granted.
The operation stops before MPC.
Decision recordThe agent identity, mandate conditions and rejection reason are recorded.
Admission is specific to the action
Authorisation is single-use and bound to the operation, key, configuration and cryptographic step. Business approval and the cryptographic threshold are independent. Changes to material conditions must be handled under the agreed control rules.
Explore securityYour systems remain part of the process
Input
Applications and accounting systems supply the intent, participants and context.
Control
Your policies and trust model determine the conditions for execution.
Output
Status and audit records return to your systems for accounting, reconciliation and investigation.
Further reading
T1 risk assessment
Inputs, policy boundaries and answers about risk assessment.
Read guideDeployment and acceptance
Define the configuration, responsibilities and pilot checks.
Read guide