 Show Posts
|
|
Pages: [1]
|
If you have opted in for RBF for the transaction, it means you have attempted double-spending, therefore, miners find it hard to fasten such transactions. I will suggest you wait for the network to forget about the transaction for your transaction to be cancelled back since your fee is very low, then you can use sufficient tx fee next.
i gave it a rest and completed my tx. all is well. love this community! |
|
|
|
rbf was enabled however i wasn't aware that i needed to have actual btc in my wallet at the time i submitted the tx. i obviously thought dumping more into my wallet to cover a lower tx would suffice but no. lesson learned. i f**king love bitcoin but sometimes it scares the s**t out of me. i think we're hunky dory. previous tx is abandoned and new tx w/ higher fee is in mempool. for some reason the hash isn't showing in any explorers but maybe that's because the abandoned tx is still lingering and thinks it's a double-spend attempt? idk. i'll sleep on it and see what happens tomorrow. i at least know how to get that abandon tx selection to work now as it's always greyed out for me. besides, not in a rush. thx for helping though. |
|
|
|
money. i knew someone here could help. deleting the mempool.dat file, cause abandon tx was greyed out, worked for me. much appreciated. stay well. |
|
|
|
|
@TryNinja
yeah, i noticed that blunder.... i know exactly what my mind was thinking and it's making me nauseous right now. i'll take a look at this post. thx.
|
|
|
|
|
this pandemic is getting old. i did it again... day drank and thought i was being a smarty pants and tried transferring my FULL remaining core wallet amt to an exchange to, i don't know, sell the top? All I know is when i woke up the next day i had nothing in my wallet and nothing went through. it's stuck. i clearly see now what i did but my scotch eyes cleary didn't. can someone please explain to me cpfp and if, or how, i can do it in core? i am using 0.21.0. I do have a backup core wallet on an old linux box and am running that as it's the full node, not pruned like this one on my laptop.
this is what i have in core:
Status: 0/unconfirmed, in memory pool
Date: 2/16/21 14:26
To: xxxxxx
Debit: -xxxxxx sat
Tx fee: -540 sat
Net amt: -xxxxxx sat
tx id: xxxxxxxx
Tx total size: 1103 bytes
Tx virtual size: 540 bytes
Output index: 0
i might add that none of the block exp are finding the tx except blockchair and txfee dot org. also tried the accelerators and they all give me errors. idk.
thx. need to quit drinking. pandemic has gotten a hold of me.
|
|
|
|
Everyone you are communicating with on the internet (e.g. websites, microsoft server, games server, basically whatever you do with your PC which has to do with the internet) has your IP (or at least he IP of your ISP if you are sitting behind a NAT).
This has no security implications at all.
In fact, it is necessary. An IP address is absolutely NO private information. It is absolutely mandatory to communicate.
Therefore each node you are connected to, sees your IP.
If you additionally accept incoming connections, they are connecting to your PC (on port 8333).
As long as there is no severe vulnerability in bitcoin core, that's completely fine.
Theoretically, a chance exists that a specifically crafted message can crash core, for example.
Or, which would be the ultimate MCA, a remote code execution with the permissions of the user running core.
The attack surface exists.
The theoretical chance of such a vulnerability also exists. But since core has been here since the beginning of BTC, it gets less and less probable each day.
Core is a properly tested software. Not some student-project.
I, personally, would assess the risk as being low or very low.
If you are using windows, you shouldn't be worried about THAT at all. Windows has way more vulnerabilities which are way more severe than bitcoin core will ever have. And most of them stay unfixed for a long period of time.
This is the conversation I had with beautyon a couple years ago when he was first helping me setup a node on my linux box. So much time as passed and I got involved in so much else that I kind of forgot about everything we discussed. NAT. I recall he wasn't 100% on whether or not my router or even modem served as a NAT but for years I was under the assumption that they did? |
|
|
|
I wanted to add a sidenode to your pruning setting: you do have to realise that when you run a pruned node, a reindex will force you to re-download the complete blockchain again.... So, eventough running a pruned node is fine, it does limit some of the functionality.
At least you don't need to verify all block & transaction (according to https://bitcointalk.org/index.php?topic=5099606.msg49318747#msg49318747). For normal user, obtain old transaction/block usually isn't needed anyway. I took it a step further. I have a laptop (computer A) running a pruned node (took less than 30 seconds to go from full node to pruned node) and a box (computer B) that doesn't get used for anything except running the node and that's running a full node. I currently, although it may not be great, have them sharing one wallet, plenty encrypted. For now, it's just for fun and learning, only keeping a few sats. Now I just need a for dummies on how and which lightning node to install. |
|
|
|
That actually brought up a 2nd question for me: pruning. I have the same wallet.dat file currently synced between two computers, two different OSes and one of them has a lot less disk space so I'm planning on pruning it right now. I'm thinking of just pruning to 20% of my current disk space as that would allow enough room for my other stuff. As far as I can tell from the research I've done I just need at least 550 MB for pruning. Correct?
You can specify how much space you want to store in blocks. E.g: prune=550 would store 550 MB of blocks, prune=5000 would store 5 GB, etc... Keep in mind that even when pruning, you will still have to download the whole blockchain (however, it will delete the old blocks on the fly, so you don't need the +200 GB space). And that's going to take some bandwidth. Just completed it. Since the blockchain was already downloaded it only took about 30 seconds to prune it. Good for my laptop node. Thanks for the input and advice! Cheers! |
|
|
|
3. You're connected to many nodes and open ports which add security vulnerability
This was the one question I had as well but if I'm running my node through something like a router that doesn't broadcast my private IP address I was told that's fine - no vpn or silly garbage like that needed. Networking was never my personal strong suit, better at hardware and building computers. |
|
|
|
Why do some folks recommend one does not use node as a wallet?
The only reason I can see for someone to not have their own node is if they don't want to have the whole blockchain downloaded in their device. A node uses a lot of bandwidth and take several GBs of space in your hard drive (for the blockchain which needs to be "updated every day"). Other than that, I can only see advantages. That actually brought up a 2nd question for me: pruning. I have the same wallet.dat file currently synced between two computers, two different OSes and one of them has a lot less disk space so I'm planning on pruning it right now. I'm thinking of just pruning to 20% of my current disk space as that would allow enough room for my other stuff. As far as I can tell from the research I've done I just need at least 550 MB for pruning. Correct? |
|
|
|
|
Why do some folks recommend one does not use node as a wallet?
|
|
|
|
|
