Knowledge Base
Integration Guidelines
Thank you for your interest in integrating Tether into your platform. Tether Tokens exist on multiple blockchains and should be treated equally and interchangeably, i.e. 1 Tether on Blockchain X = 1 Tether on Blockchain Y.
Where possible, we ask that an integrator provide support for as many protocols below as their platform currently supports/operates on and that it is made explicitly clear (both publicly and within their platform) which protocols they support.
Currently Supported Asset Protocols:
- Omni Protocol Token via Bitcoin Blockchain
- ERC20 Token via Ethereum Blockchain (and OMG Network)
- TRC20 Token via Tron Blockchain
- EOSIO.TOKEN via EOS Blockchain
- Liquid Asset via Liquid Blockchain
- Algorand Asset via Algorand Blockchain
- SLP Token via Bitcoin Cash Blockchain
Omni Protocol via Bitcoin Blockchain
For Tether’s Omni Protocol token on the Bitcoin blockchain:
Tether’s assets created and issued on the Omni protocol are identified by the Omni Protocol Property ID: USD₮ #31 and EUR₮ #41
Integration for Tether (and any Omni Protocol token) is achieved through the Omni Core client. Omni Core is a Bitcoin core clone that supports Bitcoin as well as all the Omni protocol currencies, so if you are building an exchange and integrating Bitcoin/Bitcoin core, the integration path/requirements for Omni Core would be almost identical.
Being built on top of Bitcoin core, Omni Core inherits all the RPC capabilities of Bitcoin core and adds a few additional Omni Protocol Specific RPC calls of its own.
Please see the Omni Core integration guide provided by the Omni team for the technical details needed to incorporate the client into your platform: https://github.com/OmniLayer/omnicore/wiki/Platform-Integration-of-Omni-Core
Remember Tether’s assets created and issued on the Omni protocol are identified by the Omni Protocol Property ID: USD₮ #31 and EUR₮ #41
Any other TETHER Property ID # is FAKE.
ERC20 Token via Ethereum Blockchain (And OMG Network)
For Tether’s ERC20 tokens on the Ethereum blockchain:
Our USD₮ contract address is https://etherscan.io/token/0xdac17f958d2ee523a2206206994597c13d831ec7
Our EUR₮ contract address is https://etherscan.io/token/0xabdf147870235fcfc34153828c769a70b3fae01f
Our CNH₮ contract address is https://etherscan.io/token/0x6e109e9dd7fa1a58bc3eff667e8e41fc3cc07aef
Our XAU₮ contract address is https://etherscan.io/token/0x4922a015c4407F87432B179bb209e125432E4a2A
The integration path is the same as any ERC20 compatible token. With the following exception:
NOTE: Tether’s USD₮ ERC20 Contract is based on a slightly older standard that does not return a boolean value in the Transfer function. Developers and Integrators deploying their own custom contracts should take care and use the ‘SafeERC20‘ library which is designed to handle both the old and new standard.
OMG Network: If you are interested in adding support for the OMG Network to your platform please contact business@omg.network.
TRC20 Token via Tron Blockchain
For Tether’s TRC20 token on the Tron blockchain:
Our USD₮ contract address is https://tronscan.org/#/contract/TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
The integration path is the same as any TRC20 compatible token.
EOSIO.TOKEN via EOS Blockchain
For Tether’s EOSIO.TOKEN on the EOS blockchain:
Our USD₮ contract address is https://bloks.io/account/tethertether
Liquid Asset via Liquid Blockchain
For Tether’s Liquid Asset on the Liquid blockchain:
Our USD₮ contract address is https://blockstream.info/liquid/address/H4UWQS836njW4QJ6WfkGAPjaYtK2twLnZE
Algorand Asset via Algorand Blockchain
For Tether’s Algorand Asset on the Algorand Blockchain:
Our USD₮ contract address is https://goalseeker.purestake.io/algorand/mainnet/account/XIU7HGGAJ3QOTATPDSIIHPFVKMICXKHMOR2FJKHTVLII4FAOA3CYZQDLG4
NOTE: Remember, Users wishing to receive/hold Tether Assets on Algorand must explicitly ‘Opt-in’ . For more information see the Algorand Tutorials
SLP Token via BitcoinCash Blockchain
For Tether’s SLP Token on the BitcoinCash blockchain:
Our USD₮ Token ID is https://simpleledger.info/token/9fc89d6b7d5be2eac0b3787c5b8236bca5de641b5bafafc8f450727b63615c11
