Hot answers tagged

13

Learning without thought is labor lost; thought without learning is perilous - Confucius Jump to the bottom if you want an immediate review. If not, continue along and maybe you might learn a thing or two. As of this writing iri version 1.4.1.2 is the latest release. So the details that follow will be based on this release. Before we begin, lets start ...


4

When retrieving node info from your node, you will see latestMilestone as well as latestSolidSubtangleMilestone (this will also appear in the status bar of the wallet if you use it to connect to your node). If the values are the same as the majority of nodes listed on https://iotanode.host/ (or another site that fetches and aggregates milestones of public ...


4

After looking into code of IRI : all incoming transactions that aren't known yet (i.e. not already stored in the local tangle) are immediately stored in the local tangle and broadcasted to all neighbors. There is a send_limit parameter that can be used to reduce the broadcast rate, but the default behavior is the broadcast every new transaction ASAP (...


4

When your node recieve a transaction from one of it's neighbors: this transaction is referencing 2 other transactions : t1 and t2 (trunk and branch transaction). If either t1 or t2 (or both) is not in the database of your node: then the transaction hash of t1 (or t2 or both) is added to the queue of the "transactions to request to one of your neighbors". ...


3

Via curl if the neighbor exposes the getNodeInfo API: curl -H 'X-IOTA-API-VERSION: 1.4' \ -d '{"command":"getNodeInfo"}' \ http://<hostname>:14265


2

243000 was the milestone of the latest snapshot. Therefore, if your node has not loaded or seen any transactions, latest milestone will show as 243000. The milestone hash of the snapshot will show as 999999⋯9 as the snapshot milestone does not correspond to a transaction, and the trytes conversion of all zeroes is all nines. (This value will change if there ...


2

Last Milestone index is the highest index of a milestone transaction you have seen (because it was pushed to you by another node). Last Solid Subtangle Milestone index is the highest index of a milestone transaction where you have received all referenced transactions as well (so when you start walking from them towards the beginning of the tangle, there are ...


1

Using the IRI API, you can use getNeighbors to get the addresses and then getNodeInfo to obtain the latestSolidSubtangleMilestoneIndex and latestMilestoneIndex. Only works if the neighbors have open APIs. cURL examples, courtesy of https://iota.readme.io: curl http://localhost:14265 \ -X POST \ -H 'Content-Type: application/json' \ -H 'X-IOTA-API-...


1

Probably due to this this open issue that says: latestSolidSubtangleMiletoneIndex does not update in 'getNodeInfo' until a system restart it updates. It just stays the same until a restart. So the fullnode is synchronized but following calls to getNodeInfo doesn't return updated values for latestSolidSubtangleMiletoneIndex.


1

You have 2 Nodes, both are not(!) synchronous: curl http://173.212.242.212:14265 -X POST -H 'Content-Type: application/json' -H 'X-IOTA-API-Version: 1.4' -d '{"command": "getNodeInfo"}' | jq curl http://144.217.243.6:14265 -X POST -H 'Content-Type: application/json' -H 'X-IOTA-API-Version: 1.4' -d '{"command": "getNodeInfo"}' | jq Have a look at your 1. ...


1

It means that your node is not aware of any missing transactions (which could be missing because it has seen other transactions referencing it). Whenever you reach this state and make sure no newer packets from other peers can reach it, this value will remain as it is; therefore it is a bad indicator of how synchronized your node is. Better compare the ...


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