You should never send iota to an address that was already spent. This will make it possible for an attacker to steal your iotas. This rule is uninfluenced by any snapshot.
The problem after a snapshot is, that every node deletes the transaction history, only the balances are saved. Usually your wallet doesn't show any spent addresses anymore (thus ...
In a MAM stream, every message holds a reference to the next one. To follow the stream when there is a snapshot you must always keep the ref to the next message.
Currently, to read the beginning of the stream after a snapshot you have to connect to a permanode.
(Source : https://youtu.be/_ZO2ysgzKkM at 1h23)
A milestone and a snapshot are two separate things.
Currently, the network has the coordinator set up to ensure that malicious attacks cannot occur. The specifics of what a milestone is are detailed in this answer: What does the IOTA coordinator actually do?
A snapshot is a separate technical feature of IOTA that essentially captures a snasphot of all ...
Transactions that are pending at a snapshot are forgotten, and the balance stays where it is.
As the current wallet is stateless, the wallet does not know about those transactions any more either. So, while in theory (if you have still stored the transaction trytes somewhere) you can reattach the transaction after the snapshot, the current wallet does not ...
A snapshot removes all transactions from the tangle, and only keeps the balances. The balances at snapshot time (you can verify them if you are running a full node right now) are moved into Snapshot.txt instead. Also the minimum milestone number and minimum transaction time gets increased a bit (to avoid new nodes to see old transactions from before the ...
With the Tangle you can only really verify that a particular transaction was issued by a specific party but the data inside the payload must not really be true at all.
This is of course true but it is not a problem that Iota is attempting to solve. If forgery was happening on a large scale then the company doing it would risk a lot and would be easily ...
A snapshot is designed to reduce the size of the tangle to reduce memory burden on nodes. It does this by pruning historical addresses and transactions and saving a baseline of balances at the time of the snapshot.
In order to do this, it prunes the old data, which means from the perspective of the snapshotted node, it is gone.
However, there is no ...
IOTA addresses can be used multiple times for receiving, but once spent, the security dramatically reduces. So, if the address generation algorithm has not changed (you are getting the same addresses and/or balances from the same key), and you haven't spent from that address yet, yes, it is safe to receive.
Once spent, never reuse an address.
tl;dr version: In order to find your entire balance after a snapshot, you will need to attach the same number of addresses as you had before the snapshot.
Wait a sec, why do I even have to attach addresses in the first place?
The current IOTA Wallet released by the IOTA Foundation is stateless. This means that it doesn't store any information about your ...
There is no requirement to do a protocol update when a snapshot is done, but it's a good opportunity to do it.
Remember that the tangle is still young and protocol updates are required. In the future, once tangle will be mature, I expect that snapshot will be done with no protocol update at the same time.
In theory you can, but you absolutely should not, or your iotas will be at risk!
IOTA uses one-time signatures, that means that part of the private key of an address leaks when you use it for sending iotas (= signing). Thus, it's not safe to send iotas to an used address ever again, even after a snapshot.
The current IOTA wallet 2.5.4 doesn't store any ...
The "source" of all Iotas is the genesis transaction. There will never be more than this amount of Iotas. When you want to purchase Iotas, you buy them from another IOTA user which will be an exchange in most cases.
Markov Chain Monte Carlo
The default tip selection algortihm is the Markov Chain Monte Carlo Algorithm. It is used to select ...
I am not sure that I fully understand your question. What do you mean by
I am in the snapshot
I am not in the snapshot
IOTA doesn‘t have such thing. You can miss out snapshots and that won‘t affect your balance. After a snapshot, all you have to do is keep generating addresses in your wallet until your balance is fully restored. Your addresses ...
Snapshot are publicly available for download. For instance here : https://gist.github.com/paulhandy/5eda521316dec87011128c64722aa20c
Additionnaly, there will be also Permanodes where the full history will be kept.
No, all positive balances will keep their value after an arbitrary number of snapshots.
You have 1 Terraiota
Your wallet shows that you have 0 Iota *
You login to your wallet and generate X addresses where X is the number of addresses you generated before the first Snapshot
Now you can see your balance again and spend your ...
Which tips are referenced as parent by the first (new) transactions?
An answer for this question can be found here: Clarify inner workings of the snapshot
The genesis transaction (with hash: 999⋯9) is directly approved by the Coordinator. The first transaction after the genesis simply approves the genesis transaction twice. In other words, it has the same ...
Until now there is no formal nor oficial rule that defines when a Snapshot must be conducted. Normally it occurs when the network needs update,
correction or due to a new release.
The snapshot is announced by the team and must be independently validated prior to its confirmation and then it takes place by being set to run via the coordinator.
This process ...
At the moment, a Snapshot happens when the IOTA foundation decides to do so. There are plans to add automatic snapshotting (probably based on the number of confirmed transactions since the last snapshot), but since they are only plans now, nobody knows exactly how they will work.
As currently every full node will eventually see every transaction, the number ...
There is https://thetangle.org/statistics/tokens-distribution which shows some current token distribution stats.
When there was a snapshot, you can download Snapshot.txt and analzye it yourself (there is one line for each address, with address and balance).
When there is no recent snapshot, you can run a full node, add Snapshot.ixi, and call it (just for ...
A snapshot is done to prevent the Tangle (DAG) from expanding too much in size. Snapshotting saves all the balances, while removing the history and data of all the transactions to start fresh. These addresses with balances act like a new genesis address, but no previous history or data will be attached. The image below shows some tips of the tangle in grey, ...
Starting from the bundle hash, call the findTransactions API to get the transaction hashes of all transactions in your bundle.
Pass the hashes to getTrytes to retrieve the transactions as tryte-encoded strings. You may want to sort the transactions in the original order (i. e. so that they are chained by trunk transaction hash) to avoid surprises when ...
When the IOTA foundation performs a network-wide snapshot, they define a milestone index (i.e. the index of a transaction issued by the Coordinator). Nodes who have not seen that milestone (because they are not synced) will not be able to verify the snapshot. All other nodes that have this milestone can verify it, since it confirms the same transactions for ...
Nodes will not be in different states regarding your balance as long as you don‘t sign bundles.
So you can be 100% sure that you have X Iotas on ADDRESS9 and you can be 100% sure that you have X-Y Iotas on ADDRESS9 after you sign and publish a bundle that spends Y Iotas from ADDRESS9
It makes no difference, if a node does 7 or 700 snapshots a day or if ...
The simple answer is: No.
The more complex answer: If you download this DB, uses it in your own full-node and get all the milestones after each snapshot, you could implement something like this.
I think you are probably looking for the simple answer :)
Following from the light wallet:
and the cli-wallet (line 41):
Actually upgrading is just a matter of replacing.
I usually install IRI cloning repository with git (and so first of all I rename for any eventuality the existing iri directory):
$ mv iri iri.old