The sure thing I guess i need to create a new account to create a Segwit wallet, but I think I'm gonna stick in my legacy wallet since its working great and doesn't encounter any problem in it, I think the only issue here like the others are saying is the fees in a legacy wallet.
To be honest, when you're sending with one or two inputs... or fees are at the 1 sat/byte level, you're not likely to notice much difference in fees anyway... it'll be the difference between maybe 150 sats and 250 sats etc  The differences only become really apparently when some combination of the following occurs: a. Bitcoin price moons to like $100,000, so 100 sats is worth $$$ b. fee rates spike up to 100+ sats/byte type levels, so an increase in transaction size of 100+ bytes == $$$ c. you have large numbers of inputs/outputs in your transactions making them significantly larger than "normal" Seems like you could only edit the seeds when your just creating the account but thanks  . That is correct... if you don't add the word(s)/passphrase when you create the wallet originally, if you try to do so afterwards by "restoring from seed and adding extra words", that will of course generate a completely different wallet with completely different addresses. |
|
|
|
|
If it is becoming unbearably slow... then I'd recommend:
1. Exporting the private keys for the 2 addresses you want to keep from your current wallet (NOTE: make sure you keep the seed for this wallet as well!)
2. Create a new wallet generated by importing those 2 private keys (New/restore -> Import Bitcoin addresses or private keys)
3. Create a new wallet with a new seed (New/restore -> Standard wallet -> Create a new seed)
4. Send everything from old wallet to new seed-based wallet created in step 3.
Then you can keep receiving the transactions on your "old" pool addresses, but have a 'smaller' wallet (just the 2 keys) that won't be slow to load/use etc... maybe consider consolidating any coins from this into your new "seed-based" wallet occasionally.
And you can use the new seed-based wallet for your "everyday" usage.
|
|
|
|
|
Not that I'm aware of... it would probably require the site's API to be updated/modified to allow specific custom client seeds to be used. Additionally, not all sites even support the resetseed() function.
|
|
|
|
Or is it possible to change my current wallet to a segwit? Unfortunately, it doesn't work that way. You need to create a new wallet and select native Segwit as the type. You need to create another standard wallet because the script type of your bitcoin address depends on the seed you are using. So, you need another set of seed phrase to transition from p2pkh (legacy) to p2sh (nested segwit)
Just to clarify what these two users have said... Electrum encodes the "script type" (aka the type of addresses that the wallet will generate) into the seed mnemonic itself. Most wallets do not do this. The result is that when you try to restore your Electrum wallet from the seed mnemonic, it won't prompt you asking what type of addresses you want... it will just automagically generate addresses based on the script type encoded in the seed. Because of this, you will need a "segwit" seed mnemonic... your current mnemonic will only generate "legacy" addresses (unless you do some very advanced and non-standard things during wallet creation). Addtionally, I recommend that you don't do any of the things suggested by DroomieChikito... it'll decrease your security (playing around and potentially exposing private keys) and, because you're using things in a non-standard way, there is a possibility that you'll forget what it was that you did and make things difficult for yourself later on if you need to recover your wallet for whatever reason. |
|
|
|
It's probably safe to just ignore the addresses for now... dumpwallet will have given you something better... the private keys! It should be the at the start of each line, before the date and begin with a 5, L or K... Simply import all those private keys into a nice lightweight wallet like Electrum. It'll quickly scan all of them for the transactions/balances in a matter of minutes. By default, when you import to Electrum it will import them as Legacy addresses. Get Electrum here: www.electrum.org - As always, confirm you are on electrum.org (there are a number of phishing sites)... and verify the digital signatures! |
|
|
|
As far as I know, it's simply an IP/domain-based "blacklist"... likely caused by miscreants abusing certain IP/domains for nefarious purposes in the past... now MalwareBytes thinks anything attempting to connect to these IP/domains using certain ports is "Phishing" or "Exploits"  False positives like this are a real issue... as they make people unnecessarily concerned about legitimate software, but also because they get annoying and then people stop trusting the anti-virus/anti-malware software!  |
|
|
|
By design, any wallet created for a hardware wallet in Electrum is a "watching-only" wallet, as they do NOT contain any private keys. The issue you are running into is the wallet file being encrypted using the hardware wallet device as the "key". During Wallet creation in Electrum (Standard Wallet -> Use a hardware device etc), simply UNCHECK the "Encrypt Wallet File" option:  This will allow you to open the wallet file WITHOUT the device being connected and unlocked. You'll be able to view addresses/balances etc... you just won't be able to send any transactions/sign any messages. |
|
|
|
I am using Electrum as an interface for Ledger Nano, does it mean the wallet file is totally encypted because it does not ask for a password?
There are two ways to use the Ledger Nano and Electrum... 1. Operate with an "encrypted" wallet file, which will require that you connect and unlock your Ledger Nano device before you can view the wallet in Electrum. Effectively, the HW wallet device itself is the "password" to open your wallet file. or 2. Operate with an "unencrypted" wallet file, which you can open and view all your addresses/balances etc, but cannot SEND any transactions without the hardware device connected and unlocked. You are given the choice when creating the wallet in Electrum, and it defaults to Option 1.:  I tried to view the seed but it shows a grey colored "seed" when I connected the HW wallet. Correct, the seed is not stored in Electrum, so there is nothing to view. The seed is safely and securely stored ONLY within the HW wallet itself... and by design is NEVER shown/displayed anywhere after the initial setup. |
|
|
|
You have forgotten to add the --dumpwallet option to your command. You need to use that and --dumpwithbalance. Try this: sudo python2.7 ./pywallet.py --dumpwallet --dumpwithbalance --datadir=/path/to/wallet/ --wallet=wallet.dat
and replace the /path/to/wallet/ with your actual path etc |
|
|
|
Will give it back to you after I earned some from other faucets.
That's OK... it's not expected nor required. In fact I'd suggest sending it to one of the TestNet faucets or perhaps "paying it forward" to another user that would like to experiment... The more people that benefit from being able to "test" and experiment the better as far as I'm concerned. |
|
|
|
No. You're putting that into the "if chance < 49.5" block... so it'll only be evaluated if the chance ends up being set to less than 49.5 I'd suggest putting it right underneath the losecount +=1 line... ...
if (!win) then
losecount += 1
if (losecount == 2) then
stop()
end
...
[code] [/code] |
|
|
|
Hello @HCP, done with all the process I even add already adding bitcoin testnet. I will send you a PM as you promised for some tBTC  it has two bitcoin types segwit and native segwit too. Usually what are you using? Usually just using legacy on testnet to be honest, as it's an old Electrum testnet wallet and I've just never bothered to move the coins! I've sent you 0.1 tBTC to have a play with. |
|
|
|
Also... be careful trying to "find" the ViaBTC accelerator... Last time I checked, there are a number of scammy sites that seem to have purchased google ad words and/or similar domain names... DO NOT use any of the following: viabtc-accelerator.com viabtc-com.com viabtc-transaction-accelerator.com www .btcaccelerator.net As far as I can tell, they are all SCAMS The correct url for the ViaBTC accelerator is: https://www.viabtc.com/tools/txacceleratorAnd it looks like this:  |
|
|
|
I know that there was an Electrum wallet on it, so I downloaded Electrum onto a new device, chose "Standard Wallet" --> "I have a seed", entered the 12 words, and... nothing. The wallet is empty, no funds.
There wasn't much in it; I bought a tiny amount of LTC in 2017 I think, and left it alone when the value went down... nowadays it's probably worth nothing! But still I would like to know why the wallet doesn't recover it correctly.
This is your problem.... Electrum is BTC only... if you had LTC, you'll need to get Electrum-LTC... and restore your wallet in that using your seed. NOTE: Electrum-LTC is NOT created by the Electrum devs... it is a separate project. |
|
|
|
this is a situation where using [ code ] tags and properly indenting your code makes things a lot easier! chance = 95
basebet = .000001131
nextbet = .000001131
bethigh = true
losecount = 0
enablesrc = true --set to true to use stop/reset conditions
--settings from advanced mode
function dobet()
if (win) then
chance = 95
nextbet = basebet
losecount = 0
end
if (!win) then
losecount += 1
if (losecount > 1) then
nextbet = previousbet*1.75
chance = (1/(((nextbet+(nextbet-basebet))/nextbet)))*100
if chance < 49.5 then
chance = 49.5
end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
else
nextbet = previousbet*1.75
chance = (1/(((basebet+nextbet))/nextbet))*100
if chance<49.5 then
chance=49.5
end
bethigh = !bethigh
print ("LOSE")
print(nextbet)
print(chance)
print(profit)
print(bets)
if (losecount == 2) then
stop()
end
end
end
end
Looking at that indented correctly, you can quickly see that your "if (losecount == 2) then" statement is actually contained in the else section of an "if (losecount > 1)" statement: ...
function dobet()
if (win) then
...
end
if (!win) then
losecount += 1
if (losecount > 1) then
...
else -- losecount must be <= 1
...
if (losecount == 2) then -- THIS CAN NEVER BE TRUE HERE!
stop()
end
end
end
end
So, basically, your highlighted code will never get executed... because losecount cannot be <= 1 and == 2!!?! You might want to make sure your code is properly formatted in future so that you are actually adding your code into the correct section and not accidentally adding it into another section by mistake. |
|
|
|
So it just exports a plain QR code image? That's really bad for security, especially as I imagine the vast majority of people are just going to save the QR code to their computer as opposed to printing it out. That would be like your password manager exporting all your passwords in plain text, and you saving them all in a text document on your computer. Good 2FA apps (like Aegis mentioned above) let you export to an encrypted file. I don't believe that it is meant for creating a meaningful backup per se... if you follow the wording of the workflow, the point of the QR codes that it is generating, is to allow you to migrate to a new device... That is to say: 1. Install GoogleAuth on new device 2. Create QR code on old device 3. Scan QR code using GoogleAuth on new device et voila, 2FA accounts transferred to new device. You're not supposed to generate the QR code and then actually store that QR code somehow... although, you could certainly try and abuse the functionality. However, there is no option to "save" the QR code and screenshot functionality is disabled within the GoogleAuth app... although you could use a camera to take a picture of it I guess. |
|
|
|
For this code as i have left #should be ' ' blank should i addin my corrupt key with a random letter at the end to add it up to 52 characters?
# Provide a WIF private key with a single missing character.
# Wrong Char
corrupted_wif = 'KykLRngWxXA8RkznbcQ5UzJbD2QfABiR9E6yVGvigHo2WrwBeGm'
# Should be: ''
# Missing Char
for candidate_wif in candidate_wifs(corrupted_wif):
print(candidate_wif) You only need to put your "corrupted WIF" in on the line that says: corrupted_wif = '.................' The "#should be" line is just a comment in the code, it will not be executed so can be left blank. As long as you have the line: corrupted_wif = '<WIF_MISSING_ONE_CHAR_GOES_HERE>'
Filled out correctly, then it should work OK! |
|
|
|
So, I've been offline for a couple of days... and come back to whatever this thread has devolved into... but if I'm reading this correctly: WOW777 accidentally posted from their alt account "TITANxp"... offering to give several users, including myself 1BTC... and then deleted the message... and then tried to make out that they had been scammed for 2BTC. Am I correct so far?  Looking at TITANxp's post history, they appear to be trying to sell wallet files for $10... This possibly rates as the most bizarre, convoluted "bogus wallet" selling con that I've seen. Thanks for the entertainment! |
|
|
|
5 Days? That's not so terrible. Not exactly great, but not super terrible. Just to confirm... that test was using Windows 10 as the OS wasn't it? you're not using ubuntu or some other flavour of Linux are you? |
|
|
|
|
Show Posts
