Trust

Read-only. Verifiable.
Recorded.

TxID is designed to operate safely alongside your protocol.

It cannot move funds, it explains where its answers come from, and every interaction creates a reviewable record.

Every answer, checked

  • Read-only accessno keys · no signing · no custody
  • Answer verifiedsource: live on-chain read
  • Case recordedreviewable trail · every answer

Zero

keys, seed phrases or signatures ever requested

Sourced

every answer traceable to a live read or your docs

Recorded

a reviewable case record behind every conversation

9 chains

EVM networks and Move-native Aptos

Every answer has three layers

Read-only access

No keys. No signing. No custody.

TxID only reads public blockchain data.

It never requires:

  • Private keys
  • Seed phrases
  • Signing permissions
  • Contract permissions

No assets are held. No transactions are executed.

Verified answers

Evidence behind every claim.

When TxID provides an answer, it can show the underlying source:

  • Live on-chain reads
  • Transaction data
  • Contract state
  • Protocol documentation

Users and teams can verify what happened instead of trusting a black box.

Recorded by default

Every interaction becomes a case record.

TxID stores the conversation, investigation, evidence, and outcome.

Teams can review:

  • What was asked
  • What data was checked
  • What answer was provided
  • How the case was resolved

The detail a reviewer asks for

Answers to the questions in the security questionnaire

Read-only by design

Built with clear boundaries

TxID:

  • Reads the same public data available through blockchain explorers
  • Requires no contract deployment or permissions
  • Cannot access funds or sign transactions

The safest integration is the one that never has access.

Verification tools

Ask it to prove the answer

TxID can support verification workflows including:

  • Live on-chain evidence behind responses
  • Address screening where supported
  • Contract verification
  • Protocol audit references

Not an adviser

It will not tell your users what to do with their money

Telling a user to buy, sell, hold or close is regulated advice, and a support agent giving it becomes your problem, not ours. So the assistant declines it, in one sentence, and then gives the facts that let the user decide.

Always refused, on every plan:

  • Buy, sell, hold, close, or position sizing
  • Price predictions, targets, or forecasts
  • Whether something is a good investment
  • Tax treatment, and legal or jurisdictional eligibility
  • The same question asked as an opinion, or hypothetically

There is no setting that turns this off. Conversations where a user asked for advice are labelled in your dashboard, so you can show how often it came up and that it was declined every time.

Actions (optional)

User-authorised actions, when enabled

Actions are disabled by default.

When a protocol enables them, TxID prepares transactions that users review and sign through their own wallet.

Users remain in control:

  • Explicit user request required
  • User reviews exact transaction details
  • User signs in their own wallet

Read-only mode remains the default.

Data & privacy

What TxID stores

TxID stores:

  • Conversations
  • Wallet addresses included in conversations
  • Project configuration
  • Usage metrics

TxID never stores:

  • Private keys
  • Seed phrases
  • Signing permissions

There is no mechanism for the assistant to request them.

Conversation data is kept for as long as the project is active, and is deleted with the project. There is no automatic deletion schedule today, and deletion on request is recorded rather than silent. Set out in our privacy policy.

What we have not built yet

A SOC 2 audit and configurable data retention are on the roadmap. Neither is in place today.

Dashboard roles are enforced: Admin, Developer, Support and Auditor, checked in every server action rather than hidden in the interface. Auditor reads and exports the full record and can change nothing, which is the account to hand an external auditor. Single sign-on is not built.

Nothing else on this page implies otherwise. If a control is not listed above as available today, assume we do not have it and ask us.

Send this page to your reviewer

For a data processing agreement or anything not covered here, we're one email away.

See also our privacy policy and terms.