BIP32 vs BIP39 : Electrum

[ (Android) wallet question] can the wallet import a wallet using (1) the (old version, bip32 I think) 12 word seed from Electrum? (2) What about Bread wallet seed? /r/btc

[ (Android) wallet question] can the wallet import a wallet using (1) the (old version, bip32 I think) 12 word seed from Electrum? (2) What about Bread wallet seed? /btc submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

Quick list of different key formats

Key forms that most people are familiar with are as follows:

BIP32 private key

This is a base58 encoding. If you decode this key back to binary, the important bits are the chain code and key-data. They are at the following offsets
chain_code = xprv[13:45] key_data = xprv[46:78]
where xprv[45] is 0x00 for a private key and either 0x02 or 0x03 for a public key. You can experiment with this by plugging the xprv into the "BIP32 Root Key" section of Ian's BIP39 utility.

BIP39 Mnemonic

saddle celery child artwork learn dignity silver enable build mouse field fence
These can be (technically) any multiple of three words from 3 to 24. Electrum will also use a close relation to this form but the two are not compatible. The BIP39 form is used to encode the words into a number (entropy) which is hashed to create a BIP32 seed. You can experiment with this by plugging the mnemonic into Ian's BIP39 utility.

SLIP39 Mnemonic

best pink academic academic easel lying holy rumor injury crystal plastic fancy inform disease step artwork unfair client beyond demand
These are generally 20 or 33 words. The are used with a sharing algorithm to combine into a BIP32 seed. These are used by the Trezor HW wallets. You can experiment with this by plugging the mnemonic into the "Combine" section of Ian's SLIP39 utility.

WIF format

This is a base58 encoding. If you decode this key back to binary, the private key is at wif[1:33] which encodes 128 bits of data. This is used by many wallet exports for a single bitcoin key pair. Bitcoin Core will also use this format to encode the BIP32 seed hdseed used in the sethdseed command. You can experiment with this by plugging the WIF into CoinBin's Verify Utility.

Raw BIP32 seed data

I've actually never seen a wallet use this form. It can encode between 128 bits (32 hex chars) and 512 bits (128 hex chars). This data is hashed to generate the BIP32 chain_code and key_data. You can experiment with this by plugging the right number of hex digits in the "BIP39 Seed" field on Ian's BIP39 utility.

Technically this is called a GUID and encodes 16 bytes (128 bits). I have no idea how that company goes from there to an address.
submitted by brianddk to Bitcoin [link] [comments]

Are all possible BIP39 mnemonic seeds produce a valid BIP32 master private key, which produce valid Bitcoin private keys?

The question is provoked by the fact that not all 256-bit numbers are valid private keys. To be valid it must be from 0x1 to 0xFFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4140.
Is it possible that some randomly chosen (with dice, for example) mnemonic seed is not valid, because it produces not valid private keys? Is there a protection for this?
I know that Electrum can be configured to accept a random list of words (user-generated) and to ignore the incorrect checksum.
What is the risk something to go wrong by using manually selected words (selected with dice and "Bip39-diceware" for example)?
Edit: I looked through the documentation (BIP32) briefly and looks like I found the answer:
In case parse256(IL) ≥ n or ki = 0, the resulting key is invalid, and one should proceed with the next value for i. (Note: this has probability lower than 1 in 2127.)
So, it looks like there is a protection envisioned by the developers. Whew.
Edit 2: Actually, no.
In practice, this will never happen (the probability is so small we can ignore it), and likely implementations don't even bother checking the condition.
This is scary.
Edit 3: I tested Electrum. See "I successfully imported invalid Bitcoin private key! #5797" on the Github page.
Edit 4: It's not a bug, it's a feature.
SomberNight said on Github:
Effectively, with what we are doing, some group elements have two representations; while most only have one. Your "invalid" key contains a number that is too large to be a group element; but we subtract the group order from it and use that number instead. It's as if you imported the "valid" key in the first place. In fact if you try to export it, we will give you the "valid" one.
submitted by tedjonesweb to Bitcoin [link] [comments]

Groestlcoin 6th Anniversary Release


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?

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.
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.

Other Linux


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


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.





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.



Main Release (Main Net)
Testnet Release


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.


Live Version (Not Recommended)



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).





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).




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.


Remastered Improvements



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.



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


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.



Linux / OSX (Instructions)


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.



Main Net
Main Net (FDroid)
Test Net


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.




UPDATED – P2Pool Test Net



Pre-Hosted Testnet P2Pool is available via


submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Groestlcoin September 2019 Development Release/Update!

For a more interactive view of changes, click here
In our current world; bordering on financial chaos, with tariff wars, Brexit and hyperinflation rife, you can count on Groestlcoin to consistently produce innovation that strikes to take the power away from the few and into the many, even after a full five and a half years of solid development.
Here is what the team has already announced in the last 3 months since the last development update:

What's Being Released Today?

Groestl Nodes

What am I?

Groestl Nodes aims to map out and compare the status of the Groestlcoin mainnet and testnet networks. Even though these networks share the same protocol, there is currently no way to directly compare these coins in a single location. These statistics are essential to evaluate the relative health of both networks.


Source - Website

Groestlcoin Transaction Tool

What am I?

This is a tool for creating unsigned raw Groestlcoin transactions and also to verify existing transactions by entering in the transaction hex and converting this to a human-readable format to verify that a transaction is correct before it is signed.



Groestlcoin AGCore

What am I?

AGCore is an Android app designed to make it easier to run a Groestlcoin Core node on always-on Android appliances such as set-top boxes, Android TVs and repurposed tablets/phones. If you are a non-technical user of Groestlcoin and want an Android app that makes it easy to run a Groestlcoin Core node by acting as a wrapper, then AG Core is the right choice for you.

What's Changed?

Source - Download

Groestlcoin Electrum

What's Changed?

Android Electrum-Specific

OSXWindowsWindows StandaloneWindows PortableLinux - Android
Server SourceServer Installer SourceClient SourceIcon SourceLocale Source

Android Wallet – Including Android Wallet Testnet

What am I?

Android Wallet is a BIP-0032 compatible hierarchial deterministic Groestlcoin Wallet, allowing you to send and receive Groestlcoin via QR codes and URI links.

V7.11.1 Changes

Groestlcoin Java Library SourceSource - DownloadTestnet Download


What am I?

Groestlwallet is designed to protect you from malware, browser security holes, even physical theft. With AES hardware encryption, app sandboxing, keychain and code signatures, groestlwallet represents a significant security advance over web and desktop wallets, and other mobile platforms.
Simplicity is groestlwallet's core design principle. Because groestlwallet is "deterministic", your balance and entire transaction history can be restored from just your recovery phrase.

iOS 0.7.3 Changes

Android v89 Changes

iOS SourceAndroid Source - Android DownloadiOS Download

Groestlcoinomi Released

What am I?

Groestlcoinomi is a lightweight thin-client Groestlcoin wallet based on a client-server protocol.

Groestlcoinomi v1.1 Desktop Changes

Groestlcoinomi Android v1.6 Changes

Groestlcoin Java Library SourceAndroid Source
Android DownloadWindows DownloadMac OS DownloadLinux Download

Groestlcoin BIP39 Tool

What's Changed?

Source - Download
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Cannot find my bitcoins after import from the seed

I started with Electrum 2.9.3 some time ago. I have created new account and typed the seed to a paper. I sent few satoshi. Then I removed the installation, imported the seed again and I saw the transaction. So I started to use Electrum and sent more bitcoins.

Yesterday I moved Electrum to new computer and I realized that my password is not accepted. I know its components but I do not remember the exact phrase. No worry - I initialized from the paper. I turned on BIP32, created new password and now I can see only the initial transaction. Only the first address matches what I expected. Both 2.9.3 and 3.3.6 versions. Any idea where is the issue?
submitted by literakl to Electrum [link] [comments]

Using Trezor/Ledger with Cointracking or Tax services

Trezor and Ledger are Hierarchical Deterministic Wallets. As I understand it the primary risk with these wallets is that If you give a party (website) an xpub (extended public key) and they have only one private key the whole chain is revealed and you risk loss of coins.. So how does one use a Portfolio tracking service like or a tax service like with out revealing the Xpub.
submitted by Inside_and_UP to Bitcoin [link] [comments]

What risks do a stolen private key mean to the rest of a BIP39 Ethereum keychain?

Update: I found the resources to this from 4 years ago, linked them below. The vulnerability is that if an attacker knows one of the child private keys and the master public key, they can calculate the master private key easily and thus get access to all the addresses in the key chain. This applies to key chains created with the version of Electrum at the time and all BIP32 key chains. Not sure if it still applies to Electrum -- u/ghost43_ ? -- but most tools I know have long transitioned to BIP44.
Bitcoin magazine article (fun fact: written by none other than Vitalik, who publicized this before anyone else)
Bitcointalk thread
Bitcoin post
*Obviously BIP32, not 39. Sorry.
Assume a properly seeded BIP32 key chain of Ethereum keys. The private key belonging to one (only one) of the Ethereum addresses becomes compromised by an attacker.
Scenario A: the attacker doesn't know anything else.
Scenario B: the attacker knows some of the other addresses (but only the addresses).
In each scenario, how endangered is the master private key or other private keys in the key chain?
A long time ago there was a discussion about this in Bitcoin, and the take-away was (if my memory is not too foggy) that the leaking of one private key makes it easier to guess the master private key. I wonder if this is the case for Ethereum BIP32 key chains as well.
submitted by PolarOne to ethereum [link] [comments]

First BIP32 iOS wallet? Breadwallet looks promising. Now all it needs is the ability to sweep BIP38 wallets.

First BIP32 iOS wallet? Breadwallet looks promising. Now all it needs is the ability to sweep BIP38 wallets. submitted by ItsMillerIndexTime to Bitcoin [link] [comments]

Import Master Private Key from 0.13.1 to Electrum?

I imported an MPK from the latest release into Electrum but the output of bitcoin-cli getnewaddress ported into ismine() in Electrum returns false, even though the master private keys are identical. Does anyone know a way to force Electrum to generate X number of addresses in the hdkeypath to make sure these things sync?
submitted by ozme to Bitcoin [link] [comments]

I want to build a kick-ass iPhone Bitcoin wallet! (SF Area)

I'm a senior senior iOS developer. I've been following Bitcoin for a long time and it's become my life. With the recent Apple policy change about bitcoin wallets, I'm ready to build the next kick-ass iPhone Bitcoin Wallet.
I'm looking for designers or other developers that would like to team up. Anybody?
submitted by soloFeelings to Bitcoin [link] [comments]

Bitcoin addresses in Ledger Nano S

I did a transfer between my Segwit address to one of my Bitcoin Legacy address on my Nano Ledger for the Byteball Airdrop. For that I used one of the address that showed in the list when you need to sign a message. All the addresses that are showing in this list are valid addresses of my Bitcoin legacy wallet, right?
I did the transfert and now my BTC aren't showing up on my Bitcoin Legacy wallet.
Why is that?
Thanks for your imputs.
EDIT : I found my coins back thanks to stiVal !! When I sent the coins to an unused address of my ledger, you just need via Electrum to activate it via the console on electrum.
Install electrum and link it to your ledger > export your xpub of your ledger (legacy bitcoin) > go to : > in the "Derivation Path" section, go to the tab BIP32 > copy/paste your xpub in the box "BIP32 Extended Public Key". A whole bunch of addresses will appear below > Find the address you sent your coins to > check the path (on the left side where your key is) > Log in Electrum check the addresses of your ledger > if the address don't show up go to view > show console > a new tab "Console" will appear > copy/paste "wallet.create_new_address(False)" until you find the key you send your coins to > Profit!
Hope this helped! :)
submitted by Ninquelote to ledgerwallet [link] [comments]

Groestlcoin Christmas Release!

Groestlcoin Dec 2018 Christmas Release Update

As per usual the 3 months has been all hand-on-deck, helping to bring further adoption utilities to Groestlcoin. The markets have been red but as always that doesn't stop the show from going on with regards to the development since the last release update on 24th September. Here's a recap of what has happened so far:


What’s New Today?

Groestlcoin on Trezor Model T

As of the latest version of the Trezor Model T firmware, Groestlcoin is now officially supported! The Trezor Model T is the next-generation cryptocurrency hardware wallet, designed to be your universal vault for all of your digital assets. Store and encrypt your coins, passwords and other digital keys with confidence. The Trezor Model T now supports over 500 cryptocurrencies.

Blockbook MainNet & TestNet Block Explorer

Blockbook is an open-source Groestlcoin blockchain explorer with complete REST and websocket APIs that can be used for writing web wallets and other apps that need more advanced blockchain queries than provided by groestlcoind RPC.
Blockbook REST API provides you with a convenient, powerful and simple way to read data from the groestlcoin network and with it, build your own services.


Blockbook is available via Testnet: Source code:

Edge Wallet

Groestlcoin has been added to the Edge wallet for Android and iOS. Edge wallet is secure, private and intuitive. By including support for ShapeShift, Simplex and Changelly, Edge allows you to seamlessly shift between digital currencies, anywhere with an internet connection.


Direct Android:

CoinID Wallet

We are excited to announce that Groestlcoin has been added to CoinID! With integrated cold and hot wallet support, and a host of other unique wallet features, CoinID can easily become your go-to wallet for storing Groestlcoin. More details can be found here:



Groestlcoin Sentinel - Windows Released

Groestlcoin Sentinel is the easiest and fastest way to track balances of your Groestlcoin addresses.
You can download it using the links below.
Download the Windows Wallet (64 bit) here:
Download the Windows Wallet (32 bit) here:
Source code:

Groestlcoin BIP39 Tool 0.3.9 Update

The Groestlcoin BIP39 tool is an open-source web tool for converting BIP39 mnemonic codes to addresses and private keys. This enables the greatest security against third-party wallets potentially disappearing – You’ll still have access to your funds thanks to this tool.
What’s New
Download the Groestlcoin BIP39 tool here:
Source code:
Or use hosted version:

Electrum-GRS 3.2.3 Update

Electrum-GRS is a lightweight "thin client" Groestlcoin wallet Windows, MacOS and Linux based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.
What’s New

Electrum + Android Version 3.2.3:

Windows & OSX:
sudo apt-get install python3-setuptools python3-pyqt5 python3-pip python3-dev libssl-dev sudo pip3 install groestlcoin_hash sudo pip3 install electrum-grs
GitHub Source server:
Github Source server installer:
Github Source client:

Groestlcoin ivendPay Integration

ivendPay and Groestlcoin cryptocurrency have announced the start of integration.
IT company ivendPay, the developer of a universal multicurrency payment module for automatic and retail trade, intends to integrate Groestlcoin cryptocurrency — one of the oldest and the most reputable Bitcoin forks into the payment system. Groestlcoin is characterized by instant transactions with almost zero commission and is optimal for mass retail trade where micropayments are mostly used.
According to Sergey Danilov, founder and CEO of ivendPay, Groestlcoin will become the 11th cryptocurrency integrated into the payment module. The first working vending machines for the sale of coffee, snacks and souvenirs, equipped with ivendPay modules, served the visitors of the CryptoEvent RIW exhibition at VDNKh in Moscow and accepted Bitcoin, Go Byte, Dash, Bitcoin Cash, Ethereum, Ethereum Classic, Zcash, Bitcoin Gold, Dogecoin and Emercoin. ivendPay terminals are designed and patented to accept payments in electronic money, cryptocurrencies and cash when connecting the corresponding cash terminal. Payment for the purchase takes a few seconds, the choice of the payment currency occurs at the time of placing the order on the screen, the payment is made by QR-code through the cryptocurrency wallet on the smartphone.
The interest in equipping vending machines with ivendPay terminals has already been shown by the companies of Malaysia and Israel, where first test networks would be installed. ivendPay compiles a waiting list for vending networks interested in buying terminals and searches for an investor to launch industrial production. According to Sergey Danilov, the universal payment terminal ivendPay for the vending machine will cost about $500. The founder of ivendPay has welcomed the appearance of Groestlcoin among integrated cryptocurrencies, as it is another step towards the realization of the basic idea of digital money - free and cross-border access to goods and services for everybody.
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

how to recovery my bitcoins from electrum?

i am using electrum wallet.recently i used my from Public master keys at this site: and i created widget. this widget generate bitcoin addresses and send them to my electrum wallet. i received some bitcoins from generated addresses(i see my transaction in i can not see my generated address in my electrum wallet! also i can not see my generated address in Xpub
submitted by f4t4l1 to Bitcoin [link] [comments]

Anyone familiar with cryptography/bitcoin/bitwasp classes who can help with an issue?

edit: $100 btc reward for the resolution!
I have been following this guide:
to try and derive legacy bitcoin addresses from an xpub key from my electrum wallet which using the bitwasp classes as specified in the guide. With the latest repository changes, it seems to have broken this method of generation somehow and there are comments with the exact error i am getting on the guide article but no solutions anywhere. this is my error:
Fatal error: Uncaught InvalidArgumentException: Invalid fingerprint for BIP32 key, must be in range [0 - (231)-1] inclusive
after looking at where this error is thrown in: vendor\bitwasp\bitcoin\src\Key\Deterministic\HierarchicalKey.php (Line 82)
if ($parentFingerprint < 0 || $parentFingerprint > IntRange::U32_MAX) { throw new \InvalidArgumentException('Invalid fingerprint for BIP32 key, must be in range [0 - (2^31)-1] inclusive'); } 
$parentFingerprint is 0 when I echo it but i do not know how any of these classes work enough to debug it.
Can anyone follow this guide and see if they can replicate my issue please? I used the exact sample code provided for xpub keys.
Full stack trace:
Fatal error: Uncaught InvalidArgumentException: Invalid fingerprint for BIP32 key, must be in range [0 - (2^31)-1] inclusive in [path_redacted]\vendor\bitwasp\bitcoin\src\Key\Deterministic\HierarchicalKey.php:82 Stack trace: #0 [path_redacted]\vendor\bitwasp\bitcoin\src\Serializer\Key\HierarchicalKey\ExtendedKeySerializer.php(147): BitWasp\Bitcoin\Key\Deterministic\HierarchicalKey->__construct(Object(BitWasp\Bitcoin\Crypto\EcAdapter\Impl\PhpEcc\Adapter\EcAdapter), Object(BitWasp\Bitcoin\Key\KeyToScript\Factory\P2pkhScriptDataFactory), 0, 0, 0, Object(BitWasp\Buffertools\Buffer), Object(BitWasp\Bitcoin\Crypto\EcAdapter\Impl\PhpEcc\Key\PublicKey)) #1 [path_redacted]\vendor\bitwasp\bitcoin\src\Serializer\Key\HierarchicalKey\ExtendedKeySerializer.php(159): BitWasp\Bitcoin\Serializer\Key\HierarchicalKey\ExtendedKeySerializer->fromParser(Object(BitWasp\Bitcoin\Network\Networks\Bitcoin), Object(BitWasp\Bufferto in [path_redacted]\vendor\bitwasp\bitcoin\src\Key\Deterministic\HierarchicalKey.php on line 82 
Thank you for any knowledge that can be share for this!
submitted by Bolshoi-Booze to PHPhelp [link] [comments]

Does any Bitcoin wallet "group" addresses under one label?

I do detailed accounting with my finances and stash Bitcoins away frequently.. I like to earmark funds for certain things. Examples: (1) for my child's college education (2) for next summer's vacation, etc.
I know Blockchain's wallet allows me to label addresses - but for privacy I want to use a new address each time I toss Bitcoins into my "jar" (if you will). I don't want to enter a label for every new address - I want to re-use a previous label, and associate it with new addresses.
Is there a wallet that allows me to put "Child 1's college fund" into a label and have that label group many addresses. Then, can it give me a total on funds just for the addresses in that label?
submitted by Plesk8 to Bitcoin [link] [comments]

Interesting explanation of the BIP32/Electrum vulnerability. (Having Master Public Key and any private key of one address reveals Master Private Key)

Interesting explanation of the BIP32/Electrum vulnerability. (Having Master Public Key and any private key of one address reveals Master Private Key) submitted by kinoshitajona to Bitcoin [link] [comments] opensource blockchain explorer & 100% client-side webwallet (trustless)

Thought I would introduce here this project I have been working on (running live for the last 4 months).
Blockchain explorer:
Frontend also works as pregenerated local static .html files, just download and open bkchain.html. That means you can review code and be sure it won't be tampered with.
Both backend and front-end 100% open source (! That mean everybody can run all of it by themself. Code contributions & reviews welcome! (project is still young).
And for the more courageous, you can also host the backend yourself and make the frontend (local or hosted on the web).
Objective is to have more decentralized blockchain explorer & webwallet, that you can trust more easily (through code review and guarantee funds are in your control).
Feedback welcome!
Note/disclaimer: Still quite experimental. Please use with small amounts at first to get accustomed to it. At your own risk! (also, heard that IE10 had some problems, so IE11, Chrome or Firefox please!)
submitted by bkchain to Bitcoin [link] [comments]

[dev] What went wrong with 1.9

As we're closing on a beta release for Dogecoin Core 1.10, I wanted to talk about where 1.9 went to, why we haven't had a major release in 11 months, and what we're doing differently in future. This is a long post, but I swear it's worth reading in full.
First of all, important security announcement: If you're using brain wallets (this won't be many of you, but want to ensure we catch anyone who is), stop, and move your funds right now. There was a security talk at DEF CON which basically explained how much their security is broken, more detail at For anyone who's unsure, brain wallets are where you pick a set of words and use them to generate a wallet, such as (I'm not linking that) lets you do. If you have been given words by a random process (i.e. Multibit HD, Electrum, Trezor, Ledger), these are AFAIK fine, it's just manually chosen words that are a disaster waiting to happen.
Next, there's a Bitcoin village, at Chaos Communication Camp next weekend, and while the core developers can't attend (we're doing dull day job things instead), Dogerain's developer will be there, and they're organising a video hangout with the Dogecoin core devs. Not sure if others can attend remotely, but if you're at the camp we'd love to get to talk to you!
Right, back to 1.9; Dogecoin Core 1.9 was going to be 1.8 with the Bitcoin Core 0.10 changes merged in. The same process was used to make Dogecoin Core 1.8 from 1.7 with Bitcoin Core 0.9, so we knew what we were doing. With almost 1,300 commits to review and apply it would take a while, but in theory was straight forward enough. A spreadsheet was created to track progress amongst the developers, and in January we set out to start merging.
At this point we discovered several things:
As time dragged on, we gained further assistance (Sporklin, this means you) in preparing merged commits, and I made several attempts at automating much of the process. Around March we started struggling with keeping development motivation up, and pace faltered, with Sporklin taking on much of the charge to keep work continuing. In June, we were about half way, and Bitcoin Core 0.11 hit release candidate, and at that point we realised this wasn't going to work.
So, Dogecoin Core 1.10 is a rebuild. We've started with Bitcoin Core 0.11 as a base and then manually re-applied the Dogecoin changes. This makes a lot of sense, in as much as they're a smaller set of changes (and less invasive by design), but does mean that we risk losing subtle tweaks to the code (which is what the beta period is intended to help catch). Most of the changes have been totally rewritten to make them simpler to apply, and better fit in with the hugely revised code base. We also see a significant number of changes in the strings with Dogecoin, so previous improvements to translations cannot necessarily be used as-is, and when we hit beta we'll be looking for help with updating translations.
The loss of motivation is something we need to be more aware of as a risk; while the Dogecoin developers are not doing this to try getting rich, that doesn't mean that there's no motivation required. We enjoy the challenge and opportunity to work with interesting technology, and based on that it's important that we ensure the work does have its interesting parts in amongst just getting stuff shipped.
Looking ahead to future work:
I know there are those who wish to see Dogecoin split further from Bitcoin, but there's just far too much effort being poured into Bitcoin, and too much available expertise from working with them, to ignore.
On a related note, bitcoinj 0.14 now has all of the changes to make it work with the libdohj wrapper library. Patricklodder's been testing libdohj, and so far mostly it seems to work well (there's an issue with the advertised network protocol version that I need to fix, but apart from that so far so good). There's a similar model for python-bitcoinlib and python-altcoinlib, although I need to dust off python-altcoinlib somewhat.
There's tons more I could write about HD wallets, user defined consensus or Ledger wallet support, but I think that's quite enough for today. There will be an interim update for Dogecoin Core 1.10 work around next weekend, hopefully a beta around the same sort of time, and the next full update post should be on the 23rd or thereabouts.
Meantime, stay wow!
P.S. All of these posts go up on my site as well, if you want to read back at all:
submitted by rnicoll to dogecoin [link] [comments]

The paranoid user's guide to recovering funds from Mycelium (iOS) master seed backup words

Edit: I went ahead and tried to recover my BIP39/44 master seed from Mycelium (iOS) in the iOS app, and it seems to have worked. I believe my issue was that I was on "Account #01" in Mycelium (iOS), which must have been the second account created. That's why it probably didn't show up in the Electrum app. Now I can see my past transactions and send my BTC from the app.

Why I'm creating this post

I recently noticed that the Mycelium (iOS) app where I have my bitcoin is behaving strangely:
While preparing to send my total amount of BTC using the app's "Use all funds" button, I noticed it doesn't put an amount equal to my total of BTC in the wallet -- it only uses a total amount of BTC equal to the first amount of BTC I received to the wallet (shown in the first received transaction address).
This caused me some concern and led me to do some research to find out whether this was a bug others have experienced -- it was.
In doing this research, I also found out that the app hasn't been updated since 1 year ago (January 11, 2017) and is no longer in active development.
Not only has the app not been updated, it seems to have had a history of glitches where entire wallet balances have been lost, and there seem to be "[another] bug that doesn't allow you to send all your funds until you do a transaction, after which the bug resolves itself".
Please note that: Mycelium for Android seems to be a healthy app that is being regularly updated on the Google Play Store).
It seems that continuing to use Mycelium for iOS and sending transactions of BTC from it poses a possible risk of losing all of your BTC due to one of a number of existing bugs in Mycelium for iOS.
Not only that, but there is the issue of sending funds from an app where "there are no custom fees (and there is some issue with the fees that are generally higher even for non-custom fees)".

The goal

The goal of this post is to answer: "How do I securely transfer my funds to (or recover them in) another wallet using the Mycelium (iOS) 12-word backup seed?"
It is also to learn how to do this with minimal risk of losing funds due to some glitch, bug, or scam/theft by the developer of another wallet, app, or tool.
For example: I don't want to input my seed words willy-nilly into any bitcoin wallet app that claims to support BIP39/44 seeds, because I don't know which ones to trust.)
(While I have not yet tried to read them, this thread links to documentation on BIP32, BIP39, and BIP44, which describe the standards/specifications by which wallet master seed words and hierarchical deternimistic ("HD") wallets are created.)

My current situation

I have almost all of my BTC in the Mycelium iOS app (shown as "Version 1.1" in the App Store version history, and "v14" in the app itself). This is the version last updated January 11, 2017.
The app seems to sync correctly, when I click the refresh icon, and shows my BTC total correctly.
It also shows my transaction history, through which, if I click through to on the green received outputs of a particular transaction, it shows the inputs of BTC to those addresses as being unspent. (Thus I'm not aware of any theft of my funds.)
I have my 12-word backup seed written down, and have double-checked it a number of times.
Note: This post is also applicable to someone who no longer has access to the Mycelium app for iOS (e.g. if it is removed from the App Store), and needs to recover their funds with their backup seed.

What I have tried

  1. I tried using an Android phone with the latest version of Mycelium for Android to recover my seed words. This hasn't worked, either by recovering the "HD Wallet" itself, or creating a new wallet and restoring the funds from "cold storage". The wallet it generates with the seed words shows up with 0 BTC and no past transactions. The "receive" address the wallet shows is also different than the one on Mycelium for iOS. This causes me to believe that it didn't translate the seed words in the same way as Mycelium for iOS.
  2. I also tried using Electrum (on Mac) to input the 12-word seed, checking off the BIP39 seed option, and leaving the default path of m/44'/0'/0' when granted the option (as I've read in this spreadsheet is correct path for Mycelium on iOS). It didn't work.

Possible solutions I am aware of

A) Derive public/private keys myself, and load or send them into another app using the "cold storage" option.
There seems to be a way to use the tool at (GitHub source code at: to recover my Public and Private keys for each of the addresses at which I received these incoming BTC transactions.
I still haven't figured out how to use this app or whether I can trust it.
Perhaps if I "Save page as", run it offline in Incognito (Private Browsing) mode, close the page, and then clear all cookies/cache/history, I will be safe from the possibility of the web page stealing my seed words and BTC.
B) Insert my seed words into another app that supports BIP39/44
Being on iOS primarily, my research came up with "BitWallet" — an app that seems trustworthy due to a long track record (3+ years), but isn't open-source, as an app that supports BIP39/44. I don't know if I should trust it and think it might be safer to try option "A" first.
C) Another option I haven't considered?
Maybe there is another way?
Last resort, if all else fails, is to risk sending from Mycelium on iOS to another wallet -- but without being able to choose custom transaction fees, and with the risk of losing my funds. I've created this entire post to find out how to avoid this.

Questions I have

Q1. Is there a risk to loading my seed words into multiple wallets at the same time? Or is it the equivalent of having my public/private keys written down on multiple pieces of paper? If that is an apt analogy, I suppose the risk would simply be theft of that information by an app or hackemalware (due to an increased number of possible points of attack).
Q2. How do I use Ian Coleman's app, specifically with Mycelium iOS 12-word seeds, to recover my public/private keys? Can someone please walk me through this step-by-step? (Note: I mostly understand Bitcoin as a user and in broad strokes and am not a developer.)
Q3. Once I find out that the addresses I derive from my seed are the same as those in the app (and confirm them at, I can trust that I've properly decoded my public/private keys — correct? And then I can use those to send my funds to a trusted hardware wallet for safe-keeping via "cold storage" recovery method?
Q4. Why isn't the Mycelium (iOS) seed compatible with the Mycelium (Android) app? Should it be? According to this spreadsheet, I understand that both versions use a path of: m/44'/0'/0'
Q5. How trustworthy/risky is Ian Coleman's app (GitHub)? Can I use it confidently if I "Save Page As" to my computer, run it in Incognito with the WiFi/Internet disconnected, close the tab, then clear web cookies/cache/history before turning the WiFi/Internet back on? I suppose you can look at the comments on his GitHub, and who made recent revisions to get a sense? Again, I'm not a developer so I can't read the entire code myself.
Q6. What other BIP39/44 supporting apps might work with the 12-word master seed from Mycelium on iOS, and why can I trust them?
Q7. Side-question but also important: I had used the apparently-vulnerable Electrum 3.0.3 for my previous attempt at seed recovery, without setting a wallet password. I didn't leave the app or wallet open more than a few minutes, deleted the wallet afterwards, and didn't really browse when it was open. Am I at relatively significant risk of my seed words having been stolen if it didn't translate them correctly? If so, I should probably start trying more trustworthy apps to transfer my funds quickly (possibly starting with BitWallet or other BIP39/44-supporting wallets)!

Thank you for any help you can give in putting this guide together and solving my problem of getting funds from Mycelium on iOS to a trusted hardware wallet without needing to take the risk of sending them from that app itself.
submitted by bitcoinquestionasker to Bitcoin [link] [comments]

Proposal: bip32 version bytes for segwit scripts | Thomas Voegtlin | Sep 05 2017

Thomas Voegtlin on Sep 05 2017:
BIP32 extended public/private keys have version bytes that result in the
user visible xpub/xprv prefix. The BIP's recommendation is to use
different version bytes for other networks (such as tpub/tprv for testnet)
I would like to use additional version bytes to indicate the type of
output script used with the public keys.
I believe the change should be user visible, because users are exposed
to master public keys. I propose the following prefixes:
========== =========== ===================================
Version Prefix Description
========== =========== ===================================
0x0488ade4 xprv P2PKH or P2SH
0x0488b21e xpub P2PKH or P2SH
0x049d7878 yprv (P2WPKH or P2WSH) nested in P2SH
0x049d7cb2 ypub (P2WPKH or P2WSH) nested in P2SH
0x04b2430c zprv P2WPKH or P2WSH
0x04b24746 zpub P2WPKH or P2WSH
========== =========== ===================================
I have heard the argument that xpub/xprv serialization is a format for
keys, and that it should not be used to encode how these keys are used.
However, the very existence of version bytes, and the fact that they are
used to signal whether keys will be used on testnet or mainnet goes
against that argument.
If we do not signal the script type in the version bytes, I believe
wallet developers are going to use dirtier tricks, such as the bip32
child number field in combination with bip43/bip44/bip49.
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

bitWallet 1.6 for iOS now supports Hierarchical Deterministic wallets and Mnemonic sentences (BIP32 and BIP39) - A brief overview

Here's a few screenshots of the HD wallet section.
What this means is that you can now back up your bitWallet private keys by simply writing down your deterministic seed and storing it offline with your Electrum or Armory seeds. In fact, if you have a desktop wallet that also supports BIP32, you can actually sync or recover the same wallet addresses from your desktop. I find this very helpful when labeling transactions for budgeting and bookkeeping purposes. To my knowledge, Electrum will be supporting BIP32 in version 2.0, and it will likely be a wallet standard soon.
I did test this with breadwallet already by attempting to restore a breadwallet mnemonic with bitWallet and it worked just fine. I imagine that you should be able to restore a bitWallet mnemonic into breadwallet just fine as well, but haven't tried that.
When creating a new HD wallet in bitWallet, you need to write that mnemonic sentence down and keep it safe! It will not be shown again! You can still recover your Master Extended Private Key from the wallet settings, however.
You can also create or import traditional private keys via Classic Wallets. (No BIP38 import support on the horizon.) I haven't switched over to HD wallets entirely because I'm waiting for the Electrum update, but I've been playing around with it for the past couple weeks and it seems to work quite well.
In my personal opinion, bitWallet is the best iOS for power users, hands down. Breadwallet is probably my second choice, but it's just too simple for me. Breadwallet is the first bitcoin wallet I was comfortable with recommending to my mother though, and she loves it. I think bitWallet would probably overwhelm her unless I sat with her and trained her how to use it.
Disadvantages of bitWallet (in my opinion) are thus:
While I trust the app enough to keep a couple hundred bucks worth of bitcoin in it, and while it's built on top of the Core Bitcoin Obj-C implementation, bitWallet not fully open source. Then again, even if it was fully open source like breadwallet, we still would not know if the source code had been modified before being submitted to the App Store. I think this is a risk of mobile and web wallets that we won't overcome any time soon. That being said, I trust bitWallet enough to keep my daily spending funds secure.
My second issue is with how bitWallet handles change addresses. Basically, it's up to the user to make sure that he (or she) is sending funds to a fresh change address if he wishes to avoid address reuse. Avoiding address reuse has not been a huge priority for bitWallet, but there's nothing preventing users from managing them in a slightly manual way. I think that area could use some refinement.
Overall I'm really stoked to see how far this iOS bitcoin wallet has come in such a short time. Version 1.0 couldn't even send bitcoins due to Apple's restrictions, and now we have HD wallet functionality. I've been using beta versions on iOS 7.0.2 jailbreak for the past couple weeks without any issues whatsoever. Version 1.6 is available on the App Store right now.
submitted by BashCo to Bitcoin [link] [comments]

Bitcoin Gratis Dividendos con Coinomi - Solo para usuarios de Airbitz Seed Wallet + Privat Key importieren mit einem Problem Bitcoin Meldung signieren mit Electrum und Ledger Nano. Wie geht das? Key Signing Party Crypto Wallets. Was hat es mit den 12 oder 24 Wörter auf sich? BIP32, BIP39, BIP44

BIP32 vs BIP39. TECHNICAL HELP. Close. 3. Posted by 1 month ago. BIP32 vs BIP39. TECHNICAL HELP. Can I create a BIP39 xpub key with eletrum? If not any suggestions for an alternative wallet which does allow xpub public key creation for the BIP39 standard? 11 comments. share. save. hide. report. 81% Upvoted. Log in or sign up to leave a comment ... Bitcoin Wallet Review – Electrum JP Buntinx March 3, 2017 Reviews , Wallet When it comes to finding the right mobile bitcoin wallet, it appears the number of choices is seemingly limitless. Electrum, on the other hand, uses BIP32. MultiBit supports both BIP32 and BIP44, while Eidoo supports BIP39. As a result, some wallets such as Ledger use a 24-word passphrase. Others, such as Exodus, can read a 12-word passphrase. Obviously, in these cases, it is not possible to insert only the first 12 words, as the system would not work. For this reason, therefore, you may need to convert ... Electrum Geldbörsen und BIP32 Brieftaschen. Sie verwenden einen sehr ähnlichen Algorithmus, der es beiden ermöglicht, die Haupteigenschaft des öffentlichen Schlüssels zu haben. Obwohl die BIP32 Brieftaschen weiter gehen, indem sie auch die Hierarchie-Eigenschaft enthalten. Electrum Wallets sind nur für eine Ebene konzipiert. Obwohl man das Electrum-Protokoll sicherlich erweitern könnte ... Electrum 2.0 has been causing me some frustration, insofar as it seems to be a non-standard implementation of BIP32/BIP39 (HD wallets, mnemonic seed, respectively). The wallet in question is a 2of2

[index] [46483] [6268] [43492] [10565] [35615] [12918] [33050] [13669] [17961] [24777]

Bitcoin Gratis Dividendos con Coinomi - Solo para usuarios de Airbitz

Ledger Live Bitcoin BTC News & Ledger Wallet Updates Thẩm mỹ viện Ngọc Hường 14,524 watching Live now Blockchain tutorial 29: Hierarchical Deterministic wallet - BIP32 and BIP44 ... -The BIP32 Root Keys of the wallet-An address imported with btc. -Finally a good internet connection and good autonomy for your computer Keywords: Bitcoin Bitcoin hack Bitcoin hack 2020 Bitcoin ... We’ll stop supporting this browser soon. For the best experience please update your browser. You always dream of finding software to decrypt the private key of some Bitcoin addresses. Here you are the best private key decryption software. the bitcoin... Um zu Bewiesen, dass man der Besitzer einer Bitcoin Adresse ist, kann man eine Meldung mit dem private Key signieren. Wie das mit Hilfe von Electrum und dem Ledger Nano funktioniert, wird in ...