16

There are various kind of sub-tangles (or clusters). Here are two examples: Offline Tangles: Together with a certain number of nodes you effectively go offline (or "off the grid") and issue transactions only amongst yourselves. This makes the exchange of information more efficient as you can solely focus on the people you want to interact with, and on top ...


4

Due to the dag structure of the Tangle a complete ordering of transactions is impossible. Therefore, the protocol don't relies on transaction time ordering to determine which of two conflicting transactions is the legitimate one. By design, the protocol will decide that the transaction with most weight will be the accepted one.(here is a brief explanation of ...


4

With the Tangle you can only really verify that a particular transaction was issued by a specific party but the data inside the payload must not really be true at all. This is of course true but it is not a problem that Iota is attempting to solve. If forgery was happening on a large scale then the company doing it would risk a lot and would be easily ...


4

If you want to start a subtangle, you always have to reference existing transactions that don't conflict with the "main" tangle. Otherwise your transactions will never get confirmed. More on that here: What happens to Sub Tangle if it attaches to an invalid transaction? This is our main tangle: When you start a subtangle you are going offline. You no ...


4

When your intention is to later merge the subtangle with the main tangle without doing the POW for all transactions again, your subtangle will already have to start at an existing transaction (preferrably a confirmed one since you do not know whether an unconfirmed transaction might become inconsistent before you are getting online again), or more precisely ...


4

Today, with the Coordinator According my understanding, a subtangle is build by a subset of fullnodes disconnected from the main tangle. (The main tangle being the one were the Coo broadcast the milestones.) A subtangle cannot receive milestones and therefore, validation of transactions is driven only by probability. Participants in a subtangle must trust ...


3

This is my speculation on how it is done. Due to the fact that the algorithm is randomized and I am not involved in the process, it may as well be a different algorithm. I don't know who is doing the stitching. The network is quite anonmyous, and the only thing I can say that it is somebody who is running a spammer and has modified the tip selection ...


3

Which tips are referenced as parent by the first (new) transactions? An answer for this question can be found here: Clarify inner workings of the snapshot The genesis transaction (with hash: 999⋯9) is directly approved by the Coordinator. The first transaction after the genesis simply approves the genesis transaction twice. In other words, it has the same ...


3

Successfull merging of a subtangle and the main tangle: How to start a new offline subtangle? The case, that you have to reattach your whole subtangle occurs when you start your subtangle at a transaction that is not very likely to be confirmed and conficting with the main tangle. In this example, the two transactions marked with Xs are conflicting and the ...


3

When you have a large offline subtangle (which somebody already did the POW for); it is already attached to some (very old) transaction, which has hopefully confirmed until now (when starting an offline subtangle I'd start at a "confirmed" transaction anyway - at least as long as there is the coordinator, you can just use a milestone). When you bring the ...


2

All that we know is that Tf and Tg come after Ta,Tb, Tc ...and the transactions (directly or indirectly) referenced by Ta, Tb, Tc. That is all the Tangle "knows" about the temporal order of these transactions. It makes no statement about the temporal order of the independent (neither directly or indirectly referencing each other) transactions Tf and Tg. ...


2

IMO, a distinction should be made between different partitioning scenario. Accidental/occasional partitioning It's the situation where a portion of the network is temporary disconnected for a relatively short period of time. Participant can still submit transactions to the disconnected tangle and when the disconnected tangle is back online, transactions ...


2

Entire subtangle will be treated as invalid and won't be confirmed. That means you have to reattach all of the transactions.


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