There is no miners on the tangle but they are individuals running fullnodes. They are free to run their preferred implementation of the protocol.
So if you fork the IRI and are able to convince the community that your implementation performs better... in theory it can be adopted. This is not fundamentally different that what's drive the bitcoin community (...
(I already know that this answer will disappoint you - as it did disappoint me when I found it out)
The current algorithms around the tangle depend on a central node run by the Foundation, known as the Coordinator (or Coo). This node will publish a signed milestone transaction approximately every minute. The exact rules which tips will be selected for this ...
Spam is only good, if it is widely distributed over the network. So if there are enough fullnodes which are used for the spamming transactions, everything is fine. If only a few fullnodes are spammed, this could harm the network. Additionally there is the coordinator, which is a bottleneck right now. The devs are using spamming attacks, to research the ...
Each record represents one transaction which was newly received by the node. I'll take apart one single line (which represents this transaction - so you can compare the values there). The Java code in iri that builds these tx messages is here.
tx - this is a transaction received
It is feasible to use the microcontroller as an IOTA wallet.
For example, you can store your IOTA seed on the flash, generate addresses from it, generate sign transactions. One option to get started is to use the IOTA Ledger Blue / Nano wallet code. It is a lightweight C library that can be easily ported to different hardware targets.
It is not feasible to ...
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 ...
The main two bottlenecks on the tangle are as follows:
1) The coordinator: currently, the tangle has a coordinator that ensures that the network isn't overwhelmed by a malicious attacker. Due to the coordinator, there is a limit on transactions per second which can cause slowdowns. Once the network is mature enough, the coordinator will be removed and ...
They don't expire. It's just like a bank account. We have a total amount of IOTAs (2,779,530,283,277,761). This amount is distributed through many wallets. You can look up the distribution here.
It's the distribution of a snapshot from August. I think it has changed dramatically in this few last months. The IOTA Foundation will probably release a new ...
There is a public testnet available (you can use https://seeedy.tangle.works/) to receive a seed with 2000 iota for testing).
A public testnet node: https://testnet140.tangle.works/
A testnet Tangle explorer: https://testnet.thetangle.org/live
If you want to provide your own testnet node, best ask on Slack for neighbors (#testnet channel).
Testnet uses ...
Speaking of English Wikipeda, the deletion discussion is available here.
The IOTA page in German Wikipedia has not been deleted so far.
I did not check Wikipedias in other languages; however, the Interwiki links from the German version can be a start to find some of them.
The wallet will show the sum of all your addresses.
It always empties addresses with lower addresses first.
sum = 7i
Now you want to send 2i to another address.
This is what your addresses will look like:
sum = 7i
The remaining 1i from A0 and A1 were sent to A3.
There are three different protocols and ports involved when running a node:
HTTP control / API port (default tcp 14265)
TCP neighbor port (default tcp 15600)
UDP neighbor port (default udp 14600)
The neighbor ports are only used to transfer transactions between neighbors. That's why you are not getting anything back, the UDP port simply doesn't support the ...
Proof of work does not increase over time automatically. It may be that the IOTA foundation or the majority of nodes will decide later that more PoW (or less) is needed, so they can adjust the MWM value in the protocol. Apart from that, you will have to find 14 zero trytes for every transaction hash, regardless how many nodes or transactions or other users ...
The difficulty of the POW is also called the minimal weight magnitude. It's up to you to choose this threshold (it's possible in wallet UI). High minimal weight magnitude means longer computation time, but you must be aware of few things when selecting the minimal weight magnitude :
today, on the main net : nodes running the default IRI implementation will ...
"Nelson" is a wrapper which facilitates this for IRI. It is made by the carriota.com team. Some reference information so far on it (some people are already using Nelson). There are two blog posts on Medium about CarrIOTA Nelson:
CarrIOTA Nelson: Automatic peer discovery for IOTA
CarrIOTA Nelson in a nutshell
It looks like it can be installed via npm
Variable z is just the index over which the sum in equation (13) iterates. This is similar to when you have
where i is the standard index (so no need to "define" i separately).
Now, notation z:z⇝x simply means All z such that z approves x or All z such that z⇝x. So we sum over all transactions z that directly approve our transaction x. ...
A random walker on it's way to tip to approve must randomly select a path at each step. The random walker have the choice between all transactions (i.e. site) directly approving it's current site.
Here is an example, let's assume that the random walker is currently on a site (i.e. a transaction) directly approved by 3 transactions. Let's call those 3 ...
The main contract of IOTA eXtending Interface is to provide extra functionality, e.g. messaging provided by MAM (Masked Authenticated Messaging). IOTA protocol must be set in stone to let hardware manufacturers start producing IoT devices (FPGA/ASIC-based ones), so we can't wait for all possible extensions to IOTA to be created. This is where IXI comes to ...
Timestamps in transactions are expected to be unix timestamps. Unix timestamps are timezone independent.
Most importantly, timestamps are set by the client (i.e. the sender) and nothing in the protocol guarantees that they are correct. So relying on timestamp/attachmentTimestamp to re-order the transactions is probably not the best option (unless you have ...
The IOTA page on Wikipedia was deleted because it wasn't a great Wikipedia article. It was poorly sourced, contained much information that wasn't in the sources given... They just decided to rewrite it from scratch because the article was so terrible. The only arguments in favour of keeping it seem to be about IOTA's notability. And IOTA is notable enough to ...
let me try to reply here
im desperate to understand,i seriously tried
Good thing to be curious. This Illustrated Introduction is a good starting point to learn about today's IOTA: https://blog.iota.org/the-tangle-an-illustrated-introduction-4d5eae6fe8d4
Please be aware the IOTA is undergoing heavy design changes thanks to the experience gained in the last ...
The problem as I can see it is that you are interpreting the payload length as 5 bytes, according to spec it is uint32 - so it is 4 bytes. From this point on the data is as follows, which matches the spec.
Payload Length uint32 = 4 bytes
Payload Type uint32 = 4 bytes
Indexation Key Length uint16 = 2 bytes
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 ...
The protocol does not enforce a particular tip selection algorithm, so every transaction-issuing network participant is free to choose whatever method they want. The IOTA reference implementation (IRI) has chosen MCMC. As demonstrated in Equilibria in the Tangle from https://arxiv.org/abs/1712.05385 all network participants should (in theory) converge to the ...
The Android wallet tries to retrieve latest transactions from http://iota.cool—if that fails, this notification is shown. This site seems to be down at the moment. But apart from the fact that the explorer view does not show any recent transactions, the wallet should still work fine.
Here is the source code that does this on github.
Transaction size is limited. An intensive data stream will be splitted into many transactions. Each transaction requires a small pow and the idea is that even if it is small, the pow will discourage usage of intensive data stream.
The expected way to use MAM for such use case is to just transfer securly kind of credentials encrypted on the tangle and use ...
Sergey, there should be no serious risk.
Here is a step by step process:
1) On Wallet B, generate a new address.
2) Once it is generated, send that address to the computer with Wallet A, via email or otherwise. You are at no risk publically sharing the address.
3) In Wallet A, go to the send tab and send the amount of IOTA you want to send to that ...
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 can certainly write programs based on the Tangle using:
The available libraries have different degree of maturity as stated in the IOTA roadmap where you can find more information about the languages used for core development and the tools and libraries to build applications. Pay attention that the blog post is dated March ...