No.
The new (valid) block gets broadcasted, the nodes receive the new block and parse it. Any transaction in a new (valid) block that's being parsed by each individual node gets removed from this node's mempool

They stay in the mempool untill a miner includes them into a block he/she is solving (and is successfull in doing so) OR untill the nodes prune (remove) the tx from their mempool.

You use unspent outputs funding your address to create a transaction that's creating a new unspent output funding the receiving address.
This unconfirmed transaction is indeed broadcasted to the nodes you are connected to, and these nodes relay the unconfirmed transaction to the nodes they are connected to, and so on.

I have no idear how long it'll take for your unconfirmed transaction to be broadcasted to allmost all nodes in the network, but it can't take more than a couple of seconds before you tx is in the mempool of > 99% of the connected nodes.

Do be carefull tough: unconfirmed transactions are broadcasted really fast, but they just end up in the mempool. If they don't get confirmed, most nodes prune them from their mempool after ~14 days, or if the memory usage > 300 Mb. So you really need to wait untill the tx has a couple of confirmations before sending any goods or services.

Well, that's not really how i want api documentation to be written.

That being said, it's basically a cut-and-paste example in php. Which language will you use for your project?


Sure. address, amount, confirmations, hash and auth_hmac will be posted to your callback url.

In this case, i'd probably just get the raw, signed transaction and keep rebroadcasting it every 3 or 4 days. There's always a probability you'll get lucky sooner or later, or there's also the probability the feerate will drop eventually. If you're ever concerned that the average fee will rise even more, you can always just bump the fee.

46 - mocacinno

Thanks 

this ^^

You got cleaned up once, and yet again you're going for a desktop wallet... A decent hardware wallet starts somewhere in the $70 range, maybe $140 if you go for a ledger nano X... That's nothing compared to the loss you suffered today. Learn from your mistakes, don't repeat them.


My first one was a ledger HW.1, it was dirt cheap (like 20 euro's if i remember correctly). I bought it when i was holding only a couple hundred bucks worth of BTC.
You should consider a hardware wallet as an investment if you're serious about holding crypto. It doesn't matter if you only hold $10 worth of BTC right now, if you're planning on holding more than $500 at any point in the future, you might aswell spend the $70 and buy a ledger or a trezor, it'll come in handy when your portfolio grows.

I hate to break it to you, but a CPFP will be more expensive then bumping the fee from an opt-in RBF transaction.
Paying a mining pool will be even more expensive.
Waiting untill it gets dropped from the mempool and double spending afterwards might be more expensive or cheaper, depending on the average feerate in ~2 weeks.

The cheapest option will be to keep rebroadcasting the 1 sat/byte tx and wait untill the average feerate from the tx's in the mempool goes down. This can be in 1 day, 1 week, 1 month, 1 year???

The next cheapest option will either be bumping the fee or waiting 2 weeks and double spending (depending on wether the feerate rises or drops in 2 weeks)
An even more expensive option will probably be CPFP, because the total fee you'll have payed in the end is the fee of the stuck transaction + the fee of the child transaction, which is equal to the fee of a transaction with a size of (stuck tx + child tx) minus the fee you've already payed.

Everything depends on the evolution of the optimal feerange, so you either have to wait it out and hope for the best, or if you want this fixed right now your cheapest option is bumping the fee.


It's clear to me you value your privacy, so you don't have to share the txid with us, however, could you answer this questions:

• How long are you prepared to wait
• Was the tx opt-in rbf
• Do you mind "gambling" on the probability of the fee decreasing in the near future

o_e_l_e_o is 100% correct about a CPFP, you do have other options tough:

• It's a transaction consolidating your unspent outputs, so you have the private key to re-spend those 14 unspent outputs AND you have the private key for the address that was funded by the stuck transaction. If there isn't a case of urgency, you can always wait untill the transaction drops from the mempool of most nodes, then double-spend those 14 unspent outputs. This can take up to 2 weeks, and the odds are that by then the average fee is even higher
• You can do a rbf, in case the tx was opt-in rbf
• You can pay a big mining pool to include your transaction into the next block they solve (viaBTC is known to do this)
• o_e_l_e_o has already explained CPFP
• You can also get the raw tx and keep rebroadcasting it... Sooner or later the average fee will decrease and if you kept rebroadcasting the tx every couple of days, sooner or later it'll end up in a block

There is a financial difference between the options, aswell as a difference in wait time untill confirmation, aswell as a technical difficulty difference.

I have a masters degree in sciences, I had to take an introduction in economics in my second bachelor, but that was more than 20 years ago... I must say that even after googeling, the best i came up with was the term "production function".
K = kapital
L = Labour

I'm out of my depth in an economic discussion (as mentioned above), but i suppose the kapital is decent ASIC's and cheap power, and the Labour is  studying, tuning and running these ASIC's.
An ASIC is pretty much plug-and-play, you make sure you have a mining room with shelves, A/C, power,... You buy the ASIC + PSU, plug everything in, go to the web gui, enter the pool info, and that's about it...

You need to know what you're doing and have very cheap power in order to mine succesfully, but the amount of Labour is defenately lower than the amount of Kapital.

It's a good idear to mark the address as scam, aswell as going to your local police and create a complaint. However, don't get your hopes up: the odds of actually getting your BTC back are very small (allmost nonexistant). Only if the scammer is caught and your local police is informed and connects this information to your legal complaint, you have a small chance of getting a small part of your funds back. If the thief mixes, coinjoins or exchanges to a privacy coin using an on-the-fly swap-site, the police won't even be able to follow the fund's trace, and if they ever catch the guy, odds are they'll never be able to pinpoint you as a victim.

Like it has been said before: it's more important NOT to trust your pc and learn the (expensive) lesson this ordeal has taught you. You should consider your pc to be infected, if you're not an expert there is no way of knowing if the thief installed other malware, disabled certain services, stole private info,... My best advice would be to start from scratch: clean OS, virusscanner, firewall + hardware wallet. You should never install any illegal or unknown program, script, plugin,.. on a PC that's being used for financial transactions (including crypto wallets), you should keep the attack vector as small as possible by only installing the binaries you truely need, and you should keep everything patched (and remove any app that's no longer actively supported).

Yup, you were cleaned out good... If you did not make that transaction, your funds are gone.

Phishing, malware (on your pc or a script within your browser), a vulnerability (os, browser) or unsafe storage of your credentials are usually the problem.

The thief's transaction is confirmed, so whatever somebody tells you, this means the thefth is irreversible. You can go to the police, but usually they won't even know where to start.
The only thing you can do is look at this thefth as an expensive lesson: buy a decent hardware wallet and move on... Sorry to be the barer of bad news

Soooo.... You've read the rules, and you're going to abide by them...


https://web.archive.org/save/https://bitcointalk.org/index.php?topic=5244695.new#new

I guess that would be your best option. I know that somewhere around 2018-2019 a new recovery team was hired, so i do hope that if you mail them, they'll at least try to help you recover your account. I've heared good things about them. To be honest, i've never had to deal with this issue, so i'm afraid i can't give first-hand advise.

It's a pitty you tought you were dealing with a banned account for so long, however, do realise that IF the account WAS actually banned, you would have commited a bannable offence by creating a new user (ban evasion). I guess this isn't important in this case, since you weren't actually banned.

Have you actually read the message you're linking to?


You are not banned, you probably never got banned. Your account got locked because of security reasons. Did you mail the mail address shown in the image?

Begging for merit is not going to help, making usefull posts is...
I've looked trough your post history, and all i see is that bounty hunter report crap that's filling the forum with nonsense posts. Nobody is going to give you merit for those.

My advice: if you want to become a member, start to contribute meaningfully, learn, help, share... but stop posting all those bounty reports, they bump scamtopics to the top of the unread posts, they fill the forum with nonsense. Most people that actually have merit to give won't give it to a bounty hunter (at least, i won't)

Since you're in the bitcoin discussion subforum, i'll give a bitcoin mining answer: 99,9% of the users seeking advice in this subforum should go for pool mining, unless they're looking at mining as a lottery ticket instead of a steady flow of income.

When you say:

you do not stress how much of an understatement this is for a "home" miner.

At current diff, an antminer S17+ (afaik, the latest generally available ASIC on the market) would (on average) take about 30 years to solve 1 block.

If you own 10 S17+'s, you'll only get "income" about once every 3 years (on average), unless the difficulty would drop... The power costs, on the other hand, would keep piling up.

If you have enough startup money to buy, let's say, >1000 S17+'s, you might consider solo mining a good alternative, since (on average) you'll solve a block every ~11 days, so once you have this kind of operation, it might be a good idear to cut out the middleman and save on those pool fees (and keep the transaction fees) while still being able to pay your bills regularly.

Are you sure this isn't plagiarised from https://www.bitcoinmining.com/ ?

https://web.archive.org/save/https://bitcointalk.org/index.php?topic=5244118.msg54324812#msg54324812

Yeah, if you wanted the balance of an address, the getreceivedbyaddress or listreceivedbyaddress calls would have been a logical choice (you'd still need some extra calls to find/query the funding transactions tough). listtransactions would also be fitting your usecase.  If you're looking for "fresh" deposits, you could also use listunspent (altough as soon as you spend those unspent outputs, they'll no longer be listed, so it might not be a good idear to use this call).

You'll need a decent script to keep track of which transactions were already credited to a user's account and which ones need to be credited tough...

getbalance does not give you any details, so if you're tracking deposits from multiple users, this call does not suffice

This means that you either:

• Imported private key(s) (is that still a thing in blockchain.com?, you used to be able to do this in the past)
• Have a wrong seed/wrong wallet
• Messed up the how-to when creating the electrum wallet
• Have downloaded a fake electrum version, or are unable to connect to electrum nodes

Those are the only things i can think off that would cause this behaviour, other than having a completely infected pc.

Based on my gut feeling, if i was a betting man, i'd put my money on having opened the wrong wallet, resulting in the wrong seed, resulting in 0 balances everywhere you look... It's not impossible the problem is something else tough