Tag Info

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 ...

I guess you are right for the current state of mainnet. However concepts like sharding, swarmnodes, horizontal scaling and hardware support in the form of JINN (and/or Q?????) will eventually lead to hopefully a highly scalable solution. All these features together will enable some form of collective intelligence where full-nodes are cooperating (without ...

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 ...

Sharding is the process of dividing up data. For example, if you had a database containing information about all of the people alive today it could be quite large (depending on what information you store about each person). Sharding lets you divide the dataset up across machines based on some criteria. For example, you could set up X shards and choose which ...

You are asking two questions that are somewhat contradictory: "[...] can the nodes get overburdened and cause network congestion, if there are not enough full nodes?" "[...] that the maximum tps is determined by the maximum processing power of a full node in the Tangle. Am I oversimplifying this?" The first asks if more full nodes increase scalability, the ...

A single IOTA node can already handle around 1000 transactions per second, this is quite a bit but probably not enough in the future. Once this becomes an issue sharding can be a solution. This means that only a part of the tangle is handled by cluster of nodes that for example only handle transactions starting with the letter 'A'; Another cluster will be ...

Until now there is no formal nor oficial rule that defines when a Snapshot must be conducted. Normally it occurs when the network needs update, correction or due to a new release. The snapshot is announced by the team and must be independently validated prior to its confirmation and then it takes place by being set to run via the coordinator. This process ...

At the moment, a Snapshot happens when the IOTA foundation decides to do so. There are plans to add automatic snapshotting (probably based on the number of confirmed transactions since the last snapshot), but since they are only plans now, nobody knows exactly how they will work. As currently every full node will eventually see every transaction, the number ...

I was in discord around the time this was originally posted. I figured someone would have provided the answer right after we discussed it... @Come-from-Beyond brought it up himself, and he said that it was a good write-up, and question, but he was concerned that the answer was too simple. Java (the language it was first implemented in) uses 4 bytes for an ...

You would likely store your seed the index of the first unspent address The way IOTA address generation works makes some things very easy: Let's say, your seed is AAAAAA... AAAAAA... + 0 = AAAAAA... → to generate your first address AAAAAA... + 1 = BAAAAA... → to generate your second address AAAAAA... + 2 = CAAAAA... → to generate your third address ... ...

This is meant to be a temporary measure, until a better wallet comes along. Once everyone is using a "stateful" wallet that remembers the addresses used in the past and avoids their reuse, there will be no need for this global list anymore. From https://github.com/iotaledger/iri/issues/503: After a snapshot, old transactions are removed from the database,...

Yes, Fullnodes have to sync and store every single transactions and with Fullnodes it is not possible to scale unlimited. The current Network is build by Fullnodes and is not able to scale. The solution of this bottleneck is the future implementation of swarmnodes as mentioned in the Roadmap. Swarmnodes are Nodes which don't sync and store every single ...

Right now the network is being limited by the coordinator. My following answer is made with the assumption that the coordinator has been removed or at least decentralized into the network. We need enough full nodes and suitable peer discovery algorithms to make sure no single full node can get congested. If this can be satisfied then theoretically the ...

There was no spam test so far because many building blocks have been completed in the last few days. According to the team that is planned for the future but not priority right now.

Be aware that such classification is mainly a theoretical exercise. In practice, a concrete implementation of a gossip like protocol may have properties/features/characteristics coming from different families. The gossip in IOTA is mainly in the family of Background data dissemination protocols were any new transaction is immediately broadcast to all ...

The way I understand it, full nodes store every transaction that they and their neighbors are aware of. From, to, amount, message, tag, trunk/branch transactions, etc. They also store information about wallet addresses, such as balances. Light nodes don't store much at all. Instead, they use API calls to the full node they are connected to, to get the ...