Get Help

Ethereum

Supported Assets

  • ethereum/native/eth: Ether (ETH)
  • ethereum/contract/<address>/erc-20: ERC-20 compliant tokens (replacing <address> with the contract address)

Protocol Concepts

Ethereum is accounts-oriented, meaning funds are always attached to addresses. Accounts can either be EOAs (externally-owned-accounts, i.e. wallets) or contracts with custom code. Transactions are initiated by EOAs and cause Ether to be moved and/or messages (contract calls) to be passed across an arbitrary number of contracts.

ERC-20 tokens are contracts that implement the ERC-20 standard.

References:

  • https://medium.com/@kctheservant/transactions-in-ethereum-e85a73068f74

Ubiquity Mapping

Ether (ETH)

Ubiquity tracks Ether transactions executed directly by externally-owned-accounts. Those are represented by the transfer operation with name native.

The transaction fee is sent in an operation called fee of type transfer to virtual address transaction_fees.

The currency type for Ether is native.

ERC-20

Ubiquity tracks any ERC-20 transfer operations (including contract-internal) and links them to the initiating transaction. Transfers are represented by the transfer operation called log-<number>-transfer where <number> is replaced with the log index of the ERC-20 transfer within the block.

The currency type for ERC-20 tokens is smart_token.

Features Currently Not Supported

  • Protocol-native transaction JSON format (“getTransactionReceipt”).
  • Querying and displaying contract internal transactions (moving Ether between contracts).
  • Transaction traces.
  • ERC-20 “Approval” operations (token creations).
  • Other smart contract standards.