|
|
|
|
|
Even if you use Bitcoin through Tor, the way transactions are handled by the network makes anonymity difficult to achieve. Do not expect your transactions to be anonymous unless you really know what you're doing.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
escrow.ms
Legendary
Offline
Activity: 1274
Merit: 1004
|
|
August 26, 2017, 07:42:47 AM |
|
Accelerated Transactions 8cf1e3e9e64921e6a489ed87ed9e4f3b844ff50f46f9a7363304393325d89e85 It should get confirmed when antpool find's a new block.
|
|
|
|
|
jackg
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 26, 2017, 12:14:55 PM |
|
Transactions NEVER expire. In bitcoin core, you can abandon a transaction. Otherwise, your client keeps broadcasting it. Try contacting macbook-air to get this confirmed. Transaction now has 9 confirmations.
|
|
|
|
GreenBits
Legendary
Offline
Activity: 1148
Merit: 1048
|
|
August 26, 2017, 04:54:58 PM |
|
Transactions NEVER expire. In bitcoin core, you can abandon a transaction. Otherwise, your client keeps broadcasting it. Try contacting macbook-air to get this confirmed. Transaction now has 9 confirmations. Give me some clarity on this, As an old head, I always assumed that transactions persist in the mempool for a while ( a few days, maybe a week) but I was told that eventually they will fall out of the mempool if they remained unconfirmed for a significant amount of time. Did I get some bummy info concerning this, or are you referring to the permanent nature of a transaction once it gets its first confirm? I have always been unaware of the constraint/value that determines when a transaction falls out of the mempool, if this is indeed accurate info. Please, someone clear me up on this, appreciated in advance
|
|
|
|
jackg
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 26, 2017, 05:09:05 PM |
|
Transactions NEVER expire. In bitcoin core, you can abandon a transaction. Otherwise, your client keeps broadcasting it. Try contacting macbook-air to get this confirmed. Transaction now has 9 confirmations. Give me some clarity on this, As an old head, I always assumed that transactions persist in the mempool for a while ( a few days, maybe a week) but I was told that eventually they will fall out of the mempool if they remained unconfirmed for a significant amount of time. Did I get some bummy info concerning this, or are you referring to the permanent nature of a transaction once it gets its first confirm? I have always been unaware of the constraint/value that determines when a transaction falls out of the mempool, if this is indeed accurate info. Please, someone clear me up on this, appreciated in advance If you're using core, your transaction can be removed fromthe network with the abandon transaction command. As this is a command in core, there is clearly no short constraint. Until you produce another transaction from that same inout and get that accepted by the network (as it has a higher fee) it will clear the other one from the mempool as the other transaction becomes invalid as it is a double spend of the same input. As far as I am aware, there used to be a constraint of 72 hours which seems more and more like a weird value as I have had transactions last for weeks before they get confirmed before. Also, If you are using a client like electrum, then, when you load up the client, you transaction continues to be broadcast to the network, and also block explorers like blockchain.info will keep broadcasting transactions in a way as thy go throuh their servers. (I'm interested to know if anyone's had a TX expire though)?
|
|
|
|
GreenBits
Legendary
Offline
Activity: 1148
Merit: 1048
|
|
August 26, 2017, 05:24:23 PM |
|
Transactions NEVER expire. In bitcoin core, you can abandon a transaction. Otherwise, your client keeps broadcasting it. Try contacting macbook-air to get this confirmed. Transaction now has 9 confirmations. Give me some clarity on this, As an old head, I always assumed that transactions persist in the mempool for a while ( a few days, maybe a week) but I was told that eventually they will fall out of the mempool if they remained unconfirmed for a significant amount of time. Did I get some bummy info concerning this, or are you referring to the permanent nature of a transaction once it gets its first confirm? I have always been unaware of the constraint/value that determines when a transaction falls out of the mempool, if this is indeed accurate info. Please, someone clear me up on this, appreciated in advance If you're using core, your transaction can be removed fromthe network with the abandon transaction command. As this is a command in core, there is clearly no short constraint. Until you produce another transaction from that same inout and get that accepted by the network (as it has a higher fee) it will clear the other one from the mempool as the other transaction becomes invalid as it is a double spend of the same input. As far as I am aware, there used to be a constraint of 72 hours which seems more and more like a weird value as I have had transactions last for weeks before they get confirmed before. Also, If you are using a client like electrum, then, when you load up the client, you transaction continues to be broadcast to the network, and also block explorers like blockchain.info will keep broadcasting transactions in a way as thy go throuh their servers. (I'm interested to know if anyone's had a TX expire though)? I think I heard this as well, but I was always confused by the arbitrary 72 hours ( I assumed this was roughly x number of blocks, block passage seem like the only concrete measure of time in this space, where everything is so variable. When I worked at CEX.IO, the techs told us about peoples transactions falling out of the mempool/expiring, but I only have had second hand accounts, and never made or witnessed a transaction that was subject to this rule personally. For all the incoming btc transactions on tickets, this never once actually happened on a ticket. It would always eventually confirm, the longest I have personally witnessed was about 5.5 days. Talking about bitcoin only; ive seen some shitcoin txs pend for weeks, while the devs made major changes to the wallet code. Im curious too, has anyone here ever personally had a transaction expire on them? And if you remember, what was the state of the network at the time?
|
|
|
|
jackg
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 26, 2017, 06:29:36 PM |
|
Transactions NEVER expire. In bitcoin core, you can abandon a transaction. Otherwise, your client keeps broadcasting it. Try contacting macbook-air to get this confirmed. Transaction now has 9 confirmations. Give me some clarity on this, As an old head, I always assumed that transactions persist in the mempool for a while ( a few days, maybe a week) but I was told that eventually they will fall out of the mempool if they remained unconfirmed for a significant amount of time. Did I get some bummy info concerning this, or are you referring to the permanent nature of a transaction once it gets its first confirm? I have always been unaware of the constraint/value that determines when a transaction falls out of the mempool, if this is indeed accurate info. Please, someone clear me up on this, appreciated in advance If you're using core, your transaction can be removed fromthe network with the abandon transaction command. As this is a command in core, there is clearly no short constraint. Until you produce another transaction from that same inout and get that accepted by the network (as it has a higher fee) it will clear the other one from the mempool as the other transaction becomes invalid as it is a double spend of the same input. As far as I am aware, there used to be a constraint of 72 hours which seems more and more like a weird value as I have had transactions last for weeks before they get confirmed before. Also, If you are using a client like electrum, then, when you load up the client, you transaction continues to be broadcast to the network, and also block explorers like blockchain.info will keep broadcasting transactions in a way as thy go throuh their servers. (I'm interested to know if anyone's had a TX expire though)? I think I heard this as well, but I was always confused by the arbitrary 72 hours ( I assumed this was roughly x number of blocks, block passage seem like the only concrete measure of time in this space, where everything is so variable. When I worked at CEX.IO, the techs told us about peoples transactions falling out of the mempool/expiring, but I only have had second hand accounts, and never made or witnessed a transaction that was subject to this rule personally. For all the incoming btc transactions on tickets, this never once actually happened on a ticket. It would always eventually confirm, the longest I have personally witnessed was about 5.5 days. Talking about bitcoin only; ive seen some shitcoin txs pend for weeks, while the devs made major changes to the wallet code. Im curious too, has anyone here ever personally had a transaction expire on them? And if you remember, what was the state of the network at the time? From a quick google search, I got this: https://www.reddit.com/r/Bitcoin/comments/5b9kln/unconfirmed_transactions_for_more_than_5_month/5 months waiting for a transaction to confirm (that's some great patience)! EDIT: I assume the 72 hours may have come from how fast it previously took to get a confirmation without a fee (I'm not sure if that's possible when I started as I used a web walelt who covered the fees - which does seem a good idea to do now - with only amounts you expect you'll probably need that day/week).
|
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4316
<insert witty quote here>
|
|
August 27, 2017, 05:33:52 AM |
|
As far as I am aware, there used to be a constraint of 72 hours which seems more and more like a weird value as I have had transactions last for weeks before they get confirmed before.
Seems like there is a little bit of confusion here... the "72 hours" was the previous "mempoolexpiry" value... this has been changed to 336 hours (14 days) since Core v0.14: https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_argumentsAs per this stackexchange answer... there are five ways that a transaction is removed from the mempool: As of Bitcoin Core 0.14.0, these are the ways a transaction can leave the mempool: - The transaction was included in a block.
- The transaction or one of its unconfirmed ancestors conflicts with a transaction that was included in a block.
- The transaction was replaced by a newer version (see BIP 125). aka "RBF"
- The transaction was at the bottom of the mempool (when sorted by fee per size), the mempool had reached its size limit (see the -maxmempool option), and a new higher-fee transaction was accepted, evicting the bottom.
- The transaction expired by timeout (by default 14 days after entering).
Some things to note... the 14 day mempoolexpiry value is just a default and can be set by the Node owner... so some pools may be 3 days, some 14 days, some 1 month, some 12 hours etc... Also, if the pool is running on a limited pool size (ie. maxmempool) then it may be pushed out sooner than the mempoolexpiry time... Wallets are able to (and usually do) attempt to rebroadcast transactions... which can "reset" the expiry time for a transaction. I believe this is the main reason that people end up with transactions unconfirmed for weeks. Abandoning a transaction in Core does not remove it from the network... once a transaction has been broadcast, it is there until it drops out of the mempool... all abandoning does it mark it so that your wallet will not rebroadcast it. There is nothing stopping someone else from continuing to rebroadcast or a miner "confirming" that transaction if they wish.
|
|
|
|
Maddinson100
|
|
September 14, 2017, 12:16:48 PM |
|
That has been what has been happening on the network these days, I had my transactions stuck on the network for more than 2 days and then it later got confirmed but it wasted too much time and I started getting scared that I had lost my money or stuff like that.
|
|
|
|
nightways
|
|
September 14, 2017, 01:41:27 PM |
|
Wow, that’s really long though, I got my transactions stuck on the network for almost 18 hours and I was really scared, now am seeing someone complaining of 5 days, it means there is something wrong on the network.
|
|
|
|
johnsm79
Full Member
Offline
Activity: 224
Merit: 101
trade.io - Join the Trading Revolution
|
|
September 17, 2017, 01:05:15 PM |
|
I thought few hours was long, not 5 days. Is there a chance to loose the funds?
|
|
|
|
Backupnime
Full Member
Offline
Activity: 494
Merit: 104
homt.net
|
|
September 17, 2017, 01:43:58 PM |
|
your pay for fee is too low, your not priority for processing by miner.
|
CDEX-CROSS-CHAIN DECENTRALIZED EXCHANGE PLATFORM
|
|
|
jackg
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
September 17, 2017, 02:24:15 PM |
|
I thought few hours was long, not 5 days. Is there a chance to loose the funds?
your pay for fee is too low, your not priority for processing by miner.
Transaction is now confirmed. There's absolutely no substance to your replies therefore as the matter is already resolved.
|
|
|
|
|
cissrawk
Sr. Member
Offline
Activity: 1218
Merit: 410
Secure your crypto : https://notyourkeys.org
|
|
September 19, 2017, 01:39:17 PM |
|
I already accelerated your transaction. You can submit manually in here https://www.antpool.com/user/prioritiseTransaction.htm so maybe you need it in the future, you can accelerate it by yourself.
|
|
|
|
reflector
|
|
September 20, 2017, 11:08:27 AM |
|
@ don't accelerate the transaction because it has confirmed already. I don't think it get confirmed after you have accelerate it. Please check the tx id before you accelerate it. As of now I use accelerate the transaction with the viabtc accelerator site without any fees. Antpool may be consumes the high fees to get confirm it faster.
|
|
|
|
cissrawk
Sr. Member
Offline
Activity: 1218
Merit: 410
Secure your crypto : https://notyourkeys.org
|
|
September 20, 2017, 11:27:24 AM |
|
@ don't accelerate the transaction because it has confirmed already. I don't think it get confirmed after you have accelerate it. Please check the tx id before you accelerate it. As of now I use accelerate the transaction with the viabtc accelerator site without any fees. Antpool may be consumes the high fees to get confirm it faster. September 19, 2017, 01:39:17 PM look at date mate, im curious why you didnt look at it and antpool doesnt take any fees
|
|
|
|
Genkotsu
Member
Offline
Activity: 308
Merit: 10
|
|
September 20, 2017, 02:48:40 PM |
|
your pay for fee is too low thats why transaction stuck
|
|
|
|
coindoctor
Full Member
Offline
Activity: 194
Merit: 100
路發
|
|
September 20, 2017, 04:23:27 PM |
|
The fee he used was 0.00005726 BTC
Is that too low?
|
|
|
|
|