dido:public:ra:xapend:xapend.b_stds:defact:iota:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:iota:start [2021/08/18 10:22] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:iota:start [2021/11/09 15:39] (current) char ↷ Page moved and renamed from dido:public:ra:xapend:xapend.b_stds:defact:iota to dido:public:ra:xapend:xapend.b_stds:defact:iota:start |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| : //The IOTA GUI makes it possible to choose between a [[dido:public:ra:xapend:xapend.a_glossary:f:full|Full Node]] and [[dido:public:ra:xapend:xapend.a_glossary:l:light|Light Node]]. The Full Node automatically runs an IRI [[dido:public:ra:xapend:xapend.a_glossary:i:instance|instance]] in the background, which in turn means that you need neighbors in order to participate in the Peer-to-Peer network to synchronize with the Tangle. If you run the Full Node, you have no "trust requirements", as you are completely and independently participating in the network.// | : //The IOTA GUI makes it possible to choose between a [[dido:public:ra:xapend:xapend.a_glossary:f:full|Full Node]] and [[dido:public:ra:xapend:xapend.a_glossary:l:light|Light Node]]. The Full Node automatically runs an IRI [[dido:public:ra:xapend:xapend.a_glossary:i:instance|instance]] in the background, which in turn means that you need neighbors in order to participate in the Peer-to-Peer network to synchronize with the Tangle. If you run the Full Node, you have no "trust requirements", as you are completely and independently participating in the network.// | ||
| - | : //The Light Node makes it possible to connect to a remote Full Node (whether it is your own Full Node, or someone else's publicly provided), in order to get the latest state of the network, most importantly fetching two transactions for validation which are required for issuing a transaction. When running a Light Node, it should be noted that your seed never leaves your wallet, you are still required to perform the Proof-of-Work, and all the sensitive work (such as signing) is done [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]]-side. It also should be noted that the public Full Node providers are often overwhelmed with Light Node requests, so in order to reap the full benefits of the IOTA feeless and fast transaction settlement and [[dido:public:ra:xapend:xapend.a_glossary:d:dataintegrity|data integrity]] technology, it is recommended to run a Full Node and not have to rely on the public Full Node providers (think of it like hitchhiking vs. having your own car).// | + | : //The Light Node makes it possible to connect to a remote Full Node (whether it is your own Full Node, or someone else's publicly provided), in order to get the latest state of the network, most importantly fetching two transactions for [[dido:public:ra:xapend:xapend.a_glossary:v:validation|validation]] which are required for issuing a transaction. When running a Light Node, it should be noted that your seed never leaves your [[dido:public:ra:xapend:xapend.a_glossary:w:wallet|wallet]], you are still required to perform the Proof-of-Work, and all the sensitive work (such as signing) is done [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]]-side. It also should be noted that the public Full Node providers are often overwhelmed with Light Node requests, so in order to reap the full benefits of the IOTA feeless and fast transaction settlement and [[dido:public:ra:xapend:xapend.a_glossary:d:dataintegrity|data integrity]] technology, it is recommended to run a Full Node and not have to rely on the public Full Node providers (think of it like hitchhiking vs. having your own car).// |
| ==== The IOTA Foundation ==== | ==== The IOTA Foundation ==== | ||
dido/public/ra/xapend/xapend.b_stds/defact/iota/start.1629296522.txt.gz · Last modified: 2021/08/18 10:22 by murphy
