There are different possibilities to store your IOTA on a wallet. For instance a Full Node (GUI), Headless Node, Android Wallet or a Light Wallet (GUI). When getting started with IOTA it can be very hard to understand the difference between a light and a full node and which wallet types there are.
IOTA Light Wallet (GUI)
A local interface that accesses a full node (IOTA Node) in a different environment. Download Light Wallet. Install the wallet and choose "Light Node". Then connect to a public note - for instance "https://potato.iotasalad.org:14265". We do not take any responsibility for any issues and/or losses.
IOTA Android Wallet
A interface on your Android interface that accesses a full node (IOTA Node) in a different environment. Download Android Wallet. Install the wallet and connect to a public note - for instance "https://potato.iotasalad.org:14265". We do not take any responsibility for any issues and/or losses.
IOTA Full Node Wallet(GUI)
This is an IRI (IOTA Reference Implementation) running and being accessed locally via a GUI. Any full node needs to be connected to neighbours via a static IP in order to function. Subscribe to the IOTA slack channel (slack.iota.org). This is the place you can assemble the most recent data and the main stage on the off chance that you require help! Make a point to join the sub-channels #releases, #nodesharing, #trading and #botbox. Presently you have to know how an IOTA hub functions as a rule. A hub (how about we call it "Bert") is a piece of the worldwide IOTA arrange and is always trading data with its neighbors (hubs that are associated with Bert). This data is the status of the system: who made exchanges, what number of exchanges and so on. A case: A hub, Grover, is associated with Ernie, and Ernie is associated with Bert (implying that Grover and Ernie, and in addition Ernie and Bert, are neighbors). Grover communicates another exchange and Ernie is getting this data specifically from him. Since Ernie and Bert are additionally associated, Bert gets this data, as well. Along these lines, everyone in the system is stayed up with the latest. Here and there hubs in a system may scan naturally for neighbors (programmed distributed disclosure). In any case, this isn't the situation for IOTA (this is by plan as IOTA is intended to be as simple as workable for machines) and you have to add neighbors physically to your hub. You do this by trading IP addresses with different clients that run hubs on the system utilizing the slack channel #nodesharing. Now it ends up plainly imperative that you have a static IP address, as something else, your neighbors need to refresh your IP address each time it changes keeping in mind the end goal to remain associated with you. In the event that you don't have one, look at our instructional exercise here. We do not take any responsibility for any issues and/or losses.
IOTA Headless Node
A full node running in your local console. You can access it via a simple UI called Nostalgia in your browser. It has the same requirements as a GUI full node, but has the advantage that you can open multiple Seeds (Accounts) at the same time.Download IRI File. Create in your download location a new .txt file. Select 'Document > Save As' and in the 'Spare As' window, input a name for your record including '.bat' on the end. You should likewise spare as sort: 'All Files'. Presently right tap on your .bat record and select "Alter". On the main line write: java - jolt iri-*version_number*.jar - p 14265 - n "udp://neighborIP:14265 udp://NeighborIP2:14265". On the second line type:???? stop. In the event that you utilize dyndns administrations, you can include a - e to determine association issues after IP changes: java - jostle iri-*version_number*.jar - p 14265 - n "udp://neighborIP:14265 udp://NeighborIP2:14265". Spare the progressions. You would now be able to dispatch IOTA whenever by clicking this .BAT record. Now you can decide which type of node you want to run! We do not take any responsibility for any issues and/or losses.