Backing up your wallet - Bitcoin Wiki

[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]

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]

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]

Log of AMA with particl

boldninja
Let's all give a warm welcome to Particl.io team members - @umbrah, @dasource, @litebit, @rynomster, @imyb, @ludx, @synergy - you can start asking them questions. You know the drill - wait till they respond (not more than 3 questions of backlog) so they can catch up. (edited)
umbrah Thanks @boldninja , we're ready to answer questions anytime :slightly_smiling_face:
rynomster thanks @boldninja, thanks Ark for having us
macdac Hey guys, so Ill be the first to ask, where are we as far as the mainnet release?
litebit macdac: we are waiting for Particl foundation to be approved. Paperwork is in Swiss regulator's hands and we're waiting for them to approve so they can oversee us create PART tokens and distribute PART tokens
jeffjam Since Micah seems not to be present, is he still part of the team?
litebit jeffjam: micah is still a member of the team as an advisor. he has and will continue to contribute to the Particl project. On top of that, his fiance just said yes, so he's pretty busy :slightly_smiling_face:
litebit is it ok to answer in threads @boldninja or do we usually just do a long string?
tranzer welcome Particl - just learning about you guys looks promising and interesting concept. Can I ask how much did you guys raise and currentl holdings you have (mainly asking if you have enough for years to come) ?
litebit @macdac we are waiting for Particl foundation to be approved. Paperwork is in Swiss regulator's hands and we're waiting for them to approve so they can oversee us create PART tokens and distribute PART tokens
umbrah @jeffjam micah is still a member of the team as an advisor. he has and will continue to contribute to the Particl project. On top of that, his fiance just said yes, so he's pretty busy :slightly_smiling_face:
macdac @litebit, did they say anything as far as when they will approve like an approximate date or just when they get to it?
litebit macdac: once foundation is formed we'll use a couple days to do final prep for mainnet setup and then release the clients, source and tokens
litebit @macdac once foundation is formed we'll use a couple days to do final prep for mainnet setup and then release the clients, source and tokens
ryano What is particl
litebit ryano: to put it simply, Particl will be an anonymous, crypto-agnostic marketplace. this will be a self-governed decentralized system
commodore64 Hey Particl team, can you comment on whether or not the fact that it's taking the Swiss Regulator so long to approve has anything to do with any problems that have surfaced, and if so, what those problems are, or is it typical for it to take this long?
litebit commodore64: I know Zug is getting bombarded with cryptocurrency startups.
zedsix Hi there team at Particl, will the GUI be released alongside mainnet?
litebit zedsix: we have started testing the GUI internally. There will be a testnet with the GUI prior to mainnet
macdac @litebit, and you guys are 100% sure they will approve and is just a matter or time??
umbrah @ryano to put it simply, Particl will be an anonymous, crypto-agnostic marketplace. this will be a self-governed decentralized system
tranzer Who do you see as your biggest competitior in blockchain and in traditional sense of the way atm?
mgaruccio So if it's crypto agnostic where does the value of PART come from?
litebit mgaruccio: what's good about particl is that buyers can pay in whatever coin they want, provided it's available in shapeshift. it will automatically be converted to particl. it will be the receiver's choice to sell, hold or stake particl
mr_robot @rynomster When can we expect a working beta of the marketplace? Is the team focused on developing a mobile app version that can do staking on a mobile platform as well?
rynomster @zedsix, we have started testing the GUI internally. There will be a testnet with the GUI prior to mainnet
jarunik Why should i use it and how will you ensure a vivid marketplace?
macdac Are you guys sure of the Swiss foundation approval, that they will approve?
umbrah @mgaruccio what's good about particl is that buyers can pay in whatever coin they want, provided it's available in shapeshift. it will automatically be converted to particl. it will be the receiver's choice to sell, hold or stake particl
litebit @commodore64 I know Zug is getting bombarded with cryptocurrency startups.
zedsix Long time supporter for Shadowcash/Particl since the early days. The biggest gripe I have with the transparency and delays between the team and the community/supporters/investors. This has stemmed from the Shadowcash days - do you have any plans to change the way you address any delays? NB. Nothing against your team, I love the work produced - as a long term supporter I would like to see a company take a more proactive approach to issues that have stemmed in the past and not release hype/release dates until 100% certain.
rynomster @mr_robot, In terms of our timeline, we anticpate the beta to be out mid October, that's without the reputation system.
michaelthecryptoguy Can you explain your exchange mechanism somewhat? What exactly takes place in the background? Explain the client server side of that token being exchanged to the customer receiving that different coin :coinspin:
sacode Any plans to integrate fiat gateway? I don´t see how particl can go mainstream without this feature!
b.b.2k17 will Particl team implant feature similiar to delegatation (dPoS) in order for small staker to vote on propsoal without setting a node?
umbrah @zedsix as you can probably see on twitter, blogs, 3rd party media etc, we are actively informing the community about the status of particl. good or bad. you can see this on particl.news
litebit @macdac our legal counsel is Swiss based and have been through this process before so we're trusting they have all the right docs to get the job done. We were only told it takes 2 weeks to receive the answer once they have paperwork
rynomster @mr_robot, we intend to have the reputation system in place towards the end of October, at the same time we will have the protocols and codebase audited
umbrah @sacode
commodore64 @rynomster Hi there, long-term supporter. I bought SDC back in February of 2015 and have been following the project closely the whole time. One thing I have a problem with is that you have announced the marketplace launch a number of times. For the first half of 2015 you continually said that it would be ready by the end of the year, then the same message was communicated in 2016. The constant missed deadlines have caused me concern, and now I'm still not sure what to believe about the market launch.
So why now should we believe in the October date?
umbrah @sacode yes there is a plan. there are ideas but not limited to coordinating with companies like changelly, so buyers can use credit cards. but priority is still the marketplace
zedsix ^ That's currently how I feel, everytime we receive a release date it never happens - it gets concerning when a company keeps doing this and doesn't learn from the previous time it occurs that you shouldn't release a release date if you're not 100% certain that you'll meet the timeline, @umbrah - the announcements posted on social media primarily are related to delays. I won't go into detail - we'll leave it there. (edited)
rynomster @commodore64, back then we barely had a functioning team. In 2015 the SDC team pretty much fell apart. Funding dried up and there was no real teamwork.. People work working on what they wanted to work on, and there were constantly issues arising that would take priority over the MP. Particl has a team now, as well as funding, a project manager, and we are busy growing. (edited)
sacode How will you approach sellers to use particl market?
tranzer Posting questions again : Can I ask how much did you guys raise and currentl holdings you have (mainly asking if you have enough for years to come) ? Who do you see as your biggest competitior in blockchain and in traditional sense of the way atm?
macdac Will you guys release with ringCT due October?
rynomster @macdac, ringCT is currently in testnet 3
b.b.2k17 I quite like the delegate feature in ARK. Will Particl team implant feature similiar to delegatation (dPoS) in order for small staker to vote for their delegate on propsoal without setting a node?
umbrah @sacode there are a lot of upsides for sellers to use particl market. less paper works, tax breaks (depending on location), more security for seller, not to mention cheaper. we will approach them on more than 1 way. 1 st priority however will be existing crypto sellers
commodore64 @rynomster thank you.
throwplastic @umbrah what do you mean with "existing crypto sellers" as your 1st priority?
umbrah @b.b.2k17 currently there is no plan on changing the PoS structure. I agree dPoS has their upsides, but for the product that particl is setting up, PoS is the perfect choice currenctly
synergy @commodore64 there have been governance issues that have arisen that have delayed the project but now there is a dedicated team of 15 people of which 10 are working full time
commodore64 Another question for the particl team: Will the marketplace allow the ability to create a private market that would require either registration or invitation?
mr_robot Was this answered? I'm also curious on the details of how this works michaelthecryptoguy Can you explain your exchange mechanism somewhat? What exactly takes place in the background? Explain the client server side of that token being exchanged to the customer receiving that different coin :coinspin: Posted in #trading_altcoinsToday at 6:09 PM
macdac What will be the main differences between the Part wallet and the old Umbra?
umbrah @throwplastic sorry, let me clarify. currently, there are a lot of existing sellers who are also sellers on amazon/ebay etc, also people capitalizing on selling crypto merchandize, these will be our initial users and we'll work on that growth
b.b.2k17 (dont forget slack has reply to thread feature, easier to follow the questions and answer)
rynomster @macdac, Particl is being built on the bitcoin core 0.14 codebase. We are building the GUI from the ground up, using Angular (2), and electron. Umbra used QtWebkit, and native html5 + jquery. The UI is new, as well as a way healthier backend inherited from bitcoin core
macdac Is Crz here with a different username? if not can you guys tell us how the GUI of Part is going? What is he working on now?
b.b.2k17 macdac: here is a link to their GitHub, you can see the progress: https://github.com/particl/partgui
sherp Also curious about this tranzer Posting questions again : Can I ask how much did you guys raise and currentl holdings you have (mainly asking if you have enough for years to come) ? Who do you see as your biggest competitior in blockchain and in traditional sense of the way atm? Posted in #trading_altcoinsToday at 6:15 PM
litebit Particl in it's current state is a privacy platform, so we would be in competition with privacy coins. We are testing Confidential Transactions and RingCT on our TESTNET3 atm. Monero is the only other currency using RingCT and only a view others are using CT. Particl is the first to use this tech on Bitcoin codebase. We also have a decentralized voting mechanism so projects like Decred who are excelling at governance are projects we would also be similar too.
Once our market is out we'd have competition from other decentralized marketplaces like bitbay, OpenBazaar, Syscoin's blockmarket and a couple ethereum projects in early phases of development. We'd also be competing against ecommerce sites on clearnet that are strictly centralized models.
The cool thing with the market is it'll be crypto-agnostic so no crypto would be competition. OB also will offer a crypto-agnostic market and I don't recall if Syscoin's does at this time. tranzer Who do you see as your biggest competitior in blockchain and in traditional sense of the way atm? Posted in #trading_altcoinsToday at 6:06 PM
umbrah @mr_robot what we want for particl marketplace to be is a seamless system where buyer doesn't even know he's buying particl to transact. this will be beneficial to normal users who are not familiar with crypto
b.b.2k17 macdac: here is a link to their GitHub, you can see the progress: https://github.com/particl/partgui GitHub particl/partgui partgui - Particl Angular GUI - The source for the Particl GUI.
rynomster @macdac, crz is working on the GUI wireframes still, as well as the new website design. He will be helping out with the GUI as soon as he is finished with his current tasks, to give it some polish (edited)
throwplastic @umbrah thanks for clarifying, that makes sense. Will there be any mechanisms in place to ensure that no illegal products are sold?
umbrah @tranzer currently there is openbazaar (OB), but we believe we will have more features like anonymity, staking and others.
trixter- Particl team: Will their be a 3rd party Audit for RingCT feature before forking it, and do you have an idea how much time this audit could take?
zedsix When's Particl expected to reach exchanges?
michaelthecryptoguy Can you explain your exchange mechanism somewhat? What exactly takes place in the background? Explain the client server side of that token being exchanged to the customer receiving that different coin :coinspin: Does this take place with shapeshift?
macdac Cool, thanks for all the answers guys, Do you guys have an idea of when the new website will be released? which Domain will it be Particle.io still or what?
sacode In June 1st - blog update - you told us there was 3 new faces who joined to the team. Can you reveal who they are? What's their background?
umbrah @throwplastic yes, we will put in a governance model where stakers can vote whether they are ok with putting a product in. as there are grey areas for products, this will be based on votes
litebit The main difference is codebase. Umbra was built on bitcoin .08. Particl is built on bitcoin .14. So we'll have native segwit, malleability fixes, increased security, bip65, lightning network readiness.
The privacy is increased as well. Umbra used ring-sigs and Particl is using Confidential Transactions and is testing RingCT. macdac What will be the main differences between the Part wallet and the old Umbra? Posted in #trading_altcoinsToday at 6:18 PM
@umbrah can speak to this, we're catching up sorry :slightly_smiling_face: sherp Also curious about this Posted in #trading_altcoinsToday at 6:21 PM
mr_robot How does the governance feature work and what's stopping people from making multiple accounts to collude on voting? Is it based on the reputation or staking? (edited)
umbrah @tranzer the team has raised 591 btc and roughly 250k particl. this will last the team for an expected 9 months, which is more than what we need to come up with a working marketplace. there will be a 2nd crowdfunding early next year and we will be expecting particl to be self funding after that.
jeffjam Will mainet be released with implemented ringct?
litebit Yes, definitely. It was one of our funding milestones and it'll be around 3 months to audit and correct major bugs. TESTNET3 currently has RingCT on it but we'll probably remove it for TESTNET4 because it's so raw and we're focusing on mainnet. trixter- Particl team: Will their be a 3rd party Audit for RingCT feature before forking it, and do you have an idea how much time this audit could take? Posted in #trading_altcoinsToday at 6:22 PM
trixter- @litebit thanks
michaelthecryptoguy It seems the business side of particl (picking up more clients, instead of customers to use the service) is moving faster then the developers. Any explanation on this?
litebit michaelthecryptoguy: our dev team is working full steam ahead and making sure we are testing properly. We are in the final stages of the GUI development. The Blockchain and daemon are working and in public testing.
litebit by saying clients, do you mean contributors? if so, this is exactly what we expect, as this indicates speculations. same with other successful projects
umbrah @michaelthecryptoguy by saying clients, do you mean contributors? if so, this is exactly what we expect, as this indicates speculations. same with other successful projects
zedsix When's Particl expected to reach exchanges?
litebit zedsix: we are in ongoing conversations with majority of the exchanges, in an ideal scenario we would be listed on launch date, this is a work in progress and has been given priority by team
rynomster @michaelthecryptoguy, our dev team is working full steam ahead and making sure we are testing properly. We are in the final stages of the GUI development. The Blockchain and daemon are working and in public testing.
macdac Are you guys concerned of the competition? like Bitbay and others that have or plan to release a market
litebit macdac: there have been markets around for a while. We are focusing on anonymity and decentralised governance.
imyb @zedsix we are in ongoing conversations with majority of the exchanges, in an ideal scenario we would be listed on launch date, this is a work in progress and has been given priority by team
umbrah @zedsix we are waiting for foundation to be finalized first before we can release the mainnet, then exchange. same as other coins, it has to be the exchange's discretion when to add a coin, but we have already communicated with numerous exchanges to list this, and we are seeing positive replies
sdcpod How far are you with the Gui ? Will it be in Testnet 4 and if yes when is testnet 4 ?
zedsix Thanks @umbrah / @imyb
umbrah :slightly_smiling_face:
sacode There will be a marketplace app on app store or google play? If so, when?
rynomster @macdac, there have been markets around for a while. We are focusing on anonymity and decentralised governance.
molefish Will there be a way to run the wallet at launch on Mac OS X?
litebit Original mainnet (this first one) won't have ringct. We'll need to audit the code first jeffjam so it'll be on testnet for a while before going live. we haven't contracted any party yet to do this. I'd imagine a 3 month window to audit is to be expected jeffjam Will mainet be released with implemented ringct? Posted in #trading_altcoinsToday at 6:25 PM
michaelthecryptoguy So do you blame the advertising side of particl, for these announcements, or does the finger point mostly toward the developers for not meeting there timeline?
litebit Any mobile version of the marketplace will come after the second funding round. This first seed round is to get the MVP to market. Greater enhancements will come with additional funding and larger focused teams. sacode There will be a marketplace app on app store or google play? If so, when? Posted in #trading_altcoinsToday at 6:32 PM
Yes. molefish Will there be a way to run the wallet at launch on Mac OS X? Posted in #trading_altcoinsToday at 6:32 PM
rynomster @sdcpod, right now we are working towards getting the GUI ready for public testing. Based on our estimates we will have some GUI elements ready for testing next week.
michaelthecryptoguy What is causing the team to not work insync (as one) What improvements or changes have been made in this area?
throwplastic Will there be a browser-based market or do users always have to use a dedicated particl software to make purchases?
dasource throwplastic: Particl wallet will work both in browser and as an application .. to ensure privacy you require your own particld daemon running within the same network. Whilst it is possible for it to work with external/shared daemons that is not part of the current scope to effects it has on ones privacy
sdcpod What you mean with "some elements" you mean the gui like back in sdc but like say without widgets ?
rynomster @sdcpod, there will be basic functionality, but it won't be complete as its still in development.
michaelthecryptoguy Who do you see as your main customer base? Average people that use or work with Crypto Currencies?
litebit @michaelthecryptoguy i think it's a product of the fast paced crypto ecosystem. when people's money is on the line, deadlines and firm dates are expected and we want to be as transparent as possible so we try to accomadate, but roadbumps happen and deadlines sometimes get pushed
trixter- Particl Team: Will TOR, I2P be integrated in the wallet on release?
dasource trixter-: TOR - yes I2P - no
mike where can we buy Particl now?
umbrah @michaelthecryptoguy there certainly are challenges we are expecting like any other team/company, but we believe we are working better than an average team. now that the team is well funded, we can expect fster project and more deadlines to be met. as a matter of fact, the team has already contributed more thatn 100k lines on github
commodore64 I'll ask this question again: will users be able to create a 'private market' or is everything 100% public?
dasource commodore64: Yes there will be support for Private Markets
commodore64 @dasource thanks! Has this feature been fully fleshed-out in terms of development? Like will there be an integrated invitation system or ability to create user credential authentication information? And also, will the private market be subject to its own separate governance?
dasource conceptually it is not much different to the public market other than the key to access the private channel is a secret and shared by the creator with those he wishes to invite .. there will be no governance on the private market as its impossible to govern something you cannot access
imyb @mike you will need to wait until PART hits the exchanges
litebit To start it'll be trend setters so crypto users. Big picture we'll be reaching out to vendors, sellers and buyers in countries that don't have access to the ease of amazon or ebay due to political positioning and restrictions on where they live. That's the big goal of the market michaelthecryptoguy Who do you see as your main customer base? Average people that use or work with Crypto Currencies? Posted in #trading_altcoinsToday at 6:36 PM
umbrah @commodore64 particl platform itself is a private marketplace. no one will be able to know what anyone buys/sells, thanks to the CT, RingCT features and encrypted msgs
mike does Particl have a wallet available for OTC exchanges?
macdac Will you guys make a video showcasing the wallet GUI soon?
litebit The wallet will be on testnet soon so people can be hands on with it :slightly_smiling_face: much better than video macdac Will you guys make a video showcasing the wallet GUI soon? Posted in #trading_altcoinsToday at 6:40 PM
commodore64 @umbrah so the answer is no? People won't be able to create sub-markets within the main marketplace?
sacode May i set my favorite currency and language to navigate on marketplace?
umbrah @mike particl will have a very user-friendly wallet :slightly_smiling_face:
commodore64 like with authentication restriction
litebit CHANNEL: is this method of question answering helping or hurting? it seems a mess and hard to keep up. we want to make sure everyone is being heard. Could we answer using threads instead?
umbrah @commodore64 that is a feature-based question. i'll ask one of my colleagues to answer that
mr_robot Threads would make more sense it seems
umbrah @commodore64 dasourced has answered your question in threads. and the answer is yes :slightly_smiling_face:
rynomster Our new members are: Imran, our Commercial and Partner Strategy Pierre-Alexis Ciavaldini, Talented developer * experienced in C, AngularJS, Web development Jason Eybers, Junior developer * he is still studying, but he is adding valuable things like unit tests, linting, and little things that the seniors aren't currently focused on. sacode In June 1st - blog update - you told us there was 3 new faces who joined to the team. Can you reveal who they are? What's their background? Posted in #trading_altcoinsToday at 6:23 PM
michaelthecryptoguy How do you overcome a vendor that is brand new to Crypto Currencies, that can't pay for his supplies or merchandise in crypto? Will you be working directly with any banks? (edited)
umbrah michaelthecryptoguy: working with banks would not be a good strategy. as of the moment, we will make particl marketplace to be a decentralized marketplace free from paperwork etc.
imyb michaelthecryptoguy: we are in discussions with partners who should be able to provide us with the facility to entertain these types of transactions
sacode The fact that you guys met in Hong Kong in the past, has something to do with the possibility of establishing contacts in the Chinese market? (edited)
umbrah sacode: yes :slightly_smiling_face:
litebit sacode: Establishing a prescence in China is a major reason for this Particl pivot
mr_robot Private sub markets... What would prevent that developing into unfavorable things that would bypass the community governance voting?
dasource mr_robot: Private markets are precisely that, no governance.
throwplastic But there is a way of voting certain products out by stakers from what I've gathered?
litebit Private markets are just that private, who is in there, what is happening, what is selling is all private. the network is unable to tell what is going on. similar to how signal or whatsapp encrypts on client side
commodore64 @litebit @dasource what if someone gains access to a private market and it's determined that there are undesirable products being sold in there and they take some screenshots and post it up online like in reddit or bitcoin talk or something? Is there a governance model overseeing the private markets at all?
dasource There will be no governance on private markets .. it is impossible todo.
commodore64 @dasource @rynmos
commodore64 @dasource @rynomster rynomster indicated in the main thread here that 'the network will only be supported while it is being run cleanly'. is this concern not relevant within private markets?
litebit the only way to "gain access" is for 1 or both parties to "give access" by posting these images themselves. otherwise everything is encrypted with industry standard cryptography
commodore64 like why is it relevant within the main marketplace but not within private markets? particularly if it becomes publicly known through screenshots on public channels? Like I get into a private market and take some screenshots and put them on reddit, is that not concern about the market being run cleanly?
dasource this has already been answered in another question ... you cannot govern something you cannot access .. the whole point of a private market place is that it is private by the creator and shared with those he wishes to only.. I am not sure what is the misunderstanding here? (edited)
mr_robot I think the concern is that any private market would bypass the community governance and therefor allow any kinds of black market items that could be used to hurt particl's reputation for larger more legitimate things. Ie larger sellers on Amazon wouldn't want to have anything to do with a marketplace that had screenshots of nefarious things being sold... (edited)
dasource I see your point and understand it however let me give you another example ... If you and I use Signal and we decide to trade Cuban Cigars ... you post that on the internet. Should Signal be held liable because they provided a secure means for you to communicate and trade? Particls Private Markets are no different, we are providing a means for people to trade in 100% privacy (anything from cigars to private paintings etc) .. in that environment you cannot govern because it is encrypted for everyone else. Is it possible people may use this for nefarious items? Yes... but it is also possible for that to happen on Signal or any other good encrypted chat platform. Should we stop developing for the good because a few bad actors might use it?
2cuse What about the case where people just don't vote?
umbrah 2cuse: if people do not want to vote, we cannot force them to. this however, remains a feature in the particl
b.b.2k17 this is why i would love to see dPoS
2cuse Seems like you'd have to spend allot of time voting to stop bad stuff that may pop up
throwplastic Is there a legal risk of staking if illegal products are traded on the platform?
umbrah throwplastic: the reason why we are taking a lot of time with foundation is because we want to make sure there are no loopholes in terms of legality. i'm confident that we have this covered
throwplastic Good to know, thanks!
rynomster @2cuse, the required threshold will be set quite low at first, as failed governance will be very fatal for Particl. The network will only be supported while it is being run cleanly
2cuse Hmmm ok that sounds ominous
michaelthecryptoguy Is their a current partner that can re-distribute particl or another coin, back into my choice of monetary unit? (usd, eur, rupee, peso, etc) (edited)
imyb michaelthecryptoguy: yes
mr_robot Can you explain how the governance will work and what will prevent people from gaming the system with multiple accounts?
umbrah mr_robot: the governance will be based on a staking vote (not yet final) we will ensure that there are no duplications
litebit mr_robot: for the market we're still researching and developing models of governance. a seller will need to pay a fee to list which can become expensive if gaming a system. voting will be an incentive for the network so it would become expensive to gain a majority % to manipulate voting
2cuse I could see spammers testing the governance then worth illicit goods
litebit 2cuse: of course. there is no centralized control so the network affect will be in effect :slightly_smiling_face:
macdac Will the people who were gracious enough to donate 25% or more from their bonus receive any incentive outside of just having username be mentioned?
dasource macdac: How does early access to Market sound? Open to ideas
macdac That sounds good
macdac I donated a good amount of coins
umbrah we are actively thinking of ways to reward donators. if you can think of a reasonable reward let us know :slightly_smiling_face:
dasource Thank you .. I am sure the 100s of people who genuinely missed out on the conversion will be grateful
macdac Youre welcome, ive been supporting this project since day one
macdac Early access would be nice ill think of something else and let you know
macdac Hope you guys look at the number of coins donated too when considering because I know that many people had multiple accounts and could have chosen to donate from only 1 but not the rest, I only have one Particl.io accoutn
michaelthecryptoguy Would you be willing to introduce that partner to the :ark: team? (edited)
umbrah michaelthecryptoguy: i don't see any reason not to :slightly_smiling_face:
michaelthecryptoguy :partywizard::slightly_smiling_face::sun: (edited)
michaelthecryptoguy @mike This might be something you would be interested in pursuing.
mike thanks for bringing up.
mr_robot I understand that details of particl being on what exchanges at what time is not currently possible due to the unforseen events of the delays of the terms of service. But is there still open communication with the exchanges and are they responding positively to the idea of listing particl when it's released?
umbrah mr_robot: a lot of exchanges are responding positively. we are actually expecting to be listed a few days after mainnet release, but could not confirm any of exchanges of course
commodore64 litebit, commodore64, and mr_robot @litebit @dasource what if someone gains access to a private market and it's determined that there are undesirable products being sold in there and they take some screenshots and post it up online like in reddit or bitcoin talk or something? Is there a governance model overseeing the private markets at all?
trixter- Particl Team: How much % of wallets are created and how much has been donated to this day?
dasource trixter-: 83% are ready for genesis with 125k Donated
trixter- 125k does that include the teams donation of 40k or without?
dasource that is without .. and the team will match upto 40k based on 5:1 formula ... so 125+25k=150k ... well short of the 250k we are aiming for
trixter- nice Im rooting for the project to achieve this goal. This is a uniqum in crypto that people give away money to help out other people. I hope you guys will provide an address for people to donate their staking rewards to so we can achieve this goal
sdcpod Yea staking to address function would be nice but @dasource said wont be possible im near future due another feature in the pipeline ?
umbrah we will do what we can to stake, but the priority will stil be focused on producing a marketplace
dasource I said "it was unlikely" ... however we wont know until we get down to the nitty gritty on it ... best way to donate to the cause is the increase your donation % before the genesis block
trixter- im alreaddy on 100%
sacode About marketing? Are you doing it all by yourselves or are you going to work with a specialized company?
umbrah sacode: we have a few partners in terms of Pmarketing
umbrah you might have seen taizen and leon fu videos, we have hired PR firms as well
sacode Yep i saw leon fu videos
umbrah :+1::slightly_smiling_face:
litebit we have been ramping up and beginning contracts with professionals beginning in June. in prep for mainnet and PART tokens being live in the wild
sacode So I presume we will start seeing some marketing very soon
sacode :slightly_smiling_face:
sacode This PR firms have any kind experience in crypto world?
submitted by Jarunik to ArkEcosystem [link] [comments]

Trading DOGE: Your full guide to trading Dogecoin for profit

NOTE: YES! This guide is long, but when you get started it's fast and easy.
Hi everyone,
my previous post about PTC's got so much hate. So I decided to make a full guide on how I made $120 last month. If the same interest and numbers remain you'll be making $100/month for two months, and $500/month for another month. On your third month, you'll be able to make over $750 if the market remains. These last couple of days I've just bought low sold high to people. The steps are really simple and anyone can do it, I'll show you all the steps in detail for maximum profits.
Disclaimer: I am not responsible for your money or actions. Any accusations to me (Rynsi) will not be accepted, use it on your own risk!
1. Introduction
2. Get started with Dogecoin
2.1 Install your wallet
3. Choose trading sources
3.1 USD/BTC
3.2 BTC/DOGE
4. Where to sell Dogecoin?
5. Good advise
6. Summary
7. Proof of Screenshots for the naysayers
8. Links
1. Introduction
I started trading Dogecoin (I'll talk about this coin soon) 5th of February, and saw a great potential in making money with it. With this guide, you'll make 15%-30% of your money back with each trade because the current market is limited, therfor YOU can provite this service that many people request. I started with $72 and now have $220, which makes my ROI 205.5%. I will show you how it's made step by step before it blows up and become viral!
2. Get started with Dogecoin
You can use it to buy goods and services, or trade it for other currencies (both other cryptocurrencies or traditional currency like US dollars). By far the most popular use the Dogecoin however is for "tipping" fellow internet-goers who are creating or sharing great content. Think of it as a more meaningful "like" or upvote, with real value that can be used all across the internet.
2.1 Install your wallet
To start using Dogecoin, you'll need a wallet. A wallet is just like your online bank account, only your entire account is stored securely on your local computer or in the cloud. From your wallet you can send and receive Dogecoin, manage your address book and review a history of your transactions.
Desktop wallets can be downloaded and run from your computer's desktop. Desktop wallets are more secure as they don't rely on a third-party server in the cloud:
Windows (click to download)
OS X (click to download)
Source code(if you're using Linux, you'll need to compile the wallet yourself)
For Windows and OS X users, simply extract the .zip file to a secure location on your computer, then double click on "dogecoin-qt" to run. For information on how to use your desktop wallet, check out this great site.
3. Choose trading sources
You know now how to get a Dogecoin wallet, but you will need to get an online wallet to save USD on, one exchange site to trade USD to BTC and one to trade BTC to DOGE. It might sound a lot to do in the startup phase, but it's really easy once you get going!
3.1 USD/BTC Exchange
There are a lot of options when it comes to buying BTC, but for now VirWox is the only one that accepts PayPal and VISA purchases. You can choose many different kinds of sites that accept USD/BTC trades, that is another story that is another story to be told. VirWox has a limit of depositing $780 per month, but after 60 days you can deposit $2800 per month, so trading as much as possible will be the best thing to do if you want money.
USD Storage: PayPal
USD/BTC Exchange: VirWox (ref / non-ref)
To deposit dollars with (VERIFIED) PayPal to VirWox, you need to be a verified user. This is to prevent frautend actions such as chargebacks and instant payments. The deposit will be instantly made after you complete the order and you can start trade. To trade, you first have to buy SLL with the USD on your account [!!!WARNING!!!] USE LIMIT ORDER and NOT market order.
Now do the same, but with the SLL/BTC exchange. I repeat, do NOT use the market order. Use LIMIT ORDER to get as much BTC as possible.
You have now successfully completed a USD/BTC exchange!
3.2 BTC/DOGE Exchange
This step is almost similar to the previous Exchange, but this step is only with Crypto-currency (read Bitcoin and Dogecoin).
BTC/USD Exchange: Cryptsy (ref / non-ref)
To exchange to BTC, you need to withdraw your BTC from VirWox to Cryptsy. This is made in the Cryptsy balance page, where you can generate a BTC deposit adress. Unfortunately, you have to wait 48 hours the first time for VirWox to accept your deposit manually due to security reasons, all the other transactions in this guide will be almost instant.
Now when you have BTC on your Cryptsy account, you have to do the same as you did with USD/SLL and SLL/BTC, really easy! When you have traded to DOGE, your downloaded Desktop Wallet comes in handy. Deposit the DOGE from Cryptsy to your Desktop Wallet and you're ready to go to the next step!
4. Where to sell Dogecoin?
This is a great surprise I have waited to tell you, you use REDDIT to sell Dogecoin! It's really easy to do. Go to /dogemarket/new and see what the current prices are. You can sell for the same price as others, undercut for faster sales or overcut for slower sales (but bigger profits!). You structure the post by [SERVICE] AMOUNT RATE PAYMENT TYPE (SPECIAL OFFER). Here is an example, my last post where I sold Dogecoin. If you follow my conversation in that post you will see how typical trades are being made.
When you have traded the Doge you can make a post on the /dogemarket verification thread where you achieve levels that will be shown for other users through your flare. Notice the orage flares, those indicate level of trades, age and amount you have traded. These are good for noticing legit and fake users, but always be of scammers!
5. Good advise
A. Only accept GIFT (friends and family option) from (VERIFIED) PayPal, DO NOT accept eChecks or transactions that has to be accepted first. eChecks and Instant payments can be chargebacked and gifts will prevent this from being possible.
B. If you have reached VirWox deposit limit, wait a while to see how the BTC/DOGE market is going. You might make some extra 1000's of DOGE if you wait a while.
C. Always be nice and kind to the DOGE community, they are really friendly, patient and polite, be so too!
D. Try to be fast in your transactions on /dogemarket, good service equals good reviews.
E. PEOPLE WILL TRY TO SCAM YOU! Always check for names including "shibe" or "doge" and new accounts.
F. Have fun! If you have fun trading and communicating with other people on Reddit, you will enjoy yourself and have a better time making money.
6. Summary: A step by step guide to make $100+/month
(and $500+/month after 60 days if market remains)
Download your dogecoin wallet.
Sign up to PayPal, VirWox and Cryptsy.
Add money to your (VERIFIED) PayPal account.
Deposit the money to VirWox.
Exchange money to SLL.
Exchange SLL to BTC.
Withdraw BTC to Cryptsy.
Exchange BTC to DOGE.
Withdraw DOGE to Desktop Wallet.
Make a post on /dogemarket.
Recieve PayPal money from buyer.
Send Dogecoin to buyer.
7. Proof of Screenshots for the naysayers
PayPal Proof
VirWox Proof
Cryptsy Proof
Desktop Wallet Proof
As if you haven't seen the whole iceberg, here is my reddit verification post
8. Links
Dogecoin Promotional video(a must watch)
Dogecoin Subreddit
Dogecoin Official website
Bitcoin Subreddit

Bitcoin Official website

This is my first guide: making over $100/month with a $72 investment. When your VirWox account is 60 days you'll make $500/month and when your VirWox account is 90 days you'll make $750/month (if market remains as it is).
I think it's a big effort by me trying to teach you how to make money, so I would really appreciate you using the referral links. If you find any errors in my guide, please don't hesitate to tell. I will be answering any questions regarding my guide as good as possible doesn't matter if you comment or PM.
I'm accepting any donations,
DHKzSsCVpv5QuJvHxWKENH9SKC3S58raBx
Thanks.
TL;DR Wanna be rich? read.
Edit: Formatting
submitted by Rynsi to beermoney [link] [comments]

[PSA] Bitcoin 101

Just a quick guide on Bitcoins and some frequently asked questions.
Firstly, if you have absolutely no idea what Bitcoins are, I suggest you visit www.weusecoins.com for the basic concepts, terminology and general information regarding Bitcoins.
Bitcoins are a virtual / digital currency (or commodity) that can be used to pay for goods and services over the internet.

Why would we use Bitcoins over the other forms of payment?

Absolutely No Chargebacks

The main reason for me personally is that there is zero chance of chargebacks like you might get with something like PayPal. Ever sold something to a random steam account and then have PayPal side with the buyer who claims that he did not receive the goods even though you transferred the items to him? With Bitcoins, one you receive payment, there is no chance of reversing or disputing the payment. What this means is that you can now sell to buyers who have little to no reputation and be absolutely sure that you will get your money.
The caveat here, to buyers is of course to only buy from reputable sellers as once you sent your Bitcoins, there is no way to get them back (or use a trusted middleman who will hold onto the sellers item while you send payment). Bitcoins was how I sold my Golden Baby Roshan without fear of losing the money as upon receipt of the Bitcoins, I sold them to someone here (New Zealand) for local currency.

Little to no fees and no regional restrictions

Usually Bitcoin transactions do not need fees to process (and take an average of 10 minutes to confirm) though this means that it might take a while longer for your seller to confirm that he has indeed received the payment when the network gets busy (i.e. lots of transactions being sent in the network). A small fee is sometimes included so that transactions get processed quicker and that minimum fee is 0.0001 BTC or $0.015 at todays (14 Oct 2013) exchange rate. This is processed automatically in the Bitcoin wallet (software) that you use. Also there is no geographical restrictions to who can and cannot use Bitcoins so they are available all over the world where ever internet is available.

Bitcoin Wallets and Addresses

Bitcoin wallets are the software programs that you use to hold and transact Bitcoins with. Wallets are available for almost all platforms (Windows, Mac, Linux, Android and to a certain extent on iOS). Most if not all wallets are available on the official Bitcoin project page:
http://bitcoin.org/en/choose-your-wallet
Be wary of third party wallets that are hosted by websites such as www.blockchain.info and www.coinbase.com. Although they are reputable companies that make bitcoin transacting easier (you don't have to store bitcoins on your own computer and can easily use them on any other computer as they are accessible by the web browser), they essentially hold your Bitcoins for you and if their service goes down, so does your Bitcoins. The downside of using software wallets on your computer is that they take up quite a bit of space (in the case of the full client; Bitcoin-QT)and can only be accessed if you are at your computer.
A Bitcoin address looks very much like an email address, only longer and more difficult to remember:
1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd
That long alphanumeric line above is an example of a Bitcoin address and is given to your buyer when they want to send Bitcoins to you. You can generate any number of addresses so that you do not have to use the same one for each transaction. Bitcoin wallets will hold all your addresses and make transactions easier as they usually allow for one click copying of address for you to paste somewhere else; minimizing the error of typing out such a long address. When a Bitcoin payment is sent to an address, the receiver will receive a notification that his or her address has received Bitcoins. There is then a confirmation period (10 minutes on average) for the network to confirm that Bitcoin address A has successfully sent Bitcoins to Bitcoin address B. A fully confirmed transaction has 6 confirmations though some websites make do with less confirmations.

Where to get Bitcoins?

There are plenty of ways to get Bitcoins. One of the ways to get them, is to mine them yourself though this requires some hardware and is no longer profitable to do so as you will waste more in hardware costs and electricity cost than some other players out there who know how to mine more efficiently. The next way is to simply buy them from someone near you on https://localbitcoins.com/, a website that uses your location to show the nearest Bitcoin sellers and buyers.
Some other places you can buy them are on exchanges such as www.mtgox.com or www.bitstamp.net
A list of places to buy and sell Bitcoins is available on the Bitoin wiki: https://en.bitcoin.it/wiki/Buying_bitcoins
You can also provide services (such as web design, homework help, etc) or sell your Dota 2 items for Bitcoins :)
Now that you have read this huge wall of text, feel free to ask any questions below which I will answer and include in this main post.
If you're interested in the technical know-how of the Bitcoin protocol:
http://bitcoin.org/bitcoin.pdf
Bitcoins are not backed by any government or institution thus no one person can make as many bitcoins as they want.
submitted by jerye to Dota2Trade [link] [comments]

Guide for first timers

I made this for my friends and family to use. Hope this heps someone. Much help!
bitcoins first: Get a wallet - just like physical money, you need a wallet to hold the money. use multibit - for a wallet - if you want options here a few http://bitcoin.org/en/choose-your-wallet go here and download this https://multibit.org/ how to backup your wallet https://multibit.org/help_backupWalletUsingPrivateKeys.html i recommend backing it up to at least 3 separate locations. example: harddrive, usb drive, encrypted dropbox folder.
go here to buy bitcoin also known as an exchange https://coinbase.com/?r=52dee75a8a2eed3e480000e5&utm_campaign=user-referral&src=referral-link
don't create wallet, click sign up button on top right. add bank information, and credit card info, and phone info - phone allows 2 factor authentication so your identity becomes much more difficult to fake and steal your money and information. I asked them to send me a SMS message instead of using app. this is the most reputable place to do this at. Never never use an online wallet!!!
buy some bitcoin on coinbase.com, and send yourself some bitcoin using your multibit wallet address(under the Request tab it shows your address there)
Now Dogecoin First get a wallet, - use the qt wallet. You can get it here for either Mac or Windows. http://dogecoin.com/ for linux use this guide - http://www.reddit.com/dogecoin/comments/1tvmnd/dogecoin_on_linux_the_complete_beginners_guide/
For a place to buy dogecoin. Use cryptsy, here is the link. https://www.cryptsy.com/users/register?refid=138894
click register new account. enter your information. go to your settings, and enable 2 factor authentication, use your cell phone number, and put in the number that they send to your phone. This makes it much more secure. you will send your bitcoins here and then buy dogecoin, then send the dogecoin to your wallet on your own computer. Backup the wallet after every purchase.
Send your Dogecoin to your own wallet. backup your wallet, at least 3 times. Use USB thumb drives. FYI, This might take away, the withdraw servers are slow as of right now. Took 3 days for me.
If you have any questions ask. Also you can buy Dogecoin or Bitcoin on ebay, do that at your own risk.
submitted by malak33 to dogecoin [link] [comments]

Bitcoin Core 0.14.2 released | Wladimir J. van der Laan | Jun 17 2017

Wladimir J. van der Laan on Jun 17 2017:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.14.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.14.2/
Or by torrent:
magnet:?xt=urn:btih:b4fc7820df95b8b39603ad246c241272ec403619&dn;=bitcoin-core-0.14.2&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%2Ftracker.leechers-paradise.org%3A6969&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on April 8th, 2014,
No attempt is made to prevent installing or running the software on Windows XP, you
can still do so at your own risk but be aware that there are known instabilities and issues.
Please do not report issues about Windows XP to the issue tracker.
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
Notable changes

miniupnp CVE-2017-8798
Bundled miniupnpc was updated to 2.0.20170509. This fixes an integer signedness error
(present in MiniUPnPc v1.4.20101221 through v2.0) that allows remote attackers
(within the LAN) to cause a denial of service or possibly have unspecified
other impact.
This only affects users that have explicitly enabled UPnP through the GUI
setting or through the -upnp option, as since the last UPnP vulnerability
(in Bitcoin Core 0.10.3) it has been disabled by default.
If you use this option, it is recommended to upgrade to this version as soon as
possible.
Known Bugs

Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
control and smart fee estimation does not reflect any change in target from the
smart fee slider. It will only present an approximate fee calculated using the
default target. The fee calculated using the correct target is still applied to
the transaction and shown in the final send confirmation dialog.
0.14.2 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

RPC and other APIs

P2P protocol and network code

Build system

Miscellaneous

GUI

Wallet

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCgAGBQJZRRTMAAoJEB5K7WKYbNJdqk0IANF5Q49ID3B77b0CwSKzjTxk
Ktp0qgvtig0ZMnzVlgjULUsRW8EbecWCQwmgRo8uUoCGmNS2u7u+s28kIIkicELE
BpWcW4eC6NdCCjB1CSnmX/tno4gFwOZutVj/XUXJCBEuBbo6fIK0cVDas5vw8UVa
gXL5ytwXeCws3z9f3iiD1Nl0k+J+dRb0sJ2u0A1+XqoMFfInMUFiP/fa9XWaimKo
62jD07IJDKtH4PEKG8v+FLZounRP7t1lhU0AiQ0Uj67mBmllwWD0KeZi0f4SokMX
aezEH+2UIW3Ph/QbG+ktZYUzbDALnRIHEBP4GQUuWiUPZKo3vAS3yhvh1nvYUW4=
=VBdE
-----END PGP SIGNATURE-----
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-June/014597.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Bitcoin Core 0.13.2 released | Wladimir J. van der Laan | Jan 03 2017

Wladimir J. van der Laan on Jan 03 2017:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn;=bitcoin-core-0.13.2&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%2Ftracker.leechers-paradise.org%3A6969&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on April 8th, 2014,
an OS initially released in 2001. This means that not even critical security
updates will be released anymore. Without security updates, using a bitcoin
wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin Core
randomly crashing on Windows XP. It is not clear
what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an alternative OS
that is supported.
No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk, but do not expect it to work: do not
report issues about Windows XP to the issue tracker.
but severe issues with the libc++ version on 10.7.x keep it from running reliably.
0.13.1 now requires 10.8+, and will communicate that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

Consensus

RPC and other APIs

Block and transaction handling

P2P protocol and network code

Build system

GUI

Wallet

Tests and QA

Miscellaneous

Credits

Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJYa2IbAAoJEHSBCwEjRsmmiQsIALbkHVVwO7nViQKH1Ub2qpD4
TplOuAP0/4vYotizuI12Gqdnu8SjPmhKwAgIXhVinE6TS4OzGNjy+6LtWGzpcpud
B1pcziZ72Mlfxdbdd1UhDMWEjoBumS9RmXMSqzTlMVlHRv4iiISzdaAROu1jHvdF
YTsnmKXB8OvcXOecxRMY9LrnpSzLALM2MYTDmYwlhhExHIA8ZqI2niky6GCfyfDi
KD7bgfIFJzlgFTpAdhQXOXtWoRV5iHqN7T29ot8Y+yIhVCRhHYXS93Z50GKbkqYV
MXsVAkpZF3qqcKYSPFjbif7faMdrMqcEiII6QhXdDTRGI/35IfuTDbWzzQlnVyY=
=ncCY
-----END PGP SIGNATURE-----
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013412.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Noob trying to use Armory and failing.

Hey folks. Trying to get Armory online. I stupidly tried to test send myself .25 BTC, from one on my online wallets to my cold Armory wallet. Because I'm an idiot, I thought I could get Armory online in an afternoon. I didn't realize I had to download the entire Bitcoin-Qt blockchain. Now I've filled up 12.5 gb on my computer and I cannot for the life of me figure out how to change the location of the blockchain to an external hard drive. The best part is I'm using OS X/mac and I can't find much help online.
I'm honestly surprised at how difficult it has been for me to get Armory online, and ultimately to see if I still have that damn money. Stupid, stupid move. Any tips for a newbie?
submitted by alecbg to Bitcoin [link] [comments]

[Meta] Re: Bitcoin Core 0.13.2 released | Luke Dashjr | Jan 07 2017

Luke Dashjr on Jan 07 2017:
I don't think release announcements are really appropriate for the bitcoin-dev
mailing list. People who want these can subscribe to the bitcoin-core-dev list
and/or the Core announce mailing list. Maybe sending to bitcoin-discuss would
also make sense, but not bitcoin-dev...
Luke
On Tuesday, January 03, 2017 8:47:36 AM Wladimir J. van der Laan via bitcoin-
dev wrote:
Bitcoin Core version 0.13.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.13.2/
Or by bittorrent:
magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn=bitcoin-co
re-0.13.2&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%
2Ftracker.leechers-paradise.org%3A6969&ws=https%3A%2F%2Fbitcoin.org%2Fbin%2
F
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
Compatibility

Microsoft ended support for Windows XP on [April 8th,
2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support
), an OS initially released in 2001. This means that not even critical
security updates will be released anymore. Without security updates, using
a bitcoin wallet on a XP machine is irresponsible at least.
In addition to that, with 0.12.x there have been varied reports of Bitcoin
Core randomly crashing on Windows XP. It is [not
clear](https://github.com/bitcoin/bitcoin/issues/7681#issuecomment-2174398
91) what the source of these crashes is, but it is likely that upstream
libraries such as Qt are no longer being tested on XP.
We do not have time nor resources to provide support for an OS that is
end-of-life. From 0.13.0 on, Windows XP is no longer supported. Users are
suggested to upgrade to a newer version of Windows, or install an
alternative OS that is supported.
No attempt is made to prevent installing or running the software on Windows
XP, you can still do so at your own risk, but do not expect it to work: do
not report issues about Windows XP to the issue tracker.
From 0.13.1 onwards OS X 10.7 is no longer supported. 0.13.0 was intended
to work on 10.7+, but severe issues with the libc++ version on 10.7.x keep
it from running reliably. 0.13.1 now requires 10.8+, and will communicate
that to 10.7 users, rather than crashing unexpectedly.
Notable changes

Change to wallet handling of mempool rejection
When a newly created transaction failed to enter the mempool due to
the limits on chains of unconfirmed transactions the sending RPC
calls would return an error. The transaction would still be queued
in the wallet and, once some of the parent transactions were
confirmed, broadcast after the software was restarted.
This behavior has been changed to return success and to reattempt
mempool insertion at the same time transaction rebroadcast is
attempted, avoiding a need for a restart.
Transactions in the wallet which cannot be accepted into the mempool
can be abandoned with the previously existing abandontransaction RPC
(or in the GUI via a context menu on the transaction).
0.13.2 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in
locating the code changes and accompanying discussion, both the pull
request and git merge commit are mentioned.

Consensus

  • #9293 e591c10 [0.13 Backport #9053] IBD using chainwork instead of
height and not using header timestamp (gmaxwell) - #9053 5b93eee IBD
using chainwork instead of height and not using header timestamps
(gmaxwell)

RPC and other APIs

  • 8845 1d048b9 Don't return the address of a P2SH of a P2SH (jnewbery)

  • 9041 87fbced keypoololdest denote Unix epoch, not GMT

(s-matthew-english) - #9122 f82c81b fix getnettotals RPC description
about timemillis (visvirial) - #9042 5bcb05d [rpc] ParseHash: Fail when
length is not 64 (MarcoFalke) - #9194 f26dab7 Add option to return
non-segwit serialization via rpc (instagibbs) - #9347 b711390 [0.13.2]
wallet/rpc backports (MarcoFalke)
  • #9292 c365556 Complain when unknown rpcserialversion is specified
(sipa) - #9322 49a612f [qa] Don't set unknown rpcserialversion
(MarcoFalke)

Block and transaction handling

  • 8357 ce0d817 [mempool] Fix relaypriority calculation error (maiiz)

  • 9267 0a4aa87 [0.13 backport #9239] Disable fee estimates for a confirm

target of 1 block (morcos) - #9196 0c09d9f Send tip change notification
from invalidateblock (ryanofsky)

P2P protocol and network code

  • #8995 9ef3875 Add missing cs_main lock to ::GETBLOCKTXN processing
(TheBlueMatt) - #9234 94531b5 torcontrol: Explicitly request RSA1024
private key (laanwj) - #8637 2cad5db Compact Block Tweaks (rebase of

8235) (sipa)

  • #9058 286e548 Fixes for p2p-compactblocks.py test timeouts on travis
(#8842) (ryanofsky) - #8865 4c71fc4 Decouple peer-processing-logic from
block-connection-logic (TheBlueMatt) - #9117 6fe3981 net: don't send
feefilter messages before the version handshake is complete (theuni) -

9188 ca1fd75 Make orphan parent fetching ask for witnesses (gmaxwell) -

9052 3a3bcbf Use RelevantServices instead of node_network in

AttemptToEvict (gmaxwell) - #9048 9460771 [0.13 backport #9026] Fix
handling of invalid compact blocks (sdaftuar) - #9357 03b6f62 [0.13
backport #9352] Attempt reconstruction from all compact block
announcements (sdaftuar) - #9189 b96a8f7 Always add
default_witness_commitment with GBT client support (sipa) - #9253
28d0f22 Fix calculation of number of bound sockets to use (TheBlueMatt)
  • #9199 da5a16b Always drop the least preferred HB peer when adding a
new one (gmaxwell)

Build system

  • 9169 d1b4da9 build: fix qt5.7 build under macOS (theuni)

  • 9326 a0f7ece Update for OpenSSL 1.1 API (gmaxwell)

  • 9224 396c405 Prevent FD_SETSIZE error building on OpenBSD (ivdsangen)

GUI

  • #8972 6f86b53 Make warnings label selectable (jonasschnelli)
(MarcoFalke) - #9185 6d70a73 Fix coincontrol sort issue (jonasschnelli)
  • #9094 5f3a12c Use correct conversion function for boost::path datadir
(laanwj) - #8908 4a974b2 Update bitcoin-qt.desktop (s-matthew-english)
  • #9190 dc46b10 Plug many memory leaks (laanwj)

Wallet

  • #9290 35174a0 Make RelayWalletTransaction attempt to AcceptToMemoryPool
(gmaxwell) - #9295 43bcfca Bugfix: Fundrawtransaction: don't terminate
when keypool is empty (jonasschnelli) - #9302 f5d606e Return txid even
if ATMP fails for new transaction (sipa) - #9262 fe39f26 Prefer coins
that have fewer ancestors, sanity check txn before ATMP (instagibbs)

Tests and QA

  • #9159 eca9b46 Wait for specific block announcement in p2p-compactblocks
(ryanofsky) - #9186 dccdc3a Fix use-after-free in scheduler tests
(laanwj)
  • #9168 3107280 Add assert_raises_message to check specific error message
(mrbandrews) - #9191 29435db 0.13.2 Backports (MarcoFalke)
  • 9077 1d4c884 Increase wallet-dump RPC timeout (ryanofsky)

  • 9098 ecd7db5 Handle zombies and cluttered tmpdirs (MarcoFalke)

  • 8927 387ec9d Add script tests for FindAndDelete in pre-segwit and

segwit scripts (jl2012) - #9200 eebc699 bench: Fix subtle counting issue
when rescaling iteration count (laanwj)

Miscellaneous

  • #8838 094848b Calculate size and weight of block correctly in
CreateNewBlock() (jnewbery) - #8920 40169dc Set minimum required Boost
to 1.47.0 (fanquake)
  • #9251 a710a43 Improvement of documentation of command line parameter
'whitelist' (wodry) - #8932 106da69 Allow bitcoin-tx to create v2
transactions (btcdrak) - #8929 12428b4 add software-properties-common
(sigwo)
  • #9120 08d1c90 bug: Missed one "return false" in recent refactoring in

9067 (UdjinM6) - #9067 f85ee01 Fix exit codes (UdjinM6)

  • 9340 fb987b3 [0.13] Update secp256k1 subtree (MarcoFalke)

  • 9229 b172377 Remove calls to getaddrinfo_a (TheBlueMatt)

Credits

Thanks to everyone who directly contributed to this release:
  • Alex Morcos
  • BtcDrak
  • Cory Fields
  • fanquake
  • Gregory Maxwell
  • Gregory Sanders
  • instagibbs
  • Ivo van der Sangen
  • jnewbery
  • Johnson Lau
  • Jonas Schnelli
  • Luke Dashjr
  • maiiz
  • MarcoFalke
  • Masahiko Hyuga
  • Matt Corallo
  • matthias
  • mrbandrews
  • Pavel Janík
  • Pieter Wuille
  • randy-waterhouse
  • Russell Yanofsky
  • S. Matthew English
  • Steven
  • Suhas Daftuar
  • UdjinM6
  • Wladimir J. van der Laan
  • wodry
As well as everyone that helped translating on
Transifex.
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013442.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Bitcoin Core 0.12.1 released | Wladimir J. van der Laan | Apr 15 2016

Wladimir J. van der Laan on Apr 15 2016:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.12.1 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.12.1/
Or through bittorrent:
magnet:?xt=urn:btih:25c4df2a822e840e972a50a31095632d87efadab&dn;=bitcoin-core-0.12.1&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%2Ftracker.leechers-paradise.org%3A6969&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
This is a new minor version release, including the BIP9, BIP68 and BIP112
softfork, various bugfixes and updated translations.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to
https://bitcoincore.org/en/list/announcements/join/.
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

Downgrade to a version < 0.12.0

Because release 0.12.0 and later will obfuscate the chainstate on every
fresh sync or reindex, the chainstate is not backwards-compatible with
pre-0.12 versions of Bitcoin Core or other software.
If you want to downgrade after you have done a reindex with 0.12.0 or later,
you will need to reindex when you first start Bitcoin Core version 0.11 or
earlier.
Notable changes

First version bits BIP9 softfork deployment
This release includes a soft fork deployment to enforce BIP68,
BIP112 and BIP113 using the BIP9 deployment mechanism.
The deployment sets the block version number to 0x20000001 between
midnight 1st May 2016 and midnight 1st May 2017 to signal readiness for
deployment. The version number consists of 0x20000000 to indicate version
bits together with setting bit 0 to indicate support for this combined
deployment, shown as "csv" in the getblockchaininfo RPC call.
For more information about the soft forking change, please see
https://github.com/bitcoin/bitcoin/pull/7648
This specific backport pull-request can be viewed at
https://github.com/bitcoin/bitcoin/pull/7543
BIP68 soft fork to enforce sequence locks for relative locktime
BIP68 introduces relative lock-time consensus-enforced semantics of
the sequence number field to enable a signed transaction input to remain
invalid for a defined period of time after confirmation of its corresponding
outpoint.
For more information about the implementation, see
https://github.com/bitcoin/bitcoin/pull/7184
BIP112 soft fork to enforce OP_CHECKSEQUENCEVERIFY
BIP112 redefines the existing OP_NOP3 as OP_CHECKSEQUENCEVERIFY (CSV)
for a new opcode in the Bitcoin scripting system that in combination with
BIP68 allows execution pathways of a script to be restricted based
on the age of the output being spent.
For more information about the implementation, see
https://github.com/bitcoin/bitcoin/pull/7524
BIP113 locktime enforcement soft fork
Bitcoin Core 0.11.2 previously introduced mempool-only locktime
enforcement using GetMedianTimePast(). This release seeks to
consensus enforce the rule.
Bitcoin transactions currently may specify a locktime indicating when
they may be added to a valid block. Current consensus rules require
that blocks have a block header time greater than the locktime specified
in any transaction in that block.
Miners get to choose what time they use for their header time, with the
consensus rule being that no node will accept a block whose time is more
than two hours in the future. This creates a incentive for miners to
set their header times to future values in order to include locktimed
transactions which weren't supposed to be included for up to two more
hours.
The consensus rules also specify that valid blocks may have a header
time greater than that of the median of the 11 previous blocks. This
GetMedianTimePast() time has a key feature we generally associate with
time: it can't go backwards.
BIP113 specifies a soft fork enforced in this release that
weakens this perverse incentive for individual miners to use a future
time by requiring that valid blocks have a computed GetMedianTimePast()
greater than the locktime specified in any transaction in that block.
Mempool inclusion rules currently require transactions to be valid for
immediate inclusion in a block in order to be accepted into the mempool.
This release begins applying the BIP113 rule to received transactions,
so transaction whose time is greater than the GetMedianTimePast() will
no longer be accepted into the mempool.
Implication for miners: you will begin rejecting transactions that
would not be valid under BIP113, which will prevent you from producing
invalid blocks when BIP113 is enforced on the network. Any
transactions which are valid under the current rules but not yet valid
under the BIP113 rules will either be mined by other miners or delayed
until they are valid under BIP113. Note, however, that time-based
locktime transactions are more or less unseen on the network currently.
Implication for users: GetMedianTimePast() always trails behind the
current time, so a transaction locktime set to the present time will be
rejected by nodes running this release until the median time moves
forward. To compensate, subtract one hour (3,600 seconds) from your
locktimes to allow those transactions to be included in mempools at
approximately the expected time.
For more information about the implementation, see
https://github.com/bitcoin/bitcoin/pull/6566
Miscellaneous
The p2p alert system is off by default. To turn on, use -alert with
startup configuration.
0.12.1 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

RPC and other APIs

  • - #7739 7ffc2bd Add abandoned status to listtransactions (jonasschnelli)

Block and transaction handling

  • - #7543 834aaef Backport BIP9, BIP68 and BIP112 with softfork (btcdrak)

P2P protocol and network code

    • #7804 90f1d24 Track block download times per individual block (sipa)
    • #7832 4c3a00d Reduce block timeout to 10 minutes (laanwj)

Validation

    • #7821 4226aac init: allow shutdown during 'Activating best chain...' (laanwj)
    • #7835 46898e7 Version 2 transactions remain non-standard until CSV activates (sdaftuar)

Build system

    • #7487 00d57b4 Workaround Travis-side CI issues (luke-jr)
    • #7606 a10da9a No need to set -L and --location for curl (MarcoFalke)
    • #7614 ca8f160 Add curl to packages (now needed for depends) (luke-jr)
    • #7776 a784675 Remove unnecessary executables from gitian release (laanwj)

Wallet

  • - #7715 19866c1 Fix calculation of balances and available coins. (morcos)

Miscellaneous

    • #7617 f04f4fd Fix markdown syntax and line terminate LogPrint (MarcoFalke)
    • #7747 4d035bc added depends cross compile info (accraze)
    • #7741 a0cea89 Mark p2p alert system as deprecated (btcdrak)
    • #7780 c5f94f6 Disable bad-chain alert (btcdrak)
Credits

Thanks to everyone who directly contributed to this release:
    • accraze
    • Alex Morcos
    • BtcDrak
    • Jonas Schnelli
    • Luke Dashjr
    • MarcoFalke
    • Mark Friedenbach
    • NicolasDorier
    • Pieter Wuille
    • Suhas Daftuar
    • Wladimir J. van der Laan
As well as everyone that helped translating on Transifex.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJXELrMAAoJEHSBCwEjRsmm75EH/0iyqFxXuJDbfzMmBbMTkXD2
/CXEeyMvs62F2ZeODE0SSqo9sXo4foiT9WI5Dq7BwAiF6jh/XE4QwBvc91BbPyGZ
1nOGEab+oe37xEOkn8MyGbHfCutsUldyKltVQjA3y685MxlSgTjl/nX6Pbpbxped
vZRog3KHRrpWAMrHdi6p/xgqX0ajxE6K1P16JMOx4W/gE9QgOPyy7+l/4WT6SyBj
k/pOLqJc+yQIOa9szS4pjLUqaSOirhsjXfro9FYjHqiTWQwAdvuK4xXgo1GrGIW1
PWs419uLmGl4bhg9jdY6v+PyPz4iUilRzoixVi8op1Rt9/AoNN1ViJ/LT15Hagw=
=h4Wp
-----END PGP SIGNATURE-----
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-April/012607.html
submitted by dev_list_bot to bitcoin_devlist [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]

How to Back Up Your Bitcoin Wallet How to make your Bitconnect QT wallet sync on Mac BTC wallet and mining walkthrough Bitcoin-QT wallet review Ravencoin: How to Setup Your Mac Wallet

~/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. Locating Bitcoin's data directory. 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. The Data Directory is the location where Bitcoin's data files are stored, including the wallet data file find / -name wallet.dat -print 2>/dev/null Mac . By default Bitcoin will put its data here: This should only exist when bitcoin-qt is currently running. It contains information (BDB state) relating to your wallet. MultiDoge is a light wallet, so it only needs to "skim" through the blockchain before it becomes usable. This is done quickly. But the wallet should only be for normal use. It cannot be used to mine Dogecoin, as the wallet will become slow and unresponsive if used this way. Dogecoin Core on the other hand, downloads the entire blockchain. Moving the wallet blockchain files to another directory. Note: To move the blockchain data directory we are going to use the command line parameter. Also this works with almost any crypto currency QT wallets (Bitcoin, Litecoin, Zcash4Win, Monero, Dash, Doge, Verge, etc)

[index] [21299] [26741] [23889] [12865] [28925] [9210] [1644] [2096] [9419] [10277]

How to Back Up Your Bitcoin Wallet

Elon Musk about Tesla, Bitcoin & Ethereum Giveaway, plans for the future Big interview Live Elon Musk 42,467 watching Live now After Effects character animation workflow - Duration: 1:25:25. How to Sync RavenCoin QT Wallet FAST - 2.1.1 - Duration: ... How to install Electrum Wallet for Bitcoin (BTC) on a Mac - Duration: 7:42. ... Location: United States Restricted Mode: ... Mine took 6 hours to sync to the blockchain!! In this video I will show you how to quickly fix the syncing issue with Bitconnect QT wallet on a Mac. If this fix does not work please CLICK the ... iphone bitcoin wallet, mac bitcoin wallet, my bitcoin wallet, paypal bitcoin wallet, raspberry pi bitcoin wallet, bitcoin google wallet, hack bitcoin wallet, bitcoin wallet ios, bitcoin wallet ... This short tutorial explains what a Bitcoin wallet backup is and how to create it on 3 different wallets: Blockchain.info, Bitcoin-QT and MultiBit. For more information and tutorials about Bitocin ...

Flag Counter