How To Cancel Unconfirmed Bitcoin Transaction In ...

Bitcoin Unlimited how to delete unconfirmed wallet transactions without rescan

So due to a mistake on my part while splitting my BCH and BTC, all my backups of my BCH wallet.dat file have unconfirmed transactions that are on the BTC blockchain. I downloaded the BCH blockchain using Bitcoin Unlimited in prune mode because storage is tight. I assumed that when it got past the BTC transactions it would simply delete them (they're the wrong transaction format and not in any block) but it hasn't.
All the methods of deleting transactions from wallets rely on using -zapwallettxes and -rescan, which I would rather not do (it took quite a while to download the blockchain to begin with).
Is there any way to delete those transactions from the wallet file without a rescan?
Note - the blockchain still has 10 days left to download, but the transactions are older than that.
submitted by CJYP to btc [link] [comments]

How to delete unconfirmed transactions on Bitcoin Core wallet?

I sent about $10 in bitcoin from my Bitcoin Core wallet 2 weeks ago but the transaction remains unconfirmed (and has not registered in the address to which I sent it). How can I cancel / reverse this transaction?
submitted by Duncan1949 to Bitcoin [link] [comments]

Unconfirmed transaction locally deleted in mycelium: did i just kill my bitcoin?

hey guys, happy new year. today i had some beers with friends and the mixed alcohol and bitcoin. i've had an unconfirmed tx in the mempool for about a week, and decided to try to cpfp (mycelium) but it didn't work, so i deleted the transaction locally. now on my mycelium wallet i see 0 balance and in the blockchain.info i have an unconfirmed tx that will likely stay there indefinitely. does the tx eventually expire in the mempool and get back in my wallet. i'd rather not lose all i have. fuck that was dumb. please help
submitted by TheTrillionthApe to Bitcoin [link] [comments]

Bitcoin Unlimited how to delete unconfirmed wallet transactions without rescan /r/btc

Bitcoin Unlimited how to delete unconfirmed wallet transactions without rescan /btc submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Decide to delete unconfirmed transaction after 10 days not transfer due to low fee, now my coin is disappear. Will i receive back the coin or forever loss? /r/Bitcoin

Decide to delete unconfirmed transaction after 10 days not transfer due to low fee, now my coin is disappear. Will i receive back the coin or forever loss? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

How to delete unconfirmed transactions /r/Bitcoin

How to delete unconfirmed transactions /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

How to delete unconfirmed transactions on Bitcoin Core wallet? /r/Bitcoin

How to delete unconfirmed transactions on Bitcoin Core wallet? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

How to delete unconfirmed transactions on electrum? /r/Bitcoin

How to delete unconfirmed transactions on electrum? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Unconfirmed transaction locally deleted in mycelium: did i just kill my bitcoin?

hey guys, happy new year. today i had some beers with friends and the mixed alcohol and bitcoin. i've had an unconfirmed tx in the mempool for about a week, and decided to try to cpfp (mycelium) but it didn't work, so i deleted the transaction locally. now on my mycelium wallet i see 0 balance and in the blockchain.info i have an unconfirmed tx that will likely stay there indefinitely. does the tx eventually expire in the mempool and get back in my wallet. i'd rather not lose all i have. fuck that was dumb. please help
submitted by TheTrillionthApe to CryptoCurrency [link] [comments]

Unconfirmed transaction locally deleted in mycelium: did i just kill my bitcoin? /r/Bitcoin

Unconfirmed transaction locally deleted in mycelium: did i just kill my bitcoin? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Deleting unconfirmed transactions on Electrum /r/Bitcoin

Deleting unconfirmed transactions on Electrum /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

How BitPay and other pricessors bear risk of unconfirmed and deleted after 72 hours transactions? /r/Bitcoin

How BitPay and other pricessors bear risk of unconfirmed and deleted after 72 hours transactions? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Transaction

I’m just wondering this assuming I own a hardware wallet (ledger per say) if I were to send a transaction of 1 btc to a different address while it’s being confirmed do I still technically have that bitcoin? If not where is it? Cause it’s not at the other persons wallet yet?. Assuming my knowledge is correct, you just shared the control of a specific bit of satoshis. So that means I own it until transaction is verified?
submitted by justinCrypto to Bitcoin [link] [comments]

"My transaction is stuck, what to do?" - an explainer [DRAFT]

In the last days we have been experiencing a sharp rise in price, which is historically correlated with many people transacting over the Bitcoin network. Many people transacting over the Bitcoin network implies that the blockspace is in popular demand, meaning that when you send a transaction, it has to compete with other transactions for the inclusion in one of the blocks in the future. Miners are motivated by profits and transactions that pay more than other transactions are preferred when mining a new block. Although the network is working as intended (blockspace is a scarce good, subject to supply/demand dynamics, regulated purely by fees), people who are unfamiliar with it might feel worried that their transaction is “stuck” or otherwise somehow lost or “in limbo”. This post attempts to explain how the mempool works, how to optimize fees and that one does not need to worry about their funds.

TL;DR: Your funds are safe. Just be patient* and it'll be confirmed at some point. A transaction either will be confirmed or it never leaves your wallet, so there is nothing to worry about in regards to the safety of your coins.

You can see how the mempool "ebbs and flows", and lower fee tx's get confirmed in the "ebb" times (weekends, nights): https://jochen-hoenicke.de/queue/#0,30d
* if you are in hurry there are things like RBF (Replace By Fee) and CPFC (Child Pays For Parent), which you can use to boost your transaction fees; you will need an advanced wallet like Bitcoin Core or Electrum for that though. Keep also in mind that this is not possible with any transaction (RBF requires opt in before sending, f.ex). If nothing else works and your transaction really needs a soon confirmation, you can try and contact a mining pool to ask them if they would include your transaction. Some mining pools even offer a web-interface for this: 1, 2.
Here’s how Andreas Antonopoulos describes it:
In bitcoin there is no "in transit". Transactions are atomic meaning they either happen all at once or don't happen at all. There is no situation where they "leave" one wallet and are not simultaneously and instantaneously in the destination address. Either the transaction happened or it didn't. The only time you can't see the funds is if your wallet is hiding them because it is tracking a pending transaction and doesn't want you to try and spend funds that are already being spent in another transaction. It doesn't mean the money is in limbo, it's just your wallet waiting to see the outcome. If that is the case, you just wait. Eventually the transaction will either happen or will be deleted by the network.
tl;dr: your funds are safe

How is the speed of confirmations determined in bitcoin?

Open this site: https://jochen-hoenicke.de/queue/#0,2w
Here you see how many transactions are currently (and were historically) waiting to be confirmed, i.e how many transactions are currently competing with your transaction for blockspace (=confirmation).
You can see two important things: the differently coloured layers, each layer representing a different fee (higher layer = higher fees). You can point at a layer and see which fees (expressed in sat/byte) are represented in this layer. You can then deduct which layer your own transaction is currently at, and how far away from the top your position is (miners work through the mempool always from the top, simply because the tx's on top pay them more). You can estimate that each newly mined block removes roughly 1.xMB from the top (see the third graph which shows the mempool size in MB). On average, a new block is produced every ten minutes. But keep in mind that over time more transactions come into the mempool, so there can be periods where transactions are coming faster than transactions being “processed” by miners.
The second important observation is that the mempool "ebbs and flows", so even the lower paid transactions are periodically being confirmed at some point.
In short: what determines the speed of a confirmation is A) how high you set the fees (in sat/byte), B) how many other transactions with same or higher fees are currently competing with yours and C) how many transactions with higher paid fees will be broadcast after yours.
A) you can influence directly, B) you can observe in real time, but C) is difficult to predict. So it's always a little tricky to tell when the first confirmation happens if you set your fees low. But it's quite certain that at some point even the cheap transactions will come through.

So what happens if my transaction stays unconfirmed for days or even weeks?

Transactions are being broadcast by the full nodes on the network. Each node can adjust their settings for how long they keep unconfirmed transactions in their mempool. That’s why there is not a fixed amount of time after which a transaction is dropped from the mempool, but most nodes drop unconfirmed tx’s after two weeks [IS THIS CORRECT?]. This means that in the absolute worst case the unconfirmed transaction will simply disappear from the network, as if it never happened. Keep in mind that in those two weeks the coins never actually leave your wallet. It’s just that your wallet doesn’t show them as “available”, but you still have options like RBF and CPFP to get your transaction confirmed with higher fees, or to “cancel” your transaction by spending the same coins onto another address with a higher fee.

Helpful tools to estimate fees for future transactions:

Here are some resources that can help you estimate fees when sending a bitcoin transaction, so you don't end up overpaying (or underpaying) unnecessarily. Keep in mind that in order to take advantage of this, you need a proper bitcoin wallet which allows for custom fee setting. A selection of such wallets you can find here or here.
The order here is roughly from advanced to easy.
1) https://jochen-hoenicke.de/queue/#0,24h
Here you can see a visualization of how many unconfirmed transactions are currently on the network, as well as how many were there in the past. Each coloured layer represents a different fee amount. F.ex the deep blue (lowest layer) are the 1sat/byte transactions, slightly brighter level above are the 2sat/byte transactions and so on.
The most interesting graph is the third one, which shows you the size of the current mempool in MB and the amount of transactions with different fee levels, which would compete with your transaction if you were to send it right now. This should help you estimating how high you need to set the fee (in sat/byte) in order to have it confirmed "soon". But this also should help you to see that even the 1sat/byte transactions get confirmed very regularly, especially on weekends and in the night periods, and that the spikes in the mempool are always temporary. For that you can switch to higher timeframes in the upper right corner, f.ex here is a 30 days view: https://jochen-hoenicke.de/queue/#0,30d. You clearly can see that the mempool is cyclical and you can set a very low fee if you are not in hurry.
2) https://mempool.space
This is also an overview of the current mempool status, although less visual than the previous one. It shows you some important stats, like the mempool size, some basic stats of the recent blocks (tx fees, size etc). Most importantly, it makes a projection of how large you need to set your fees in sat/byte if you want your transaction to be included in the next block, or within the next two/three/four blocks. You can see this projection in the left upper corner (the blocks coloured in brown).
3) https://whatthefee.io
This is a simple estimation tool. It shows you the likelihood (in %) of a particular fee size (in sat/byte) to be confirmed within a particular timeframe (measured in hours). It is very simple to use, but the disadvantage is that it shows you estimates only for the next 24 hours. You probably will overpay by this method if your transaction is less time sensitive than that.
4) https://twitter.com/CoreFeeHelper
This is a very simple bot that tweets out fees projections every hour or so. It tells you how you need to set the fees in order to be confirmed within 1hou6hours/12hours/1day/3days/1week. Very simple to use.
Hopefully one of these tools will help you save fees for your next bitcoin transaction. Or at least help you understand that even with a very low fee setting your transaction will be confirmed sooner or later. Furthermore, I hope it makes you understand how important it is to use a wallet that allows you to set your own fees.
submitted by TheGreatMuffin to u/TheGreatMuffin [link] [comments]

[ Bitcoin ] Technical: Taproot: Why Activate?

Topic originally posted in Bitcoin by almkglor [link]
This is a follow-up on https://old.reddit.com/Bitcoin/comments/hqzp14/technical_the_path_to_taproot_activation/
Taproot! Everybody wants it!! But... you might ask yourself: sure, everybody else wants it, but why would I, sovereign Bitcoin HODLer, want it? Surely I can be better than everybody else because I swapped XXX fiat for Bitcoin unlike all those nocoiners?
And it is important for you to know the reasons why you, o sovereign Bitcoiner, would want Taproot activated. After all, your nodes (or the nodes your wallets use, which if you are SPV, you hopefully can pester to your wallet vendoimplementor about) need to be upgraded in order for Taproot activation to actually succeed instead of becoming a hot sticky mess.
First, let's consider some principles of Bitcoin.
I'm sure most of us here would agree that the above are very important principles of Bitcoin and that these are principles we would not be willing to remove. If anything, we would want those principles strengthened (especially the last one, financial privacy, which current Bitcoin is only sporadically strong with: you can get privacy, it just requires effort to do so).
So, how does Taproot affect those principles?

Taproot and Your /Coins

Most HODLers probably HODL their coins in singlesig addresses. Sadly, switching to Taproot would do very little for you (it gives a mild discount at spend time, at the cost of a mild increase in fee at receive time (paid by whoever sends to you, so if it's a self-send from a P2PKH or bech32 address, you pay for this); mostly a wash).
(technical details: a Taproot output is 1 version byte + 32 byte public key, while a P2WPKH (bech32 singlesig) output is 1 version byte + 20 byte public key hash, so the Taproot output spends 12 bytes more; spending from a P2WPKH requires revealing a 32-byte public key later, which is not needed with Taproot, and Taproot signatures are about 9 bytes smaller than P2WPKH signatures, but the 32 bytes plus 9 bytes is divided by 4 because of the witness discount, so it saves about 11 bytes; mostly a wash, it increases blockweight by about 1 virtual byte, 4 weight for each Taproot-output-input, compared to P2WPKH-output-input).
However, as your HODLings grow in value, you might start wondering if multisignature k-of-n setups might be better for the security of your savings. And it is in multisignature that Taproot starts to give benefits!
Taproot switches to using Schnorr signing scheme. Schnorr makes key aggregation -- constructing a single public key from multiple public keys -- almost as trivial as adding numbers together. "Almost" because it involves some fairly advanced math instead of simple boring number adding, but hey when was the last time you added up your grocery list prices by hand huh?
With current P2SH and P2WSH multisignature schemes, if you have a 2-of-3 setup, then to spend, you need to provide two different signatures from two different public keys. With Taproot, you can create, using special moon math, a single public key that represents your 2-of-3 setup. Then you just put two of your devices together, have them communicate to each other (this can be done airgapped, in theory, by sending QR codes: the software to do this is not even being built yet, but that's because Taproot hasn't activated yet!), and they will make a single signature to authorize any spend from your 2-of-3 address. That's 73 witness bytes -- 18.25 virtual bytes -- of signatures you save!
And if you decide that your current setup with 1-of-1 P2PKH / P2WPKH addresses is just fine as-is: well, that's the whole point of a softfork: backwards-compatibility; you can receive from Taproot users just fine, and once your wallet is updated for Taproot-sending support, you can send to Taproot users just fine as well!
(P2WPKH and P2WSH -- SegWit v0 -- addresses start with bc1q; Taproot -- SegWit v1 --- addresses start with bc1p, in case you wanted to know the difference; in bech32 q is 0, p is 1)
Now how about HODLers who keep all, or some, of their coins on custodial services? Well, any custodial service worth its salt would be doing at least 2-of-3, or probably something even bigger, like 11-of-15. So your custodial service, if it switched to using Taproot internally, could save a lot more (imagine an 11-of-15 getting reduced from 11 signatures to just 1!), which --- we can only hope! --- should translate to lower fees and better customer service from your custodial service!
So I think we can say, very accurately, that the Bitcoin principle --- that YOU are in control of your money --- can only be helped by Taproot (if you are doing multisignature), and, because P2PKH and P2WPKH remain validly-usable addresses in a Taproot future, will not be harmed by Taproot. Its benefit to this principle might be small (it mostly only benefits multisignature users) but since it has no drawbacks with this (i.e. singlesig users can continue to use P2WPKH and P2PKH still) this is still a nice, tidy win!
(even singlesig users get a minor benefit, in that multisig users will now reduce their blockchain space footprint, so that fees can be kept low for everybody; so for example even if you have your single set of private keys engraved on titanium plates sealed in an airtight box stored in a safe buried in a desert protected by angry nomads riding giant sandworms because you're the frickin' Kwisatz Haderach, you still gain some benefit from Taproot)
And here's the important part: if P2PKH/P2WPKH is working perfectly fine with you and you decide to never use Taproot yourself, Taproot will not affect you detrimentally. First do no harm!

Taproot and Your Contracts

No one is an island, no one lives alone. Give and you shall receive. You know: by trading with other people, you can gain expertise in some obscure little necessity of the world (and greatly increase your productivity in that little field), and then trade the products of your expertise for necessities other people have created, all of you thereby gaining gains from trade.
So, contracts, which are basically enforceable agreements that facilitate trading with people who you do not personally know and therefore might not trust.
Let's start with a simple example. You want to buy some gewgaws from somebody. But you don't know them personally. The seller wants the money, you want their gewgaws, but because of the lack of trust (you don't know them!! what if they're scammers??) neither of you can benefit from gains from trade.
However, suppose both of you know of some entity that both of you trust. That entity can act as a trusted escrow. The entity provides you security: this enables the trade, allowing both of you to get gains from trade.
In Bitcoin-land, this can be implemented as a 2-of-3 multisignature. The three signatories in the multisgnature would be you, the gewgaw seller, and the escrow. You put the payment for the gewgaws into this 2-of-3 multisignature address.
Now, suppose it turns out neither of you are scammers (whaaaat!). You receive the gewgaws just fine and you're willing to pay up for them. Then you and the gewgaw seller just sign a transaction --- you and the gewgaw seller are 2, sufficient to trigger the 2-of-3 --- that spends from the 2-of-3 address to a singlesig the gewgaw seller wants (or whatever address the gewgaw seller wants).
But suppose some problem arises. The seller gave you gawgews instead of gewgaws. Or you decided to keep the gewgaws but not sign the transaction to release the funds to the seller. In either case, the escrow is notified, and if it can sign with you to refund the funds back to you (if the seller was a scammer) or it can sign with the seller to forward the funds to the seller (if you were a scammer).
Taproot helps with this: like mentioned above, it allows multisignature setups to produce only one signature, reducing blockchain space usage, and thus making contracts --- which require multiple people, by definition, you don't make contracts with yourself --- is made cheaper (which we hope enables more of these setups to happen for more gains from trade for everyone, also, moon and lambos).
(technology-wise, it's easier to make an n-of-n than a k-of-n, making a k-of-n would require a complex setup involving a long ritual with many communication rounds between the n participants, but an n-of-n can be done trivially with some moon math. You can, however, make what is effectively a 2-of-3 by using a three-branch SCRIPT: either 2-of-2 of you and seller, OR 2-of-2 of you and escrow, OR 2-of-2 of escrow and seller. Fortunately, Taproot adds a facility to embed a SCRIPT inside a public key, so you can have a 2-of-2 Taprooted address (between you and seller) with a SCRIPT branch that can instead be spent with 2-of-2 (you + escrow) OR 2-of-2 (seller + escrow), which implements the three-branched SCRIPT above. If neither of you are scammers (hopefully the common case) then you both sign using your keys and never have to contact the escrow, since you are just using the escrow public key without coordinating with them (because n-of-n is trivial but k-of-n requires setup with communication rounds), so in the "best case" where both of you are honest traders, you also get a privacy boost, in that the escrow never learns you have been trading on gewgaws, I mean ewww, gawgews are much better than gewgaws and therefore I now judge you for being a gewgaw enthusiast, you filthy gewgawer).

Taproot and Your Contracts, Part 2: Cryptographic Boogaloo

Now suppose you want to buy some data instead of things. For example, maybe you have some closed-source software in trial mode installed, and want to pay the developer for the full version. You want to pay for an activation code.
This can be done, today, by using an HTLC. The developer tells you the hash of the activation code. You pay to an HTLC, paying out to the developer if it reveals the preimage (the activation code), or refunding the money back to you after a pre-agreed timeout. If the developer claims the funds, it has to reveal the preimage, which is the activation code, and you can now activate your software. If the developer does not claim the funds by the timeout, you get refunded.
And you can do that, with HTLCs, today.
Of course, HTLCs do have problems:
Fortunately, with Schnorr (which is enabled by Taproot), we can now use the Scriptless Script constuction by Andrew Poelstra. This Scriptless Script allows a new construction, the PTLC or Pointlocked Timelocked Contract. Instead of hashes and preimages, just replace "hash" with "point" and "preimage" with "scalar".
Or as you might know them: "point" is really "public key" and "scalar" is really a "private key". What a PTLC does is that, given a particular public key, the pointlocked branch can be spent only if the spender reveals the private key of the given private key to you.
Another nice thing with PTLCs is that they are deniable. What appears onchain is just a single 2-of-2 signature between you and the developemanufacturer. It's like a magic trick. This signature has no special watermarks, it's a perfectly normal signature (the pledge). However, from this signature, plus some datta given to you by the developemanufacturer (known as the adaptor signature) you can derive the private key of a particular public key you both agree on (the turn). Anyone scraping the blockchain will just see signatures that look just like every other signature, and as long as nobody manages to hack you and get a copy of the adaptor signature or the private key, they cannot get the private key behind the public key (point) that the pointlocked branch needs (the prestige).
(Just to be clear, the public key you are getting the private key from, is distinct from the public key that the developemanufacturer will use for its funds. The activation key is different from the developer's onchain Bitcoin key, and it is the activation key whose private key you will be learning, not the developer's/manufacturer's onchain Bitcoin key).
So:
Taproot lets PTLCs exist onchain because they enable Schnorr, which is a requirement of PTLCs / Scriptless Script.
(technology-wise, take note that Scriptless Script works only for the "pointlocked" branch of the contract; you need normal Script, or a pre-signed nLockTimed transaction, for the "timelocked" branch. Since Taproot can embed a script, you can have the Taproot pubkey be a 2-of-2 to implement the Scriptless Script "pointlocked" branch, then have a hidden script that lets you recover the funds with an OP_CHECKLOCKTIMEVERIFY after the timeout if the seller does not claim the funds.)

Quantum Quibbles!

Now if you were really paying attention, you might have noticed this parenthetical:
(technical details: a Taproot output is 1 version byte + 32 byte public key, while a P2WPKH (bech32 singlesig) output is 1 version byte + 20 byte public key hash...)
So wait, Taproot uses raw 32-byte public keys, and not public key hashes? Isn't that more quantum-vulnerable??
Well, in theory yes. In practice, they probably are not.
It's not that hashes can be broken by quantum computes --- they're still not. Instead, you have to look at how you spend from a P2WPKH/P2PKH pay-to-public-key-hash.
When you spend from a P2PKH / P2WPKH, you have to reveal the public key. Then Bitcoin hashes it and checks if this matches with the public-key-hash, and only then actually validates the signature for that public key.
So an unconfirmed transaction, floating in the mempools of nodes globally, will show, in plain sight for everyone to see, your public key.
(public keys should be public, that's why they're called public keys, LOL)
And if quantum computers are fast enough to be of concern, then they are probably fast enough that, in the several minutes to several hours from broadcast to confirmation, they have already cracked the public key that is openly broadcast with your transaction. The owner of the quantum computer can now replace your unconfirmed transaction with one that pays the funds to itself. Even if you did not opt-in RBF, miners are still incentivized to support RBF on RBF-disabled transactions.
So the extra hash is not as significant a protection against quantum computers as you might think. Instead, the extra hash-and-compare needed is just extra validation effort.
Further, if you have ever, in the past, spent from the address, then there exists already a transaction indelibly stored on the blockchain, openly displaying the public key from which quantum computers can derive the private key. So those are still vulnerable to quantum computers.
For the most part, the cryptographers behind Taproot (and Bitcoin Core) are of the opinion that quantum computers capable of cracking Bitcoin pubkeys are unlikely to appear within a decade or two.
So:
For now, the homomorphic and linear properties of elliptic curve cryptography provide a lot of benefits --- particularly the linearity property is what enables Scriptless Script and simple multisignature (i.e. multisignatures that are just 1 signature onchain). So it might be a good idea to take advantage of them now while we are still fairly safe against quantum computers. It seems likely that quantum-safe signature schemes are nonlinear (thus losing these advantages).

Summary

I Wanna Be The Taprooter!

So, do you want to help activate Taproot? Here's what you, mister sovereign Bitcoin HODLer, can do!

But I Hate Taproot!!

That's fine!

Discussions About Taproot Activation

almkglor your post has been copied because one or more comments in this topic have been removed. This copy will preserve unmoderated topic. If you would like to opt-out, please send a message using [this link].
[deleted comment]
[deleted comment]
[deleted comment]
submitted by anticensor_bot to u/anticensor_bot [link] [comments]

Failed transaction from 10 days ago ... re-broadcast?

I understand the mempool is jammed and transaction fees are up.
About 10 days ago I tried to self-transfer bitcoin from a hot wallet (wasabi) to hardware (using electrum). I used 1 sat/byte fee. At the time the fees had just started rising and I was ok waiting several days/weeks for it to confirm. For the first week, I could see the unconfirmed tx in both wallets.
Yesterday I noticed that wasabi put the funds back into my wallet, and the transaction was deleted from my history completely. I still see the unconfirmed inbound tx in electrum, but it says "Local". Both wallets are pointed at my own Node.
Since electrum saw the inbound transaction, is there any way to push this tx through? It seems like in wasabi I can "double spend" these funds.
submitted by hanzed0000000x to Electrum [link] [comments]

How secure is bitcoin from inflation attack?

I just found out that in 2010 BTC was hacked and inflated with 92 bilion BTC. Is this true ?
submitted by cenourinha123 to Bitcoin [link] [comments]

EVERYONE WITHDRAW BEFORE ITS TOO LATE

I am starting to lose my patience. I am quite sure ALL of us know how bitcoin transaction works, and know that a VAILD TXID will be produced when a bitcoin transaction is made. UNCONFIRMED transaction WILL BE SHOWN in the BLOCKCHAIN. But I can't find my transaction on the network. ITS NOT IN THE MEMPOOL. MEANING the BITCOINS ARE STILL WITH YOU. STOP LYING FFS.
http://prntscr.com/h9u7vp (screenshot from support chat)
here is the video showing that the transaction is not sent to the network or dropped from mempool and needs to be resend.
https://youtu.be/IHmjBB9a94c
I am sure I am not the only one. There are many people having the same problem. And Purse.io is giving them the same replies thinking we are idiots. So before this issue is solved for every poor soul out there. I suggest people cancel all buy orders and get their money out before its too late or another wallet "maintainence" happened. Or purse got hacked and stuff....
PS: this is a repost. Purse.io removed my last post. they are definately hiding something...
here is the screenshot of the original post
http://prntscr.com/ha78ww
removed post
http://prntscr.com/ha797c
submitted by willy_00 to PurseIO [link] [comments]

Almost 48 hours and no confirmation yet. Are my bitcoins lost forever?

I've sent a tx 2 days ago and it STILL hasn't been confirmed. What happens in this scenario? Do my bitcoins go back to my wallet? Can't I rebroadcast the transaction?
EDIT: It's a shame stuff like this is happening when bitcoin was supposed to be the "instant payment, low fee" solution to fiat money.
EDIT 2: It seems like it has already been rejected
Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database.
EDIT 3: I opened my wallet and it automatically rebroadcasted the tx. It got confirmed within an hour now, same fee.
submitted by Some1CP to btc [link] [comments]

This is kind of insane

This is kind of insane submitted by rancymancy to btc [link] [comments]

Bitcoin core - unconfirmed transaction

Last week I posted here about making a transaction from my Bitcoin Core wallet even though the network is over 3 years out of sync, see my post here. Appreciate the advice that I didn't need to wait for the network to fully sync before making the transaction.
I sent the remaining coins to my LBC account, but after 48 hours it still remains unconfirmed. I'm aware these transactions can take a while (says up to 14 days on the LBC website) but I've researched a little bit about unconfirmed transactions and seems it's relatively common.
I'll give it some more time, but if it remains unconfirmed is there anything I can do? I've read on this post that you can "Run bitcoin core with -zapwallettxes -rescan flags" but the unconfirmed transaction will not be gone until the blockchain fully loads. As mentioned mine is out of sync by over 3 years and I don't think my shitty laptop will be able to download all of that, so is there any alternative option? Or have I misunderstood this slightly?
Appreciate any help
edit - forgot to mention I had not included a transaction fee, I didn't recall having to manually input that with transactions in the past (haven't used it in a few years), I wonder whether this is the reason it remains unconfirmed?
submitted by thedudeabides9 to BitcoinBeginners [link] [comments]

Do Bitcoin transactions ever expire?

Transaction expiration is a common myth/misconception. Once a Bitcoin transaction is created, it never automatically expires. In theory, a transaction could be created, get stuck at 0 confirmations for some years, and then all of a sudden confirm.
Several wallets have the behavior of deleting outgoing transactions from their transaction list after a few days of being unconfirmed. This is insane, and could lead to losses. Consider the following example
  1. You send a transaction. It gets stuck due to having a too-low fee.
  2. Your wallet deletes the transaction after a number of days.
  3. You still want to send the transaction, so you create a new transaction with the same value but a higher fee. This confirms.
  4. The recipient uses child-pays-for-parent (CPFP) to get the first transaction to also confirm. You have now paid twice, losing BTC, even though the first transaction "expired".
It is possible to create two transactions that are mutually exclusive. For example, the proper way of increasing the fee in the above example would be to send another transaction that uses exactly the same coins as the first transaction. Since a single coin can't be spent more than once, only one of the transactions will ever confirm. Actual losses due to the insane expiration behavior of certain wallets are rare because wallets often accidentally use the same coins when recreating an "expired" transaction, but it is very reckless to rely on this.
This myth may have been started by Bitcoin Core's default behavior of removing transactions from its memory pool after 72 hours (later changed to 2 weeks). Due to this behavior, it became likely in most cases that a transaction would never confirm after it went 72 hours unconfirmed. However, just because most nodes will forget about a transaction doesn't mean that everyone must or will do so. You have to plan for the worst case, not the typical case.
submitted by alifkhalil469 to BtcNewz [link] [comments]

Best Bitcoin Unconfirmed Transaction Software  Get Funds ... Unconfirmed Bitcoin Transaction Hack FREE 2020 - YouTube how to confirm btc ( bitcoin ) unconfirmed transaction ... Withdraw Any Bitcoin Blockchain Unconfirmed Transaction ... confirm unconfirmed bitcoin transaction fast - YouTube

Oct 9, 2017 00:23 695 words 4 minutes read ethereum pending transaction geth Ethereum transactions model is vastly different from Bitcoin. Instead of using UTXO (unspent transaction outputs)transaction uniqueness and order are achieved using transaction nonce. It is an integer (uint256) counter whichis incremented for It can take up to 2 weeks for bitcoin full nodes to forget about your unconfirmed transaction. When that happens your wallet will show the coins back in your wallet. It is also possible that in that time period some miner picks up your transaction and incorporates it into a block i.e. the transaction confirms and the recipient gets the money. So to summarize you can simply wait for either of ... Tags bitcoin / electrum / child pays for parent / unconfirmed transaction Bitcoin is becoming more and more popular. The amount of transactions per day is increasing and is at an all times high: While this is good news, it also has its downsides. Because the size of each mined block is fixed to 1MB, the amount of tran This is extremely dangerous because even if you delete it from your wallet, the unconfirmed transaction is still floating around on the network and may be confirmed at some point. If you do zapwallettxes and then resend the transaction with a higher fee, then both transactions may confirm. MtGox famously lost a lot of money this way. Unconfirmed transaction means that your transaction is being broadcast through the network until some miner write it down into a block. If the unconfirmed transaction is not confirmed into the blockchain after some days, it is deleted from the network. Nowadays, there is no easy way to delete your unconfirmed transaction. Unless you broadcast ...

[index] [14359] [27256] [8534] [38111] [38637] [4027] [44810] [17799] [38279] [35435]

Best Bitcoin Unconfirmed Transaction Software Get Funds ...

This new Software Bypass Bitcoin Unconfirmed Transactions by ToolsBlock, send funds and directs them to your wallet directly. BITCOIN Unconfirmed Transacti... #bitcoinunconfirmed #btctransaction #bitcoinscript By Far The BEST Bitcoin Unconfirmed Transaction Software In 2020 (Profitable). This is a review on the mos... #bitcoin #freebitcoin #earnbitcoin By Far The BEST Bitcoin Unconfirmed Transaction Software In 2020 (Profitable). This is a review on the most profitable, ea... Share your videos with friends, family, and the world Get your blockchain pending transactions confirmed fast

#