Private Key Address
🔞 ALL INFORMATION CLICK HERE 👈🏻👈🏻👈🏻
Private Key Address
hey, i am searching for a documentation describing the process of calculation the corresponding bitcoin address from a private key. does anyone has a link to such a document? gimme_bottles
i read that article, but i don't get how to get the address from a private key, i only see the generation process of a bitcoin address.
i read that article, but i don't get how to get the address from a private key, i only see the generation process of a bitcoin address.
Companies claiming they got hacked and lost your coins sounds like fraud so perfect it could be called fashionable. I never believe them. If I ever experience the misfortune of a real intrusion, I declare I have been honest about the way I have managed the keys in Casascius Coins. I maintain no ability to recover or reproduce the keys, not even under limitless duress or total intrusion. Remember that trusting strangers with your coins without any recourse is, as a matter of principle, not a best practice. Don't keep coins online. Use paper or hardware wallets instead.
Are you wondering how to get the public key from the private key?
Are you wondering how to get the public key from the private key?
Companies claiming they got hacked and lost your coins sounds like fraud so perfect it could be called fashionable. I never believe them. If I ever experience the misfortune of a real intrusion, I declare I have been honest about the way I have managed the keys in Casascius Coins. I maintain no ability to recover or reproduce the keys, not even under limitless duress or total intrusion. Remember that trusting strangers with your coins without any recourse is, as a matter of principle, not a best practice. Don't keep coins online. Use paper or hardware wallets instead.
#include #include #include #include #include #include #include #include #include "hash.h" unsigned char* privkey2addr(unsigned char* input) { unsigned char* output; int ret; /* return value of the sign-function */ ECDSA_SIG *sig; /* result of the signing process, containing both r and s */ EC_KEY *eckey = EC_KEY_new(); /* create new key for the signing process */ EC_GROUP *ecgroup = EC_GROUP_new_by_curve_name(NID_secp256k1); /* set secp256k1 as the signing method */ unsigned char *r, *s; if(eckey == NULL || ecgroup == NULL) { /* check for errors */ printf("Initializing of eckey or ecgroup failed!\n"); return NULL; } if(EC_KEY_set_group(eckey,ecgroup) != 1) { /* set signing method and check for errors */ printf("Setting group for eckey failed!\n"); return NULL; } if(EC_KEY_generate_key(eckey) != 1) { /* generete key and check for errors */ printf("Generating eckey failed!\n"); return NULL; } sig = ECDSA_do_sign(input, 32, eckey); /* sign the input */ if(sig==NULL) { /* error? */ printf("Signing of input failed!\n"); return NULL; } ret = ECDSA_do_verify(input, 32, sig, eckey); /* verify result */ if(ret == -1 || ret == 0) { /* error? */ printf("Verifying failed!\n"); return NULL; } r = malloc(32); /* allocate 32 bit space for both r and s */ s = malloc(32); if(BN_bn2bin(sig->r, r) != 32) { /* export BIGNUM to array of chars, check for invalid length */ printf("Invalid result length!\n"); return NULL; } if(BN_bn2bin(sig->s, s) != 32) { /* export BIGNUM to array of chars, check for invalid length */ printf("Invalid result length!\n"); return NULL; } int i; printf("X: "); /* print both r and s for debug reasons */ for(i=0; i<32; i++) { printf("%02x", (unsigned char) *(r+i)); } putc('\n', stdout); printf("Y: "); for(i=0; i<32; i++) { printf("%02x", (unsigned char) *(s+i)); } putc('\n', stdout); unsigned char *pubkey_raw; /* raw public key '*/ pubkey_raw = malloc(65); /* reserve 65 byte of space for the pubkey */ *pubkey_raw = 0x04; /* merge 0x04, r and s to the pubkey */ for(i=0; i < 32; i++) *(pubkey_raw+i+1) = *(r+i); for(i = 0; i < 32; i++) *(pubkey_raw+i+33) = *(s+i); free(r); /* free no longer required memory */ free(s); EC_KEY_free(eckey); EC_GROUP_free(ecgroup); ECDSA_SIG_free(sig); unsigned char *pubkey_stage1; /* public key after first stage */ pubkey_stage1 = malloc(20); /* reserve 20 bytes of memory */ pubkey_stage1 = RIPEMD160(SHA256(pubkey_raw, 65, (unsigned char*) NULL), 32, (unsigned char *) NULL); /* hash it! */ unsigned char *pubkey_stage2; /* public key after seconf stage */ pubkey_stage2 = malloc(25); /* reserve 25 bytes of memory */ *pubkey_stage2 = 0x00; /* put 0x00 at the beginning for main network */ for(i = 0; i < 20; i++) /* add the result of stage one */ *(pubkey_stage2+i+1) = *(pubkey_stage1+i); unsigned char *result; /* the binary address */ result = malloc(32); /* reserve 32 bytes of memory */ result = SHA256(SHA256(pubkey_stage2, 32, (unsigned char*) NULL), 32, (unsigned char*) NULL); /* calculate checksum */ for(i = 0; i < 4; i++) /* append checksum to binary address */ *(pubkey_stage2+i+21) = *(result+i); printf("Binary address: "); /* print binary address */ for(i=0; i<25; i++) { printf("%02x", (unsigned char) *(pubkey_stage2+i)); } putc('\n', stdout); output = malloc(35); output = base58(pubkey_stage2); return output; } unsigned char* base58(unsigned char* input) { unsigned char *output; BIGNUM *a; BIGNUM *b58; BIGNUM *rem; int i; unsigned char *bc58; bc58 = malloc(1); *bc58=58; unsigned char *rest; rest = malloc(1); const char *alphabet = "123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz"; BN_CTX *ctx = BN_CTX_new(); BN_CTX_init(ctx); a = BN_new(); BN_init(a); b58 = BN_new(); BN_init(b58); rem = BN_new(); BN_init(rem); BN_bin2bn((const unsigned char*) input, 25, a); BN_bin2bn((const unsigned char*) bc58 , 1, b58); output = malloc(35); i = 0; while(BN_is_zero(a) != 1) { BN_div(a, rem, a, b58, ctx); BN_bn2bin(rem, rest); *(output+i) = alphabet[*rest]; i++; } int n = 0, b = 0; for(b = 0; b < 25; b++) { if(*(input+b)==0) n++; if(*(input+b)!=0) break; } printf("%i, %i\n", n, i); for(b = 0; b < n; b++) { *(output+i+b) = alphabet[0]; } return output; }
Private Key: 1809c5d482b97ec84dd7e94cc4cbed460fd878025b52b1011970a3626e64eda8 X: c2429880bd9be5ebe72f00cc34a878cc6e5060f749b7b37957a2f087817e36c0 Y: 4117f999affb005828fd957cfaccc60530c871a05b7d205746d2ca68082d2d7d Binary address: 0075c5672c37a9140631a0bf915c0e6aa356a832b04bd05648 1, 33 Address: 5ZL8VhHCBiePTgdNn4uQYanWMMgHFYijB1 355a4c3856684843426965505467644e6e34755159616e574d4d67484659696a423100
I looked not at your code, but your numbers. The calculation from private key to public key is wrong. Why, I don't know. Private key 1809c5d482b97ec84dd7e94cc4cbed460fd878025b52b1011970a3626e64eda8 (I am assuming this is big-endian, like it usually is) shoudl have public key 04 AE 64 14 8F B6 68 4D 51 CF 03 C5 60 D7 36 28 2E 86 54 FB 54 D2 21 0D 67 4A F1 32 B1 ED 2D 2E 87 D0 B1 05 D0 97 5D C7 5C 31 91 CF 7E 64 ED FB 06 98 AF 85 7A 4A 0A BF 45 D0 06 01 00 9C 9E B8 8A which is 04 X = AE 64 14 8F B6 68 4D 51 CF 03 C5 60 D7 36 28 2E 86 54 FB 54 D2 21 0D 67 4A F1 32 B1 ED 2D 2E 87 Y = D0 B1 05 D0 97 5D C7 5C 31 91 CF 7E 64 ED FB 06 98 AF 85 7A 4A 0A BF 45 D0 06 01 00 9C 9E B8 8A calculated by a known working utility.
Companies claiming they got hacked and lost your coins sounds like fraud so perfect it could be called fashionable. I never believe them. If I ever experience the misfortune of a real intrusion, I declare I have been honest about the way I have managed the keys in Casascius Coins. I maintain no ability to recover or reproduce the keys, not even under limitless duress or total intrusion. Remember that trusting strangers with your coins without any recourse is, as a matter of principle, not a best practice. Don't keep coins online. Use paper or hardware wallets instead.
yes, it is all big endian. thanks for your example, it is great to have some values to work with
Sr. Member
Offline
Activity: 416
Merit: 258
printf("X: "); /* print both r and s for debug reasons */ for(i=0; i<32; i++) { printf("%02x", (unsigned char) *(r+i)); } printf("Y: "); for(i=0; i<32; i++) { printf("%02x", (unsigned char) *(s+i)); }
Jump to:
Please select a destination:
-----------------------------
Bitcoin
-----------------------------
=> Bitcoin Discussion
===> Legal
===> Press
===> Meetups
===> Important Announcements
=> Development & Technical Discussion
===> Wallet software
=====> Electrum
=====> Bitcoin Wallet for Android
=====> BitcoinJ
=====> Armory
=====> Mycelium
=====> Hardware wallets
=> Mining
===> Mining support
===> Pools
===> Mining software (miners)
===> Hardware
=====> Group buys
===> Mining speculation
=> Bitcoin Technical Support
=> Project Development
-----------------------------
Economy
-----------------------------
=> Economics
===> Speculation
=> Marketplace
===> Goods
=====> Computer hardware
=====> Digital goods
=======> Invites & Accounts
=====> Collectibles
===> Services
===> Currency exchange
===> Gambling
=====> Games and rounds
=====> Investor-based games
=====> Gambling discussion
===> Lending
=====> Long-term offers
===> Securities
===> Auctions
===> Service Announcements
=====> Micro Earnings
===> Service Discussion
=====> Web Wallets
=====> Exchanges
=> Trading Discussion
===> Scam Accusations
===> Reputation
-----------------------------
Other
-----------------------------
=> Meta
===> New forum software
===> Bitcoin Wiki
=> Politics & Society
=> Beginners & Help
=> Off-topic
=> Serious discussion
===> Ivory Tower
=> Archival
===> Корзина
===> CPU/GPU Bitcoin mining hardware
===> Chinese students
===> Obsolete (buying)
===> Obsolete (selling)
===> MultiBit
-----------------------------
Alternate cryptocurrencies
-----------------------------
=> Altcoin Discussion
=> Announcements (Altcoins)
===> Tokens (Altcoins)
=> Mining (Altcoins)
===> Pools (Altcoins)
=> Marketplace (Altcoins)
===> Service Announcements (Altcoins)
===> Service Discussion (Altcoins)
===> Bounties (Altcoins)
=> Speculation (Altcoins)
-----------------------------
Local
-----------------------------
=> العربية (Arabic)
===> العملات البديلة (Altcoins)
=====> النقاشات
===> إستفسارات و أسئلة المبتدئين
===> التعدين
===> النقاشات الأخرى
===> منصات التبادل
=> Bahasa Indonesia (Indonesian)
===> Jual Beli
===> Mining (Bahasa Indonesia)
===> Altcoins (Bahasa Indonesia)
=> Español (Spanish)
===> Mercado y Economía
=====> Servicios
=====> Trading y especulación
===> Hardware y Minería
===> Esquina Libre
===> Mercadillo
=====> Mexico
=====> Argentina
=====> España
=====> Centroamerica y Caribe
===> Primeros pasos y ayuda
===> Altcoins (criptomonedas alternativas)
=====> Minería de altcoins
=====> Servicios
=====> Tokens (Español)
=> 中文 (Chinese)
===> 跳蚤市场
===> 山寨币
===> 媒体
===> 挖矿
===> 离题万里
=> Hrvatski (Croatian)
===> Trgovina
===> Altcoins (Hrvatski)
=====> Announcements (Hrvatski)
===> Off-topic (Hrvatski)
=> Deutsch (German)
===> Anfänger und Hilfe
===> Mining (Deutsch)
===> Trading und Spekulation
===> Projektentwicklung
===> Off-Topic (Deutsch)
===> Treffen
===> Presse
===> Altcoins (Deutsch)
=====> Announcements (Deutsch)
===> Marktplatz
=====> Auktionen
=====> Suche
=====> Biete
=> Ελληνικά (Greek)
===> Αγορά
===> Mining Discussion (Ελληνικά)
===> Altcoins (Ελληνικά)
=====> Altcoin Announcements (Ελληνικά)
=====> Altcoin Mining (Ελληνικά)
=> עברית (Hebrew)
=> Français
===> Actualité et News
===> Débutants
===> Discussions générales et utilisation du Bitcoin
===> Mining et Hardware
===> Économie et spéculation
===> Place de marché
=====> Échanges
=====> Produits et services
=====> Petites annonces
===> Le Bitcoin et la loi
===> Wiki, documentation et traduction
===> Développement et technique
===> Vos sites et projets
===> Hors-sujet
===> Altcoins (Français)
=====> Annonces
=> India
===> Mining (India)
===> Marketplace (India)
===> Regional Languages (India)
===> Press & News from India
===> Alt Coins (India)
===> Buyer/ Seller Reputations (India)
===> Off-Topic (India)
=> Italiano (Italian)
===> Guide (Italiano)
===> Progetti
===> Discussioni avanzate e sviluppo
===> Trading, analisi e speculazione
===> Mercato
=====> Mercato valute
=====> Beni
=====> Servizi
=====> Esercizi commerciali
=====> Hardware/Mining (Italiano)
=====> Gambling (Italiano)
===> Accuse scam/truffe
===> Mining (Italiano)
===> Alt-Currencies (Italiano)
=====> Annunci
===> Raduni/Meeting (Italiano)
===> Crittografia e decentralizzazione
===> Off-Topic (Italiano)
=> 日本語 (Japanese)
===> アルトコイン
=> Nederlands (Dutch)
===> Markt
===> Gokken/lotterijen
===> Mining (Nederlands)
===> Beurzen
===> Alt Coins (Nederlands)
===> Off-topic (Nederlands)
===> Meetings (Nederlands)
=> 한국어 (Korean)
===> 대체코인 Alt Coins (한국어)
=> Pilipinas
===> Altcoins (Pilipinas)
=====> Altcoin Announcements (Pilipinas)
===> Pamilihan
===> Others (Pilipinas)
=> Polski
===> Tablica ogłoszeń
===> Alternatywne kryptowaluty
=====> Nowe kryptowaluty i tokeny
=====> Tablica ogłoszeń (altcoiny)
=> Português (Portuguese)
===> Primeiros Passos (Iniciantes)
===> Economia & Mercado
===> Mineração em Geral
===> Desenvolvimento & Discussões Técnicas
===> Criptomoedas Alternativas
===> Brasil
===> Portugal
=> Русский (Russian)
===> Новички
===> Бизнес
=====> Барахолка
=====> Обменники
===> Идеи
===> Кодеры
===> Майнеры
===> Политика
===> Трейдеры
===> Альтернативные криптовалюты
=====> Токены
=====> Бayнти и aиpдpoпы
===> Хайпы
===> Работа
===> Разное
===> Oбcyждeниe Bitcoin
=====> Новости
=====> Юристы
=> Română (Romanian)
===> Anunturi importante
===> Offtopic
===> Market
=====> Discutii Servicii
===> Minerit
===> Tutoriale
===> Bine ai venit!
===> Presa
===> Altcoins (Monede Alternative)
=====> Anunturi Monede Alternative
=> Skandinavisk
=> Türkçe (Turkish)
===> Bitcoin Haberleri
===> Pazar Alanı
===> Madencilik
===> Ekonomi
===> Servisler
=====> Fonlar
===> Proje Geliştirme
===> Alternatif Kripto-Paralar
=====> Madencilik (Alternatif Kripto-Paralar)
=====> Duyurular (Alternatif Kripto-Paralar)
===> Konu Dışı
===> Yeni Başlayanlar & Yardım
===> Buluşmalar
=> Other languages/locations
Welcome, Guest . Please login or register .
News : Latest Bitcoin Core release: 0.21.0 [ Torrent ]
Topic: get address from private key (Read 5179 times)
All Bitcoin private keys and Altcoin private keys | Check Bitcoin address
get address from private key
How to create a Bitcoin wallet address from a private key
Hex private key to address calculator (type legacy (P2PKH))
What are Public Keys , Private Keys , & Wallet Addresses ?
What is Docker?
TCP/IP Model
RTF File
CSS Transition
How to Use Instagram?
MBR VS GPT
FAT32 Format
Error 503 Code
Windows Hosts File
Mobi to PDF
What is STEM?
JavaScript Void 0
SQL Delete Row
JavaScript Replace
Python JSON Parser
cmd Delete Folder
What is NFC?
Content Type JSON
Convert HEIC to JPG
Math Random Java
WordPress for Beginners
Qualitative VS Quantitative
JavaScript Split String
Accented Letters on Mac
Windows 10 Product Key
Google Docs Landscape
Antimalware Executable
Windows 10 Start Menu
Windows 10 Command Line
Google Account Recovery
About
Alumni Network
Open Source
Shop
Support
Sponsors
Academic Honesty
Code of Conduct
Privacy Policy
Terms of Service
Copyright Policy
Learn to code — free 3,000-hour curriculum
In the previous article , we looked at different methods to generate a private key. Whatever method you choose, you’ll end up with 32 bytes of data. Here’s the one that we got at the end of that article:
60cf347dbc59d31c1358c8e5cf5e45b822ab85b79cb32a9f3d98184779a9efc2
We’ll use this private key throughout the article to derive both a public key and the address for the Bitcoin wallet.
What we want to do is to apply a series of conversions to the private key to get a public key and then a wallet address. Most of these conversions are called hash functions. These hash functions are one-way conversions that can’t be reversed. We won’t go to the mechanics of the functions themselves — there are plenty of great articles that cover that. Instead, we will look at how using these functions in the correct order can lead you to the Bitcoin wallet address that you can use.
The first thing we need to do is to apply the ECDSA or Elliptic Curve Digital Signature Algorithm to our private key. An elliptic curve is a curve defined by the equation y² = x³ + ax + b with a chosen a and b . There is a whole family of such curves that are widely known and used. Bitcoin uses the secp256k1 curve. If you want to learn more about Elliptic Curve Cryptography, I’ll refer you to this article .
By applying the ECDSA to the private key, we get a 64-byte integer. This consists of two 32-byte integers that represent the X and Y of the point on the elliptic curve, concatenated together.
In Python, it would look like this:
Note: as you can see from the code, before I used a method from the ecdsa module, I decoded the private key using codecs . This is relevant more to the Python and less to the algorithm itself, but I will explain what are we doing here to remove possible confusion.
In Python, there are at least two classes that can keep the private and public keys: “str” and “bytes”. The first is a string and the second is a byte array. Cryptographic methods in Python work with a “bytes” class, taking it as input and returning it as the result.
Now, there’s a little catch: a string, say, 4f3c does not equal the byte array 4f3c , it equals the byte array with two elements, O& lt;. And that’s wh at codecs.dec ode method does: it converts a string into a byte array. That will be the same for all cryptographic manipulations that we’ll do in this article.
But we can do better. As you might remember, the public key is some point (X, Y) on the curve. We know the curve, and for each X there are only two Ys that define the point which lies on that curve. So why keep Y? Instead, let’s keep X and the sign of Y. Later, we can derive Y from that if needed.
The specifics are as follows: we take X from the ECDSA public key. Now, we add the 0x02 if the last byte of Y is even, and the byte 0x03 if the last byte is odd.
In our case, the last byte is odd, so we add 0x03 to get the compressed public key: 031e7bcc70c72770dbb72fea022e8a6d07f814d2ebe4de9ae3f7af75bf706902a7 . This key contains the same information, but it’s almost twice as short as the uncompressed key. Cool!
Previously, wallet software used long, full versions of public keys, but now most of it has switched to compressed keys.
From now on, we need to make a wallet address. Whatever method of getting the public key you choose, it goes through the same procedure. Obviously, the addresses will differ. In this article, we will go with the compressed version.
What we need to do here is to apply SHA-256 to the public key, and then apply RIPEMD-160 to the result. The order is important.
SHA-256 and RIPEMD-160 are two hash functions, and again, we won’t go into the details of how they work. What matters is that now we have 160-bit integer, which will be used for further modifications. Let’s call that an encrypted public key. For our example, the encrypted public key is 453233600a96384bb8d73d400984117ac84d7e8b .
Here’s how we encrypt the public key in Python:
The Bitcoin has two networks, main and test. The main network is the network that all people use to transfer the coins. The test network was created — you guessed it — to test new features and software.
We want to generate an address to use it on the mainnet, so we need to add 0x00 bytes to the encrypted public key. The result is 00453233600a96384bb8d73d400984117ac84d7e8b . For the testnet, that would be 0x6f bytes.
Now we need to calculate the checksum of our mainnet key. The idea of checksum is to make sure that the data (in our case, the key) wasn’t corrupted during transmission. The wallet software should look at the checksum and mark the address as invalid if the checksum mismatches.
To calculate the checksum of the key, we need to apply SHA-256 twice and then take first 4 bytes of the result. For our example, the double SHA-256 is 512f43c48517a75e58a7ec4c554ecd1a8f9603c891b46325006abf39c5c6b995 and therefore the checksum is 512f43c4 (note that 4 bytes is 8 hex digits).
The code to calculate an address checksum is the following:
Finally, to make an address, we just concatenate the mainnet key and the checksum. That makes it 00453233600a96384bb8d73d400984117ac84d7e8b512f43c4 for our example.
That’s it! That’s the wallet address for the private key at the start of the article.
But you may notice that something is off. You’ve probably seen a handful of Bitcoin addresses and they didn’t look like that. Well, the reason is that they are encoded with Base58 . It’s a little bit odd.
Here’s the algorithm to convert a hex address to the Base58 address:
What we get is 17JsmEygbbEUEpvt4PFtYaTeSqfb9ki1F1 , a compressed Bitcoin wallet address.
The wallet key generation process can be split into four steps:
Depending on the form of public key (full or compressed), we get different addresses, but both are perfectly valid.
Here’s the full algorithm for the uncompressed public key:
If you want to play with the code, I published it to the Github repository .
I am making a course on cryptocurrencies here on freeCodeCamp News. The first part is a detailed description of the blockchain.
I also post random thoughts about crypto on Twitter , so you might want to check it out.
If you read this far, tweet to the author to show them you care. Tweet a thanks
Learn to code for free. freeCodeCamp's open source curriculum has helped more than 40,000 people get jobs as developers. Get started
freeCodeCamp is a donor-supported tax-exempt 501(c)(3) nonprofit organization (United States Federal Tax Identification Number: 82-0779546)
Our mission: to help people learn to code for free. We accomplish this by creating thousands of videos, articles, and interactive coding lessons - all freely available to the public. We also have thousands of freeCodeCamp study groups around the world.
Donations to freeCodeCamp go toward our education initiatives, and help pay for servers, services, and staff.
You can make a tax-deductible donation here .
Mature Video Full
Vagina Peeing
Porn Russian Dirty Talking Pickup
Boy Fuck Grannies
Naked House
