In fact, the button was not replaced, but added. So for some transactions you can still see the reattach button, and for others the new promote button.
The behaviour of these two actions is different:
Reattach will pick two new random tips and create a copy of your transaction bundle attached to them. This needs more PoW (one PoW per transaction in the ...
It depends on what you define as cold storage.
IOTA is stored on addresses in the Tangle. The Tangle is similar to Blockchain in that it's decentralized among all the users. Your Seed is merely a password to access the balances inside the addresses in the Tangle that you own.
Therefore, your Seed is what you are trying to store securely.
You have several ...
Dice may not be best. IOTA Seeds are made up of A-Z and the number 9, and are 81 characters long. So you need a 27 sided dice, or need to do a LOT of dice rolls.
Once you come up with a seed, download the light wallet from github: https://github.com/iotaledger/wallet/releases
Then, input the seed you came up with there. Then, you can create addresses.
1) Get the latest wallet: https://github.com/iotaledger/wallet/releases
2) Try using different Nodes - Tools -> Edit Node Configuration Min Weight Magnitude should always be 14 or above. Curl Implementation can be tried both, Webgl 2 and CCurl
3) Generate a few address and re-attach them to tangle until your full balance shows up
While one single transaction is pending, there is no threat to your balance (apart from the obvious, that if the transaction confirms later, your balance will decrease by the transaction amount).
However, if you have more than one transaction spending from the same address pending (where the transactions have different bundle hashes, i. e. the second one is ...
Every double-spending is an address reuse but not every address-reuse is a double-spending.
Let's say you have an address with a balance of 100i
You send 100i from the address to another address and 100i from the address to yet another address.
You send 40i to from the address to another address and 70i from the address to yet another ...
It's safe to keep your seed. Even if you double-spend or reuse your address, your seed doesn't get exposed, only the private key of one address of your seed is partially revealed. You can generate an infinite amount of addresses with one seed.
What's the difference between a private key and a seed?
What is the difference between "double-spending&...
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 ...
Your IOTA are not stored on your phone, they are stored on the decentralized tangle. Your seed is your password to access your IOTA, anytime, anywhere. As long as you have your seed saved in a place other than your phone, which you definitely should, then you will be totally fine.
See: How can I set up a cold storage?
IOTA's proof-of-work is formed by successively hashing the data in a transaction, including a nonce, and increasing the nonce until producing a hash which ends with a particular number of zeroes. This is hard to calculate, but easy to verify given the nonce. Here you can see the weightMagnitude of a transaction is simply a calculation of the number of ...
There is no green light. If you sign a transaction a second time, even if it is pending, you reveal your private key and the address is insecure. All remaining funds on that address might get stolen.
The light wallet on your computer prevents you from doing that. The Android wallet doesn't.
The only way to get out of this situation is to promote (as often ...
This button will create a transaction that will send 0 iota to the newly created address.
That way, the address appears on tangle explorers (and senders might use this as an indication that the address is indeed correct).
Furthermore, if you create a new address and attach it, and pass it to somebody to pay you, and you need another address before that ...
RNG would work but we don't use it
because we would have to store all of the private keys. It's just more convenient to have only one seed from which you generate all the private keys. Furthermore, all current APIs use seeds and you can't even sign a transaction without the seed unless you are doing it manually (The API functions are specified to take a ...
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....
You attach a 0-value-transaction with a newly generated address to the Tangle. (do the POW, tip selection, ...)
It could be used as a precaution e.g. a wallet only allows you to send IOTAs to addresses that are already attached to the Tangle so that you cannot mistype and send to an address without an owner.
But the light wallet has ...
It has been observed that the more addresses in your wallet, the longer it takes for your computer to retrieve all associated addresses from the Tangle.
The new wallet should remedy this -- it will be stateful, and store your previous addresses locally, so you don't have to re-retrieve them every single time you log in.
AFAIK, the current wallet don't support this kind of complex scenario (i.e. sending to multiple addresses simultaneously). You have to craft a proper Bundle to send funds to multiple addresses.
Case 1 :
Assume that you have 600 iotas in <MY_ADDRESS>
Assume that you need to send 200 iotas to Alice
Assume that you need to send 300 iotas to Bob
1) Can I say that is more difficult to infer the source of a wallet owner since address will not be reused after an withdrawal?
Although no one cannot infer the "seed" from addresses, it is still possible to track paths of the transactions. Unless the transaction goes to an exchange address or you use IOTA mixer (see links below), you cannot have a complete ...
A transaction will likely remain pending if it doesn't confirm within ~ 1 hour. That is just a rough estimation and may change in the future. Anyone can reattach it, so it will have another chance to get confirmed.
Never resend (reusing the address which is bad), always reattach until confirmed.
The current GUI wallet 2.5.4 throws a warning if you try to ...
Download the Iota Wallet for Desktop from -> https://github.com/iotaledger/wallet/releases
Get the "IOTA.Wallet.Setup.2.5.4.exe" (or newer)
After you install it this is what you see. In the "SEED" field enter your generated seed and click login. Yo are done.
Careful: In order to see if you didn't make a typo on your seed note the last three characters (...
Your goal is to instruct Bitfinex to broadcast a transaction to the tangle. One that sends the IOTA balance Bitfinex is storing for you (under their seed) over to an address generated under your seed.
What is a seed
A seed is the password you use to manage your balance on the IOTA network. This network is like a database of password-protected balances ...
When you press the button "Generate new address", this is what happens:
generate new private key from the seed
generate address from the new private key
send a 0-value transaction to the address
Your Iotas remain on the old addresses, where they were before.
If your old addresses are compromised for some reason, you can send all your Iotas to the new ...
The missing balance should be due to your unconfirmed addresses not getting synchronized by the nodes, thus disappearing from the Tangle. Attach those addresses to the Tangle again, and your missing balance shall come back.
Wallets would have to keep track of their own adresses, if they already used them and what they already used them for.
Another solution is to switch seeds after every snapshot and just send all your IOTA to the first address of the new seed.
What would work as well is to ask a Permanode (node that doesn‘t do ...
It means that the node your wallet is talking to did not return the expected response to your API call. Usually it is a problem with the node and the issue can be fixed by changing to another one.
The Bitfinex node has been known to report "I'm depressed, leave me be." during times of heavy network load, which could cause this error.