#LEDGER LIVE SYNCHRONIZATION ERROR SERIES#

If M圜oin has specific operation fields (like additionalField we added for example), you will be able to display them later. You will find the detailed and commented fields here. They all share the same model, with an extra field that can store any additional data you may need to display. In short, transactions history in Ledger Live is a list of Operation, that are confirmed, unconfirmed or pending (not yet fetched from explorer). We could also have allowed the concept of “SELF” operation. But in fact, that’s semantic, we, Ledger, have put. Another example that is possible in most blockchains is a “self” transaction yields two operations (sending out, sending in). A typical example is contract or token transfers (one transaction to move a token generate a token operation and a fee operation in the ethereum account). But in some blockchains (like Ethereum) one transaction that concerns the account associated addresses can result in 0 to N operations. Most of the time, a transaction yield of one operation. It’s always in the context of an account, in other words, an operation does not exist on its own. The same abstraction applies as for Account on top of blockchain: an Operation is a view of a transaction that happened in the blockchain that concerns the contextual account. An account does not have transactions, it has operations. Note the wording “Operation” is used instead of “Transaction”. This type is not required at light sync step and will soon be removed from this section It’s generally an additional field like m圜oinResources. for staking), or anything that may be displayed or used in your implementation. If needed by the blockchain, an account can also contain coin-specific resources related to a single account, like its “nonce” or additional balances (e.g. We will focus only on the Account type as we won’t cover the Token integration in this document.Īll main accounts share a common ground, that you will find defined and commented here. They are aggregated as a single AccountLike type, used across Ledger Live implementations. ChildAccount which is a variant of TokenAccount but more in context of a CryptoCurrency (typically used for Tezos).TokenAccount which is a nested level account, inside an Account and that is associated to a TokenCurrency.Account which is a top level account associated to a CryptoCurrency - the “main” account.

In Live Common, there are currently 3 types of accounts: Moving from the blockchain to the concept of account is not necessarily trivial (in blockchains like Bitcoin, the concept of account does not exist – you don’t create or destroy, this concept is a view, a lense, that we abstract for the user).

#LEDGER LIVE SYNCHRONIZATION ERROR SERIES#

While blockchain tracks the series of transactions, assets motions that happen between addresses, an account essentializes that from the point of view of a user that owns a set of addresses and wants to view the associated funds they detain and be able to perform transactions with it.Įssentially what the user wants to see at the end is his balance, a historic graph, and a series of past operations that were performed.

More technically, an account is a view of the blockchain in the context of a specific user. Ledger Live model is essentially an array of Account because many accounts can be created, even within a same crypto currency. AccountĪn account represents a wallet where a user detains crypto assets for a given crypto currency. Generic types can be found in ledgerjs/packages/types-live, with some documentation.

Ledger live synchronization error