The Stack Overflow podcast is back! Listen to an interview with our new CEO.

Hot answers tagged

12

Two reasons: When your transaction is seen by the network, it could be already deep in the tangle (several milestones old) which makes it unlikely to get picked for confirmation. This is often caused by PoW being done by a low-end device (or non-working GPU acceleration), so when PoW takes 10 minutes already, there have already been 10 milestones before the ...


12

Reattach: The process of reattaching a transaction is simply doing the proof of work and tip selection process to reattach the transaction to a different part of the Tangle. Reattach once every 30 minutes that a transaction remains pending, and then if still pending after 5 reattachments be sure to contact the sender to verify that the transaction ...


10

Anyone can issue a transaction for any amount from any address. Such a transaction won't be confirmed without knowledge of the private key. Your case is about an attempt to pretend that funds have been stolen.


10

The validity of a transaction (let's call it target-tx) can be evaluated with this algorithm: random selection of 100 new transaction for each of them: count 1 if there is a path to target-tx (i.e. if this random transaction indirectly—or directly—validates target-tx) once you have done this evaluation for all 100 transactions, the number you have is a ...


8

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 ...


7

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 ...


7

As others already stated, these transactions are not valid as they do not have the correct signature (some of them even have some text - stating that they don't have the correct signature - tryte-encoded in the signature field). The reason why creating these transactions is so successful: Currently tangle explorers do not validate transactions well enough (...


7

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 ...


7

The best way, to get your transaction through is to run your own full node on a seperate Server. This makes transactions faster and gives you more control. However, if you don't run your own full node, I recommend you to check https://iota.dance/nodes and choose the first/highest node (which is the public node providing the best chances, because of the lowes ...


5

Reattachments won't help and the transfer can't be deleted. Sending 1i to A will help because after that the pending transfer won't be a doublespending.


4

The wallet doesn't keep an open connection to the full node. Here is the flow : get the tips (connection required) do the pow (offline) post the transaction (connection required) transaction is pending (no connection required) Changing the node when you have a pending transaction has no impact on anything.


4

If λ is the average rate at which transactions are issued in the tangle, then the cumulative weight of any single transaction (i.e. the count of transactions that directly & indirectly reference that single transaction) is expected to behave as follows, where up until the Cut the growth is exponential, and linear thereafter with slope λ. One could argue ...


4

If the POW last for a long time, your transaction will be attached to relatively old transactions when it will be broadcasted to the network. It will looks like a "lazy tip". "Lazy tip" have less chance to be selected by the random walk, so yes a fast CPU/GPU increase your chance to see your transaction confirmed.


4

The transaction might get attached to the part of the tree that will never be validated for example because there were too many tips in the Tangle tree waiting for validation so that it gets “forgotten” by the tip selection algorithm. The tip selection algorithm is biased towards the transactions from the top of the tree - this is controlled by the Depth ...


4

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 ...


3

A transaction has not failed even if it does not confirm. You should never make a new transaction, but replay the first one until it confirms. The only time a transaction will not confirm, is if the signature is invalid (not possible to do with wallet), or if the address (or one of them) you spend from have a lower balance than the transaction requires. ...


3

When sending a transaction, and another transaction of the wallet is still pending, you will usually have to wait. In case your first transaction does not exactly use up the amount of your first few addresses, the change will be sent to a new address of your wallet, so that you do not have to reuse the key of the address for spending the second part. As ...


3

After five days, there is almost zero chance that it get approved by a new transaction because the tip selection algorithm will select recent transactions. According to an IOTA dev (on slack), if the transaction isn't confirmed in less than one hour it will probably remain "pending" forever (or at least up to the next snapshot because it will be forgotten). ...


3

When your transaction is younger than 30 minutes, there is a significant chance that other transactions will use it as a tip for their transaction (and therefore confirm it). So, first, if you reattach early, you are wasting your PoW resources. To make matters worse, when you reattach really early (maybe even multiple times), there are two transactions on ...


3

tl;tr With wallet 2.5.6 and IRI 1.4.1.4 : a transaction is confirmed if and only if it is confirmed by a milestone. To check the confirmation status of a transaction, the light wallet call the getInclusionStates api call. More precisely, the wallet will do that in 2 steps : ask to the full node it's latest solid milestone index (API GetNodeInfo). Let's ...


3

According to How does reattaching a transaction increase the chance for confirmation? two main reasons can be identified: Your computer takes a lot of time for the POW, which results in an attach position not in front of the tangle. Thus other tx will not pickup your tx. (see also Does the tip selection depend on how quickly the proof of work is done? and ...


2

I was able to get it to go through. I used this tool to automatically promote/reattach every 30 minutes, and my transaction has been confirmed now.


2

You cannot move IOTA's that are not confirmed to one of your addresses - so you have to wait for confirmation before sending it on. It's recommended to create a new address for each incoming transfer because - If you get two to same address, the first may conrift fast, and second can be pending for a while . If you then spend the first arrivals before ...


1

Why are there 2 transactions? The empty transaction is the wallet telling the network your address exists. This is not required to send transactions to the network. The transaction with 250 MIOTA is, as expected, your exchange withdrawal. Why is it not confirmed? The answer lies in the way a tip (unconfirmed transaction) is selected for confirmation. ...


1

The number of path to check is indeed arbitrary. The idea is that you must check enough paths so that the estimation of portion of tips approving your transaction is accurate.


1

Ok so first of all generating a new address, doesn't move any of your funds to the new address. So each address only contains the amount of iota which had been deposited before. This is the reason why it makes sense to generate a new address for each deposit, so you have the ability to send multiple, legitimate transactions at a time. Yes, you are able to ...


1

Yes, it is ok to have more pending transaction as long as the used funds for those transactions do not overlap. Usually, the client would prevent you from broadcasting such transactions.


1

I had to continue to reattach the transaction using different nodes in order for it to finally confirm.


1

When you transfer iota to bitfinex, you have to distinguish between 2 things: first you transfer iotas to your deposit address. second, bitfinex transfer iota from your deposit address to his wallet. Consequently 2 transactions occur, and you have an influence by reattaching or promoting only on the first (the second is handled by bitfinex, so if their ...


1

If you have 1i in another wallet (not related to the seed with your 2i address) - for example wallet C -, you can use that wallet to send 1i to the address of wallet A that currently has the 2i. Afterwards (when this transaction is confirmed), your balance of that address will be 3i, so you can reattach the pending 3i transaction again. However, you should ...


Only top voted, non community-wiki answers of a minimum length are eligible