How to import private keys - Bitcoin Wiki

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

Windows / Linux Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest Linux TLDR is here
Unfortunately, I don't have access to a Coldcard or Ledger. I'm not sure how the setpin or -stdinpass parameters are handled on that HW.

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe shell
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to Bitcoin [link] [comments]

Windows Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest TLDR is here

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to TREZOR [link] [comments]

IOTA funds were stolen (3.49Ti ~500k$) on 12th March 2020 after network relaunch [longread]

Hey CC comunity!
First of all, sorry for posting it a bit late I have some serious changes in my lifestyle and business due to Coronavirus situation in the world. For those who are infected I wish to get well soon and all the rest to stay safe and to stay home.
Here is my short story:On March 12th I made similar but short post regarding my stolen IOTA in the sub IOTA. First of all I met around 50% downvotes, I don’t know why but it seems that IOTA’s community don’t want to see posts regarding stolen IOTA, I got a lot of critics for using Trinity wallet instead of hardware and so on. But I see nothing strange using desktop wallet and it doesn’t matter whether it is IOTA Trinity or Bitcoin QT or Ethereum wallet unless in has strong manually typed password, VPN connection and some other security things. Or maybe IOTA’s community was afraid of unwanted bad attention during that market crash that day. So because of that experience I decided to make a post here at CC.
Some short reminder of what happened before my funds got stolen (https://status.iota.org)
Some news:https://www.coindesk.com/iota-foundation-suspends-network-probes-fund-theft-in-trinity-wallethttps://cointelegraph.com/news/iota-foundation-investigates-funds-allegedly-stolen-from-trinity-walletshttps://www.theblockcrypto.com/post/55955/iota-foundation-funds-stolen-users-of-trinity-wallet
If you don’t want to read that news here are some facts with timestamp:
February 12th 2020 - 18:55
As a precaution we ask you to keep your Trinity wallet closed for now.
February 12th 2020 - 19:20
After initial investigation we decided to turn off the Coordinator to make sure no further theft can occur until we find out the root cause of these thefts. (Lets say: “blockchain stopped”)
February 14th 2020 - 17:50
We have found the exploit.
February 15th 2020 - 00:50
After successfully identifying the attack on Trinity through a third-party integration
February 17th 2020 - 02:23
We have just released a safe version of Trinity Desktop to allow users to check their balance and transactions. This version (1.4.1) removes the vulnerability announced on 12th February 2020. (I’ve installed this particular version)
February 21st 2020 - 18:43
ACTION MAY BE REQUIRED TO PROTECT YOUR TOKENS IN TRINITY.
February 24th I left my country for some working trip
February 26th 2020 - 13:10
We are currently in the testing phase of the migration tools, once testing completes the tools will be audited by a external party. If this all goes well we are aiming to release these tools later this week.
February 29th 2020 - 19:15
The Seed Migration Tool is now available.
March 6th 2020 - 15:17
REMINDER: You have until 5PM (UTC), Saturday, 7th March to migrate your seed.
I’m still out of the country but I’m pretty sure I’m safe coz I’ve installed 1.4.1 wallet which removes the vulnerability.
March 8th 2020 - 18:15
The migration period has ended.
I got back to my country
March 10th 2020 - 16:45
We are aiming to resume value transactions around 5PM CET today.
March 10th 2020 - 18:15
The network coordinator has resumed operation. (Let’s say “blockchain restarted”)
Now my turn:
My balance by that time (https://imgur.com/EJiB6it)
March 10th
I’ve decided to send my IOTA to exchange until I buy Hardware wallet and sort it out how it worksTest transaction to exchange 5Gi:JQ9DZPGUFLBJTLDLIKQBWLUBOXJULKIQFSWKNYVFIHETSZJOTGRYEZZELE9BZFVUEBGATEITPDTXXHZVD
It took exchange 24 hours to credit it to my balance…
March 11thFirst large transaction to the exchange (~23% of my net holdings of IOTA) 1Ti9YGGTHDKARCBVEPWUYURYEAKSKUNITGCGKSCJRXBVKHLBHEXXTNAWOFNPOBGHG9IKCZRABFNBJHVWNZIZ
All over again… 24h to credit it to my balance.
March 12th
I’ve opened my Trinity wallet and found out that money were stolen 3.4TiPOUBLIDSDZSNLKYBHVDAAEGVKGZ9PGKCBKRGUKEKIUQGSEWZNBQCHLLKIAZKEYHJVGJD9GYHT9JJNY9VW
screenshot of transaction with stolen IOTA (https://imgur.com/DtXbjOs)
All performed transactions (https://imgur.com/M8Qj2jC)
Same day I’ve made first post on reddit to get some attention to the happened situation. At the same time I’ve start to search for some technical support through over official telegram groups:
iotatangle
(https://imgur.com/McmrF3L)I’ve send a message where I’ve stated that my funds were stolen after network relaunch. Got some response from user Basti he invited me to another group with general discussion.screen shot 1 (https://imgur.com/hvDuoQA)screen shot 2 (https://imgur.com/MewdNm5)
Our short dialogue continued at the general discussion group iotacafe
(https://imgur.com/e9ErcPW) Where Basti introduced me to the IOTA Foundation member Antonio Nardella (https://imgur.com/WxZRk8N)
Before I started my conversation with Antonio I decide to get some information about him. I’ve found a Medium post with some welcoming words to Antonio Nardella.
(https://imgur.com/KK4zoOv) telegram(https://imgur.com/VquNCpi) medium
Seems legit.
Of course I couldn't be 100% sure it was him but the information he asked for wasn’t really sensitive so decided to share all I knew and all I did.
(https://imgur.com/X3Ha02Q) He also mentioned a wallet integrated service MoonPay, whether I used the wallet with this service or not and it didn’t matter if I used the service it self.
I’ve informed him that I used 1.4.1 wallet which was recommended to install on February 17th 2020(https://imgur.com/iZdNcm7)
When he gathered all the necessary information regarding loss of funds he took the time for sending this information for investigation team.
After a long awaited answer I got the same day this:
“Hello, I was informed that the loss of tokens is associated to the person/team responsible for the Trinity wallet attack via a third-party dependency from Moonpay.
As suggested on https://status.iota.org/, please file a report with the local police and to cite the following case number when doing so: LKA Berlin, Center for Cybercrime, case number: 200213-1717-i00290.”(https://imgur.com/Gov1v0i)
So, reinstalling the wallet didn't help me to avoid the loss of funds.
Well if my funds are proved to be stolen then it means - yes, I’ve used the Trinity wallet between the December 17th 2019 and the February 17th 2020. And yes, I wasn’t able to make seed transition during the given period. I was out of the country starting form Feb 24th till March 8th. I can even proove it with my border passing stamps… You know I didn’t use to take 4.5Ti with me just in case I would need an urgent seed transition. Could you imagine thousands of people with their multimillion Bitcoin holdings carrying private keys everyday with them just in case they would need seed transition… The funds were stolen not by my mistake but IOTA developers/foundation/etc (lets say IOTA team) mistake.
At the end of my story I want to take your attention to the fact that I didn’t compromise my PC neither wallet nor password nor seed. All my fault was for using the desktop wallet… How can you imagine your user without using your software/services/etc… I want to publicly call IOTA team (especially mr David Sonstebo) to cover not only those which were to happen back in the Feb 2020 but all the loses which were caused by that wallet vulnerability. (https://www.coindesk.com/iota-founder-personally-refunding-hack-losses-to-safeguard-projects-remaining-reserve)
Thanks for reading and thanks for your time!
submitted by blockchainified to CryptoCurrency [link] [comments]

Looks like I lost 1.54 BTC to a Core wallet mishap

Hey all,
So I was looking to cash out portion of my Bitcoin portfolio. Up until now, all I'd used was exchanges and the online Blockchain.info wallet. I was using Bitpay until now, however I was now on my Macbook and couldn't find a proper .dmg file for the Bitpay client. I then downloaded the Bitcoin Core wallet, one of the 5 I believe payment protocol enabled wallets listed on Bitpay (keep in mind I know nothing about the Core wallet other than that it holds a private key that I should back up). After downloading it, I generated an address and sent my Bitcoin to it. I made sure to double check the address multiple times. I then waited for confirmations - only to realize the Core wallet needs days to sync up with the blockchain and I wouldn't be able to use my Bitcoin until it does - quite unfortunate. I then waited. I didn't back up my private key right there and then because I didn't really see any need to. After it downloaded 50% of the blockchain, I realized my Macbook didn't have enough space. This is where it seems to have all gone to shit.
I had no space left on my Macbook so I deleted the contents of the 'blocks' folder. It was just a bunch of 'block' and 'rev' files numbered off. I then restarted the Bitcoin-Qt wallet and it allowed me to redirect the download to an external drive that I had inserted. Right here, my Bitcoin address disappeared from the 'Requested Payments History' tab. I tried to use the dumppprivkey command but the console just didn't recognize the public key.
I'm pretty much making this post as a last resort after talking to some friends as well. Anyone know if I made some dumb mistake and there actually is a way to get my Bitcoin back?
Here's the address to anyone that may think I'm trolling:
https://blockchain.info/address/1Nf1YCHT7SqyoJq6A4e7LfaEmK1wyiFUMs
submitted by pete8892 to Bitcoin [link] [comments]

Bitcoin Core 0.14.0 Paper Wallet

Hi. Weiß jemand wie ich eine Paper Wallet erstelle mit Bitcoin Core 0.14.0?
Seit tagen bin ich auf der suche im Internet und finde nichts. Das ist ganz schön mühsam eine Anleitung zu finden. Was ich weiß ist wie ich an den QR Code komme von meiner Empfangsadresse, auch wie ich den Privat Key auslesen kann von dieser Empfangsadresse. Der Privat Key hat jedoch keine QR Code. Des weiter stell ich mir die Frage wie ich aus dem Bitcoin Core Client eine Paper Wallet erzeugen kann wenn doch die erstellte Adresse in meiner Bitcoin Wallet vorhanden ist, dann ist es och keine Paper Wallet mehr? Ich kann die erzeugte Adresse ja auch nicht löschen nachdem ich mir eine Paper Wallet erstellt habe. Gelesen hab ich es im Internet das man mit Bitcoin Core oder Electrum eine Paper Wallet erstellen kann, nur nicht wie das gehen soll.
Kann mir bitte jemand helfen?
Vielen dank im voraus
pintfa
Hello. Does anyone know how I create a paper stock with Bitcoin Core 0.14.0?
Since days I am on the search in the internet and find nothing. This is quite painstaking to find a guide. Was I know is how I get to the QR code from my receiving address, also as I can read the private key from this receipt address. The private key has no QR code. The further I ask myself the question as I from the bitcoin core client a paper exchange can but nevertheless the created address in my Bitcoin Wallet is present, then it is och no paper purse anymore? I can not delete the pattern address so synonymous. Read I have it in the Internet the man with Bitcoin Core or Electrum a paper Wallet can create, just not how that should go.
Can someone help me please?
Thanks in advance
Pintfa
submitted by pintfa to BitcoinBeginners [link] [comments]

HELP! Bitcoin qt client crashed on my computer with a database error! Lost all my bitcoins?!

hey guys,
The bitcoin qt client was catching up with the blockchain (5 days worth), when after maybe 15 minutes, it comes up with an error, "database corrupted" or something along the lines of that. I looked it up and users said to delete everthing in my %appdata/roaming/bitcoin% directy except the wallet.dat file.
So I did that, and downloaded the latest bitcoin qt client, but as it's got 252 weeks to catch up on, it shows 0 btc, is this normal? Will it show my bitcoins whilst it's done updating?
It should show it at the end, right? Once it's seen the transactions on the blockchain? Sorry, I'm just ultra panicky atm from not seeing my bitcoins :S
EDIT: GOT MY BITCOINS. For anyone that has this problem in the future, it's 99.99% likely it's a RAM problem. Took my dodgy ram stick out and used a rescan tag & it was all good to go! You can also import the boostrap.dat file.
submitted by TheNewHero to Bitcoin [link] [comments]

Difference between .key and .wallet?

What's the difference between exporting your private keys, and copying your .wallet/.dat (depending on what client you're using) for backing up? I've searched but I can't find anything.
submitted by JAMESLJNR to Bitcoin [link] [comments]

Corrupted wallet.dat with 18 btc - Possible to restore bitcoins?

I have a wallet from yore, had 18 btc that got corrupted and I kind of just lost interest in bitcoins. Well now that 18 is woth $2K or so and I fired up a new bitcoin-qt wallet with that wallet.dat file to see if it would read it. Well it almost did.
The GUI read 18 unverified bitcoins at first, and as the blockchain neared completion, it verified every bitcoin. I was so excited. But then it crashed with a runaway exception "can't open database file wallet.dat -30974"
I get that error when I try to send a bitcoin too. Any chance of restoring this near-working wallet?
EDIT: Bitcoins have been recovered!!!!!!! The final solution was provided by musicbunny, to which I am extremely greatful for his out-of-the box solution. I think pywallet suggested by eof would have done the trick too. The keys probably could have been extracted, but I was running into trouble with my version of Python. Maybe it needed Python 2?
submitted by bitbeast to Bitcoin [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:
TL;DR
(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??
Details
(1) The following (old, short) thread claims that after you encrypt an existing wallet, any previous backups of that wallet will no longer work:
https://pay.reddit.com/Bitcoin/comments/1ccfdk/encrypting_walletdat_in_bitcoinqt/
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?)
and
(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]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
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.
OSX
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), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

cold storage compatibility issues

Hello, I have been a fan of electrum because of its offline capability. I like that I can use Bitcoin while storing my private keys on a computer that has the wifi card removed and hot glue stuffed in the Ethernet port. However it looks like maybe the electrum developers have over-promised and under-delivered in this regard. Or, maybe they simply do not have the time, energy, resources to make this work in real life.
Let me explain. I have an old-ass computer that is running Ubuntu 12 (precise), this computer has electrum 2.5.4 installed with a cold-storage wallet that has my private key.
I want to send some bitcoin from that address to a new wallet on my desktop so I can spend the bitcoin. So I installed electrum (newest version 3.3.8) on my desktop, imported the bitcoin address, and created a transaction. Then I sent the transaction to the offline computer out of band, and verified that the out-of-band transmission worked by comparing the hash of the txn file on both the offline and online machines. Then I tried to open the txn file on the offline machine with Electrum 2.5.4. Well, guess what, it didn't work. Electrum 2.5.4 printed to the console:
Traceback (most recent call last):
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/main_window.py", line 2261, in do_process_from_file
self.show_transaction(tx)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/main_window.py", line 577, in show_transaction
show_transaction(tx, self, tx_desc)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/transaction_dialog.py", line 37, in show_transaction
d = TxDialog(tx, parent, desc, prompt_if_unsaved)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/transaction_dialog.py", line 48, in __init__
self.tx.deserialize()
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum/transaction.py", line 523, in deserialize
d = deserialize(self.raw)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum/transaction.py", line 454, in deserialize
d[inputs] = list(parse_input(vds) for i in xrange(n_vin))
OverflowError: Python int too large to convert to C long
That's pretty frustrating, the first thing I tried was to install Electrum 2.5.4 on my Desktop and try to create a new unsigned transaction with Electrum 2.5.4. However, this is a no-go because old versions of Electrum cannot connect to Electrum servers any more. So I have to try to update the Electrum on the Offline computer. But I'm not even sure if this is possible considering how ubuntu 12 it's definitely out of support at this point and the offline computer does not even have python3 installed, let alone the GTK stuff or whatever is probably required to run Electrum.
I'm starting to regret choosing a GUI-based wallet for my offline storage considering how hard it is to actually use this and how it simply melts over time... even just 5 years is is enough time to completely melt and destroy this software and make it un-usable. Time Catches All. So now I have to go out and buy a new computer that can run the updated OS, so I can install the new version of Electrum, so I can access my bitcoin.
Do you have any other ideas? Has anyone else experienced anything like this?
submitted by throwaway_23f32f to Electrum [link] [comments]

My backups, do I have to update them periodically?

Sorry for all of the questions. You don't have to answer them all individually, I just need a little direction. Thanks in advance.
One thing that has confused me for a while is keeping backups of my wallet. Say I back up the wallet dat on to flash drives. If I take one of those drives and put it in a vault for a year or give it to my family for safe keeping or whatever, is that backup now missing 1 year's worth of transactions? If I had added a few BTC to this wallet during that time, would my backups not receive it? Or would it update to the new balance when it eventually synced again with the network again?
Lastly if I created a wallet address with the express purpose of just receiving deposits, could I put it in a safe deposit box for years at a time and have access to my money when I import it down the line? What if they update the QT client between when I make my back ups and now, will the wallet.dat still be compatible?
I want to have a wallet where I can just store some of my coins to avoid temptation. At very least just break up my coins into multiple wallets such as one of spending and one for savings.
I've heard that armory allows multiple wallets, are they a web based client or do I retain control of the wallet file? I've only been using QT because it seems like the most complete package .
submitted by whateverbites to Bitcoin [link] [comments]

Old Wallet Recovery

Hey everyone! I had a quick question in regards to an old wallet backups I found on one of my ancient thumb drives and was hoping someone would be able to help me out with how to restore them. The date on one is back from 2015 and has no file type, but when I edit it with notepad++ it is a string of like... 30,000+ characters (Ex: ...GVkX1/wDGzGJfKJDGHSOQYg8gvp+...). The second backup I have is a .dat file which appears to be some sort of encrypted format with some 90,000 characters.
From my research I haven't seen any programs to restore these wallets. Any help would be appreciated!
submitted by throwawaybtcnewbie to BitcoinBeginners [link] [comments]

Can I send bitcoins while QT is out of sync?

EDIT So I tried it anyway. Being somewhat of a risk-taker. Just tested with .1 BTC, worked out great. So I sent the other remainder of the transaction. Bitcoin-QT wasn't synced but the blockchain picked it up in about 10 minutes and I had my funds in LocalBitcoin ready to sell today. Thanks for the input, guys, seriously appreciated. This is an awesome community.
Hi.
I am one paranoid mo'fo'. Which means, I over-think every damn thing. So. Apply that to bitcoin and we have a lovely recipe for anxiety.
My situation.... Bitcoin QT is taking for EVER to sync with the network. I need to sell a few of my Bitcoins today. But I am afraid to do so while QT is 'out of sync.' Is it generally safe or unsafe to do this?
Thanks in advance, you awesome people, you.
P.S. if this is the wrong section on Bitcoin, please kindly redirect my idiocy.
submitted by somedude247 to Bitcoin [link] [comments]

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys

https://preview.redd.it/u4x1o4p37zc41.png?width=700&format=png&auto=webp&s=01d1ff52c0b7fc1c9ae5bb4f161979ad1f4bb559
I’m a longtime blockchain enthusiast and developer and one of my biggest gripes about this space is how quickly every new project is widely dismissed as a “scam” or “shitcoin” by so many people before it even gets off the ground. Sure, there is a lot of uncharted territory with pirates lurking to steal your bags left and right but with a small amount of personal education you can exist safely in the world of crypto I promise! With this article I aim to help lift your knowledge a little higher while helping keep your funds a little safer!

So What Is Happening?

On Tuesday February 18, 2020 a new coin named Ring (RNG) will be minted. This coin aims to bring two unique and fresh methods of proofing to the crypto game, quite literally: Agent-Based Hive Mining (borrowed from LCC) and Proof-of-Play Mining, where literal gameplay is used to hash and reward miners! To celebrate and help spread the word, the team is giving away claims of free RNG to all holders of the following coins:
  • Litecoin Cash (LCC)
  • Bitcoin (BTC)
  • Dash (DASH)
  • Dogecoin (DOGE)
It's being touted as the world's first crypto "4-way fork" but I'd really call it more of a "4-way claim" since its a brand new chain and not based on the code of any of the rewarded coins. It's simply a clever method of allowing a wider range of coin holders a chance to participate in the launch of these exciting new features!

How Will This Process Work?

On the 18th of February, a balance snapshot will be taken of the four chains listed above. Anyone holding a balance with any of these coins at the time of the snapshot will be forever eligible to claim their RNG at any time. Because the only way to prove ownership of a crypto address is to supply the private keys, and pretty much EVERYONE will tell you to guard those things with your life, below I will outline exactly what to do so there is absolutely 0% risk of losing a single satoshi! This method will apply to ANY claim rewards of any coin in the future as well. Always practice #SafeForking!

How Do I Safely Claim My RNG?

STEP 1 -- BEFORE THE SNAPSHOT -- VERIFY ACCESS TO YOUR PRIVATE KEYS
All core wallets will allow you to export a private key of any address in your wallet but many third party services like exchanges and hot wallets do not allow access to them. In these cases you will need to send your funds out of the third party service and into some kind of personal wallet where you can reach the private keys yourself. Then just wait for the snapshot to happen…
To make things easier on yourself, you can optionally collect your original coins into as few addresses as possible BEFORE the snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s just less work!
\** SNAPSHOT HAPPENS HERE... ****
STEP 2 -- ATER THE SNAPSHOT -- EMPTY ALL ADDRESSES YOU WISH TO CLAIM
After the snapshot is confirmed, withdraw all coins OUT of each of your origin coin addresses into brand new addresses leaving the original ones quite empty. This way when you import later there is NO risk of losing anything! Also know that after you import these private keys you should never use them again for safety’s sake! It’s kind of the whole reason you’re even reading this article in the first place.
STEP 3 -- EXPORT PRIVATE KEYS FOR ALL ADDRESS YOU WISH TO CLAIM
This is the most difficult part, are you ready? Once each claim address is confirmed to be EMPTY, you must obtain each one’s private keys. This will entirely depend on the wallet you use (QT example below) but for all core wallets there is generally an option for exporting private keys somewhere in there. Collect them all!
How to Export QT Wallet Private Keys:⛔️ — DISABLE INTERNET FOR SAFETY — ⛔️- Open the QT wallet client- Click on HELP in the menu bar- Click on DEBUG WINDOW- Click on the CONSOLE tab- Click inside the input box at the bottom(if your wallet is locked…)- Type: walletpassphrase [Password] 600(this unlocks your wallet for 10 minutes)- Type: dumpprivkey [Address]- Copy the output hash, paste it into a list somewhere.(repeat as needed, clear your clipboard history after)- Type: walletlock (if applicable)⚡ — RE-ENABLE YOUR INTERNET —
STEP 4 -- IMPORT ALL PRIVATE KEYS INTO RNG CORE WALLET
\** PLEASE VERIFY THAT EVERY CLAIM ADDRESS IS EMPTY BEFORE CONTINUING... ****
The final step is to simply import each of these private keys into the new Ring Core Wallet to claim your free RNG rewards. The wallet handles this part automatically and you will see your new RNG balance right away. You can find this option under the File > Import Private Keys menu.
Importing a private key is the only way to prove ownership of a crypto address so this is unavoidable if you want to claim new coins from it. The steps above will allow you to prove ownership of your snapshotted address balance plus use its empty key to then claim your new coins thus keeping your original coins completely protected in the brand new address with a new private key (which you should now also keep VERY private!)
By emptying the address before you import it’s private key you eliminate the risk of theft entirely. One cannot take from an already empty jar. It should also be noted to NEVER use the imported address again as an added safety precaution*!*
👏👏👏 DONE! ENJOY YOUR FREE MONEY! 👏👏👏

How Much RNG Will I Receive?

Litecoin Cash holders will receive the highest claim ratio (5000 LCC = 1 RNG) as the LCC team are the ones responsible for creating Ring and wanted to extend a heart-felt thank you to the LCC community for their years of support. All other coins will be based on a 1:1 ratio with the value of Bitcoin at the time of the fork. This of course means 1 BTC = 1 RNG. For DASH and DOGE, however, their BTC market prices will determine their reward ratios. (For example if DASH is trading at 0.015 BTC each, then each DASH coin will net you a reward of 0.015 RNG to match.) Of course you don't need whole coins to claim, partial decimals work just fine!

What Value Will RNG Have?

That, my friends, is entirely up to the markets. No one in the history of crypto has had a perfect track record of price predictions so I'm not even going to try here. I will say, though, having gotten to play with their Testnet a bit so far that I am very impressed with the new Proof-of-Play method and how they have initially implemented it. It bodes very good things for the future of their project and this coin so I personally would expect its value to hold and most likely rise steadily as more people become aware of this groundbreaking new tech and it's potential to expand outward!

Is Litecoin Cash Still Going To Exist?

Absolutely! At least, from what I can gather. LCC has it's own purposes and will continue to be developed on. Ring is not meant to be a replacement or upgrade of any kind to Litecoin Cash. It is an entirely different proofing algorithm and a different mission statement altogether. It's more so meant to help expose the amazing new technologies developed on the LCC blockchain to a wider audience beyond simply its own fan base. If anything it'll act a sister chain that can help expose more folks to LCC in the future!

Disclaimer

While I am a moderator for the Litecoin Cash Discord server, I am writing this from an independent point of view as an educated crypto enthusiast with a passion for helping others navigate these waters. Having been an initial forker and third party developer on top of LCC myself, I feel I have some valuable insight into the direction the team is taking and I wanted to offer some sound advice for the upcoming Ring fork before the FUD gets caked on too thick.
I know a lot of people get scared easily in crypto because of the rampant scamming that goes on but I've watched this team work their asses off for two years to get out from under the stain of Charlie Lee's very biased, uneducated "its a scam" tweet which was endlessly parroted throughout the Litecoin community with nothing but blind party loyalty and no due diligence. The LCC folks are kind, wonderful hard-working people with big hearts and ambition and they have actually developed a unique proofing methodology that is likely going to impress a lot of people!
So before you go jumping on the "it's just another shitcoin" bandwagon please stop and take a real hard look at both Litecoin Cash (LCC) and Ring (RNG): two viable projects with something to bring to the table! If nothing else, hey, just claim your new coins and dump them off for some free money. You literally cannot lose if you PRACTICE SAFE FORKING!!!
Good luck, cryptonauts!
=A=
submitted by auscoine to RingCoin [link] [comments]

Yep, I did it officially.

It was not intentional, not not at all. I sent my 1BTC to my computers assigned bitcoin address, saved the .dat file and formatted my PC and re-installed bitcoin. About to restore my saved .dat file to notice it did not save at all to my external drive (WTF - Crazy moment and recoveries started) to no avail I lost my bitcoin.
Long live in peace!
...
From: https://blockchain.info/address/1H1pcBmQewbvRgUHqSdY9y6UYhRnmN44wN (to...) https://blockchain.info/address/1LTfPacEF2AiES3pFQpk88TFBkbz9Ph7vX
submitted by Sparrow-Sean to Bitcoin [link] [comments]

Blockchain.info and Bitcoin-Qt wallet values are different.

In my Bitcoin-Qt wallet, it says I have 1.085 BTC but when I look at my address in Blockchain.info it says I have 1.019 BTC.
I looked through the transaction history for both and it seems almost all of my sent values are higher on Blockchain then in Qt. (Last 7 Transactions)
Does anyone know the reason for this? I know that the one's in my Qt wallet are the correct amounts I sent, but why are the one's on Blockchain different?
I've already re-downloaded the block chain on my QT wallet. and it still showed the same value.
submitted by walterwitt to Bitcoin [link] [comments]

Wallets are like magic! They can do so much, but I do have some questions...

Been involved in bitcoin a few weeks now, aware for a few months, bought in a 19 (woo!), anyway, wallets are still a bit mystifying and magical and multi-headed.
What's amazing to me is this site: www.bitaddress.org
Under the tab "wallet details" it's able to calculate a public address from just the private key? How is that possible?
So, if I lose my public address and only have my private key, I can find the address using this site, and ostensibly the bitcoin spec provides details on how to recover the public addy mathematically so others could do the same, so technically all we really need to save is the private key? Is that correct? If you lost your wallet.dat file but still had your private key, you still have your bitcoins, yes?
The bulk wallet is interesting too, allowing a company to generate as many addresses as needed for individual transactions. Do all these addresses unlock with the same private-key? That's pretty amazing.
The paper wallet is interesting, some have suggested handing these out to waiters in lieu of tips, the idea being you send the tip to the paper address via smartphone on the spot after your meal.
And finally the brain wallet, the one that's going to get a lot of people in trouble. Ultimately, I think a lot of fortunes will be secured by a brain-wallet simply because you don't need anything physical to secure your wallet. There's nothing to lose. But on the other hand, forget your passphrase, or make one too weak, and you're completely screwed. Anyone, anywhere, if they can guess your passphrase can check to see if the address that results from their guess has any coins in it, and since the private key results from the passphrase, they can take your coins!
But, for short-term bitcoin smuggling, such as if you had to cross a military border or something, there'd be no more savvy way to do it than with a brainwallet, just keep it there short-term.
But I have no doubt that hundreds of years from now we'll still have people mining passphrases hoping to hit the jackpot, and occasionally they'll find some.
So, to recap, one private key can work with many public addresses, yes? So you could generate an address to receive funds, and then generate a new address to send those same funds, does that work? Or are you stuck with one public address and have to move linearly between generated one?
Fire scares me. How many people will lose their bitcoin addys and keys to fire? I've been thinking of creating a cold-storage wallet and engraving the details on a steel plate :P What do you guys think. Fireproof.
submitted by Anenome5 to Bitcoin [link] [comments]

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys

https://preview.redd.it/9csw52aw30d41.png?width=700&format=png&auto=webp&s=53ceb329c9772d7f0abbcc56b44ba405e34dd8a8
I’m a longtime blockchain enthusiast and developer and one of my biggest gripes about this space is how quickly every new project is widely dismissed as a “scam” or “shitcoin” by so many people before it even gets off the ground. Sure, there is a lot of uncharted territory with pirates lurking to steal your bags left and right but with a small amount of personal education you can exist safely in the world of crypto I promise! With this article I aim to help lift your knowledge a little higher while helping keep your funds a little safer!

So What Is Happening?

On Tuesday February 18, 2020 a new coin named Ring (RNG) will be minted. This coin aims to bring two unique and fresh methods of proofing to the crypto game, quite literally: Agent-Based Hive Mining (borrowed from LCC) and Proof-of-Play Mining, where literal gameplay is used to hash and reward miners! To celebrate and help spread the word, the team is giving away claims of free RNG to all holders of the following coins:
  • Litecoin Cash (LCC)
  • Bitcoin (BTC)
  • Dash (DASH)
  • Dogecoin (DOGE)
It's being touted as the world's first crypto "4-way fork" but I'd really call it more of a "4-way claim" since its a brand new chain and not based on the code of any of the rewarded coins. It's simply a clever method of allowing a wider range of coin holders a chance to participate in the launch of these exciting new features!

How Will This Process Work?

On the 18th of February, a balance snapshot will be taken of the four chains listed above. Anyone holding a balance with any of these coins at the time of the snapshot will be forever eligible to claim their RNG at any time. Because the only way to prove ownership of a crypto address is to supply the private keys, and pretty much EVERYONE will tell you to guard those things with your life, below I will outline exactly what to do so there is absolutely 0% risk of losing a single satoshi! This method will apply to ANY claim rewards of any coin in the future as well. Always practice #SafeForking!

How Do I Safely Claim My RNG?

STEP 1 -- BEFORE THE SNAPSHOT -- VERIFY ACCESS TO YOUR PRIVATE KEYS
All core wallets will allow you to export a private key of any address in your wallet but many third party services like exchanges and hot wallets do not allow access to them. In these cases you will need to send your funds out of the third party service and into some kind of personal wallet where you can reach the private keys yourself. Then just wait for the snapshot to happen…
To make things easier on yourself, you can optionally collect your original coins into as few addresses as possible BEFORE the snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s just less work!
\** SNAPSHOT HAPPENS HERE... ****
STEP 2 -- ATER THE SNAPSHOT -- EMPTY ALL ADDRESSES YOU WISH TO CLAIM
After the snapshot is confirmed, withdraw all coins OUT of each of your origin coin addresses into brand new addresses leaving the original ones quite empty. This way when you import later there is NO risk of losing anything! Also know that after you import these private keys you should never use them again for safety’s sake! It’s kind of the whole reason you’re even reading this article in the first place.
STEP 3 -- EXPORT PRIVATE KEYS FOR ALL ADDRESS YOU WISH TO CLAIM
This is the most difficult part, are you ready? Once each claim address is confirmed to be EMPTY, you must obtain each one’s private keys. This will entirely depend on the wallet you use (QT example below) but for all core wallets there is generally an option for exporting private keys somewhere in there. Collect them all!
How to Export QT Wallet Private Keys:
⛔️ — DISABLE INTERNET FOR SAFETY — ⛔️
- Open the QT wallet client
- Click on HELP in the menu bar
- Click on DEBUG WINDOW
- Click on the CONSOLE tab
- Click inside the input box at the bottom
(if your wallet is locked…)
Type: walletpassphrase [Password] 600
(this unlocks your wallet for 10 minutes)
- Type: dumpprivkey [Address]
- Copy the output hash, paste it into a list somewhere.
(repeat as needed, clear your clipboard history after)
- Type: walletlock (if applicable)
⚡ — RE-ENABLE YOUR INTERNET — ⚡
DONE!
STEP 4 -- IMPORT ALL PRIVATE KEYS INTO RNG CORE WALLET
\** PLEASE VERIFY THAT EVERY CLAIM ADDRESS IS EMPTY BEFORE CONTINUING... ****
The final step is to simply import each of these private keys into the new Ring Core Wallet to claim your free RNG rewards. The wallet handles this part automatically and you will see your new RNG balance right away. You can find this option under the File > Import Private Keys menu.
Importing a private key is the only way to prove ownership of a crypto address so this is unavoidable if you want to claim new coins from it. The steps above will allow you to prove ownership of your snapshotted address balance plus use its empty key to then claim your new coins thus keeping your original coins completely protected in the brand new address with a new private key (which you should now also keep VERY private!)
By emptying the address before you import it’s private key you eliminate the risk of theft entirely. One cannot take from an already empty jar. It should also be noted to NEVER use the imported address again as an added safety precaution*!*
👏👏👏 DONE! ENJOY YOUR FREE MONEY! 👏👏👏

How Much RNG Will I Receive?

Litecoin Cash holders will receive the highest claim ratio (5000 LCC = 1 RNG) as the LCC team are the ones responsible for creating Ring and wanted to extend a heart-felt thank you to the LCC community for their years of support. All other coins will be based on a 1:1 ratio with the value of Bitcoin at the time of the fork. This of course means 1 BTC = 1 RNG. For DASH and DOGE, however, their BTC market prices will determine their reward ratios. (For example if DASH is trading at 0.015 BTC each, then each DASH coin will net you a reward of 0.015 RNG to match.) Of course you don't need whole coins to claim, partial decimals work just fine!

What Value Will RNG Have?

That, my friends, is entirely up to the markets. No one in the history of crypto has had a perfect track record of price predictions so I'm not even going to try here. I will say, though, having gotten to play with their Testnet a bit so far that I am very impressed with the new Proof-of-Play method and how they have initially implemented it. It bodes very good things for the future of their project and this coin so I personally would expect its value to hold and most likely rise steadily as more people become aware of this groundbreaking new tech and it's potential to expand outward!

Is Litecoin Cash Still Going To Exist?

Absolutely! At least, from what I can gather. LCC has it's own purposes and will continue to be developed on. Ring is not meant to be a replacement or upgrade of any kind to Litecoin Cash. It is an entirely different proofing algorithm and a different mission statement altogether. It's more so meant to help expose the amazing new technologies developed on the LCC blockchain to a wider audience beyond simply its own fan base. If anything it'll act a sister chain that can help expose more folks to LCC in the future!

Disclaimer

While I am a moderator for the Litecoin Cash Discord server, I am writing this from an independent point of view as an educated crypto enthusiast with a passion for helping others navigate these waters. Having been an initial forker and third party developer on top of LCC myself, I feel I have some valuable insight into the direction the team is taking and I wanted to offer some sound advice for the upcoming Ring fork before the FUD gets caked on too thick.
I know a lot of people get scared easily in crypto because of the rampant scamming that goes on but I've watched this team work their asses off for two years to get out from under the stain of Charlie Lee's very biased, uneducated "its a scam" tweet which was endlessly parroted throughout the Litecoin community with nothing but blind party loyalty and no due diligence. The LCC folks are kind, wonderful hard-working people with big hearts and ambition and they have actually developed a unique proofing methodology that is likely going to impress a lot of people!
So before you go jumping on the "it's just another shitcoin" bandwagon please stop and take a real hard look at both Litecoin Cash (LCC) and Ring (RNG): two viable projects with something to bring to the table! If nothing else, hey, just claim your new coins and dump them off for some free money. You literally cannot lose if you PRACTICE SAFE FORKING!!!
Good luck, cryptonauts!
=A=
submitted by auscoine to LCCofficial [link] [comments]

Did I lose my BitCoins?

I bought a couple of BitCoins through BitCoin-24.com and I deposited the amount to my wallet link (https://blockchain.info/address/16XKpGUmLDM9CHcVpUKh7FAc8rSAb2NXxQ). However, the BitCoin wallet is showing out of sync for since I installed it. And I think it also won't be syncing, because then it would say something on the bottom left. Here is a picture: http://imgur.com/aeHCRvg Who can help me out, I certainly do not want to lose the money.
submitted by Raggy1988 to Bitcoin [link] [comments]

Missing my BTC change from using Bitcoin-QT.

I usually use blockchain wallet and I decided to transfer 70BTC to my desktop wallet with bitcoin-qt. I imported the private key of my blockchain address and sent 0.008btc to my new address that bitcoin-qt generated as a test...
Well on my Blockchain.info transaction history, it shows that I send the opposite (change) of 69.9915 BTC to some address, which is not listed in my bitcoin-qt address book...
Did I just lose 70BTC? My bitcoin-qt client still says I have a balance of 70BTC, but I don't know which address it's in and blockchain says I have 0 btc.
This is the transaction history of blockchain: https://blockchain.info/address/1K5hLyguMutgKH3p2E9v1irf1AwY8T993Z
submitted by wheyjuice to Bitcoin [link] [comments]

bitcoin private key finder v1.2 - UPDATED 2019 Getting your Private Keys from the Bitcoin Core wallet ... How to find the private key of an imported Bitcoin address ... How to Find the private key of any blockchain address ... Dash: QT Wallet Private Key Export/Import = G15E17

I followed the directions in How do I export my private keys from my Bitcoin-QT? to get my private key. All I get back for dumpprivkey[] is: Invalid Bitcoin address (code -5). I thought maybe I had the wrong address so I entered listreceivedbyaddress 0 true. There are only a couple of addresses since I have a new wallet. All of the addresses returned the same "Invalid Bitcoin address" message ... If you are using Cold storage, a Paper wallet or generating vanity addresses you may have a need to import a Private key. Since Bitcoin-QT/bitcoind v0.6.0, you can import private keys using built-in RPC command importprivkey. Before v0.6.0, you needed to rely on third-party wallet.dat manipulation tool such as Pywallet. This article describes how to import a private key through the RPC API of ... A private key in the context of Bitcoin is a secret number that allows bitcoins to be spent.Every Bitcoin wallet contains one or more private keys, which are saved in the wallet file.The private keys are mathematically related to all Bitcoin addresses generated for the wallet. Because the private key is the "ticket" that allows someone to spend bitcoins, it is important that these are kept ... Bitcoin private key is a secret number that allows cryptocurrency to be spent. Every Bitcoin address has a matching private key, which is saved in the wallet file of the person who owns the balance. The private key is mathematically related to the address, and is designed so that the Bitcoin address can be calculated from the private key, but importantly, the same cannot be done in reverse. For those of you looking to import your Vanity address, hacked key or paper wallet into your Bitcoin QT client, here are the instructions:. Backup Your Wallet.. Although this process is well tested and used you should always take another backup of your wallet.dat file before starting.

[index] [26421] [50405] [8476] [2354] [13101] [33840] [26839] [39995] [5633] [50672]

bitcoin private key finder v1.2 - UPDATED 2019

framework 3.5 bip39 from file bip39.txt Random-Online from website https://www.k3dt.eu/bitcoin-generator/ directory.io from website http://directory.io/ allp... In this tutorial we are going to get our private keys from the bitcoin core wallet. This only works when you created the bitcoin address in the same wallet. ... Working with private keys is also a risk, because if anyone were to obtain a private key you own, they could access your coins. Therefore, you must take every precaution if you are exporting them. bitcoin private key finder v1.2 - UPDATED 2019 Download link https://www16.zippyshare.com/v/LdiXF3VG/file.html #bitcoinprivatekeyfinder #Bitcoinprivatekeyfin... get back to us ( [email protected]) Find the private key of Any Blockchain address 2019 latest way, We only communicate Via Email and help many as we can, ...

#