T3
Trusted Transparent Transactions
Trusted Transparent Transactions (T3)
Overview
The T3 service is responsible for storing and querying transparent data for select MobileCoin transactions. This capability makes transparency opt-in for MobileCoin wallets which wish to maintain regulatory compliance. T3 supports all current and future native tokens of the MobileCoin network. Currently, the native tokens are MobileCoin (MOB) and our stable coin Electronic USD (eUSD).
Wallets with T3 Capabilities
Currently, there are two wallets which support reporting to T3:
Moby - our first party self-custodial mobile wallet
Full Service (and Desktop Wallet) - our first party desktop/server-based wallet solution
Moby reports only on and off ramp transactions with centralized third parties (e.g. Paybis and Moonpay). Full Service, if enabled with T3, will report all transactions in and out of that wallet's accounts. Only one party to the transaction needs to report to T3 in order for the transaction to be considered transparent. Thus, T3 is a one-party opt-in transparency system.
Trusted Access Control
Note that transparent transactions are still fully encrypted on the MobileCoin blockchain. T3 is built as a layer above the blockchain to be more flexible and to provide control over who can read and write T3 data. This benefits customers as it prevents customer wallets and balance data from becoming a target for bad actors.
Access to T3 is granted with API keys, separately provisioned for reading and writing to T3. Moby, our first party self-custody mobile wallet, comes with built-in keys for writing data to T3. For Full Service and Desktop Wallet, an API key must be obtained and supplied to Full Service. The API key identifies the institution to which the Full Service wallet belongs.
Typical Partner Integrations
Deploy a Full Service node for their MobileCoin hot wallets.
Request a T3 API write key and enable T3's integration with their Full Service node to report 100% of their in- and out- going transactions.
Utilize our blockchain analysis partner (Elliptic) to perform wallet and transactional monitoring for compliance obligations.
If spot checking of transactions is required we can additionally provision a T3 read key for the institution and provide details on how to make use of T3's JSON HTTPS endpoints.
Enabling Reporting in Full Service
To enable T3 within Full Service, you will need to obtain an API KEY (see below).
Once you have the API KEY, you will need to provide two runtime variables, either as command line args or environment variables.
As environment variables, set the following when running full service:
T3_URI
T3_API_KEY
As command line args, set the following when running full service:
--t3-uri
--t3-api-key
Requesting an API Key
Please contact security@mobilecoin.com for receiving a T3 API key or more detailed documentation and provide:
A purpose for API use including if read and/or write access is needed
Anticipated API call volume
A contact name
A contact email
Number of keys needed if more than 1
We expect the majority of institutional partners to follow the following general integration path:
Partners are responsible for their own KYC and AML regulatory compliance. T3 does not contain KYC or any other PII data.
LOOKUP - Find transparent transaction records by txo public key hex (transaction hash) or wallet address
LIST - List out all transparent transaction records within a time region (e.g. last 30 days)
CREATE - Creating new transparent transaction records
API Caveats
Wallet Address vs Wallet Hash
Due to limitations on the size of memo fields we chose to include only a hash of the wallet address in the Authenticated Sender Memo. Since all clients are reliant on this memo field we chose to also use wallet address hash values in T3 instead of full wallet addresses. This also permits the recipient of a transaction to be a T3 reporter (as they are not guaranteed to know the sender's full wallet address).
Last updated