Hot answers tagged

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

Not all nodes see the same state of the tangle at the same time. So it can be expected that two nodes pick the same tip (which might actually even not be a tip anymore) at the same time and issue their transactions building on this node concurrently. It is not a problem if some transactions are directly confirmed by two others. However, on average a new ...


3

You want it confirmed because transactions which do not become part of consensus (heavy part of tangle) are pruned/discarded by full nodes (because they aren't relevant and are taking up memory) and fall into oblivion. Using the Tangle for data transactions is to have an immutable and trustless way of making a statement about the state of some data. For ...


1

I would question your first sentence. If you are not interested in getting your transaction confirmed, why do you want the transaction on the tangle anyway? One of the use cases of putting data on the tangle is to later prove that the transaction has existed before (and give an approximate time it was inserted). For example to have "unforgeable" car ...


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