txshield
Request Institutional Briefing

Institutional digital-asset infrastructure

Transaction assurance for institutional digital assets.

Verify digital-asset transactions before they reach signing.

TXShield provides an independent control layer between transaction creation and institutional custody or signing infrastructure. Evaluate proposed transactions against organisational controls and current network conditions, then receive a decision before execution.

Request Institutional Briefing View Architecture

Your private keys remain with your signing infrastructure.

THE PRE-SIGNING CONTROL POINT
YOUR WORKFLOWTransaction / InstructionTreasury · Trading · Settlement · Applications
TXShieldTransaction Assurance
  • APPROVE
  • HOLD
  • REJECT
Approved transactions proceed
YOUR EXISTING INFRASTRUCTURECustody / MPC / HSMSigning and execution stay in your control

Held or rejected transactions do not advance to signing.

For banks, custodians, exchanges and market infrastructureDeepest coverage on Solana Explore the trust boundary

INDEPENDENT ASSURANCEA control point before signing

EXISTING INFRASTRUCTUREComplements custody, MPC and HSMs

OPERATIONAL ACCOUNTABILITYDecisions with audit evidence

01 / Architecture

A clear place in
your transaction workflow.

An independent assurance layer between the systems that create transactions and the infrastructure that signs them. Your institution retains custody, authorisation and execution.

  1. TRANSACTION CREATION

    Your applications

    Treasury, trading, settlement and tokenisation

  2. INDEPENDENT CONTROL

    TXShield

    Transaction Assurance Layer

  3. TRANSACTION DECISION

    APPROVEHOLDREJECT

    Only approved transactions proceed

  4. SIGNING & EXECUTION

    Your signing stack

    Existing custody, MPC or HSM infrastructure

  5. SETTLEMENT NETWORK

    Blockchain / DLT

    Your supported digital-asset network

Conceptual integration. TXShield evaluates the transaction; your existing systems enforce the decision and control signing and submission.

Independent control before signing

No custody of your private keys

Decision evidence where supported

02 / Institutional use cases

Built around digital-asset
operations.

Apply a common assurance control across your transaction workflows. Scope each integration to the assets, networks and controls available today.

01

Digital-asset custody

Add an independent assurance check before transaction instructions reach MPC, HSM or other signing infrastructure.

Custodians & banks
02

Treasury operations

Apply organisational controls before digital-asset transfers are authorised, with transactions held for review when policy requires it.

Treasury & operational risk
03

Tokenised assets

Introduce transaction controls around issuance, transfer and settlement workflows on supported networks.

Tokenisation & asset management
04

Trading & execution

Assess proposed transactions for technical and execution risk before signing, including costs and exposure to adverse execution.

Trading desks & exchanges
05

Digital-asset platforms

Introduce a control point within existing withdrawal, treasury and operational transaction workflows.

Exchanges & infrastructure providers
06

Institutional DeFi

Apply transaction controls when interacting with supported on-chain applications, including asset and execution-risk checks.

On-chain operations

03 / Assurance capabilities

Four dimensions of transaction control.

Understand whether a transaction should proceed, require review or be rejected. Capability depth varies by network and deployment.

INTEGRITY

Transaction Integrity

Assess whether the proposed transaction’s expected effects are consistent with the instruction. Surface unexpected behaviour before signing.

  • Proposed transaction assessment
  • Unexpected effects and unsafe assets
POLICY

Policy Enforcement

Apply organisational transaction controls to determine whether a transaction can proceed, needs review or should be rejected.

  • Configurable transaction controls
  • Approve, hold or reject decisions
EXECUTION

Execution Assurance

Evaluate relevant network conditions, likely transaction success and costs. Surface technical risks and adverse execution exposure, including MEV.

  • Execution feasibility and fee guidance
  • Slippage and front-running exposure
EVIDENCE

Audit & Decision Evidence

Keep a record of the outcome and the context in which the decision was made. Signed, append-only records are available on the institutional tier.

  • Decision and policy context
  • CSV, JSON and PDF exports

TXShield focuses on technical transaction assurance. Dedicated KYT, AML and sanctions workflows remain with your compliance infrastructure. ChainEvidence is a separate product.

04 / Security & trust

Your keys.
Your custody.
A separate assurance layer.

TXShield operates before signing. It does not hold your private keys, sign your transactions or replace your custodian. Your institution controls whether and how a transaction is authorised and submitted.

Read our security posture
01

Private keys stay in your signing stack

Transaction assessment does not require access to your wallet, MPC or HSM private keys.

02

Authenticated, encrypted communication

Hosted API access uses scoped, rotatable API keys and TLS-encrypted communication.

03

Scoped access and decision evidence

API keys, institutional policies and audit records are scoped to the owning account. Signed audit records are available on the institutional tier.

04

Architecture and security review

Request a security questionnaire, deployment discussion or sub-processor information for your evaluation.

05 / Deployment

Fit the control to
your infrastructure.

Hosted service or a licensed installation in your environment. Agree the network scope, controls and evidence requirements during evaluation.

MANAGED SERVICE

Hosted

TXShield operates the service. Your existing applications integrate through an authenticated API, with scoped credentials for each submitting system.

Discuss hosted integration
YOUR ENVIRONMENT

Self-hosted

Run TXShield within your own infrastructure under a licence agreement, alongside your custody or signing systems. Installation scope and terms are agreed individually.

Discuss deployment requirements

06 / Network coverage

Deepest on Solana.
Coverage is network-specific.

Solana is the deepest current implementation. Other networks offer transaction analysis and risk screening, with scope agreed per evaluation.

Review your network requirements
Current capability depth by network
NetworkAvailable scope
Solana DEEPEST COVERAGEPre-signing transaction assessment, risk screening, institutional policy controls and signed decision records.
EVM networksRisk screening and basic simulation. Availability is restricted; confirm access and scope during evaluation.
Tron · Bitcoin · HyperliquidTransaction analysis.

Confirm network and feature availability for your deployment before integration.

07 / Developers & integration

One control point.
Your existing signing flow.

Send a proposed transaction to the TXShield API or service. Use the returned decision in your authorisation workflow, then pass approved transactions to your existing signing infrastructure.

Request Developer Access Documentation on request
INTEGRATION CONTRACT
Input
Proposed transaction / instruction
Service
TXShield transaction assurance
Output
Decision and supporting context
Next step
Your existing signing flow

API reference, TypeScript and Python SDK resources are shared with customers and evaluation partners on request.

Institutional briefing

Start with your
transaction workflow.

Review where TXShield fits, which controls your team needs and what an institutional pilot would cover.

Request Institutional Briefing contact@txshield.dev