Backing up your wallet - Bitcoin Wiki

The International 2018 in Vancouver FAQ (Updated!)

Hey there again, you punks.
So with a tip coming from some of the moderators on the board, I've decided just to quickly update this FAQ that I wrote a few months back since TI is next week and I'm sure many of you still have a ton of questions. I've gotten some more information that I can pass down to you in regards to Vancouver but also now TI as well, including updated marijuana laws and beer recommendations.
Two quick notes:

VANCOUVER WEATHER

This summer has been an extremely hot season in Vancouver (at least in Vancouverite standards). Like anyone who attended in Seattle last year, there is noticeable smoke in the air in the city due to the fires all over the Pacific North West. If you have breathing issues or health related problems do to particles in the air, be advised that there is currently an Air Quality Advisory in effect so act accordingly. Wind/Rain will most likely clear up any issues going into next week, but just a heads up in case new fires flare up or we aren't blessed with some light rain. Forecast is looking to be sunny through midweek and the finals, with an average of about 23-25C.

THE PACIFIC NATIONAL EXHIBITION IS OPEN!

A staple for Vancouver residents since 1910, the PNE will be open from August 18th-September 3rd (closed on August 20th & 27th). If you're looking to do something after a midweek day, the PNE is the perfect place to go checkout for a fun night out filled with events, concerts, beer gardens, crazy carny food, rides, maybe BSJ, shopping and a lot more. This article will tell you everything you need to know about the PNE, how to get there and what's going on.
ALSO BOYZ II MEN AUGUST 18TH GET HYPED.

PLACES TO STAY

Yes, but it's not exactly regulated by AirBnB. Feel free to stay at one through AirBnB but know that it might be a little tricky to deal with issues if they come up with your rental. Also while you're at it, check out VRBO.
The general piece of advice you'll get from any local about where to stay for TI is going to be anywhere that's on the Skytrain Expo Line (the line in dark blue). The Expo Line will take you to Stadium-Chinatown station, which is where Rogers Arena is 30 seconds away. As in Seattle, the closer to downtown you are, the more expensive it is to stay.
Unlike Seattle Center, there aren't very many budget hotels left, if at all in the Downtown core. The cheaper hostels are available, though fair warning, many of them are placed on Granville Street, which is a place that many Vancouverites will tell you to avoid while you're here (Though I have never stayed at a hostel on Granville, if anyone has an experience, feel free to share). Check out the Ramada Inn and the Days Inn near Waterfront for some cheaper-ish options.
In my mind, there are two places that I would keep a look-out for avoiding while you visit Vancity.
  1. Granville Street. During the day time it's normally fine, filled with some cool shops (Golden Age Collectibles, The Rock Shop, Movieland Arcade) but it's packed to the absolute max with dumbasses at night due to the amount of night clubs. There's police around every weeknight, but since you're in Vancouver for a good time, head towards Gastown, Chinatown or Main Street for places to party.
  2. Downtown East Side. If you've researched anything about Vancouver, you'll know that this area as where a large portion of the cities homeless reside. There is rampant drug use, poverty and sex work in this neighborhood, focused mainly between 5-10 blocks in the area of Main/Hastings. That being said, the community is an especially strong one, with fantastic human beings supporting the less fortunate. Though there isn't too much danger in terms of being robbed, you might want to just avoid the area at night. Be respectful to the people of this community and you'll have no problems.

TRANSIT

Sadly, no there isn't. We know, it absolutely sucks and everyone in Vancouver is aware. Your options are public transit or a taxi.
Super shitty if you don't like paying for parking. If you can, park outside of the Downtown core near a Skytrain and then head over to the Arena. Commercial Drive is pretty good for this if you can find certain spots. Tinseltown as well if you buy a movie ticket on non-event days.
If you've ever been to any major city, you'll notice that Vancouver shares the same load-up card/tap system that places like London share. It's called Compass Card and it's fairly easy to use. Just load up money onto the card, tap it when you enter and tap when you leave. It'll do all the calculations for you. Note that certain zones will cost more just due to how far you're traveling.
Yes it does! Car2Go and Evo are two of Vancouver's most popular car share services. Hot tip would be to register before you head over to Vancouver and it'll help mitigate the fact that UbeLyft aren't in Vancouver just yet. Just drive safely.
The easiest way to get to downtown from YVR, if you aren't getting picked up/taking a taxi is to take the Canada Line. It will take you directly to Waterfront station, from there you can take multiple buses, the Expo Line (the main line that will take you to Rogers Arena) or the Seabus (going to North VancouveLonsdale).

ALCOHOL

19 years old.
Vancouver has an exploding craft beer culture and you'll be happy to find that the variety of different beers/ciders to drink is absolutely massive, probably to the point of being intimidating.
Here are some of my favorite breweries and the beers that you should look out for when you're at the liquor store/pub:
Twin Sails Brewing
Dat Juice Pale Ale
Two Straws MilkShake IPA
Short Pants Mosaic IPA
Brassneck Brewing
Changeling Sour
Passive Aggressive IPA
Bjorn Again Farmhouse Ale
Steel & Oak
Changeling Sour
Passive Agressive IPA
Bjorn Again Farmhouse Ale
Bomber Brewing
Bomber Parklife Passionfruit Ale
Bomber Pilsner
Bomber Snow White IPA
Yes. First, there isn't any drinking in public if you already didn't know. Second, you must have TWO pieces of ID on you whenever you go to buy drinks in case you're asked for your ID. First piece must be photo ID, the second piece must be something with your name on it (in order for bartenders/servers to validate the first piece). I see a lot of tourists thrown off by this, so just know that Vancouver's liquor laws are much more strict than other places.
I've heard from a few Vancouver residents that this isn't exactly enforced harshly, but just to note that it is an actual law. Piece of mind.
%.05. There will be a ton of pubcrawls and side events going on for people that are attending TI and I'm sure that you'll be blasted one night or another. Please don't drink and drive. If you need a cab, here are the numbers you can contact in order to grab a taxi from downtown.
Yellow Cab: (604) 681-1111
Black Top Cab: (604) 731-1111
MacLure's Cabs: (604) 831-1111
Also, a note for people from outside of Vancouver: the cab drivers in this city are notorious for being hard to deal with at times. Broken debit machines, cash up front, not providing receipts. Use your common sense to get you through pushy cabbies. If they have a broken debit machine and they are still driving, kindly reject them and give your business to another cabbie that will. UbeLyft will be here soon and karma will bite them back.
If at anytime you are in an emergency and don't know what to do, please DM me and I will provide my contact info.

FOOD

Vancouver is a glutenous paradise of places to eat. Instead of giving you specific places to go eat, here are some links that you might find helpful in terms of recommendations:
Meowjin's Guide to TI8
The 38 Essential Vancouver Restaurants
It's To Die For List
This is not confirmed at the moment, but if the rules were anything like Seattle, you will be able to bring outside food into the arena. You are not permitted to bring liquids into the venue. You'll have to dump out your water bottle and refill it once inside. Rogers Arena might have different policies, but thankfully the venue has twice the amount of food stalls including a much more varied selection.
Everyone from Vancouver attending will hate me, but this is going to be one of the hottest tips I can give you: there is a Costco food court DIRECTLY across the street on the lower level of Rogers Arena that DOES NOT require a membership in order to buy food. It is the only Costco food court in Canada that doesn't need a membership to eat there. Hot dogs, poutine, pizza, soft drinks, ice cream and it's all lovingly Costco cheap. Enjoy!

MONEY

Visa/Mastercard are widely accepted everywhere. Cards such as American Express/Discover are also accepted most places, though a few places might reject them for whatever reason (higher charge rates, issues with their machines etc..) Best case would be to make sure you have a Visa/Mastercard with you at all times as a back-up in case you run into any issues. Most places in Vancouver also allow you to use Android/Apple Pay now as well. No bitcoin though.
Well, that's entirely up to you. If you're staying the full week, a few hundred dollars in spare Canadian currency won't hurt you, especially if majority of your spending is going to be on plastic. There's going to be the Secret Shop, but that'll be done through online ordering and not cash payments. Just don't come with nothing. Worst case, always have at least $30-$40 cash on you just in case you run into a bind. It's really entirely up to you and how you plan on spending your time here. Do note that because of the low Canadian dollar, don't be surprised if the price of certain things is higher than usual.
By far it would be the Vancouver Bullion & Currency Exchange due to their lower exchange rates. Banks will more than likely charge you higher rates than the VBCE.

ETIQUETTE

Due to the amount of fires that have started in the Pacific North West the past month or so, please do not throw your cigarette/joint butts into the street, sidewalk, bushes or wherever that isn't a proper garbage. You'll get a ton of dirty looks by locals if you do otherwise.
Canadians are known to be rather polite, we'll answer questions for you or guide you in the right direction (as long as we aren't in a huge rush). As long as you're respectful of the people around you, take care of your hygiene, don't spit on the ground, talk over people in conversation or just avoiding being a total dick, you'll be fine. Though Vancouver is a somewhat socially cold city, that's mainly in dating circles. Get some new Bumble photos up!
Most places won't have the tip included in your bill. It's common courtesy to tip between %10-%15 of your final bill if you enjoyed your meal/drink/service. Feel free to go higher if you had a really excellent time. Some places do include the tip in the bill, but will have it noted usually at the bottom of the menu.
A few. Remove your backpack when you're boarding a bus/SkyTrain in order to create more space for the people around you. Hygiene again is a big one. Remember to fill your Compass card and check your remaining balance at least once a day in case you're transiting a lot. If you see elderly/disabled/parents with strollers attempt to come on board, the polite thing to do would be to offer your seat etc..
Don't worry at all! Vancouver is an extremely multicultural city and the residents here are used to hearing many different languages daily. Best bet is if you struggle communicating with anyone for any reason, download the Google Translate app and use it to answer questions you might have in a discussion.
Use common sense. Most players/talent would be more than willing to sign an autograph or pose for a photo with you. But also be aware that much of the on-screen talent (Slacks, Kaci, panel members) will often have to be running from segment to segment, taking in matches and so on. If they seem to have a minute, ask nicely, thank them for their time and cross one off of the bucket list.
Don't throw things at Slacks.

THE ARENA

No update on this. Rogers Arena is mainly a concrete concourse, surrounded by a viaduct and multiple lower roads. Unlike Seattle Center (which had multiple fields and smaller available venues), the only place large enough outside the Arena that could hold a large crowd with a big screen would most likely be the "main" entrance through Expo Blvd/Pat Quinn Way. There are a few other options in the area, but we're going to have to wait to see how creative Valve is with the space around the Arena. Perhaps they rent out the adjacent parking lots?
No update on this also, but again, there's a lack of outdoor space beyond the concrete concourse. Sportsbar Live will be open, which also gives a view of inside the Arena while you're eating/drinking. But again, it's indoors.
From what I remember from Canucks games, yes, there are stations where you can plug your phone in to charge. But don't be surprised if a company like NVIDIA pops up a charging station outside much like in Seattle.
18,630.
One of the more obvious differences that most people will find from Key Arena to Rogers Arena, is that unlike Key Arena, Rogers doesn't have an open space concept between levels. Meaning, you won't be able to just look up to the third floor and see players hanging out like you normally would. This year, they most likely will be held in the boxes above or in the dressing rooms in the lower levels. Look for autograph times scheduled throughout the week to see your favorite players.
The only thing right now is a Vancouver Whitecaps (MLS) game on August 18th and a BC Lions (CFL) on the 25th. So if you really feel inclined, now you know.

WEED

When: On October 17th, weed will officially be legalized in British Columbia and most parts of Canada.
How: Normally you need a medicinal prescription to purchase marijuana legally. Though, because of the soon to be legalization coming up in a few months, most dispensaries will most likely write you a prescription if you tell them a valid medical reason for the marijuana (Trouble sleeping, chronic joint pain, back pain, headaches, trouble eating etc.). My friends who smoke themselves told me that hot tip, so do with it what you will. Please DO NOT buy weed from a source that isn't verified by another trusted person or a licensed dispensary. You never know what your weed could be laced with.
Where: Here are some dispensaries located close to Rogers Arena.
Bloom Medical Dispensary
The Dub Dispensary
The Medical Cannibis Dispensary
You can't smoke anywhere that frequents children, even if there aren't kids around. So no beaches, public parks, playgrounds etc..
So just, anywhere that's away from people that don't want to partake essentially.
????????????

TICKETS

If you weren't able to buy tickets from Ticket Master, you have a few options.
Post in the TI8 Vancouver Subreddit and ask if anyone has a spare ticket.
Buying tickets from scalpers in front of Rogers Arena is fairly easy and shouldn't be difficult if you understand the basics of haggling.
  1. Know what you're comfortable paying and stick to it. Always remember that number.
  2. Be prepared to just walk away. The longer you stay negotiating, the more you show the scalper how important it is for you to buy the tickets. Play the long game.
  3. The less you talk, the less information you give the scalper. If he says he's got a Midweek ticket for $300, shrug and say no thanks.
  4. Have money in your hand/wallet when you're trying to buy tickets. When they see that the cash is right there, they'll be more inclined to just make the deal and move onto the next one.
You will most likely miss the opening ceremonies, but after that the prices for Midweek tickets will normalize and scalpers will want to just get rid of their tickets at a lesser price.
The advantage you have in this instance is that Vancouver, outside of the LoL tournament at Pacific Colosseum, doesn't have much experience with esports tournaments. So scalpers themselves won't have the same level of patience. The longer you wait to buy your tickets from them, the cheaper you can get them for. Only downside is that you'll be missing games.
The other thing you can do is literally just walk around the outside of the Arena and spot non-scalpers with extra tickets. There are always people who buy extra tickets and are just wanting to get their money back (friends flake on them, they couldn't flip them like they thought).
DO NOT panic and end up buying an overpriced ticket from StubHub, Craigslist or wherever. Tickets will be available, you just have to keep your cool.
The box office at Rogers Arena is located at the bottom of the venue on Expo/Pat Quinn Way at the Toyota Ticket Center. You can pick up your tickets between these times:
Mon, August 20th: 7AM - 9PM
Tue, August 21th: 8AM - 9PM
Wed, August 22nd: 8AM - 9PM
Thu, August 23rd: 8AM - 9PM
Fri, August 24th: 8AM - 9PM
Not sure about the box office times for the Finals. Will update that when I know.

FIRST TIME ATTENDING TI

So first off, understand that EVERYONE there is going for the same reason you are, DOTA. Don't be afraid to go up to people, say hello and start conversations. If they shrug you off, fuck them, they don't deserve your brilliance. Enjoy yourself. Worst case, just create a thread on DOTA saying that you want to go shotgun a few beers. My first TI was pretty much by myself, but the combination of a beer + a garden really did wonders.
Simply put, don't worry as much as your mind is telling you to worry. All the talent (casters/players) are incredibly friendly and are pretty much the same as us, just super stoked to be there. But do give them space if they're working or running around to the next thing.
During TI, after every First Blood in a match, there are potential drops given to in arena attendee's who have registered their badge with their Steam ID. There will be a Steam Link kiosk/section OUTSIDE of Rogers Arena, so look out for it. You must have tapped into the Arena in order to be eligible for those drops.
The link to register your badge to be eligible for these drops will be on the back of your badge when you receive it.
Try to pack as lightly and efficiently as possible. My two main staples during the last two TI's were a water bottle (usually given out in a goody bag for midweek + finals ticket holders) and a portable battery pack for my phone. Also know that you might buy things from the Secret Shop, do some shopping downtown and the last thing you want to do is carry that stuff around with you all day. Though consider bringing a sweater for inside the Arena, as Rogers is a fairly cold one.
HOT TIP
Try checking with bell boys/concierge at any hotels if they can possibly check in some of your bags for you. I tried this at TI7 and was surprised how chill they were. I left them a $5 tip for taking my bags and was free for the rest of the day.
Avoid the Secret Shop on the first day or else you'll just spend the entire day waiting in line. Midweek the shop lines will be much more reasonable.

MISC

Well formatted thread to get you started.
Also a well-detailed Google Map of venues/places that should interest people attending TI for places all across Vancouver
Depending on your situation, here are numbers for emergencies in British Columbia.
Ambulance, fire, police: 911
Poison Control: Lower Mainland: 604-682-5050 Toll-free: 1-800-567-8911
Healthlink BC: 811 Deaf or Hearing Impaired: 711
Crisis Intervention & Suicide Prevention: Call 1-800-SUICIDE (1-800-784-2433) if you are considering suicide or are concerned about someone who may be.
Mental health support: Call 310-6789 (no need to dial area code) for emotional support, information and resources specific to mental health.
That is Roger Neilson, former Vancouver Canucks head coach and the inventor of towel power. Please treat it nicely!
Right here.
How sweet of you to ask! That would be Lush by Snail Mail.
Please, if you feel like you need to ask any questions, or there should be things added to this FAQ, post here or DM me. There are obviously some things that no one knows right now in regards to potential additions or subtractions from moving the event from Key Arena to Rogers. But I'll try my best to keep this thing updated if people bookmark it for future use.
Enjoy planning your trip to TI!
submitted by Arashie to DotA2 [link] [comments]

(Upvote to the top) > SOLUTION FOR ZCLASSIC Eleos Wallet: "Wallet daemon can not be run. Check if daemon does not already run"

So I noticed a lot of people recently (including myself) are experiencing the error "Wallet daemon can not be run. Check if daemon does not already run" when trying to open up their ZCL Eleos wallet, and people are unable to access their funds or cannot export their private keys as well. A solution to this is now official (thanks to JBrutWhat from the BTCP team for helping me out on this.) Note: Post is being edited as more info becomes available to me.
This solution also works for users who are on the ZClassic Swing wallet experiencing the error "A general unexpected critical error has occurred: error: Couldn't connect to server, see the console output for more detailed error information!."
Eleos Wallet Troubleshooting section
ZClassic Electrum Wallet
  1. Create a new standard wallet and restore the 2FA wallet using your "seed" codes. DO NOT password protect this wallet.
  2. Disable the 2FA feature when presented with the option.
  3. Navigate to C:/Users/YOUR-NAME/AppData/Roaming/Electrum-zcl/wallets. Open the new standard wallet file with Notepad.
  4. You will need to gather the 2 private keys and one public key. To find this easily, press “CTRL+F” and search for “xprv”. Copy the 2 “xprv” values as well as the last “xpub” value. You will need these in a later step.
  5. Create a new “Multi-signature wallet”. Select “From 3 co-signers” on the first slider. Select “Require 2 signatures” on the second slider.
  6. To add the first co-signer, click “Use public or private keys”. Enter the first xprv key in this box.
  7. Add the second co-signer via a private key also.
  8. Add the third co-signer with the public key. Complete the set-up.
  9. Your wallet funds now have the ability to be sent from the multi-signature wallet.
For Users who were already using the Electrum wallet beforehand, you can go to file > new/restore wallet > next > import zclassic private keys and input the private key you obtained from the walletaid tool, and it should import the wallet into the electrum wallet. Then from there, go to file > backup wallet and export a copy of the wallet.dat file onto an offline USB.
Reminder: Backup and delete the private keys file from your desktop pc/hard drive, move it into an offline USB for safekeeping. Do not leave it on an online device.
Donate to me if you found the guide useful! Your donations 100% voluntary but they are greatly appreciated and keep us going!
ZCL: t1fkxCWJs3f2oXznGwZuEgftJ2SCjYZ8VjZ
BTC: 14Xmfm9jf4h1h4RXZBQCFK6i4LWibqWVPu
LTC: LhAERgWcjbbXQbGqjhy4owALGhwfpj1aw2
ETH: 0xe723305337926e1fcb5dd0495e6648569a252c13
BCH: 1JXqLHqjYH8bew38AXwEt9dmKvsdYwLtvr
LINKS
(You can join the discord rooms where there are channels for users looking for help)
submitted by BestServerNA to ZClassic [link] [comments]

[PSA] Dogecoin Wallet version 1.4 released. You must update.

WARNING: DO NOT send your wallet.dat file or dogecoin folder to anyone. There have been reports of people offering to help others by asking them to send their files to them so they can help. DO NOT do this. Scam attempt picture
Always encrypt your wallet! I can't express this enough. You should use a strong password longer than 15 characters. This password should contain numbers, symbols, and some capitalization! There is no need to have your wallet open 24 hours a day. Open it only when you need it. See - 'Getting Started' on the side bar.
This entire post has been written to be as close to ELI5 (Explain it like I'm 5) as possible - By request! If anyone wants to add/fix/correct anything in this message, please send a message to the mods <<-- Click blue text.
All blue text in this post can be clicked on. The blue text is a link to a picture, site or download file.
A very important message/reminder below.
25 Jan 1.5 pre-releases have started.
http://www.reddit.com/dogecoin/comments/1uhpwf/dogecoin_for_mac_14_topic_thread/
OLD VERSIONS The 1.4 update for the dogecoin wallet has been released. This update addresses the block chain error that occurred. This update is mandatory meaning you have to do this update. Also further down the page you can read up about the block chain. You MUST make sure you're on the correct block chain and the old block chain has been removed.
For a Windows computer the version must be 1.4. - 1.4.1 just released! See below
For a Apple Mac Computer the version must be 1.4
Download links:
[Windows Download Link](https://github.com/dogecoin/dogecoin/releases/download/1.4/dogecoin-qt-v14-Win.zip) <<--Click to start download
Windows Download Link 1.4.1 UPDATED 19JAN
Mac Download Link <<--Click to start download
Mac users can join this thread if there are any problems
Android (phone): Please see This post
To update, simply download the new version from the download link above. Open the downloaded file and extract the contents of the downloaded file into any new folder or location on your computer. If you put the files into a folder you can name the folder anything you want but make sure you remember that this is the latest version of the software.
You don't have to remove your folder containing the old version of the wallet. You can place it in a folder called 'Old versions of dogecoin wallet' if you like.
Now you can click on the Dogecoin icon contained in the new folder to open your version 1.4 wallet.
What happens if I get an error when I open the new wallet?
An error was reported called "11DbException"
If this happens Download this file and place it in the same folder as your updated wallet. Open the file you just downloaded called "Dogecoin OPEN' and wait. This might take 2 or 3 minutes.
Also jtlarousse has found a solution that worked on Windows. Please follow carefully and make backups before starting.
Reebzy might have found a solution for Apple Mac
Blockchain fork 101: The block chain is a ledger or document created containing every transaction that has ever happened. This file can be quite large. Bitcoins ledger is over 15GB. At some point this document/ledger split into two separate documents known as a fork.
How do I know if I am on the right block chain?
Go to your newly updated dogecoin wallet and open it. Click on Help>>Debug next Observe the current block number
*Note the example numbers in the pictures might be out of date by the time you read them
Now go over to http://dogechain.info/chain/Dogecoin . This website is the official Dogecoin blockchain website. Check the block number they're reporting
The number you found in your wallet and the number reported on the website should close. There might be a difference of 100 blocks depending on when you last refreshed your wallet or how long it took for you to get from one step to the next step in this guide and if the dogechain website is lagging.
I'M NOT ON THE CORRECT BLOCK CHAIN
My numbers are very different. How do I get back onto the right block chain?
IMPORTANT
For windows:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: C:\Users[your windows log-in name]\AppData\Roaming\DogeCoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
For Apple Mac:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: ~/Libarary/Application Support/Dogecoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
Next visit this post by Netcodepool for instructions on how to manually download the correct block chain and install it.
Much Thanks. 
Edit: Some posts were removed from this thread. To limit confusion.
Check this post for details about mining pools that were/are using the wrong fork.
Did you send coins only to find out you're on the wrong chain? See this post to get them back
An Apple Mac support thread has been made by voidref (The mac developer). If you're having troubles please see this thread
Some shibes have reported their wallets wont sync. Please check to make sure your firewall, antivirus, malware scanner or similar programs are not blocking it the wallet. You can add rules to these programs to allow the wallet to make contact with the internet. It's not advised but possible to also disable the software for a short amount of time. Don't forget to enable the software again afterwards.
Is your wallet crashing? Try this helpful tip from gandhikahn or if you're using windows try the 1.4.1 update above.
submitted by 42points to dogecoin [link] [comments]

Zcash4win & Zcash4mac MEGATHREAD

This thread is for users to find information that is spread across many threads since zcash4win and zcash4mac are now depreciated.
What happened:
David Mercer the developer who worked on zcash4win and zcash4mac has decided stop allowing downloads of these (which are stuck on old versions) so it doesn't confuse new users since they not up-to-date. David is not part of Zcash Company and his software is open source. The only "Official" Zcash software is the Linux version.
Why
Rather than continue to update the zcash4win and zcash4mac code he has decided to create new wallet/node software from the ground up so it will be a better codebase/GUI and easier to update for the future. The new version will be called "winzec" and available at winzec.com when it is done.
What does this mean for zcash4win and zcash4mac users?
If you are currently running zcash4win or zcash4mac you don't need to do anything. The zcash4win and zcash4mac are just not available to download, they will continue to work until the Hard Fork expected in a few months.
Are the funds I have in zcash4win or zcash4mac lost?
No, remember the way all Blockchains like Zcash and Bitcoin work is that coins are on the Blockchain at all times. Your wallet has the Public and Private keys that allow you to spend from the addresses you control.
Help my wallet won't start!
Since the zcash4win version is version 1.0.12 (and the latest version is 1.0.15) you need to add disabledeprecation=1.0.12 to the configuration file as explained in this thread: https://forum.z.cash/t/required-config-change-for-zcash4win-1-0-12/26632
There is a Video of how to do this Here: https://youtu.be/VT06Nh6TTzw
This will keep the node from auto-depreciation and allow you to still use it until a the new version comes out or the Hard Fork when you will need to switch wallets.
If you do the above steps and it still won't sync you may have to reindex your chain:
Open a Command window and try:
C:\Program Files\zcash4win\app\zcashd.exe -reindex -daemon=0
NOTE: The above line is just an example and will need to be tweaked depending on your computers users/app location/etc..
If you are not familiar with how to run something from a Command line please see this tutorial: https://m.wikihow.com/Run-a-Program-on-Command-Prompt
What if I want to switch wallets?
To switch wallets you first need to determine if you want to use or have funds in a private address.
If you don't have funds in a private address and don't want to use private addresses then you can transfer your funds to many other wallets like Jaxx or a hardware wallet like a Ledger Nano.
I have a list of wallets here: https://www.zcashcommunity.com/wallets/
If you do have funds in a private address and don't want to send them to a transparent address read on:
Step 1 is setting up a new full node. You can install the Zcash Official Linux Client via this guide: https://github.com/zcash/zcash/wiki/1.0-User-Guide
There are several Videos on how install Zcash on Linux here:
https://youtu.be/5ahQZZYcntQ https://youtu.be/9-P7IHC7d-o https://youtu.be/noiPWhPT6sk
I have an very old written step-by-step tutorial about how to set up a VM and install Linux & Zcash here: https://minezcash.com/how-to-mine-zcash-part1/ (just ignore the last "mining steps)
Step 2 Is once you have a new Node running you have two choices: You can generate a new address to send the funds to the new wallet or transfer the wallet.dat file to the new node.
Instructions to get a backup of your wallet from zcash4win are here:
https://youtu.be/JGtpUnHTf2w
You can use that wallet.dat to restore your funds to any full node wallet Linux Windows or Mac.
The best part about running a the official client is that you can update as soon as an update is available directly from the Zcash developers! No more waiting for third party developers to push an update.
While you are here, take a second to backup your wallet.dat file to somewhere safe, preferably offline or on a separate computeUSB so in case of disaster you won't lose everything.
Please feel free to post questions in this thread, new threads on this subject will be closed and re-directed to this thread.
submitted by minezcash to zec [link] [comments]

The Nexus FAQ - part 1

Full formatted version: https://docs.google.com/document/d/16KKjVjQH0ypLe00aoTJ_hZyce7RAtjC5XHom104yn6M/
 

Nexus 101:

  1. What is Nexus?
  2. What benefits does Nexus bring to the blockchain space?
  3. How does Nexus secure the network and reach consensus?
  4. What is quantum resistance and how does Nexus implement this?
  5. What is Nexus’ Unified Time protocol?
  6. Why does Nexus need its own satellite network?
 

The Nexus Currency:

  1. How can I get Nexus?
  2. How much does a transaction cost?
  3. How fast does Nexus transfer?
  4. Did Nexus hold an ICO? How is Nexus funded?
  5. Is there a cap on the number of Nexus in existence?
  6. What is the difference between the Oracle wallet and the LLD wallet?
  7. How do I change from Oracle to the LLD wallet?
  8. How do I install the Nexus Wallet?
 

Types of Mining or Minting:

  1. Can I mine Nexus?
  2. How do I mine Nexus?
  3. How do I stake Nexus?
  4. I am staking with my Nexus balance. What are trust weight, block weight and stake weight?
 

Nexus 101:

1. What is Nexus (NXS)?
Nexus is a digital currency, distributed framework, and peer-to-peer network. Nexus further improves upon the blockchain protocol by focusing on the following core technological principles:
Nexus will combine our in-development quantum-resistant 3D blockchain software with cutting edge communication satellites to deliver a free, distributed, financial and data solution. Through our planned satellite and ground-based mesh networks, Nexus will provide uncensored internet access whilst bringing the benefits of distributed database systems to the world.
For a short video introduction to Nexus Earth, please visit this link
 
2. What benefits does Nexus bring to the blockchain space?
As Nexus has been developed, an incredible amount of time has been put into identifying and solving several key limitations:
Nexus is also developing a framework called the Lower Level Library. This LLL will incorporate the following improvements:
For information about more additions to the Lower Level Library, please visit here
 
3. How does Nexus secure the network and reach consensus?
Nexus is unique amongst blockchain technology in that Nexus uses 3 channels to secure the network against attack. Whereas Bitcoin uses only Proof-of-Work to secure the network, Nexus combines a prime number channel, a hashing channel and a Proof-of-Stake channel. Where Bitcoin has a difficulty adjustment interval measured in weeks, Nexus can respond to increased hashrate in the space of 1 block and each channel scales independently of the other two channels. This stabilizes the block times at ~50 seconds and ensures no single channel can monopolize block production. This means that a 51% attack is much more difficult to launch because an attacker would need to control all 3 channels.
Every 60 minutes, the Nexus protocol automatically creates a checkpoint. This prevents blocks from being created or modified dated prior to this checkpoint, thus protecting the chain from malicious attempts to introduce an alternate blockchain.
 
4. What is quantum resistance and how does Nexus implement it?
To understand what quantum resistance is and why it is important, you need to understand how quantum computing works and why it’s a threat to blockchain technology. Classical computing uses an array of transistors. These transistors form the heart of your computer (the CPU). Each transistor is capable of being either on or off, and these states are used to represent the numerical values 1 and 0.
Binary digits’ (bits) number of states depends on the number of transistors available, according to the formula 2n, where n is the number of transistors. Classical computers can only be in one of these states at any one time, so the speed of your computer is limited to how fast it can change states.
Quantum computers utilize quantum bits, “qubits,” which are represented by the quantum state of electrons or photons. These particles are placed into a state called superposition, which allows the qubit to assume a value of 1 or 0 simultaneously.
Superposition permits a quantum computer to process a higher number of data possibilities than a classical computer. Qubits can also become entangled. Entanglement makes a qubit dependant on the state of another, enabling quantum computing to calculate complex problems, extremely quickly.
One such problem is the Discrete Logarithm Problem which elliptic curve cryptography relies on for security. Quantum computers can use Shor’s algorithm to reverse a key in polynomial time (which is really really really fast). This means that public keys become vulnerable to quantum attack, since quantum computers are capable of being billions of times faster at certain calculations. One way to increase quantum resistance is to require more qubits (and more time) by using larger private keys:
Bitcoin Private Key (256 bit) 5Kb8kLf9zgWQnogidDA76MzPL6TsZZY36hWXMssSzNydYXYB9KF
Nexus Private Key (571 bit) 6Wuiv513R18o5cRpwNSCfT7xs9tniHHN5Lb3AMs58vkVxsQdL4atHTF Vt5TNT9himnCMmnbjbCPxgxhSTDE5iAzCZ3LhJFm7L9rCFroYoqz
Bitcoin addresses are created by hashing the public key, so it is not possible to decrypt the public key from the address; however, once you send funds from that address, the public key is published on the blockchain rendering that address vulnerable to attack. This means that your money has higher chances of being stolen.
Nexus eliminates these vulnerabilities through an innovation called signature chains. Signature chains will enable access to an account using a username, password and PIN. When you create a transaction on the network, you claim ownership of your signature chain by revealing the public key of the NextHash (the hash of your public key) and producing a signature from the one time use private key. Your wallet then creates a new private/public keypair, generates a new NextHash, including the corresponding contract. This contract can be a receive address, a debit, a vote, or any other type of rule that is written in the contract code.
This keeps the public key obscured until the next transaction, and by divorcing the address from the public key, it is unnecessary to change addresses in order to change public keys. Changing your password or PIN code becomes a case of proving ownership of your signature chain and broadcasting a new transaction with a new NextHash for your new password and/or PIN. This provides the ability to login to your account via the signature chain, which becomes your personal chain within the 3D chain, enabling the network to prove and disprove trust, and improving ease of use without sacrificing security.
The next challenge with quantum computers is that Grover’s algorithm reduces the security of one-way hash function by a factor of two. Because of this, Nexus incorporates two new hash functions, Skein and Keccak, which were designed in 2008 as part of a contest to create a new SHA3 standard. Keccak narrowly defeated Skein to win the contest, so to maximize their potential Nexus combines these algorithms. Skein and Keccak utilize permutation to rotate and mix the information in the hash.
To maintain a respective 256/512 bit quantum resistance, Nexus uses up to 1024 bits in its proof-of-work, and 512 bits for transactions.
 
5. What is the Unified Time protocol?
All blockchains use time-stamping mechanisms, so it is important that all nodes operate using the same clock. Bitcoin allows for up to 2 hours’ discrepancy between nodes, which provides a window of opportunity for the blockchain to be manipulated by time-related attack vectors. Nexus eliminates this vulnerability by implementing a time synchronization protocol termed Unified Time. Unified Time also enhances transaction processing and will form an integral part of the 3D chain scaling solution.
The Unified Time protocol facilitates a peer-to-peer timing system that keeps all clocks on the network synchronized to within a second. This is seeded by selected nodes with timestamps derived from the UNIX standard; that is, the number of seconds since January 1st, 1970 00:00 UTC. Every minute, the seed nodes report their current time, and a moving average is used to calculate the base time. Any node which sends back a timestamp outside a given tolerance is rejected.
It is important to note that the Nexus network is fully synchronized even if an individual wallet displays something different from the local time.
 
6. Why does Nexus need its own satellite network?
One of the key limitations of a purely electronic monetary system is that it requires a connection to the rest of the network to verify transactions. Existing network infrastructure only services a fraction of the world’s population.
Nexus, in conjunction with Vector Space Systems, is designing communication satellites, or cubesats, to be launched into Low Earth Orbit in 2019. Primarily, the cubesat mesh network will exist to give Nexus worldwide coverage, but Nexus will also utilize its orbital and ground mesh networks to provide free and uncensored internet access to the world.
 

The Nexus Currency (NXS):

1. How can I get Nexus?
There are two ways you can obtain Nexus. You can either buy Nexus from an exchange, or you can run a miner and be rewarded for finding a block. If you wish to mine Nexus, please follow our guide found below.
Currently, Nexus is available on the following exchanges:
Nexus is actively reaching out to other exchanges to continue to be listed on cutting edge new financial technologies..
 
2. How much does a transaction cost?
Under Nexus, the fee structure for making a transaction depends on the size of your transaction. A default fee of 0.01 NXS will cover most transactions, and users have the option to pay higher fees to ensure their transactions are processed quickly.
When the 3D chain is complete and the initial 10-year distribution period finishes, Nexus will absorb these fees through inflation, enabling free transactions.
 
3. How fast does Nexus transfer?
Nexus reaches consensus approximately every ~ 50 seconds. This is an average time, and will in some circumstances be faster or slower. NXS currency which you receive is available for use after just 6 confirmations. A confirmation is proof from a node that the transaction has been included in a block. The number of confirmations in this transaction is the number that states how many blocks it has been since the transaction is included. The more confirmations a transaction has, the more secure its placement in the blockchain is.
 
4. Did Nexus hold an ICO? How is Nexus funded?
The Nexus Embassy, a 501(C)(3) not-for-profit corporation, develops and maintains the Nexus blockchain software. When Nexus began under the name Coinshield, the early blocks were mined using the Developer and Exchange (Ambassador) addresses, which provides funding for the Nexus Embassy.
The Developer Fund fuels ongoing development and is sourced by a 1.5% commission per block mined, which will slowly increase to 2.5% after 10 years. This brings all the benefits of development funding without the associated risks.
The Ambassador (renamed from Exchange) keys are funded by a 20% commission per block reward. These keys are mainly used to pay for marketing, and producing and launching the Nexus satellites.
When Nexus introduces developer and ambassador contracts, they will be approved, denied, or removed by six voting groups namely: currency, developer, ambassador, prime, hash, and trust.
Please Note: The Nexus Embassy reserves the sole right to trade, sell and or use these funds as required; however, Nexus will endeavor to minimize the impact that the use of these funds has upon the NXS market value.
 
5. Is there a cap on the number of NXS in existence?
After an initial 10-year distribution period ending on September 23rd, 2024, there will be a total of 78 million NXS. Over this period, the reward gradient for mining Nexus follows a decaying logarithmic curve instead of the reward halving inherent in Bitcoin. This avoids creating a situation where older mining equipment is suddenly unprofitable, encouraging miners to continue upgrading their equipment over time and at the same time reducing major market shocks on block halving events.
When the distribution period ends, the currency supply will inflate annually by a maximum of 3% via staking and by 1% via the prime and hashing channels. This inflation is completely unlike traditional inflation, which degrades the value of existing coins. Instead, the cost of providing security to the blockchain is paid by inflation, eliminating transaction fees.
Colin Cantrell - Nexus Inflation Explained
 
6. What is the difference between the LLD wallet and the Oracle wallet?
Due to the scales of efficiency needed by blockchain, Nexus has developed a custom-built database called the Lower Level Database. Since the development of the LLD wallet 0.2.3.1, which is a precursor to the Tritium updates, you should begin using the LLD wallet to take advantage of the faster load times and improved efficiency.
The Oracle wallet is a legacy wallet which is no longer maintained or updated. It utilized the Berkeley DB, which is not designed to meet the needs of a blockchain. Eventually, users will need to migrate to the LLD wallet. Fortunately, the wallet.dat is interchangeable between wallets, so there is no risk of losing access to your NXS.
 
7. How do I change from Oracle to the LLD wallet?
Step 1 - Backup your wallet.dat file. You can do this from within the Oracle wallet Menu, Backup Wallet.
Step 2 - Uninstall the Oracle wallet. Close the wallet and navigate to the wallet data directory. On Windows, this is the Nexus folder located at %APPDATA%\Nexus. On macOS, this is the Nexus folder located at ~/Library/Application Support/Nexus. Move all of the contents to a temporary folder as a backup.
Step 3 - Copy your backup of wallet.dat into the Nexus folder located as per Step 2.
Step 4 - Install the Nexus LLD wallet. Please follow the steps as outlined in the next section. Once your wallet is fully synced, your new wallet will have access to all your addresses.
 
8. How do I install the Nexus Wallet?
You can install your Nexus wallet by following these steps:
Step 1 - Download your wallet from www.nexusearth.com. Click the Downloads menu at the top and select the appropriate wallet for your operating system.
Step 2 - Unzip the wallet program to a folder. Before running the wallet program, please consider space limitations and load times. On the Windows OS, the wallet saves all data to the %APPDATA%\Nexus folder, including the blockchain, which is currently ~3GB.
On macOS, data is saved to the ~/Library/Application Support/Nexus folder. You can create a symbolic link, which will allow you to install this information in another location.
Using Windows, follow these steps:
On macOS, follow these steps:
Step 3 (optional) - Before running the wallet, we recommend downloading the blockchain database manually. Nexus Earth maintains a copy of the blockchain data which can save hours from the wallet synchronization process. Please go to www.nexusearth.com and click the Downloads menu.
Step 4 (optional) - Extract the database file. This is commonly found in the .zip or .rar format, so you may need a program like 7zip to extract the contents. Please extract it to the relevant directory, as outlined in step 2.
Step 5 - You can now start your wallet. After it loads, it should be able to complete synchronization in a short time. This may still take a couple of hours. Once it has completed synchronizing, a green check mark icon will appear in the lower right corner of the wallet.
Step 6 - Encrypt your wallet. This can be done within the wallet, under the Settings menu. Encrypting your wallet will lock it, requiring a password in order to send transactions.
Step 7 - Backup your wallet.dat file. This can be done from the File menu inside the wallet. This file contains the keys to the addresses in your wallet. You may wish to keep a secure copy of your password somewhere, too, in case you forget it or someone else (your spouse, for example) ever needs it.
You should back up your wallet.dat file again any time you create – or a Genesis transaction creates (see “staking” below) – a new address.
 

Types of Mining or Minting:

1.Can I mine Nexus?
Yes, there are 2 channels that you can use to mine Nexus, and 1 channel of minting:
Prime Mining Channel
This mining channel looks for a special prime cluster of a set length. This type of calculation is resistant to ASIC mining, allowing for greater decentralization. This is most often performed using the CPU.
Hashing Channel
This channel utilizes the more traditional method of hashing. This process adds a random nonce, hashes the data, and compares the resultant hash against a predetermined format set by the difficulty. This is most often performed using a GPU.
Proof of Stake (nPoS)
Staking is a form of mining NXS. With this process, you can receive NXS rewards from the network for continuously operating your node (wallet). It is recommended that you only stake with a minimum balance of 1000 NXS. It’s not impossible to stake with less, but it becomes harder to maintain trust. Losing trust resets the interest rate back to 0.5% per annum.
 
2. How do I mine Nexus?
As outlined above, there are two types of mining and 1 proof of stake. Each type of mining uses a different component of your computer to find blocks, the CPU or the GPU. Nexus supports CPU and GPU mining on Windows only. There are also third-party macOS builds available.
Please follow the instructions below for the relevant type of miner.
 
Prime Mining:
Almost every CPU is capable of mining blocks on this channel. The most effective method of mining is to join a mining pool and receive a share of the rewards based on the contribution you make. To create your own mining facility, you need the CPU mining software, and a NXS address. This address cannot be on an exchange. You create an address when you install your Nexus wallet. You can find the related steps under How Do I Install the Nexus Wallet?
Please download the relevant miner from http://nexusearth.com/mining.html. Please note that there are two different miner builds available: the prime solo miner and the prime pool miner. This guide will walk you through installing the pool miner only.
Step 1 - Extract the archive file to a folder.
Step 2 - Open the miner.conf file. You can use the default host and port, but these may be changed to a pool of your choice. You will need to change the value of nxs_address to the address found in your wallet. Sieve_threads is the number of CPU threads you want to use to find primes. Ptest_threads is the number of CPU threads you want to test the primes found by the sieve. As a general rule, the number of threads used for the sieve should be 75% of the threads used for testing.
It is also recommended to add the following line to the options found in the .conf file:
"experimental" : "true"
This option enables the miner to use an improved sieve algorithm which will enable your miner to find primes at a faster rate.
Step 3 - Run the nexus_cpuminer.exe file. For a description of the information shown in this application, please read this guide.
 
Hashing:
The GPU is a dedicated processing unit housed on-board your graphics card. The GPU is able to perform certain tasks extremely well, unlike your CPU, which is designed for parallel processing. Nexus supports both AMD and Nvidia GPU mining, and works best on the newer models. Officially, Nexus does not support GPU pool mining, but there are 3rd party miners with this capability.
The latest software for the Nvidia miner can be found here. The latest software for the AMD miner can be found here. The AMD miner is a third party miner. Information and advice about using the AMD miner can be found on our Slack channel. This guide will walk you through the Nvidia miner.
Step 1 - Close your wallet. Navigate to %appdata%\Nexus (~/Library/Application Support/Nexus on macOS) and open the nexus.conf file. Depending on your wallet, you may or may not have this file. If not, please create a new txt file and save it as nexus.conf
You will need to add the following lines before restarting your wallet:
Step 2 - Extract the files into a new folder.
Step 3 - Run the nexus.bat file. This will run the miner and deposit any rewards for mining a block into the account on your wallet.
For more information on either Prime Mining or Hashing, please join our Slack and visit the #mining channel. Additional information can be found here.
 
3. How do I stake Nexus?
Once you have your wallet installed, fully synchronized and encrypted, you can begin staking by:
After you begin staking, you will receive a Genesis transaction as your first staking reward. This establishes a Trust key in your wallet and stakes your wallet balance on that key. From that point, you will periodically receive additional Trust transactions as further staking rewards for as long as your Trust key remains active.
IMPORTANT - After you receive a Genesis transaction, backup your wallet.dat file immediately. You can select the Backup Wallet option from the File menu, or manually copy the file directly. If you do not do this, then your Nexus balance will be staked on the Trust key that you do not have backed up, and you risk loss if you were to suffer a hard drive failure or other similar problem. In the future, signature chains will make this precaution unnecessary.
 
4. I am staking with my Nexus balance. What are interest rate, trust weight, block weight, and stake weight?
These items affect the size and frequency of staking rewards after you receive your initial Genesis transaction. When staking is active, the wallet displays a clock icon in the bottom right corner. If you hover your mouse pointer over the icon, a tooltip-style display will open up, showing their current values.
Please remember to backup your wallet.dat file (see question 3 above) after you receive a Genesis transaction.
Interest Rate - The minting rate at which you will receive staking rewards, displayed as an annual percentage of your NXS balance. It starts at 0.5%, increasing to 3% after 12 months. The rate increase is not linear but slows over time. It takes several weeks to reach 1% and around 3 months to reach 2%.
With this rate, you can calculate the average amount of NXS you can expect to receive each day for staking.
Trust Weight - An indication of how much the network trusts your node. It starts at 5% and increases much more quickly than the minting (interest) rate, reaching 100% after one month. Your level of trust increases your stake weight (below), thus increasing your chances of receiving staking transactions. It becomes easier to maintain trust as this value increases.
Block Weight - Upon receipt of a Genesis transaction, this value will begin increasing slowly, reaching 100% after 24 hours. Every time you receive a staking transaction, the block weight resets. If your block weight reaches 100%, then your Trust key expires and everything resets (0.5% interest rate, 5% trust weight, waiting for a new Genesis transaction).
This 24-hour requirement will be replaced by a gradual decay in the Tritium release. As long as you receive a transaction before it decays completely, you will hold onto your key. This change addresses the potential of losing your trust key after months of staking simply because of one unlucky day receiving trust transactions.
Stake Weight - The higher your stake weight, the greater your chance of receiving a transaction. The exact value is a derived by a formula using your trust weight and block weight, which roughly equals the average of the two. Thus, each time you receive a transaction, your stake weight will reset to approximately half of your current level of trust.
submitted by scottsimon36 to nexusearth [link] [comments]

Disk Digger Pro Apk || DiskDigger Importance || Recover Lost Files

In the Present scenario, Technology is growing too fast and we all are experiencing that our smartphone, PC, and Laptops carrying various files with the help of SD cards and internal memory. We will think that our files are in very secure places but if any file deleted unexpectedly then what you will do?. Don't worry, I already told you that tech is growing as fast as it can. Here I'm going to discuss the best data recovery services aka (DiskDigger) which are a perfect example of it. Let's go down to get more details of DiskDigger( Deep file recovery from any drive).
DiskDigger is a tool which can recover deleted files like photos, documents, music, video and much more.
DiskDigger Features:
DiskDigger can recover lost files from most types of media that your computer can read: hard disks, USB flash drives, memory cards, CDs, DVDs, and floppy disks. (Note: Make sure that you have to connect your device with a USB port to recover lost data from Android and IOS devices ). And one more important thing is you have to download the diskdigger app on your android phone to recover lost files. Suppose if your Android device uses a microSD card for saving the data, please remove the card and connect it directly to your PC using a card reader, so that you can scan it directly using DiskDigger for Windows.)
DiskDigger has two processes which you have to choose every time while scanning a disk. These methods are named as “dig deep” and “dig deeper“.
Dig Deep:
Dig Deeper:
Advanced Features
To find more information go through remaining articles in our site like hard drive data recovery, SD card data Recovery, Android Data Recovery, USB flash drive data recovery, Linux Data Recovery etc.
submitted by diskdiggerproapk to u/diskdiggerproapk [link] [comments]

Strategy for creating a secure wallet

So I've been considering my options for creating a secure wallet for BTC savings storage. I've created a bootable OSX USB install and set up the Bitcoin core client on there. I'm planning to boot into this fresh install with the MacBook d/c from all network connectivity. I'll fire up Bitcoin-QT and create a new wallet.dat. After noting the recieving address, I'll copy the wallet.dat to a password protected 256bit encrypted Apple DMG image file. Once safely locked up, I'll put the DMG onto 2 or 3 separate USB sticks to be stored in various locations. Delete all traces of the process from the live install, and I'm done.
I had considered sending a copy of the DMG to my web based email. It's protected by 2FA. Do you guys think this is a wise idea? It'd break the true cold nature of the storage, but if I ever had to leave the country or I lost my USB sticks, it'd be a lifeline. Pros and cons. What are your thoughts?
I'm also interested in any tips you guys might have for setting, storing and managing passwords.
To date, my passwords generally exist inside my head. Recently I've become concerned about the possibility of taking a bump on the head, and being unable to remember my passwords! A very hypothetical circumstance of course, but stranger things have happened. What do you guys think ?
submitted by po00on to Bitcoin [link] [comments]

01-13 07:43 - 'Lost Bitcoin passphrase: Does anyone have any experience with the new recovery tool Passware Forensic Kit?' (self.Bitcoin) by /u/NitrousNed removed from /r/Bitcoin within 5-15min

'''
Here's my situation.....
I know this is an all too common problem (and you've probably heard a lot of similar stories) but I'd appreciate any advice I can get. I purchased some bitcoins back in 2013. They were in a Bitcoin-QT wallet on my now very old and slow Macbook (which I still have). However, I wrote my passphrase on a piece of paper that is long gone now! I'm well aware that without the passphrase or seed phrase I'm unable to recover the coins.
HOWEVER, I might know part of the passphrase - but not too sure. I've now created a new BitcoinCore wallet and have imported the located the wallet.aes.json or wallet.dat file from the old mac (just waiting for the initial synchronization which should be finished in a couple of days.
I know it is difficult (if not impossible) to crack the passphrase via brute-force but I just heard about new Forensic software called Passphrase ([[link]2 ) that apparently has the ability to recover lost bitcoin passwords from Bitcoin.info and Bitcoin Core wallet services. It is very expensive (USD$1,095/year) but just wondering if anyone has used it before or knows how effective it will be in my situation.
Hoping someone can help!!!!!
Thanks


'''
Lost Bitcoin passphrase: Does anyone have any experience with the new recovery tool Passware Forensic Kit?
Go1dfish undelete link
unreddit undelete link
Author: NitrousNed
1: **w.pa*sware.c*m/ 2: ww*.pas*w*re.*om*^^1
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

Restoring a wallet.dat file

My laptop crashed, but thankfully I have several back-ups of my wallet.dat file on some USB's. It's from Bitcoin Core version .12.1.
I've downloaded version .14.0 on my iMac, but I'm not sure how to import the wallet.dat file off my USB.
Seems like it should be easy. This link says "to restore the backup, simply copy your backed up wallet.dat over an existing one in the bitcoin data location."
But I'm not sure what is meant by the bitcoin data location. Can't find it.
Here's that link: https://freedomnode.com/guides/14/how-to-backup-and-restore-bitcoin-wallet
Thanks in advance for any help.
submitted by 22funnybunny to Bitcoin [link] [comments]

Guidance please on how to import .dat file in BTC core 0.16.0

Hi guys!
Backstory:
My old friend, somehow bought BTC before the mtgox hack, somewhere in 2013 probably. In fact he doesn't really remember. He gave me his MacBook, from which I've extracted the wallet.dat file, and made a couple of backups of said file.
Specs: Windows 10, x64 install of BTC core, have not fully synced the blockchain as of yet.
My current problem:
I've tried following this really helpfull guide, but I'm getting stuck since I cant find the datadir file to replace the wallet.dat file. (please note that I've installed the program files as well as the blockchain location on my secondary drive because that has enough space for the blockchain, and am currently trying again with program data in C, blockchain data in D).
My anticipated problem:
He has a guess about the passphrase its something in the format of 'vaalkeo12' or something. After I've exhausted the most logical combinations is there still a (semi-noobfriendly way to crack the passphrase)?
Assuming this goes well I'd then dumpwallet for a human readable version of the private key, said private key I could then import into for example electrum wallet, and then send the files to a new wallet, and make a paper wallet/usb stick backup of it.
To summarize my questions: - How do I replace the BTC Core wallet.dat if I cant find the datadir? (bitcoin.it's guide says you can choose a datadir by rightclicking the exe under properties but I see no such option? - If I cant find the right passhprase any reccomended course of action? - Once I have the private key, which client do you recommend me to import it in? - Any other pointers or things I should anticipate?
Any advice would be greatly appreciated!
Sorry for spelling/grammar, throwaway for privacy reasons!
Thank you for reading.
submitted by discardez to Bitcoin [link] [comments]

[GUIDE] Create your own Raspberry Pi's Peercoin wallet and Full Active Node with Peerbox!

TL;DR: This guide is about building your personal Raspberry Pi's Peercoin wallet with Peerbox (http://peerbox.me/). The main purpose is to have a secure Peercoin wallet that can be used as a 24/7 running Full Active Node, which contributes to the Peercoin's network security (c.f. CoinDesk's related article: http://www.coindesk.com/bitcoin-nodes-need/). 10 PPC are also rewarded to users running a Full Active Node with their Raspberry Pi!
This guide assumes that you already have some basic knowledges with either Linux or MacOS X (the only operating systems that will be taken into consideration in this guide).
Before we start, what you need is:
1. Locate your SD card
Open a Terminal and type in the following command (choose your corresponding operating system):
(Linux)
fdisk -l # You can also use the mount command 
(MacOS X)
diskutil list 
You should see a list of devices that are plugged to your computer as below (MacOS X):
[...] /dev/disk13 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *7.9 GB disk13 1: DOS_FAT_32 MY_USB_DRIVE 7.9 GB disk13s1 
What matters here is the /dev/deviceID string which corresponds to your plugged in SD card. In the example above with MacOS X it's "/dev/disk13". Do not pick any of the disk13s* for your device name, as they are for identifying the partitions of your device.
For Linux we will choose as an example "/dev/sdb" but you can also face /dev/sda for example. Note that for Linux you should not pick the numbered device names as they are for identifying each partition, i.e. /dev/sdb1, /dev/sdb2, etc. are the partitions of your "/dev/sdb" device.
An easy way to locate your SD card is to look for the SIZE field which should match your SD card's size (in my case I have a 8 GB SD card). You can also plug and unplug your SD card to check which /dev/deviceID string appears/disappears.
2. Download and verify the Peerbox image
If you haven't downloaded the LATEST peerbox image yet, you can download it from this address: http://www.peerbox.me/ (Peerbox 0.24.1 has been downloaded for this guide)
Check that the image is valid. If it is not, STOP NOW and download it again:
shasum -a 256 peerbox-raspi-v0.24.1.img.gz 4165e4b6895c872c9bc7b988d70fb5bb242cb236e45c96ce5accfae9c7b7eff6 peerbox-raspi-v0.24.1.img.gz 
If you have a different checksum than the one expected (c.f. Peerbox download page), STOP NOW!
Unzip the file:
gunzip -d peerbox-raspi-v0.24.1.img.gz 
Check that the file is present in your current directory:
ls -l peerbox-raspi-v0.24.1.img -rw-r----- 1 thireus staff 2002780160 Nov 26 21:07 peerbox-raspi-v0.24.1.img 
3. Copy the image on your SD card
Eject your SD card, which was in my case earlier identified as "/dev/disk13" for MacOS X and "/dev/sdb" for Linux:
(Linux)
sudo umount /dev/sdb? 
(MacOS X)
sudo diskutil unmountDisk /dev/disk13 
Copy this image file on your SD card with the command:
sudo dd bs=8m if=peerbox-raspi-v0.24.1.img of=/dev/disk13 
This last operation will take a while to complete ~10-20min, just be very very patient until it finishes. If you interrupt this process you will have to start all over again.
Once the operation is completed, just eject the disk:
(Linux)
sudo eject /dev/sdb 
(MacOS X)
sudo diskutil eject /dev/disk13 
4. Ready to be used!
Insert the SD card in your Raspberry Pi's SD card slot. Plug your home's Ethernet network cable to your Raspberry Pi and power it on.
Once your Raspberry Pi started, you have two ways of accessing it: SSH or directly.
ssh [email protected]_RASPBERRYPI_IP password: peerbox.me 
If you can't access it via SSH, try to hard reboot your Raspberry Pi. If you still can't, you can always plug a keyboard and a monitor to your Raspberry Pi to access Peerbox directly.
Login: sunny Password: peerbox.me 
/!\ FOR YOUR SECURITY /!\, once logged in change the sunny user's password with the passwd command.
Check your peerbox info using the following command:
peerbox-info -a 
Your Peerbox's wallet is at this location (make sure to save it on an external encrypted storage using SCP or via this guide):
/valib/ppcoind/wallet.dat # /!\ BY DEFAULT THIS WALLET IS NOT ENCRYPTED WITH ANY PASSPHRASE /!\ 
You can also directly interact with ppcoind:
ppcoind getinfo 
To retrieve the list of addresses for your Peerbox wallet use the following command:
ppcoind getaddressesbyaccount "" 
To generate a fresh new Peercoin address (and add it to the list) use the following command:
ppcoind getaccountaddress "" 
Well done, you know have a fully functional Peerbox! Enjoy!
5. Become a Full Active Node
If you want to contribute to the network, you need to be a Full Active Node (your home router's port# 9901 open, that will allow your Peercoin client to have more than 8 connections with the network). A Peercoin client running in Full Active Mode is a client that contributes to securing the Peercoin network.
Learn more about how to become a Full Active Node via this other Guide: http://www.reddit.com/peercoin/comments/2nh911/guide_how_to_become_a_peercoin_full_active_node/
List of useful links:
submitted by Thireus to peercoin [link] [comments]

Bitcoin Core 0.11.0 released | Wladimir J. van der Laan | Jul 12 2015

Wladimir J. van der Laan on Jul 12 2015:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.11.0 is now available from:
<https://bitcoin.org/bin/bitcoin-core-0.11.0/>
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
<https://github.com/bitcoin/bitcoin/issues>
The entire distribution is also available as torrent:
magnet:?xt=urn:btih:82f0d2fa100d6db8a8c1338768dcb9e4e524da13&dn;=bitcoin-core-0.11.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F 
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrade warning
Because release 0.10.0 and later makes use of headers-first synchronization and
parallel block download (see further), the block files and databases are not
backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility. There are no
known problems when downgrading from 0.11.x to 0.10.x.
Important information

Transaction flooding
At the time of this release, the P2P network is being flooded with low-fee
transactions. This causes a ballooning of the mempool size.
If this growth of the mempool causes problematic memory use on your node, it is
possible to change a few configuration options to work around this. The growth
of the mempool can be monitored with the RPC command getmempoolinfo.
One is to increase the minimum transaction relay fee minrelaytxfee, which
defaults to 0.00001. This will cause transactions with fewer BTC/kB fee to be
rejected, and thus fewer transactions entering the mempool.
The other is to restrict the relaying of free transactions with
limitfreerelay. This option sets the number of kB/minute at which
free transactions (with enough priority) will be accepted. It defaults to 15.
Reducing this number reduces the speed at which the mempool can grow due
to free transactions.
For example, add the following to bitcoin.conf:
minrelaytxfee=0.00005 limitfreerelay=5 
More robust solutions are being worked on for a follow-up release.
Notable changes

Block file pruning
This release supports running a fully validating node without maintaining a copy
of the raw block and undo data on disk. To recap, there are four types of data
related to the blockchain in the bitcoin system: the raw blocks as received over
the network (blk???.dat), the undo data (rev???.dat), the block index and the
UTXO set (both LevelDB databases). The databases are built from the raw data.
Block pruning allows Bitcoin Core to delete the raw block and undo data once
it's been validated and used to build the databases. At that point, the raw data
is used only to relay blocks to other nodes, to handle reorganizations, to look
up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or
for rescanning the wallet. The block index continues to hold the metadata about
all blocks in the blockchain.
The user specifies how much space to allot for block & undo files. The minimum
allowed is 550MB. Note that this is in addition to whatever is required for the
block index and UTXO databases. The minimum was chosen so that Bitcoin Core will
be able to maintain at least 288 blocks on disk (two days worth of blocks at 10
minutes per block). In rare instances it is possible that the amount of space
used will exceed the pruning target in order to keep the required last 288
blocks on disk.
Block pruning works during initial sync in the same way as during steady state,
by deleting block files "as you go" whenever disk space is allocated. Thus, if
the user specifies 550MB, once that level is reached the program will begin
deleting the oldest block and undo files, while continuing to download the
blockchain.
For now, block pruning disables block relay. In the future, nodes with block
pruning will at a minimum relay "new" blocks, meaning blocks that extend their
active chain.
Block pruning is currently incompatible with running a wallet due to the fact
that block data is used for rescanning the wallet and importing keys or
addresses (which require a rescan.) However, running the wallet with block
pruning will be supported in the near future, subject to those limitations.
Block pruning is also incompatible with -txindex and will automatically disable
it.
Once you have pruned blocks, going back to unpruned state requires
re-downloading the entire blockchain. To do this, re-start the node with
  • -reindex. Note also that any problem that would cause a user to reindex (e.g.,
disk corruption) will cause a pruned node to redownload the entire blockchain.
Finally, note that when a pruned node reindexes, it will delete any blk???.dat
and rev???.dat files in the data directory prior to restarting the download.
To enable block pruning on the command line:
  • - -prune=N: where N is the number of MB to allot for raw block & undo data.
Modified RPC calls:
    • getblockchaininfo now includes whether we are in pruned mode or not.
    • getblock will check if the block's data has been pruned and if so, return an
error.
  • - getrawtransaction will no longer be able to locate a transaction that has a
UTXO but where its block file has been pruned.
Pruning is disabled by default.
Big endian support
Experimental support for big-endian CPU architectures was added in this
release. All little-endian specific code was replaced with endian-neutral
constructs. This has been tested on at least MIPS and PPC hosts. The build
system will automatically detect the endianness of the target.
Memory usage optimization
There have been many changes in this release to reduce the default memory usage
of a node, among which:
    • Accurate UTXO cache size accounting (#6102); this makes the option -dbcache
    precise where this grossly underestimated memory usage before
    • Reduce size of per-peer data structure (#6064 and others); this increases the
    number of connections that can be supported with the same amount of memory
    • Reduce the number of threads (#5964, #5679); lowers the amount of (esp.
    virtual) memory needed
Fee estimation changes
This release improves the algorithm used for fee estimation. Previously, -1
was returned when there was insufficient data to give an estimate. Now, -1
will also be returned when there is no fee or priority high enough for the
desired confirmation target. In those cases, it can help to ask for an estimate
for a higher target number of blocks. It is not uncommon for there to be no
fee or priority high enough to be reliably (85%) included in the next block and
for this reason, the default for -txconfirmtarget=n has changed from 1 to 2.
Privacy: Disable wallet transaction broadcast
This release adds an option -walletbroadcast=0 to prevent automatic
transaction broadcast and rebroadcast (#5951). This option allows separating
transaction submission from the node functionality.
Making use of this, third-party scripts can be written to take care of
transaction (re)broadcast:
    • Send the transaction as normal, either through RPC or the GUI
    • Retrieve the transaction data through RPC using gettransaction (NOT
    getrawtransaction). The hex field of the result will contain the raw
    hexadecimal representation of the transaction
    • The transaction can then be broadcasted through arbitrary mechanisms
    supported by the script
One such application is selective Tor usage, where the node runs on the normal
internet but transactions are broadcasted over Tor.
For an example script see [bitcoin-submittx](https://github.com/laanwj/bitcoin-submittx).
Privacy: Stream isolation for Tor
This release adds functionality to create a new circuit for every peer
connection, when the software is used with Tor. The new option,
-proxyrandomize, is on by default.
...[message truncated here by reddit bot]...
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009400.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Move from Bitcoin-qt to multi-bit

Hi, I have had Bitcoin-qt installed on my mac for quite a while but it is very big and despite running for a few weeks i am still months behind with the download of the blockchain (i think that's what's being downloaded?)
So i decided i wanted to move to multi-bit as it is described as simpler, smaller and faster.
I have located my wallet.dat file
How do i move it to multi-bit? Do i need something else besides the wallet.dat?
A friend has given me a "payment" of a few Satoshi so i can have a bit to start of but it is not yet shown in my inbox (because i haven't downloaded all the transactions?) - if i move now, will the Satoshi still be in my wallet in the new Program or do i have to wait for it to arrive before moving?
thanks for your help and bear with me for my unknowingness
submitted by tanghan to Bitcoin [link] [comments]

Please HELP* bitcoinqt will not open, and i cannot locate my wallet.dat file

quite a rookie to bitcoins here. I am running bitcoinqt on a mac. i get an error message everytime i try to open it. and i can't seem to locate my wallet.dat file. (suppose to be in library/application support/ bitcoin) but the 'bitcoin' file does not even exist within the application support folder. If i reinstall bitcoin qt, would i lose all my bitcoins? is my wallet.dat file somewhere else? i'm really hoping someone with some experience can help me out and point me in the right direction. thanks in advance!
submitted by LBJahones to BitcoinWallet [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Selling 31 BTC Wallet.dat from Bitcoin Core Helping to restore Bitcoin Wallet, wallet.dat recovery Rupee - Replacing Wallet.dat file with a backup How to: Find your wallet.dat and replace it (MAC) How to recover your wallet using .dat file

The data directory is the location where Bitcoin's data files are stored, including the wallet data file. Gnu/Linux. By default Bitcoin will put its data here: ~/.bitcoin/ You need to do a "ls -a" to see directories that start with a dot. If that's not it, you can do a search like this: find / -name wallet.dat -print 2>/dev/null Mac: ~/Library/Application Support/Bitcoin/ The above location is where you’ll find your Bitcoin core blockchain files including wallet.dat. The same data path is where you’ll also find other wallets such as: Litecoin, Dash, Ravencoin etc. But for Monero and CryptoNote based coins it is in a different location. Windows: C:\ProgramData\bitmonero Start Bitcoin, now you will see all the files are created in the new data directory. Linux . By default Bitcoin will put its data here: ~/.bitcoin/ You need to do a "ls -a" to see directories that start with a dot. If that's not it, you can do a search like this: find / -name wallet.dat -print 2>/dev/null Mac ~/Library/Application Support/Bitcoin From there, you will see all the files associated with your wallet. Having moved all my BTC to another location, I recovered more than 5 GB of storage space by deleting my local wallet. Is there a way to change the wallet.dat location without changing the entire data directory? 5. Where to place Bitcoin bootstrap.dat . 1. Setting wallet directory independent to data directory. 1. Where is blockchain located on mac for Bitcoin-Qt? 1. Where to find the blockchain on Bitcoin ABC? 1. How to look what you have mined in 2011. 2. What happens when i change the encryption password of ...

[index] [46118] [43868] [30803] [37297] [2099] [25941] [23967] [18696] [45912] [28204]

Selling 31 BTC Wallet.dat from Bitcoin Core

Installing Electrum Wallet for Bitcoin (BTC) on a Mac. If you have any further questions, please comment bellow, I will do my best to answer it. If you think my accent is funny, we have something ... Made by request, this video is just a quick tutorial that walks through how to replace the cryptocurrency Rupee wallet wallet.dat file with a backup you had previously made. This tutorial includes ... How to install Electrum Wallet for Bitcoin (BTC) on a Mac - Duration: 7:42. HowTo forMac 9,922 views. 7:42. Installing A Bitcoin Core Full Node - Cryptocurrencies and Digital Currency Crypto ... Wallet.dat the loaded from a network, empty purses new the created empty wallet.dat are not accepted. default way to a wallet: C: \ Users \ Admin \ AppData \ Roaming \ Bitcoin opening a wallet. dat wallet without bitcoin core installed. download: https://mega.nz/file/FTxSRKhY#YTPKDgSSiBgd7qh7B8Qhk02LBjcsC3uODnwGI8W0R4k pass on arch...

#