I'll quote learn.iota.org here, because they have a good explanation.
The IOTA GUI makes it possible to choose between Full Wallet, and
Light Wallet. The Full Wallet automatically runs an IRI (IOTA
Reference Implementation) instance in the background, which in turn
means that you need neighbors in order to participate in the network
and be ...
Core Client a.k.a. Full Node
Full Nodes store all transactions since the last snapshot. It is required to be online (= available to its neighbours) 24/7
A Permanode is a Full Node that doesn't do snapshots and stores all transactions since the genesis transaction.
A Light Client does not store any transactions. To make ...
You are right: it's easy to implement a wallet to steal user's seed.
If you are a developer, you can:
write your own wallet and trusting your own code.
read and understand the code written by a third party and put your trust in it.
If you aren't a developer, you must put your trust in someone else's code. You must educate yourself by reading forums and ...
Short answer it depends.
A little longer answer, the needed time for the proof of work depends on:
the device that calculates the hash.
the load of this device (with other stuff).
the minWeightMagnitude (here you can read more about it).
Furthermore the IOTA Foundation is planing/working on a external CPU called Jinn. Jinn is a ternary CPU so more ...
A full node stores the whole Tangle, it needs neighbours to broadcast transactions to and you need a static IP address or any other static address so that your neighbours can broadcast transactions to you.
As a light node you do not store the Tangle and you don't need any neigbours.
You just need to select a host (e.g. https://node....
If you are asking about nodes as "client" this is the answer.
Any information about Swarm nodes has not been disclosed though "Nelson" is something different from Swarm, which is a wrapper library for Full nodes that let you use the auto peer discovery feature to make maintaining neighbors easy.
Headless nodes also known as Full nodes are the core backbone ...
Iota is a decentralized protocol. There is no central server managing any kind of session.
When you execute a transaction on one client, you do the pow to attach it to the tangle (it usually take a few seconds). Once the transaction is attached : the transaction is now a tip and is broadcasted on the network.
The transaction will be visible in other ...
Since RocksDB has problems with the ARM architecture, you need special version of RocksDB. Here is a complete tutorial: https://medium.com/biilabs/deploy-iota-fullnode-on-asus-tinker-board-fcd2cff8331f
A complete deployment script for IRI on the ARM architecture can be found here: https://github.com/deviceproof/iota-deploy
A wallet should be open source -- this way, it can be vetted by the community to ensure there are no loopholes or trojans.
Aside from that, you should look to the community and determine which wallets are used, for what reasons, where they come from, and their track record to determine which wallet you want to use.
If you want to run your own full node, you'll use iri (or Nelson, or both).
The light nodes still have to compute POW for every transaction they want to introduce into the network, which should be limiting the impact of DDoS quite a lot.
On the other hand, there are nodes which are configured not to require POW (they will perform it themselves instead), and these nodes are very susceptible to DDoS attacks.
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 ...
The issue is that a larger history will result in nodes being in need of more hard drive space and finally result in degraded performance as a larger database is slower than a smaller one.
There are a lot of smaller nodes running on VPS out there, which could not store the entire history. The database since the last snapshot is already almost 11 GB in size ...
The average duration of the pow is determined by the minWeightMagnitude (i.e the difficulty of the puzzle to solve) and the computing power of the device.
On Bitcoin, the difficulty of the pow is adjusted is such a way that there is a new block every 10 minutes (on average). (basically it is driven by the total computing power of the network)
On the Tangle,...