|
Unless you have access to the private key (or can export it from block.io) then your chances of being able to do anything are relatively slim. If you had the private key, you could probably import it into another wallet (like Electrum) and then send a new transaction with a proper fee.
Given that most block explorers can't even see that transaction, it is likely it hasn't propagated well, so most nodes wouldn't even reject the new transaction as a double spend.
|
|
|
|
Unrelated:
Public service announcement:
In the past i was able to help people using 3 tactics:
1) push their transaction to antpool's priority queue
2) push their transaction to ViaBTC's free priority queue
3) give them advice on how to create a CPFP, RBF or double spending the inputs of the unconfirmed transaction
However....
1) Lately, somebody, has been spreading around the link to antpool's priority queue, so people who are cheaping out on their fees can abuse this system to save a couple of bucks
2) ViaBTC's free slots are gone in less than a second... I haven't been able to push a single transaction to their queue today
3) I can still give advice on CPFP, RBF or Double spending... However, do know that this advise is rather technical...
So, from now on, i will only help people to fix their own problem... I will no longer be pushing their transactions to priority queues... I haven't discussed this with HCP (yet), but i do hope he shares the same idear....
Sadly, it seems like the ones who were spamming AntPool accelerator have now switched to ViaBTC. I get the impression people are botting it to get transactions submitted to gain "tips"...  Once again, the greed of a few has ruined it for everyone else  What this means, is that there are now pretty much no "easy" options left for getting transactions unstuck. I will continue to try ViaBTC (and AntPool) when and where I can, but what used to be pretty much a guaranteed confirmation is now maybe a 1% chance at best. To avoid issues, please either pay the required Bitcoin fees, (or move to altcoins  ) |
|
|
|
As I already suggested to you via PM, the most likely cause is that the site is reporting the balance incorrectly. The bot does not calculate your balance, it simply reports the balance given to it by the gambling site API. If there is a problem with the figures being reported by the API, there isn't a lot the boy can do about it... Garbage in, garbage out I would theorise that running multiple bots on the same site (same account?) Could be causing issues with the site reporting incorrect balance figures... If you run one bot does and slow the betting down, does this problem continue to happen? If it doesn't then the problem is definitely the site and not the bot. PS. On an unrelated note, You should be careful running multiple accounts on gambling sites, most sites disapprove of this behaviour and may ban your accounts and possibly freeze your fund!  |
|
|
|
You can get BTG out of a 2FA wallet... It's not the easiest task in the world, and requires that you have the BitcoinGold Core wallet installed and fully synced... But it is definitely possible. Have a look at the fairly lengthy tutorial here: https://bitcointalk.org/index.php?topic=2550529.msg26001755#msg26001755There are also services that will do it for you (for a fee of course) |
|
|
|
|
That only shows the "Master Private Key" aka "xprv"... you still need a way to generate the addresses and individual private keys from that... I believe that guys wants Mycelium to give out the individual WIF format private key for a given address...
|
|
|
|
I think I'll wait until either BTG is worth more or Electrum starts supporting it.
Might play around with that after the new year though just to learn all this a bit more.
I can tell you now that "Electrum" will likely never support BTG. Given ThomasV never even "supported" BCH which was a much "bigger" fork in terms of mining support and value... I very much doubt he has even looked at BTG What you need is a 3rd party dev (or the BTG dev crew) to create a fork of Electrum that works with BTG... like Jonald Fyookball made with ElectronCash. Again, that project like ALL Electrum forks is not developed by the Electrum devs or supported by them. I'd suggest contacting the BTG via their social media contacts for updates on whether they intend to release an Electrum compatible wallet. |
|
|
|
|
As far as I'm aware, there is no way to do this within Electrum itself... you'd need to dump the codes out and then run them through an external QRCode generator of some description.
The console in Electrum is a very basic Python Interpreter... and is not a "full" Python environment... and not able to affect the Electrum GUI as far as I can tell.
|
|
|
|
Thanks so much This is best explanation I've heard to date anywhere. Question: how long does it take to fall off the mempool? And does Electrum try to resend the transaction?
It can take anywhere from 72 hours to 14 days... the newer versions of Bitcoin Core (kind of the "default" Node software) are setup to have a max mempool time of 14 days... earlier versions were 72 hours... but node owners can set this value to whatever they want. It's possible that Electrum does rebroadcast... I honestly don't know for sure... I'm not sure if there is a way to stop it (ie. no "walletbroadcast=0" type option that I know of like Bitcoin Core has)...  I can't recall if Electrum has a "cancel" transaction option if you right click on it |
|
|
|
guys im not infected. i never downloaded anything unknown. that client downloaded from the site itself
Huh? you mean Electrum Auto downloaded and installed itself? if so, then it definitely sounds like you got a scam version. Electrum has NEVER had an autodownload or update feature that I'm aware of... That sounds highly suspicious to me. and noone know that i have btc so i believe its a bug or anyhthing like that
when i tried to increase fess for last transactions money gone.
No one needs to know if you have BTC or not... if you're running a scam version of the software, the hackers don't need to know who you are or where you live. They'll have your private keys. Just because nothing happened for a while doesn't mean your wallet wasn't compromised. They may have been waiting for big deposit or for BTC value to increase etc. I very much doubt that there there is a bug in the wallet so big that it autosends coins to some random address... that's a ridiculous claim. The more likely answer is either your wallet got compromised by something you did (claimed any fork coins lately? exported your private keys? typed something into a website?) or by a scam version of the wallet. Have you confirmed the digital signature of the file you downloaded and installed? |
|
|
|
the seed recovery script would fix this for you in a matter of seconds... https://github.com/gurnec/btcrecover/blob/master/docs/Seedrecover_Quick_Start_Guide.mdIf you're not able to follow the install instructions, as advised above, you would need to find a (very) trusted 3rd party to run it for you. Once found, you should consider the seed completely compromised (as it has now been entered on a device other than your nano) and you would be well advised to move your coins to a new wallet with a new seed as soon as practical. |
|
|
|
There is no obvious way to tell if a transaction has been "accelerated" or not... and I doubt anyone receiving bitcoins would even care. Why would they? They got their bitcoins... Anyone can "accelerate" any given TransactionID (assuming the transaction satisfies the conditions of the service they're using, ie. for ViaBTC, min 10 sats/byte fee and no unconfirmed parent transactions). You could for instance just look at any random transaction waiting in the mempool and go and accelerate it on ViaBTC assuming it met the requirements. ViaBTC only provides 100 slots PER HOUR. Given how high fees are right now, and the 100,000+ unconfirmed transactions out there, it is understandably a VERY popular service (nevermind the scores of users trying to leverage it for income by "begging" for tips to accelerate peoples transactions  )... Their website is possibly suffering under the strain when thousands of people all click submit at the top of hour... personally, I have had a great deal of success with it... (assuming I haven't screwed up my fee calculation and sent with a fee <10 sats/byte ... but we won't talk about that!  ) |
|
|
|
4. I went to Home and opened the newly installed Armory. It ran its opening scans and was then online (I trust the BCH chain?). I “Import or Restore Wallet” using the Root Key. I then had the same wallet on both Home and Work. While importing the wallet it got stuck on “scan transaction history”. I’ve restarted, let Bitcoin ABC run until its up-to-date and still no luck. It constantly gets stuck with only a few seconds left on the “scan transaction history” stage.
I suspect we're going to need to see the Armory logs to understand what is happening... armorylog.txt and dbLog.txt (or export logs from within Armory). Copy/Paste the contents of your log files to https://pastebin.com/ click the "create new paste" button and then cop/paste the generated URL for your paste here. |
|
|
|
You didn't answer my question... What is LTE wallet?? the .asc file will be the signature/hash file used for verifying the digital signature of the wallet installer file... it is of no use to you when trying to recover a wallet. It was a completely empty wallet with no history. Balance: 0.mBTC I know I have the correct seed.
Like I said... Assuming that Electrum is connected (green dot) and properly synced (click "tools -> network" and see if you have the same number of blocks as the current blockchain height (check current height here: https://blockchain.info/)... ie. if current height = 499717 and Electrum has 499717 blocks then your Electrum is properly synced.)... If your seed is not showing ANY history... then you have the wrong seed... You may have typed that seed in 100% according to what you have written down, but it is NOT the seed for the wallet you think it is. |
|
|
|
No one knows for sure... what you need to realise is that these "within X blocks" things are ESTIMATES ONLY! (based on the network conditions/average fees AT THAT TIME) There is ZERO guarantee that if you select 1 block, that it will only take one block... it could be that 100,000 people send transactions 1 minute after yours with fees that are all higher... your transaction gets bumped to the bottom of the fee size pile, you end up waiting 2 days. All you do by increasing the fee, is increase the odds of getting a faster confirmation than if you set a lower fee. As every says ALL the time... check here: https://bitcoinfees.earn.com/ and here: https://btc.com/stats/unconfirmed-tx and then set your fee RATE accordingly. Remember it has NOTHING to do with the $ value or the total value of your fee... it is the RATE (satoshis/byte or BTC/kB) that will likely determine how soon your transaction is picked up. For example, 10000 byte transaction with 10 sats/byte fee = 100,000 satoshi fee (0.001 btc)... will likely take a LOT longer than a 226 byte transaction with 300 sats/byte fee = 67,800 satoshi total fee (0.000678 btc) Turn off dynamic fees and set your fee manually at your own risk. |
|
|
|
Yes, that new address has a new private key... however, if you have an HD wallet (does it have the HD symbol in the bottom right corner or is it crossed out?) there is a chance that having one compromised private key could compromise your entire wallet (as all the private keys are "related" in a very complicated mathematical way) If it is non-HD wallet (HD symbol crossed out) all the private keys are randomly generated and not related. The only "risk" comes from accidentally using that compromised privkey/address again in the future. In my opinion, the safer option is to move to a new wallet... but moving all the coins to a new private key/address is definitely better than doing nothing. Also, can I name the wallet.dat file anything I want or does it always have to have the .dat extension to work?
I believe that Bitcoin Core allows you to specify the wallet file at runtime using the -wallet option, so theoretically you can name it whatever you want... wallet.dat is just what it defaults to if no wallet file is specified. You might want to be careful renaming it... I've seen posts by several users on here that have previously done this and then been unable to remember/locate the file at a later date Also can you please help me understand how to do a rescan of the blockchain within Bitcoin Core client?
to do a rescan... simply start it using: path\to\Bitcoin\installdir\bitcoin-qt.exe -rescan
On windows... likely to be something like: C:\Program Files\Bitcoin\bitcoin-qt.exe -rescan or add rescan=1 to the bitcoin.conf file in your Bitcoin data directory (where your wallet.dat is)... if you don't have a bitcoin.conf, just make one using a text editor. Just remember that once you have done the rescan, you should remove rescan option from your bitcoin.conf or it will do it EVERY time you start the program! |
|
|
|
p.s i dont using this scripts. i given it like sample.
See... the thing is, is that you're asking us for assistance with your issue, but you are giving us a script that you're not even using. Without seeing your ACTUAL code, there is no way we can debug it and have any certainty how or why your script is broken... or if it is the bot that has some weird overflow issue. I understand this is because you have some "super secret" strategy that you don't want to share (given your redacting of bet amounts/chances etc), but working under these conditions effectively makes anything that we suggest or theorise, pure guesswork. You will need to either give up the code (PM is fine if you're rather it was not made public) OR you will need to debug the code yourself... If you want to try and debug it, do what chilly suggested... put a check right at the end of the dobet() function: if nextbet < 0 then
print("nextbet: " .. nextbet)
print("base: " .. base)
print("someVariableThatYouWantToSeeTheValueOf: " .. myVariable)
print("profit: " .. profit)
stop()
end
This will enable you to see what the various values of things are to try and figure out WHY it is attempting to generate negative bets... and stop the bot at that point to avoid it losing money etc. |
|
|
|
A CPFP strategy will most likely NOT help you here. CPFP requires that you create a 2nd transaction that pays the "proper" fees for BOTH itself AND the previous transaction! In effect, you're actually paying more because you have to pay for the 2nd transaction as well! For instance: Transaction 1 = 60,000 bytes @ 5 sats/byte = 300,000 sats <-- Stuck due to low fee Transaction 2 = 226 bytes... ?fee rate? CPFP fee = (Total Size of Both Transactions * Proper Fee rate ) - amount already paid lets say a "proper" fee is 400 sats/byte... so you need to pay: ((60,000 + 226) * 400) - 300,000) = 24,090,400 - 300,000 = 23,790,400 sats = 0.237904 BTC A miner would now see your second transaction offering a MASSIVE fee rate of 105,267 sats/byte... yes, 105K sats/byte... and be like "I WANT IT!!!?!"... but to get it, they also have to include your unconfirmed transaction...  So, intentionally setting up a transaction that requires CPFP is likely to cost you more than just paying the proper fee in the first place.
At this stage, I'd say your best course of action was to wait for the transaction to fully drop (you may need to prevent your wallet attempting to rebroadcast)... after it has dropped, redo the transaction in smaller "chunks"... use a fee of AT LEAST 11 sats/byte (to account for rounding issues)... and then accelerate each one using ViaBTC... it'll take a while, (you have a metric shitton of dust by the looks of it ) but you should get there in the end. I'd recommend maybe no more than 20 inputs per transaction, just to keep the size down and make it less likely for that to cause issues... then after all those transactions are confirmed (will probably be around 30-40 transactions in total), you can then do the same thing with all your new UTXOs... granted, it isn't the "cheapest" solution in terms of total fee or time required, but you should end up paying no more than maybe a total combined fee of around 15 sat/byte... still going to be around 0.009 total fees... but that's unavoidable really. In future, you should probably try combining them a bit more regularly... especially if you spot a time of either low total transactions and/or low fees... your wallet is like a car, proper care and maintenance will help prevent issues or just don't accept/collect dust |
|
|
|
|
It sounds like the real issue here is that your blockchain is NOT synced... If you don't have a lot of harddrive space, you have two options:
In both cases, please please PLEASE ensure you have made (several) copies of your wallet.dat before doing anything... 7 BTC would be a LOT to lose.
Option 1. Run Bitcoin Core in "pruned" mode... this will still require downloading the total 180Gigs of blockchain data... but it will only "store" up to the maximum size limit set... I believe the minimum is something like 550megs... I'd recommend say 5-10 gigs as a "reasonable" amount.
PROs:
more "secure" than Option 2, no need to export private keys
CONs:
The issue with pruned mode, is that if you need to "rescan" or "reindex" at any point... it will most likely need to redownload ALL the blockchain data again.
SLOW
Option 2. Dump the "1mAo" privkey from the wallet that is currently showing that address... import that privkey into lightweight wallet of your choice (Personally, I'd recommend Electrum).
PROs:
Quick and easy
Doesn't require downloading full blockchain
CONs:
Less "secure" as it involves exporting/importing private keys (not something to be done lightly with 7 BTC on the line)
Privacy concerns of running transaction via a 3rd party node.
As you can see, both options have some PROs and CONs... you need to work out with is more important to you... security or convenience, then make your choice as appropriate.
If you have access to a second PC it is possible to "reduce" your risks by doing the export/import "offline" etc...
|
|
|
|
|
Because it was generated from a 2fa seed... And it's still technically a 2FA wallet... Ie. MultiSig, you've just disabled The requirement to use TrustedCoin on THIS copy of the wallet as it now contains two private keys, so can sign the "2of3" transactions without using TrustedCoin.
The other output is most likely change... You can tell if the output address in the preview window is highlighted in "yellow"... That equals Change address. Receive addresses should be highlighted in green.
|
|
|
|
|
Show Posts
