Bitcoin Wallet Passphrase Cracker CryptoCoins Info Club

My bitcoin-qt wallet encryption passphrase is not recognized: "The passphrase entered for the wallet decryption was incorrect"

I have an older backup when the wallet was not yet entcrypted. Can I just exchange the current wallet.dat with the non encrypted back-up and use my wallet as before?
Edit: Sorry could open the wallet now. I used a passphrase, where I was sure I can never forget - BUT - for additional security I put a few hyphens between the syllables of that word. AND I FORGOT THAT I DID THAT. - Maybe that can serve as an example for others to not rely too much on ones memory.
submitted by reflexfelix to Bitcoin [link] [comments]

"Wallet decrypter returned empty response" when importing from bitcoin-qt to

So I've had a bitcoin wallet for a while using bitcoin-qt (I started it over a year ago). I'd like to move my wallet/accounts/funds/keys/everything to now since it's been a long while since I've used bitcoin-qt and I have over 60 weeks of catching up with the blockchain to do. I have a balance of 7.35mBTC that I want to transfer over to and I've tried using blockchain's import tool but I get a "Wallet decrypter returned empty response" whenever I try to import my wallet.dat file or a wallet backup that I make through File > Backup Wallet in the bitcoin-qt client. I don't know what's wrong, but I just want my 7.35mBTC in my wallet rather than in bitcoin-qt.
submitted by CarlFriedrichGauss to Bitcoin [link] [comments]

Even More Satoshi-era Bitcoin Moves—What's Going on?

Even More Satoshi-era Bitcoin Moves—What's Going on?

Even More Satoshi-era Bitcoin Moves—What's Going on?
Another batch of 50 Bitcoin (BTC)—that has been lying dormant since 2010 and is worth around $570,000 today—was moved today, according to
The block explorer’s data shows that these 50 coins were first transferred to the address on November 9, 2010, as a coinbase transaction. This means the Bitcoin was a block reward received by a miner.
The wallet hadn’t received or sent any other transactions—until today. The only exception is 0.00000547 BTC that was sent to the address in late August as part of a spam-like transaction aimed at over 300 different wallets. Most likely, that was a so-called “dusting attack” primarily used by malicious actors to trace BTC movements.
Today, the coins have been transferred to three different addresses: two Bech32 (a SegWit format) and one P2SH, mainly used for multi-signature and non-native SegWit transactions.
The transfers were 30.16, 12.48 and 7.34 BTC, in size. Upon confirmation, the new wallets split the coins into 2–3 additional transactions each and sent them further down the line.
As Decrypt reported, increasingly more coins from the earliest days of Bitcoin are “waking up” lately. Since the start of October, two large caches—50 BTC ($570,000) and 1,000 BTC ($11.4 million)—were moved out of their deep slumber. Prior to that, another batch of 50 BTC was transferred in May.
Yet, not everyone thinks this is a big deal. Referring to today's movement of coins, Ingo Fiedler, co-founder of Blockchain Research Lab, told Decrypt, "Those coins were minted nearly two years after network launch. I would not consider them satoshi-era Bitcoin and do not see any significance in them moving."
It's not as though Satoshi is returning, right?
📷 Telegram TOTBTC: 📷 Register at:
submitted by TOTBTC-Official to u/TOTBTC-Official [link] [comments]

Guide for novice crypto investors

Bitcoin is a decentralized system, any user of which could control the movement of their own funds. You can use the currency to make transactions, pay for purchases, receive transfers, and exchange it for cash. For transactions, a special address is used, encrypted with a 16-character key. The buyer decodes the code to transfer bitcoins to the specified address.

Bitcoin Mining

Mining is a process that ensures the security of the BTC system, which adds new blocks to the blockchain in chronological order (new transactions). Blocks are added when the codes are decrypted, the transaction is completed, and bitcoins are transferred or exchanged.
The main cryptocurrency is generated by miners using software that solves cryptographic problems. The reward for a new block is agreed by all network participants, but usually amounts to 12.5 bitcoins. Part of the user fees for transactions also goes to reward the miners. Cryptographic tasks become more complex every year to prevent inflation (mining complexity).

Features of the transaction

  1. Anonymity. The address that Bitcoin is sent to consists of 30 characters. You can track the flow of transactions, but the address is not always associated with a real person.
  2. Security. The balance of bitcoins is fixed in a cryptographic system with a public key. Only the owner of a private key can send cryptocurrency to other addresses.
  3. Unable to cancel. It is no longer possible to cancel the transaction after the transaction has been completed.
  4. Deregulation. Everyone can use cryptocurrency.
  5. Coverage and speed. Information about the transaction is transmitted incredibly quickly, and confirmation is received within a few minutes. No one knows the buyer’s physical location.

Where to buy Bitcoin?

There are Deposit systems that use crypto-exchanges. So, to buy Bitcoin, you will first need to top up your balance, buy the digital currency itself, and then withdraw it to your Bitcoin wallet, paying a Commission for withdrawing coins. The cheapest method of buying is buying on the stock exchange. The exchange rate is as close as possible to the market rate.

BTC rate

The current exchange rate of the coin is calculated based on the average price on the largest currency exchanges. For example, you can track the exchange rate on our Bitniex exchange. The Bitcoin exchange rate is constantly changing, during the day it can change by 10% in one direction or another.

The choice of crypto-currency wallet

A cryptocurrency wallet is a place where digital currency will be stored. The most secure method of storage is using paper or electronic wallets.

TOP secure cryptocurrency wallets

These wallets are one of the most secure crypto wallets in the world:
submitted by Bitniex to Bitniex [link] [comments]

Particl Marketplace: Where Sellers Meet Buyers

Particl Marketplace: Where Sellers Meet Buyers
People had been speculating since the dawn of crypto when the world’s largest online marketplaces, the ones of the Amazon caliber like eBay, Etsy or AliExpress, and, well, Amazon itself, would start to accept cryptocurrencies. There were a slew of rumors, opinions, and theories thickly interspersed with false reports popping up here and there of Amazon and its little cousins being on the verge of embracing cryptocurrencies. On top of that, someone has actually posted a petition on to add Ether to Amazon as a payment method.
by StealthEX
Long story short, that was a waste of time. High hopes fell flat, and people lost religion. But not all. As the common wisdom goes, when hope dies, action begins. This exposition describes one such effort which tries to bring to fruition the idea of a decentralized marketplace for trading goods and services. And as you might have already figured it out, with a cryptocurrency as a means of payment. So let’s welcome Particl Marketplace and see what it has to offer – and what Amazon has missed.

What is it, in simple words?

Particl Marketplace is an online marketplace where you can trade goods and services. Not a big deal, you may think. However, what distinguishes it from places like Amazon as well as cryptocurrency-enabled marketplaces is the decentralized nature of purchases on Particl. You can think of it as a variety of a decentralized cryptocurrency exchange (aka DEX) where trades are being conducted on-chain. But in case of Particl, it is goods and services that are being traded, not fiat or crypto, with deals on-chain as well, fully encrypted and decentralized.
Particl is a global peer-to-peer privacy-centered marketplace that uses an automated two-party escrow system. It is crypto-agnostic and designed to work with any cryptocurrency, creating a secure, highly-scalable environment supported by a privacy-focused blockchain-based platform. The team behind the project sees its mission in developing “a new decentralized, private and democratic economy” that is governed by the network of its users, with no central authority or middleman getting in the way.
In the project developers’ own words, Particl enables everyone to participate in a free, anonymous exchange of all kinds of goods, without paying any fee and regardless of geographical location. To be sure, you are already thinking about Silk Road and its dark fate, and that the government is going to crack down monumentally on Particl one day. Well, the outcome may vary as the payments on the platform are made using its own cryptocurrency PART, with its laser focus on privacy and anonymity. But more on this later.

How did it grow up?

The development of the Particl project started in early 2017 with the release of the white paper describing the team’s vision for the marketplace, which was shortly followed by a successful seed funding that brought in enough funds ($750,000) to support the development of the project for a year (it turned out sufficient to last for over two years).
These donations helped to establish the Particl Foundation, a non-profit Swiss organization with the goal of providing legal protection for the project to ensure its sustained development and compliance with government regulations. It receives 10% of all the staking rewards generated on the Particl network, making the project self-sustainable and free for most uses.
Unlike other such projects in the crypto arena, Particl has been using its own blockchain from day one, which happened to be July 17, 2017. It was specifically designed to be crypto agnostic by supporting and working with any cryptocurrency. Additionally, it supported the smart contract tech out of the box, giving users an ability to build all kinds of decentralized applications (dApps) that can be directly integrated into the Particl marketplace.
On May 31, 2018, the Particl Marketplace, the Holy Grail of the entire endeavor, was made available for alpha testing on the testnet of the project, which later split into development and stable branches. It went live with the mainnet release of the Particl Open Marketplace on August 12, 2019, which featured Particl Desktop 2.0.0, a client-side application providing user interface and built-in wallet functions.
On November 25, 2019, the Particl Desktop 2.3.0 client was released that enabled Bitcoin payments and marked the introduction of untraceable transactions. With the help of the new in-wallet exchange module, everyone can easily swap their bitcoins for the native PART coin. Moreover, the module allows seamless integration of third-party accountless exchange services right into the marketplace, with StealthEX being one of them.

How is it different from other marketplaces?

The common solution many P2P marketplaces implement to protect buyers and sellers from the other party failing to honor their end of the bargain is through third-party escrow, where the “third-party” in the majority of places and cases is the platform itself that the market participants must mutually trust. In short, it is a single point of failure. And the selling (pardon the pun) point of the entire Particl’s marketplace is its decentralized escrow, which is a thing entirely between the two parties engaged. No middlemen allowed here!
And these are not empty words. Particl implements the concept best known as Mutually Assured Destruction (aptly shortened as MAD), a military doctrine you are certainly familiar with, and probably even afraid of, that consists in a mutual destruction of two belligerent parties in an all-out nuclear holocaust. If you are curious, the idea stems from the game theory and has a lot to do with the Nash Equilibrium, of John Nash’s fame. In a nutshell, Particl removes the need for a trusted escrow agent by introducing MAD escrow smart contracts.
A MAD escrow contract allows to lock funds in a multi-signature address that can be released only if all the parties sign off on the transaction. So both the seller and the buyer lock in the contract an agreed amount for a specified period of time, with the buyer also depositing the payment for the items purchased. The escrowed funds are released when both parties confirm the fulfillment of the agreement. Should one party break the terms, the funds remain locked for good causing a mutual financial loss until both parties agree to sign off.
Another crucial aspect of Particl Marketplace is its end-to-end privacy. The problem with conventional marketplaces acting as an escrow agent is that the communication between the parties should be open to the agent for it to serve as an arbitrator. With Particl, it is no longer required, and all messages between the buyer and the seller are encrypted. Despite being public, only their recipient can decrypt them, which effectively makes messages untraceable.
This is also where the PART coin turns up quite handy. It enables three different privacy modes, and with the most secure mode, the Anon mode, PART transactions utilize the RingCT privacy protocol, which hides both the amount transferred and the identity of the parties transacting. Accordingly, every part of the entire Particl trading environment is thoroughly decentralized, and the full anonymity of market participants is maintained at all times, making the platform a completely trustless marketplace. Big Brother is no longer watching you.
Aside from that, you can stake PART and generate a source of passive income for yourself. Particl uses a custom Proof-of-Stake consensus protocol, allowing you to get a piece of the pie in the form of new coins created at each block according to the scheduled inflation process. The annual inflation rate is initially set to 5% and goes down 1 percentage point every year until it finally floors at 2% indefinitely. Moreover, these rates are a bare minimum as they assume that all PART coins have been staked. Otherwise, the income will be bigger and better as the same rewards are paid to fewer coins.
Additionally, your passive income through staking PART will be augmented by the fees generated through the everyday marketplace operations. Whether it is network fees collected via PART transactions or marketplace listing fees paid by the sellers, all of them contribute to the stakers’ rewards. At the end of the day, staking PART can turn into a profitable business once the Particl platform starts to attract more traffic. In simple words, the more popular the market gets, the more fees it generates, the more coins the stakers earn.
As PART is a standalone cryptocurrency, it can be used outside Particl Marketplace as well. So if you plan on using it for purposes other than eCommerce, it is traded on several exchanges, for example, HitBTC and Bittrex, with more exchanges to list PART in the future. There are native Particl wallets available for storing PART such as Particl Qt with Ledger support, Particl-cli, and Particl Copay Wallet, with the latter available for both the desktop and the mobile. There is also a third-party multicurrency Flare Wallet, enabling cold staking for Particl.
Running Particl is a collective effort, which means no operational costs and no company bagging profits from it. The marketplace buyers don’t pay any commissions other than tiny network confirmation fees, while the sellers are only charged a small listing fee to keep spam listings to a minimum. This creates a highly competitive environment, with the sellers making more profits and the buyers having access to cheaper goods and services as a result.

What’s in the pipeline?

The next major release of the Particl Marketplace should have been Particl Desktop 2.4.0, but it was later rebranded as Particl Desktop 3.0 to reflect its breakthrough nature. It is set for release in the second half of 2020 and will enable the addition of user-created markets and storefronts, effectively turning the Particl marketplace into a network of specialized markets.
And if you think about it, that makes perfect sense. Say, you have a social network account highly merited and full of karma that you want to sell, whatever your reasons might be. Then creating a dedicated market for trading such accounts privately and securely may look extremely appealing to you. Whether it is the right thing to do is another matter, of course.
Kidding aside, it is obviously not about selling or offering something that the society on the whole doesn’t approve of or frowns upon. If you are a freelancer, for example, a graphics designer or a translator, you would be certainly interested in the future freelancer markets – along with your potential employers. Put simply, birds of a feather should flock together.
To keep things in perspective, popular freelancer markets that exist today charge up to 10-20% of what you would get from your client if you negotiated directly. All in all, establishing communities across the marketplace seems to be the next logical step in the natural evolution and growth of the platform. In fact, it is a little surprising that the Particl team didn’t come up with this idea earlier.
Meanwhile, we wish Particl success and good luck in achieving their goals and aspirations.
And remember if you need to exchange your coins StealthEX is here for you. We provide a selection of more than 250 coins and constantly updating the list so that our customers will find a suitable option. Our service does not require registration and allows you to remain anonymous. Why don’t you check it out? Just go to StealthEX and follow these easy steps:
✔ Choose the pair and the amount for your exchange. For example ETH to PART.
✔ Press the “Start exchange” button.
✔ Provide the recipient address to which the coins will be transferred.
✔ Move your cryptocurrency for the exchange.
✔ Receive your PART coins!
Follow us on Medium, Twitter, Facebook, and Reddit to get updates and the latest news about the crypto world. For all requests message us via [email protected].
The views and opinions expressed here are solely those of the author. Every investment and trading move involves risk. You should conduct your own research when making a decision.
Original article was posted on
submitted by Stealthex_io to StealthEX [link] [comments]

Recovery of my wallet

Upfront, my mothefatherlanguage IS NOT English, so pretty please excuse my grammer and spelling mistakes if I made one (or more)...
So apparently over the last few months bitcoin has raised a lot in value and I had still had some in my wallet. Now I forgot my password and on my old laptop I tried about 100 versions and tweaks to it and wrote them down to keep track.
In the meanwhile I got a new laptop and wanted to get rid of the old one, so what did I do? I copied my wallet.dat file, installed the newest bitcoin-qt (I think that's the name of the wallet I used). I posted my wallet.dat file in the map where I installed this wallet and now I need to a few things: 1. Now if now downloading the blockchain and putting in the correct password will work. Or didn't I copy the right files? 2. If I'm still on track of retreaving my bitcoins, is it possible to install the wallet on an external harddrive and download the chain on there? Because my current harddrive is not big enough.
  1. And if I'm still on track now, are there programs shich can help me open my wallet with brute force, with which I mean I input the general shape of my password and give the program the symbols allowed instead of others so he can do all the different combinations.
Thanks in advance for responding to my post!
Love and kisses Mr Booger
submitted by Bloogert to Bitcoin [link] [comments]

My thoughts on Ben Lawsky's proposal from the point of view of a startup with no funding

When you store money in a safety deposit box essentially, you, the bank and the government have signature on the box. With the government having final say on seizing the funds.
EDIT: Are we actually securing virtual currency?- i'm not so sure.
Our users backup one of their keys offline and hold the password to decrypt the other one. essentially, THEY are securing it.
So, Ninki Wallet enters alpha testing then, this bomb drops:
(n) Virtual Currency Business Activity means the conduct of any one of the following types of activities involving New York or a New York Resident:
(1) receiving Virtual Currency for transmission or transmitting the same;
(2) securing, storing, holding, or maintaining custody or control of Virtual Currency on behalf of others;
(3) buying and selling Virtual Currency as a customer business;
(4) performing retail conversion services, including the conversion or exchange of Fiat Currency or other value into Virtual Currency, the conversion or exchange of Virtual Currency into Fiat Currency or other value, or the conversion or exchange of one form of Virtual Currency into another form of Virtual Currency; or
(5) controlling, administering, or issuing a Virtual Currency.
In the development of Ninki Wallet we wanted to bring a new level of security and usability to Bitcoin, we decided on a 2 of 3 multi-signature architecture in order to give the user of the wallet ultimate control, provide a layer of services ourselves via countersigning and at the same time limit our exposure in the event of a server hack, ie. even if they get our key, they can't spend our user's funds.
Under the definitions proposed by Mr. Lawsky
(2) securing, storing, holding, or maintaining custody or control of Virtual Currency on behalf of others;
I am not 100% sure, but it does appear we fall into the above category, as do other web wallets
Storing: we technically store 2 of the 3 private keys but can only access one. The other is AES256 encrypted by the user's password via a salted pbkdf2 and using a CSPRNG to generate the IV for the encryption itself. ie. from our point of view we are storing nothing!
Question: Is storing encrypted data the same as storing data? Are we actually storing virtual currency?
Securing: We are definitely securing virtual currency
Transmitting: We countersign the transactions and broadcast them to the Bitcoin network, we are definitely transmitting.
It appears we need a Bitlicense, even if one of our users in Japan sends Bitcoin to a user in New York, we are in breach of these regulations.
Given our wallet can send and receive to/from external Bitcoin addresses, how can we possibly ever comply! Someone sets up a wallet account, provides their address and ID, full compliance etc., then someone sends them money from a Bitcoin qt client running in NY which is received in our wallet, we are in breach!
So, where to go from here:
Option 1:
Exclude US IP addresses altogether
Users can always use VPN to use our service. All it would take is one incident of a NY user using our site, and we are in breach.
Option 2:
Try and comply.
The demands are way too much for what is essentially a project that aspires to develop into something bigger, we are not in a position to appoint compliance officers etc. I mean, get real!
Some of the demands could be automated quite easily, things like reporting transactions over $10,000 involving a NY resident, however we then need to take an address and ID from every user who joins our site- just to prove they don't live in NY!
We are not in a position to do that, i mean, think about the logistics there. All kinds of ID from all over the world.
Option 3:
Give up. Not an option.
Also, I guess once these come into effect, and other web wallets, bitgo etc. will be breaking the law as they currently don't ask for addreses/identification.
Does anyone have any ideas?
submitted by Ninki-Ben to Bitcoin [link] [comments]

Please Advise: How to restore old (2013) wallet and get back in this rodeo?

Last time I traded BTC was Dec 2013, when my Mt Gox account got hacked - all USD funds were used to buy BTC, and those coins were then transferred to an unknown attacker. This happened a few months before their complete meltdown however, so I don't believe I was included in the bankruptcy lawsuit (though I did apply). Oh well, a few hundred bucks gone :'(
I quit running my low-payout miner shortly thereafter - basically took the BTC I had left, put it in storage, and forgot about it, thinking "the rest might be worth something, someday".
Over these last couple months, I started looking into how to access it and possibly liquidate. Now, I come to you fine redditors, please help me to not get burned again.
So what I have is an old wallet.dat or two, with anywhere from 0.05 to 0.5 btc in it, and all the software I used at the time. Not at home rn but I believe I used Bitcoin-Qt v0.5. I have tried simply running that again, but it never fully syncs with the network. I have tried on multiple PCs and after about a week of sync time, the client crashes more and more often, until it crashes immediately on startup every time. Afaict that client no longer works to sync with the blockchain.
I have also read about the split that created bitcoin cash, and I figure if my coins can be split I'd be leaving money on the table to not pursue it. But idk if I can do that by just downloading the latest Bitcoin-Core and copying my wallet over, or if I need to take a more careful approach.
So here are the questions I haven't been able to confidently answer myself:
1) Am I correct in my assumption that I need an up-to-date blockchain to open (decrypt with password, view balances) a wallet at all?
2) What is the safest way to open this old wallet, allowing me to have my BTC, and BCH if possible?
3) I may have forgotten my password and need to batch-test many combinations of ~10 keywords, so I need about (10!) guesses. Can I do this from a command line / script or would I need a different utility?
4) About how long would the turnaround time be - after getting my wallet sync'd up to date w/ blockchain - to create an account somewhere and sell the coins? (All using USA banks/providers since I suspect it will be safer this way.)
(Bonus Question) Are graphics cards still usable for mining? I basically pay a fixed cost for electric no matter what my usage is, so I figure if I can I might as well do it.
Thank you so much for any help you can provide! I hope to be back in this market with you all very soon!
submitted by CStheCS to Bitcoin [link] [comments]

Anyone use KeyScrambler (anti-key logging software)

Was wondering if anyone in here has ever used KeyScrambler or know a lot about it? It encrypts keystrokes at the driver level and decrypts them for legitimate apps, thereby defeating key logging malware. It supposedly works with many bitcoin wallets, including at Qt based wallet.
Anyone know if this is effective? Or if it's been vetted for security holes? I can't find any criticism about it.
submitted by protekt0r to Monero [link] [comments]

Happy new year, shibes! First update of 2016

In a bit of a change, I want to use this update to focus on what we need help with. As always, we're primarily limited by the amount of time available to make progress, and it would be brilliant to get more contributions to the code, web site, design, etc. So, right now I'm mostly sinking time into CATE, initially to get a HD wallet out, and longer term hoping to make it into a functional decentralised exchange. There's Dogecoin Core 1.10.4, which is an internal release intended to help us test the changes in Bitcoin Core 0.11.4, act as a bridge rather than making the jump directly to Dogecoin Core 1.11 based on Bitcoin Core 0.12. Lastly, there's the Ethereum sidechain work which is on hold while we get existing projects progressed, but there is a bounty for that one, so if you can code, you may want to look into that.
CATE first of all - if you know Java, especially if you know the JavaFX framework, please do come help with this. Immediate priorities that can easily be picked up by someone else:
For all of these we'll need pull requests raised, there's instructions on how to do this in the Github instructions, or give me a yell here if you get stuck:
Dogecoin Core - the current work on 1.11.4 is stuck because Qt 5.5 doesn't compile with print support on OS X. If anyone wants to investigate further, it would be brilliant. There was a theory it required CUPS to compile, but I believe latest is no, it just doesn't want to compile. Otherwise it's looking like we'll move back to an earlier version of Qt.
Ethereum - there's a bounty for this one! We're setting up an Ethereum-based fund (it's actually in beta testing, make sure it's stable) for this at the moment, but we've had 5k Ethereum and 2 BTC offered ( ). It's a much more complex task, as it requires getting coins to go not just to Ethereum, but back again, to claim the bounty, but it's also not small change (about $5k at current values I believe). An excellent start would be modifying BTC relay to do one-way burn to Dogecoin, and we'll continue working on how to get freeze/thaw to work. It's going to need at least a soft fork to enable freeze/thaw, which means we need the current softfork finished (please upgrade if you're a miner, we're so very close) first, as well as getting some progress on Dogecoin Core 1.11.
Lastly, if anyone wants to help with the website, please do go ahead and submit changes. It's a Github based website, so you can submit pull requests as with any other project. It's up at:
I'm aware a lot of what I'm talking about will be new to many of you, but much of it's new to the devs too, just take a deep breath and dive into the various guides out there. And with that, I'll leave you in peace for a bit!
submitted by rnicoll to dogecoin [link] [comments]

Lore v2 QT on Raspberry Pi

To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (, I thought if anyone was interested I'd show you how to get the full QT version running on the Pi on the Jessie with Pixel desktop. This works and has been soak tested for several days now on a standard Raspberry Pi 3. I have since added some coins and it stakes a handful of times a day.
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
These instructions assume you are starting from scratch with a completely blank OS.
Download Jessie with Pixel from:
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
sudo nano /etc/dphys-swapfile 
and Change the CONF_SWAPSIZE from 100 to:
Exit nano with control + x to write out the file.
Then, run the following to restart the swapfile manager:
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start 
Now, launch the browser and download the Lore 2.12 binaries for ARM here:!k2InxZhb!iaLhUPreA7LZqZ-Az-0StRBUshSJ82XjldPsvhGBBH4 (Version with fee fix from 6 September 2017)
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written ( and the versions of Boost and the Berkeley DB need to be the same as below.)
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
In the Terminal window, change directory to where you put the binaries, e.g.:
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x * 
That marks the binaries as executable.
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget tar -xvzf download cd boost_1_62_0 sudo ./ sudo ./b2 install 
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
sudo ldconfig 
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
sudo apt-get install qrencode libprotobuf-dev libevent-pthreads-2.0-5 
Now we need to install the Berkeley Database version 6.2.23. This is the version Lore v2 uses. Bitcoin still uses 4.8 which is 10 years old! This doesn't take too long.
wget tar -xvzf db-6.2.23.tar.gz cd db-6.2.23/build_unix ../dist/configure --prefix=/usr --enable-compat185 --enable-dbm --disable-static --enable-cxx 
I find this next section of the Berkeley instructions worked better just switching to root, which can be fudged by running sudo su before the rest:
sudo su make make docdir=/usshare/doc/db-6.2.23 install chown -v -R root:root /usbin/db_* /usinclude/db{,_185,_cxx}.h /uslib/libdb*.{so,la} /usshare/doc/db-6.2.23 
Now we're going to go up a couple of directories to where the binaries were:
cd ../.. 
Then run the client!
And there you have it. Should hopefully end up looking a bit like this:
Using the Bootstrap can save a while syncing. Download it at:
Place the bootstrap.dat file into the ~/.lore directory.
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop 
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None; 
Power usage and payback time
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
Securing your Pi
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
You'll be prompted to enter the old and the new passwords.
Security by default
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
sudo apt-get install ufw sudo ufw allow from to any port 22 sudo ufw --force enable 
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. if you're on a 10.0. address).
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
You can query the status of the firewall like this:
ufw status 
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options:
Back up & Recovery
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
In Windows, one way is to use Bitlocker drive encryption for the entire drive. You should follow the instructions here to encrypt your flash drive before your wallet.dat is on there, and don't forget the password!!
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself:   There are almost certainly free packages with similar functionality, I have just used that one for years.
Either way, if you want to just make sure your USB drive is encrypted, you can do so in one-click in Finder before you put the sensitive files on it:
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
./bitcoin-qt -rescan 
And if that doesn't do the job, do a full reindex of the blockchain:
./bitcoin-qt -reindex 
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
In the meantime, feel free to comment with your best practices.
submitted by patcrypt to blackcoin [link] [comments]

Lost Bitcoins help!

I'm new to bitcoin, had someone send me bitcoins to an address I set up through the Desktop version Bitcoin-qt. So far it's taken a week to sync 1 time, and it came across an error. Bitcoin started "reindexing blocks" got back down to a year or so then another error. I ended up going over to blockchain and opening a wallet. And added my address as a "watch only" address. I've been trying to insert the private keys but I have no idea what the hell I'm doing and i've tried almost everything I can think of. Also my encryption program GPA keeps showing an error when trying to decrypt my private keys. Been trying to retrieve the bitcoins for almost 3 weeks, googling what I need to do with no luck. Please someone help, I'm ready to throw in the towel, but I'm too persistent to give up. I lost a good amount of money, i'll reward whoever can help me retrieve the bitcoins. Its $75 worth, but would help me out greatly. Thanks!
TL;DR: I suck at bitcoin, please help me figure out how to retrieve my lost bitcoins!
submitted by rchamma to BitcoinBeginners [link] [comments]

Of Wolves and Weasels - Day 745 - Weekly Wrapup #100!

Hey all, GoodShibe here!
This was your week in Dogecoin:
(Note: We now have a Weekly Wrapup Time Capsule that collects all 100+ Weekly Wrapups!)
This Week’s oWaWs
Top Images/Memes of the Week
Community Chest: Seeking Community Feedback
Other Dogecoin Communities
Dogecoin Attractions – Neat or interesting things to check out/ Take part in this Week
Other Interesting Stuff
Did I miss anything? Do you have a Dogecoin community you want featured? Let me know!
It’s 8:45AM EST and Sunday is FunDay, right? Right? Our Global Hashrate is holding at ~1430 Gigahashes per second and our Difficulty is holding at ~16674.
As always, I appreciate your
submitted by GoodShibe to dogecoin [link] [comments]

(1) Is it true that encrypting an *existing* bitcoin-qt wallet.dat file will "invalidate" any existing backups? (2) Can I use unicode characters - eg ♥ - in the bitcoin-qt wallet passphrase?

I have an existing bitcoin-qt wallet.dat file which I want to encrypt - using the command in the bitcoin-qt Settings menu, involving creating a passphrase.
I have 2 (possibly somewhat related) questions:
(1) If you encrypt an existing wallet.dat file, will the backups of the old wallet.dat file still work?
(2) Can you include unicode characters - eg ♥ - in the passphrase used to encrypt a bitcoin-qt wallet.dat file?
Worst-case scenario: The answers to (1) and (2) are both "no" - and I attempt to encrypt an existing wallet using unicode, and my backups no longer work (due to a new pool of addresses somehow being created?) and the passphrase isn't what I think it is (due to the unicode characters somehow being misinterpreted?) - and then I could lose all my coins??
(1) The following (old, short) thread claims that after you encrypt an existing wallet, any previous backups of that wallet will no longer work:
Obviously, the the first response in that thread was slightly wrong, for saying that the "server" creates a new pool of 100 addresses to draw on. So using word "server" here was certainly incorrect - but maybe the gist of what they were saying might still be correct? (if you simply change "server" to "client").
I can actually understand that there might be reasons why encrypting a wallet.dat file could cause a new pool of 100 addresses to be generated.
But it does not make sense to me that this would make any older (unencrypted) backups instantly useless.
It seems to me that these older, unencrypted backups would still have their private keys intact, and could thus be used in certain (perhaps limited?) ways - such as:

(2) It seems that including a few unicode characters in the bitcoin-qt wallet passphrase would make it a lot stronger (since unicode is a much larger set of characters than ascii), so I would like to include a few.
But it would be more reassuring if it could be explicitly stated that this is indeed supported.

Possible catastrophic interaction between (1) and (2)?
If the answers to (1) and (2) were both "no" (ie, if you encrypt an existing bitcoin-qt wallet.dat file then any existing backups will not work, and unicode characters do not work in bitcoin-qt passphrases), then I'm worried there could be some kind of catastrophic interaction between (1) and (2) where I lose all my coins, as follows:
(1) I encrypt my existing wallet - making my old, unencrypted wallet.dat file now invalidated (due to something involving a new pool of addresses being generated?)
(2) I use a passphrase which includes unicode characters which bitcoin-qt appears to accept at the time of creation, but which doesn't work at the time of trying to decrypt the wallet.dat file (due to something going wring with how the supposed unicode characters are actually interpreted while being entered or copied-and-pasted?).
In this possible worst-case scenario, my old backups of wallet.dat no longer work, and my newly encrypted wallet.dat has some password which I'm not able to correctly enter anymore.
Sorry to be so paranoid about this!
Other remarks:
(a) I did do a (limited) test of unicode capability for bitcoin-qt wallet.dat passphrases: simply by creating a new (empty) wallet.dat file, and creating a passphrase for it involving unicode characters, and then attempting to change the passphrase (which requires entering the old passphrase that contained unicode characters).
This did seem to work ok: it let me re-enter the old passphrase (which included unicode characters) to create a new passphrase.
However, since this is an empty wallet (and since bitcoin-qt would ask for the passphrase only when attempting to actually spend from an encrypted wallet), I did not see a way to fully test whether the passphrase actually worked to decrypt a unicode-passphrase-encrypted wallet for the purpose of spending from it.
(I'm still downloading the rest of the blockchain and it's going to take at least another week on my slow connection, so don't see how I could send a small amount to the new wallet to test it either. My existing wallet.dat file was originally created on an internet-connected machine a long time ago, but it's been offline ever since, so in some sense it's kinda-sorta been in somewhat "cold" storage all this time, and I would prefer to avoid putting it online on a "hot" internet-connected machine until absolutely necessary.)
(b) Long-term, I am actually also in the process of setting up a proper cold storage system based on Armory, which I have installed on 2 Ubuntu machines (one offline and one online).
But I have a slow internet connection, and the backups of this old wallet.dat file have been sitting around unencrypted for ages (I've been relying simply on then being physically inaccessible).
Now some "things" are coming up over the next few days where I some better security right away, and it's probably going to take over a week for Armory/bitcoind to update my local copy of the blockchain.
So in the meantime, I also need some basic additional security right now - so encrypting the existing bitcoin-qt wallet.dat file using a strong passphrase (and making some new backups) seems like it could be a reasonable initial approach.
Thanks for any help!
submitted by encrypt_throwaway to Bitcoin [link] [comments]

Guide: How to redeem and sell bitcoin diamond (bcd) from ledger nano s (Segwit)

I spent two days to figure this out but I think I know how to solve this, just currently stuck and need your help! I had btc stored on a nano s segwit wallet before the fork.
Bitcoin diamond was forked from bitcoin on block #495866 (nov 24 2017) and launched the mainnet Jan 5 2018 (I think). There is currently very little information about this project and very little support on exchanges, wallets and mining.
The only light wallet currently have a splitting tool is Bither for Android but they do not support Segwit. If you had your btc in a segwit wallet before the fork you can't use this method.
Otherwise follow this: Or this:
You get 10 bcd for every btc and current price is 0.001 btc. That means you get $160/ forked btc which is 1% free money. Is it worth it? For me it is. You can use same method for both SBTC and BCD. Other methods can be used for BTX, BCX and BFX but have to wait for me. Need segwit support in Coinomi and/or Bither.
In my BCD case it was a bit more complicated but hopefully possible.
  1. Move btc from ledger nano to somewhere save
  2. Download the BIP39 converter (standalone version). Unplug your internet and run the html:
  3. Enter your ledger 24 word mnemonic. Select BIP49 derivation path. Find your btc address that contained btc right before block 495866, copy private key. Use a block explorer:
  4. Find the tx ID that sent those btc and verify in bcd explorer if you have any bcd before you continue (click on the actual address will not work for some reason, shows empty). My tx had 3000 confirmations.
  5. Now the complicated part =) You have to build bitcoin diamond core app from source because it doesn't exist yet:
  6. I built it for windows x64 using this guide (by cloning bitcoin diamond from github instead of bitcoin when you come to that step). Took 1h.:
  7. Actually quite cool you can run Ubuntu on Windows 10! You can build for 32 bit as well but not when you have installed dependencies for x64. The last step will copy the binaries to your windows folder: "make install DESTDIR=/mnt/c/workspace/bitcoindiamond"
  8. Run bitcoindiamond-qt in windows and let it sync with network. Took me 12h with fiber connection.
  9. Go to help and open console. If your wallet is encrypted, decrypt for 10min using: "walletpassphrase your-wallet-passphrase 600".
  10. Import old btc address as watch-only to check bcd balance. True means it will rescan the blockchain. Rescan took 1h with a decent PC (no SSD):
  11. If you see your BCD balance, now Import your btc private key into the watch-only address. No need to rescan again, thus "false".:
Ok here is where I'm stuck. I can see my balance but it's not spendable. I also tried to import private key directly (with sync) with empty core wallet but balance is still zero. It does not pick up the transaction! Anyone know how to solve this?
Rest of the guide when this is solved:
submitted by Joohansson to CryptoCurrency [link] [comments]

Electrum 2.0 has been tagged | Thomas Voegtlin | Mar 01 2015

Thomas Voegtlin on Mar 01 2015:
Hash: SHA1
Dear Bitcoin devs,
I just tagged version 2.0 of Electrum:
The website will be updated later today. The release
notes are a bit dense, due to the large amount of changes and new
features in this release. In the coming weeks we will be adding more
detailed documentation to the wiki and to the website.
There has been a very long hiatus in Electrum releases, because it
took me a lot of time to decide about the new seed derivation method
and wallet structure. Now that this part is done, I hope that we will
resume to a faster release pace.
I would like to thank all the people who contributed to this release,
developers, beta testers, but also people from this list who provided
useful feedback.

Release 2.0

phrase includes a version number, that refers to the wallet
structure. The version number also serves as a checksum, and it
will prevent the import of seeds from incompatible wallets. Old
Electrum seeds are still supported.
and use a gap limit of 20.
P2SH addresses ("2 of 2", "2 of 3").
transactions, that includes the BIP32 master public key and
derivation needed to sign inputs. Serialized transactions can be
sent to cosigners or to cold storage using QR codes (using Andreas
Schildbach's base 43 idea).
"2 of 3" multisig wallets and Google Authenticator. Note that
wallets protected by this service can be deterministically restored
from seed, without Trustedcoin's server.
wallets, to send and receive partially signed transactions.
window that pops up if you click on the QR code
outputs, and raw hexadecimal scripts.
start the daemon if it is not already running, and the GUI will
connect to it. The daemon can serve several clients. It times out
if no client uses if for more than 5 minutes.
keys. A watching-only wallet is created by entering a list of
addresses in the wizard dialog.
wallet files cannot be read by older versions of Electrum. Old
wallet files will be converted to the new format; this operation
may take some time, because public keys will be derived for each
address of your wallet.
the command line:
stable. Another script was added to Android, called Authenticator,
that works completely offline: it reads an unsigned transaction
shown as QR code, signs it and shows the result as a QR code.
Version: GnuPG v1
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Another Wallet Cracked - How To Determine Point Of Entry?

I use Bitcoin-QT for my wallet. Earlier today it was drained of the entire amount. The wallet was being run on Ubuntu with version v0.8.6.0-g03a7d67-beta & QT version 4.6.2. The computer does not have a public faced IP. It does have port 8333 forwarded to it. The wallet was encrypted using a password I do not use anywhere else. I'm currently checking for recently changed files, etc but I'm not finding anything useful. The only thing that comes to mind was recently using vanitygen on it to find a custom address.
Here is the blockchain link of the withdrawal:
I'm guessing at this point it's no longer safe to use this wallet. I'm betting the private keys have been copied, and no addresses in it are safe to use.
Edit: I think I found the point of entry. One of the machines on the network hosts a word press site. This machine only has port 80 forwarded to it. The file "wp-redirect.php" was the last file altered. An IP from Leaseweb - Netherlands kept hammering this file until the timestamp that correlates with the BTC transfer occurred. The file wp-redirect has been renamed. I can put it up somewhere if someone would like to view its contents.
Edited Edit: Still unknown how the wallet was decrypted.
tldr: Even if you think your wallet is safe, it's not.
submitted by Go3Team to Bitcoin [link] [comments]

Questions regarding wallet recovery

Been in the Bitcoin space since 2012, so I am a bit embarrassed to ask these questions.
I have a bunch of Bitcoin QT/core wallets ranging from 2013-2015 that I know for a fact have transactions histories on them. I am trying to look at potential funds on them (0.1BTC and whatnot left over on them). However, when I look at them, I find a 0 balance and no transaction history, even when the wallet.dat file is like 300-500kb when they are usually 80kb. All of my wallets would have been encrypted. My question is, would you see the balance/transaction history before decrypting the wallet? If so, can anyone think of a reason why I don't see anything in these wallets?
Which leads me to my next question, when I move these wallets, every time I restart Bitcoin Core it rescans the network. Is there any way/software that I can import multiple wallet.dat files to check all the wallets at once rather than waiting 1-2 hours between files for rescans.
Thank you all so much, and god bless Bitcoin!
submitted by btcwalletquestion to Bitcoin [link] [comments]

Sweeping from paper wallet - Invalid private key (code -5)

So a while ago I created a few paper wallets with BIP38 passphrases. Everything seemed to go according to plan, their balances transferred in and I can check them on the blockchain. But now, I'm trying to get some of the coins out...
I followed the various guides (this Litecoin one proving most helpful), but am still getting the "code -5" error.
I open my Vertcoin-qt wallet and enter walletpassphrase 'myqtpassphrase' '60' and that works (I think), but then I enter importprivkey 6PvTSw...keystuff and I get the error. Am I supposed to enter the QT passphrase, or the BIP38 passphrase from the paper wallet?
I've tried the Android app, but when that scans the QR, it says "Cannot classify input."
L'il help, please?
Edit to add: Reading here, it sounds like I need to decrypt the BIP38 wallet before trying to import it?
submitted by iamthinksnow to vertcoin [link] [comments]

Bitcoin wallet.dat Recovery

I'm attempting to recover a wallet for someone and have run into a few problems. Basically I was provided with the wallet.dat file the bitcoin qt client uses. The person had encrypted their wallet, and forgot part of the password used to decrypt it. I'm trying to extract the hash in the wallet using a python script in john the ripper, but when I run it on the file I DO get a hash out, however it is 64 char longer than the standard bitcoin hash. Is there a reason? I cant use this hash and I'm wondering if its a version issue or if there is a better piece of software to recover the encryption hash.
submitted by Risin247 to Bitcoin [link] [comments]

Help with staking coins Please

Hello everyone!
I am new to Hyper, and the Hyper qt wallet.
I am seeing that I have to decrypt my wallet, or at least 'unlock' it with my encryption pass phrase in order to stake coins. Is this correct? It seems counter secure, considering I was under the impression I should have my wallet encrypted to prevent possible theft. I have no experience with Bitcoin QT/Core either, only Lightweight clients.
Also, can anybody ELI5 how the staking works? Thae video posted on this subreddit does not explain it. How often is it compounded? 5%, but how often?
submitted by pablo325 to hypercrypto [link] [comments]

May have just lost my bitcoin savings...

So early on in the year I realized I still had 20 bitcoins on the exchange (after a while of being out of the loop in the bitcoin world). I took these off and made a cold storage true crypt hidden volume. I then added those in and bought some additional bitcoins before and during the beginnings of the major bubble.
I decided to decrypt the volume to transfer the btc to a new wallet (I wanted a change from bitcoin-qt), but when I type in my password to the inner volume of the truecrypt container nothing is inside. I'm freaking out a bit... that is around 3k in bitcoins that seem to have disappeared.
The weird part is in the outer volume I created a couple placeholder text documents with other passwords and semi-private documents inside, and I can view them fine. Why the eff would my wallet.dat backup just go missing like that? Is that even possible?
I made a watch only address on and it still shows my 30btc in the address.
I clearly remember verifying everything worked right after I made the volume and transferred the wallet over... I guess I don't really expect anyone to be able to help, but man this sucks.
submitted by SlimyMeatballs to Bitcoin [link] [comments]

Bitcoin Brain Wallet Cracking Tools - YouTube How to get a bitcoin wallet  What is the best bitcoin wallet?  Bitcoin wallet review Bitcoin Wallet - Download, Encrypt, Backup, & Use - YouTube Bitcoin wallet decrypt. Opens wallet file with forgotten ... HOW TO ENCRYPT AND DECRYPT WALLET

Send, receive, and store SLP tokens directly in your Bitcoin Cash wallets. These tokens exist on the Bitcoin Cash blockchain itself. Instead of being used as a currency, SLP tokens can represent literally anything—from dollar-pegged stablecoins to virtual gaming assets and loyalty points. More than just a safe place to store Bitcoin . Take control of your Bitcoin. Our non-custodial wallet ... On the other hand there are few QT wallets which will ask your password just for the purpose of staking or minting. So always remember this before encrypting your wallets; “If you lose your passphrase or password you lose all of your funds”. Either memorize your password or at least note it down in a paper and put it in a safe place. Alright, let’s see how to unlock the wallet now. In ... QT wallet – Most of the crypto currency core wallets are developed using QT software framework. They are available for Windows, Linux and Mac. QT wallets are professional client and offers full function that’s available for a currency. Also they are heavy as it is known to download the complete blockchain to your local computer. Alternatively you can also run bitcoin-qt with the -server option. Flaskwallet is not a thin client, you need to run bitcoin nodes to manage them through the RPC API. You can also connect to many altcoin daemons. I have use this app to manage a dozen or so different crypto currencies. See the caveats section though. Features¶ Manage multiple crypto currencies and nodes/wallets; Sign messages ... Securing the Bitcoin-Qt or bitcoind wallet ... If something goes wrong with your system, and you need to decrypt the new user's files, you'll need its decryption key. ecryptfs-unwrap-passphrase. It will ask you for your user's password and give you the decryption key. WRITE DOWN OR SAVE THE CODE IT RETURNS because you will need it if you ever have to pull your data off while the OS is not ...

[index] [36090] [398] [41281] [41708] [5052] [168] [44544] [17205] [35221] [30392]

Bitcoin Brain Wallet Cracking Tools - YouTube

Make some extra $$ lending: Signup for DavorCoin: OR Signup for Bitconnect: This is a short video on setting up, ... Published on May 1, 2017 This is a video tutorial on how to encrypt & decrypt your PIVX Wallet. By encrypting your wallet, it will provide a layer of protection and safety; we would recommend you ... This is a step by step guide to using the Bitcoin wallet client. How to download it. How to Encrypt is and protect your Bitcoin. How to back up your wallet a... Bitcoin Brain Wallet Cracking Tools ----- Bi... part two of my tutorial on how to decrypt the android bitcoin wallet to find the seed and transfer it to multibitHD so that you can (if you choose to) claim bitcoin cash (assuming you had bitcoin ...