Hi there,
today during cleanup of my old files I found (probably) bitcoin wallet with file extension fw2. Is there anyone who knows what SW should I use to try it to open?
It seems that fw2 is SQLite database file which has internally encoded all data so I'm not exactly sure what the file is containing. There are (Card, CardData, Category, Metadata and TemplateData) tables.
Thanks for any clue!
From here http://filext.com/file-extension/FW2it says "FlexWallet". Never heard of that though. |
|
|
|
Some wallets, for instance the Samourai wallet; offer the ability to connect to a trusted node (your own)
Wouldn't it be great if this could be done by simply scanning a qr-code..
I’m sure that if this functionality was built directly into the Core GUI, then most of the wallet providers would adapt and make it super easy to pair your node and your phone.
So what do you think?
Is this possible / desirable?
The probleme here is, that for this functionality, you need to have a listening server at your bitcoin-core and opened a specific port in your firewall, and port forwarding enabled if you have a router and want this to work over the internet (and a static IP address or dynamic DNS). I could continue this list here. So, there are many things to setup, which just can't be setup through a simple QR code. A simple QR code would be possible, if everything was centralized. But as you run your node on your own computer, you have to do the whole setup your own. And that highly depends on your environment and how your node accesses the internet. So, to sum up: It's not that simple and there is no easy way to simplify this "trusted node" connection. It would surely be nice if there was one, but it's just the decentralized technology itself which makes it difficult. |
|
|
|
so it took me a few days to finally finish downloading the chain with bitcoin core when it was done i added my old wallet it rescanned then after maybe an hour it gave an error then the pogram crashed now whenever i open bitcoin core it says rescanning which takes over an hour then it crashes again after it opens randomly here is the debug.log file hopefully someone can help me i have an i3 cpu with 8 gigs of memory and its being saved on a sata drive not an SSD https://pastebin.com/M0d3bHHqDo you have your wallet.dat on your internal disk? If not, that may also be a reason. For example, I had it on a NAS once and faced the same error. Just make sure your wallet is located on an NTFS file system. |
|
|
|
|
I never actually faced this error in the logs "flood attack".
Did you change anything in the default configuration? Does this happen continuously or only at specific times?
Maybe it could be that there are many nodes that need to download the blockchain nearby, causing this flood, but I'm just guessing here.
|
|
|
|
There are many popular wallets which have quite secure seeds and generate mnemonics which are quite difficult to crack in reasonable time.
But I just want to know if I generate private key from my own 400 digits (only numeric) then how it would be less secure than 24 mnemonic recovery phrase?
With 400 digits there are (10)^400 = 1e400 possibilities, with 24 mnemonic recovery phrase (assuming only small letters and an average word length of 8 characters) there are 26^(8*24) = 5e271 possibilities. There are even less as here I count all possible char combinations, but in an mnemonic, there are only words that make sense. But just as a rough estimation, it should be ok. |
|
|
|
|
You would have to consider lots of details you are probably not aware of now.
There might be some security advantages by not having the code opened to everyone (security by obscurity), but on the other hand, as soon as you have open ports, there may be other kinds of attacks on your client that make it even more vulnerable than the proven standard clients, such as memory leak attacks. And furthermore, you can see from the protocol that your client will behave slightly different than the normal one. So an attacker may detect this and focus even more on attacking your client, so it might evoke even more attention than if you just go with the masses and use a standard client.
|
|
|
|
Bitcoin.conf :
prune=550
rpcport=8332
maxconnections=125
maxuploadtarget=0
rpcuser=USERHIDDEN
rpcpassword=PASSWORDHIDDEN
daemon=1
keypool=100
I don't know about the current defaults, but a may also help |
|
|
|
|
Look at the horizon and note what you can see. Climb up a hill and look at the horizon again. If you can see farther, the earth cannot be flat.
|
|
|
|
|
It can happen and even without your wallet rebroadcasting the transaction, it may still be a longer time in the mempool. Some clients don't forget the transactions in the mempool that rapidly, I had to experience this as well.
|
|
|
|
When I first came into contact with it, 1 BTC was a little bit less than 700$. I see a lot of regrets here. Maybe the price will be twice tomorrow. And there will be regrets again  I think you cannot really regret anything here, as the market at earlier times was so unpredictable, one could as well have lost a lot of money, if everything went different. One should rather be happy to be finally on the boat and and be one of the few people on earth to experience the next big growth  |
|
|
|
|
The log file is in the folder of your client.
You can download the client as *.zip file and then you only need to extract it. In that case, you would need no uninstall, you can just run it out of the "./bin" folder
|
|
|
|
|
Death penalty just has got no place in a modern, cultivated and civilized society. That's it.
Often, the perpetrators suffer from psychical issues, which is a lot of suffering already.
With our knowledge today, there would be many possible institutions that could help such people, nevermind the fact that we have the technology to provide for them to be arrested as long as necessary and therefore to prevent any further damage to the public.
Today, we should be at a point to get rid of medieval methods and try to arrive at the 21st century.
I can only support the European supplier decisions.
|
|
|
|
|
This is interesting. As with all now established currencies and systems, there were a lot of haters and people who didn't believe in it.
Starting solely from its long existence already, bitcoin has proven to be stable. In my opinion, it's only a question of time when the public interest will rise (you probably need to have a few role models that have a lot public impact that spread the word), and then, the value growth will go on rapidly.
|
|
|
|
|
As you are new to coding, whatever you do, try it on the testnet first in order to prevent losing btc.
|
|
|
|
Especially for npm I can recommend you the bitcoin plugin which does the TCP communication handling for you: https://www.npmjs.com/package/bitcoinIf you want to work with promises (resolve, reject) instead of classical callbacks (which I definitely can highly recommend if you want to avoid ugly code), then this plugin should be very helpful: https://www.npmjs.com/package/bitcoin-promise(It's also what we use at foxmixer.com to generate the addresses out of the bitcoin client). |
|
|
|
If you have a general intention about what should happen to your bitcoins after your death, there might be a solution to do it, that I have long been wanting to realize but I didn't have the time yet: Some sort of script / application that you can control from your smartphone in regular intervals using a password. If this confirmation does not happen anymore within, let's say a year, you could define a payout to somewhere (a friend, spouse, donation, whatever). What you have to make sure is that the server on which the script is running also does so a year after dying, so maybe a vps or something that can be payed ahead (supposing you have enough trust in your vps provider ). Advantage of this way would be that you would not have to tell anybody of this ahead. |
|
|
|
|
Thumbs up on this one. Thanks for the work you put into it. Nice video to convince newbies to join the bitcoin community.
|
|
|
|
My username is Casy  I'd like to improve several pages and fix minor bugs. |
|
|
|
|
Show Posts
