Hot answers tagged

6

A bundle can also have only 1 transaction (zero value tx), 3 transactions (if there is no remainder, therefore no change address) or more transactions (if there is a remainder and/or there are multiple output addresses). The transactions in a bundle are always linked via trunk transaction hash (so trunk transaction hash of the first transaction in a bundle ...


6

Let me complement the whitepaper based answer with a bit more explicit technical arguments. Confirming just one transaction would lead just to a linked list of transactions - in other words, a blockchain. Confirming more than two transactions would (1) increase the work required to select valid tips and (2) increase the probability than an invalid tip is ...


5

In the whitepaper it's written The edge set of the tangle is obtained in the following way: when a new transaction arrives, it must approve two (1) previous transactions. 1: This is the simplest approach. One may also study similar systems where transactions must approve k other transactions for a general k ≥ 2, or have an entirely ...


4

In IOTA, every new (unconfirmed) transaction is known as a tip. These tips should each reference two previous transactions. Choosing which tips to extend is decided by a Random Walk Monte Carlo algorithm which uses random tip selection to ensure that only good transaction branches grow. How consensus is reached if random numbers are being used is explained ...


4

The 2 parents of a transactions are called trunk transaction and branch transaction. You get them like this: (It's python but the names and arguments in other libraries are very similar) getTips returns a list of transaction hashes tips = api.get_tips()['hashes'] Call getTrytes to fetch a transaction from its hash. (tips[0] for the first transaction in ...


3

First of all, the property of a transaction being a tip is volatile and can change before the walk even finishes. So even if the function was guaranteed to find a tip, by the time it returned it could already be a non-tip (as somebody else approved it). Also keep in mind that the property of a transaction being a tip is not the same in the whole network, a ...


3

The tip count is the number of tips currently "in memory" (i.e not in permanent storage/database). Therefore it's 0 when IRI restart. A new entry is added to the set of tips "in memory" when a new transaction is received and there is no approvers for this transaction in the local database. There is no process/code to scan the database to find tips at ...


3

GREAT question! This was actually JUST discussion in the Iota Foundations most recently published research paper! The idea is this: confirm more transaction then you are creating to reduce the number of tips ( tips are unconfirmed transactions ). By making the required confirmations, 1 then the IOTA's ledger would not be called a tangle, it would be called ...


2

A transaction is confirmed once it is transitively approved from a milestone transaction. (At the moment, milestone transactions are chosen by the coordinator, but in the future the MCMC algorithm will be used to choose them on every node). Therefore, if your transaction is merely approved by another transaction, you have won nothing. To get your ...


2

Tips in the context of iota (if they are not meaning small payments, as in tipbot) refer to transactions that have not been confirmed by other transactions. When you make a new transaction, you (or rather the node you are connected to) will have to choose two tip transactions that your transactions should approve. Instead of just randomly selecting two tips ...


1

It seems like my question has been made obsolete by changes to the current wallet. The new Promote function does actually send a second transaction that attaches to the first and also to the latest milestone. This does apparently improve confirmation chances.


Only top voted, non community-wiki answers of a minimum length are eligible