when i look at the first 2 addresses, bitaddress.org is the same as blockchain.com, before, i created the test with another 64 characters
So finally what do you have? 3 phrases, 3 addresses and 3 private keys? 2 phrases gives address as expected and in both bitaddress and blockchain page produce the same WIF you have? And you have also 1 address (which should be loaded), 1 WIF and 1 phrase, and now what? Phrase cannot be encoded into WIF you have? Or WIF does not create address you expect to have? Or everything works but address is empty? And of course for these 3 WIFs or 3 phrases you generated 6 addresses, both compressed and uncompressed? |
|
|
|
yes like i said it was created july 30 with a year of birth and subsequent numbers for 64 characters long and have get a address and private key WIF.
i'm providing 2 more addresses, it starts with the preceded day, preceded month and preceded yearjust to be sure.
I hesitated before using 1 of 3, to protect the private key.
i tried a character range on bitaddress and got 2 addresses, one of which is the same, that was just testing.
for example you add a 64 character word to blockchain.com and then try to re-create it at bitaddress.org
OK So you have used site bitaddress.org in 2015, right? Then you generated what a) brain wallet using as a phrase 64-characters long text, which contained some date. b) paper wallet using your passphrase to BIP38 Encrypt? (but then private key starts from 6) And what is the problem now? Or you think you remember but you receive wrong results? Maybe in the meantime something has changed on bitaddress (personally I do not think so). You may go to their git page with a history of releases: https://github.com/pointbiz/bitaddress.org/releasesand try to download older version of page, open from your disk and then try to recreate address. The fact that you changed phrase and gave us another address means nothing, it is a really long way from key to address. |
|
|
|
try client.query(`SELECT * FROM colours_strength_table WHERE id == ${id}`,
function(err, rows) {
for (let r in rows) {
}
}) |
|
|
|
You said it was paper wallet, please tell how you generated key: 1) You had a text input, like "10-10-1900 bla bla bla", 64 characters long; then you used tool to generate paper wallet, so it probably took your text, calculated hash etc. 2) You generated input "10101900123456789"..., 64 characters long, which was treated as hex encoded private key, so it could be converted to both un- and compressed addresses. How did you generate 3 addresses from one private key? Or did you use 3 different private keys? Now, what do you have? Both compressed and uncompressed address from private key in WIF form (5... K...)? You may use that tools: (preferably offline, you may also download page from git and launch from local disk, not web) * https://iancoleman.io/bitcoin-key-compression/Does your input (52 or 51 characters WIF) used there produces the same addresses? Does your input converts into 64 characters which looks familiar? If it is not a secret - are you native English speaker? If not, which language do you use? Do you use translator? You wrote: i have a wallet created like a paper wallet, by my birthday date and enough 64 character numbers to get the address and private key Why you needed 64 characters to generate address? i selected 1 of 3 addresses with private key and saved that year.
it starts from previous birthday, last month and previous year. What was the source of 3 addresses? What is the correlation between address and year? |
|
|
|
Thanks again for your code. He really helped me out a lot.
I get 4 different addresses from it on 4 different derivation paths. I reuse the first deterministic key every time.
Intuitively, I understood how it works))
But the maximum speed of this code is 5 per processor core per second. I would like to speed up. Once every ten)))
Very slow, indeed. I have just checked (curiosity...) and my code generates 2048 addresses in about 12 second using one thread (it gives around 160 per sec), one address per seed. It counts only addresses generated from proper seed, so there was additionally checksum verification, rejection wrong seeds etc. If it would be intended to generate addresses only (without checksum tests), it would be much faster. And if you generate multiple addresses from one seed, the result should be even better. |
|
|
|
Sanka555 uses piece of code which I posted here long time ago. Obtaining the address is correct, four repeated lines are used to create address on the specific derivation path - of course it is not parametrized (coin, account, address number, hardened or not), but idea is correct. It corresponds to path 84'/0'/0'/0 There is nothing wrong with reusing variable deterministicKey. Of course if you would like to generate x addresses, you must keep "one to last" key and then generate child based on it. Sanka555: what exactly is slow and what does it mean 'slow'? Which speed do you expect? Now I am guessing, I have no time now to check source code: If you launch it only once, it is possible that during first launch you must initiate Digests (functions for hash) etc. Some of them probably are reused later. Try to launch the same code several times, just to see if next iterations have different execution time than the first one. Other approach would be to see what you may externalize and initialize before you calculate address. Update: I was right, method HDKeyDerivation.createMasterPrivateKey(seed); creates HmacSha512 digest, which may take some time. You may take a look how I calculate address in my program (and what is externalized or calculated outside). See method check() (line 126): https://github.com/PawelGorny/lostword/blob/master/src/main/java/com/pawelgorny/lostword/Worker.javaI really have no idea how to help you, as you create many topics about similar issues and it seems you really do not know what you do. |
|
|
|
You create several topics about the same issue. I have already wrote you how the algorithm works: https://medium.com/geekculture/cryptocurrency-911-how-does-12-word-seed-phrase-work-9d892de9732If you cannot rewrite it into proper java code, it is better not to do it at all, as you may produce many bugs. But if you want to have it done, contact me and I may prepare software for you, you will not pay much  Coming back to subject: if you have only 11 words, you may produce 128 12th words, so you may have 128 correct seeds. import org.bitcoinj.core.Utils;
import org.bitcoinj.crypto.MnemonicCode;
import java.io.IOException;
import java.security.MessageDigest;
import java.security.NoSuchAlgorithmException;
import java.util.*;
public class Find12 {
private static final int TARGET_SIZE = 12;
private static List<String> WORDS;
private static MessageDigest SHA256;
private static int CONCAT_LEN_BITS;
private static int CONCAT_LEN_BITS_DIV_33;
private static int CONCAT_LEN_BITS_MINUS_CONCAT_LEN_BITS_DIV_33;
private static int CONCAT_LEN_BITS_MINUS_CONCAT_LEN_BITS_DIV_33__DIV8;
public static void main(String args[]) throws IOException {
String[] input = new String[]{"faith","always","acquire","host","amused",
"mercy","horn","service","series","stove","off"};
Find12 find12 = new Find12();
find12.findSeed(input);
}
public Find12() throws IOException {
WORDS = new MnemonicCode().getWordList();
try {
SHA256 = MessageDigest.getInstance("SHA-256");
} catch (NoSuchAlgorithmException var1) {
throw new RuntimeException(var1);
}
this.CONCAT_LEN_BITS = 11 * TARGET_SIZE;
this.CONCAT_LEN_BITS_DIV_33 = CONCAT_LEN_BITS/33;
this.CONCAT_LEN_BITS_MINUS_CONCAT_LEN_BITS_DIV_33 = CONCAT_LEN_BITS - CONCAT_LEN_BITS_DIV_33;
this.CONCAT_LEN_BITS_MINUS_CONCAT_LEN_BITS_DIV_33__DIV8 = CONCAT_LEN_BITS_MINUS_CONCAT_LEN_BITS_DIV_33/8;
}
private void findSeed(String[] input) {
for(int i=0; i<WORDS.size(); i++){
List<String> seed = new ArrayList<>(Arrays.asList(input));
seed.add(WORDS.get(i));
if (checksumCheck(seed)){
System.out.println(Utils.SPACE_JOINER.join(seed));
}
}
}
private boolean checksumCheck(List<String> words){
boolean[] concatBits = new boolean[CONCAT_LEN_BITS];
int wordindex = 0;
int hash;
for(Iterator checksumLengthBits = words.iterator(); checksumLengthBits.hasNext(); ++wordindex) {
String entropyLengthBits = (String)checksumLengthBits.next();
int entropy = Collections.binarySearch(WORDS, entropyLengthBits);
if(entropy < 0) {
return false;
}
for(hash = 0; hash < 11; ++hash) {
concatBits[wordindex * 11 + hash] = (entropy & 1 << 10 - hash) != 0;
}
}
byte[] var13 = new byte[CONCAT_LEN_BITS_MINUS_CONCAT_LEN_BITS_DIV_33__DIV8];
for(hash = 0; hash < var13.length; ++hash) {
for(int hashBits = 0; hashBits < 8; ++hashBits) {
if(concatBits[hash * 8 + hashBits]) {
var13[hash] = (byte)(var13[hash] | 1 << 7 - hashBits);
}
}
}
byte[] var14 = hash(var13, 0, var13.length, SHA256);
boolean[] var15 = bytesToBits(var14);
for(int i = 0; i < CONCAT_LEN_BITS_DIV_33; ++i) {
if(concatBits[CONCAT_LEN_BITS_MINUS_CONCAT_LEN_BITS_DIV_33 + i] != var15[i]) {
return false;
}
}
return true;
}
private boolean[] bytesToBits(byte[] data) {
boolean[] bits = new boolean[data.length * 8];
for(int i = 0; i < data.length; ++i) {
for(int j = 0; j < 8; ++j) {
bits[i * 8 + j] = (data[i] & 1 << 7 - j) != 0;
}
}
return bits;
}
public byte[] hash(byte[] input, int offset, int length, MessageDigest sha256) {
sha256.reset();
sha256.update(input, offset, length);
return sha256.digest();
}
}
Seed from the example (faith always acquire host amused mercy horn service series stove off) produces: faith always acquire host amused mercy horn service series stove off ability
faith always acquire host amused mercy horn service series stove off across
faith always acquire host amused mercy horn service series stove off ahead
faith always acquire host amused mercy horn service series stove off alley
faith always acquire host amused mercy horn service series stove off announce
faith always acquire host amused mercy horn service series stove off armed
faith always acquire host amused mercy horn service series stove off ask
faith always acquire host amused mercy horn service series stove off avocado
faith always acquire host amused mercy horn service series stove off axis
faith always acquire host amused mercy horn service series stove off banana
faith always acquire host amused mercy horn service series stove off beef
faith always acquire host amused mercy horn service series stove off bind
faith always acquire host amused mercy horn service series stove off bonus
faith always acquire host amused mercy horn service series stove off breeze
faith always acquire host amused mercy horn service series stove off buffalo
faith always acquire host amused mercy horn service series stove off buyer
faith always acquire host amused mercy horn service series stove off canoe
faith always acquire host amused mercy horn service series stove off catalog
faith always acquire host amused mercy horn service series stove off certain
faith always acquire host amused mercy horn service series stove off champion
faith always acquire host amused mercy horn service series stove off clap
faith always acquire host amused mercy horn service series stove off cloud
faith always acquire host amused mercy horn service series stove off coast
faith always acquire host amused mercy horn service series stove off comic
faith always acquire host amused mercy horn service series stove off corn
faith always acquire host amused mercy horn service series stove off cream
faith always acquire host amused mercy horn service series stove off crunch
faith always acquire host amused mercy horn service series stove off damage
faith always acquire host amused mercy horn service series stove off delay
faith always acquire host amused mercy horn service series stove off desk
faith always acquire host amused mercy horn service series stove off despair
faith always acquire host amused mercy horn service series stove off disagree
faith always acquire host amused mercy horn service series stove off donor
faith always acquire host amused mercy horn service series stove off dumb
faith always acquire host amused mercy horn service series stove off dutch
faith always acquire host amused mercy horn service series stove off ecology
faith always acquire host amused mercy horn service series stove off end
faith always acquire host amused mercy horn service series stove off entry
faith always acquire host amused mercy horn service series stove off erase
faith always acquire host amused mercy horn service series stove off excess
faith always acquire host amused mercy horn service series stove off fabric
faith always acquire host amused mercy horn service series stove off faith
faith always acquire host amused mercy horn service series stove off fence
faith always acquire host amused mercy horn service series stove off film
faith always acquire host amused mercy horn service series stove off flush
faith always acquire host amused mercy horn service series stove off fold
faith always acquire host amused mercy horn service series stove off frequent
faith always acquire host amused mercy horn service series stove off garden
faith always acquire host amused mercy horn service series stove off gauge
faith always acquire host amused mercy horn service series stove off glimpse
faith always acquire host amused mercy horn service series stove off gospel
faith always acquire host amused mercy horn service series stove off guess
faith always acquire host amused mercy horn service series stove off harvest
faith always acquire host amused mercy horn service series stove off hedgehog
faith always acquire host amused mercy horn service series stove off holiday
faith always acquire host amused mercy horn service series stove off humble
faith always acquire host amused mercy horn service series stove off illegal
faith always acquire host amused mercy horn service series stove off indicate
faith always acquire host amused mercy horn service series stove off inmate
faith always acquire host amused mercy horn service series stove off invite
faith always acquire host amused mercy horn service series stove off join
faith always acquire host amused mercy horn service series stove off kitchen
faith always acquire host amused mercy horn service series stove off label
faith always acquire host amused mercy horn service series stove off lawsuit
faith always acquire host amused mercy horn service series stove off lesson
faith always acquire host amused mercy horn service series stove off live
faith always acquire host amused mercy horn service series stove off love
faith always acquire host amused mercy horn service series stove off manual
faith always acquire host amused mercy horn service series stove off maximum
faith always acquire host amused mercy horn service series stove off merry
faith always acquire host amused mercy horn service series stove off minor
faith always acquire host amused mercy horn service series stove off monkey
faith always acquire host amused mercy horn service series stove off mushroom
faith always acquire host amused mercy horn service series stove off negative
faith always acquire host amused mercy horn service series stove off net
faith always acquire host amused mercy horn service series stove off number
faith always acquire host amused mercy horn service series stove off obtain
faith always acquire host amused mercy horn service series stove off orange
faith always acquire host amused mercy horn service series stove off output
faith always acquire host amused mercy horn service series stove off panther
faith always acquire host amused mercy horn service series stove off patient
faith always acquire host amused mercy horn service series stove off permit
faith always acquire host amused mercy horn service series stove off pill
faith always acquire host amused mercy horn service series stove off plug
faith always acquire host amused mercy horn service series stove off potato
faith always acquire host amused mercy horn service series stove off pride
faith always acquire host amused mercy horn service series stove off prosper
faith always acquire host amused mercy horn service series stove off quit
faith always acquire host amused mercy horn service series stove off rack
faith always acquire host amused mercy horn service series stove off rather
faith always acquire host amused mercy horn service series stove off reform
faith always acquire host amused mercy horn service series stove off renew
faith always acquire host amused mercy horn service series stove off retreat
faith always acquire host amused mercy horn service series stove off river
faith always acquire host amused mercy horn service series stove off rural
faith always acquire host amused mercy horn service series stove off satisfy
faith always acquire host amused mercy horn service series stove off scan
faith always acquire host amused mercy horn service series stove off seminar
faith always acquire host amused mercy horn service series stove off service
faith always acquire host amused mercy horn service series stove off shoe
faith always acquire host amused mercy horn service series stove off similar
faith always acquire host amused mercy horn service series stove off slam
faith always acquire host amused mercy horn service series stove off smooth
faith always acquire host amused mercy horn service series stove off soft
faith always acquire host amused mercy horn service series stove off speak
faith always acquire host amused mercy horn service series stove off squeeze
faith always acquire host amused mercy horn service series stove off stand
faith always acquire host amused mercy horn service series stove off struggle
faith always acquire host amused mercy horn service series stove off sugar
faith always acquire host amused mercy horn service series stove off surface
faith always acquire host amused mercy horn service series stove off system
faith always acquire host amused mercy horn service series stove off test
faith always acquire host amused mercy horn service series stove off thunder
faith always acquire host amused mercy horn service series stove off token
faith always acquire host amused mercy horn service series stove off tonight
faith always acquire host amused mercy horn service series stove off tray
faith always acquire host amused mercy horn service series stove off trend
faith always acquire host amused mercy horn service series stove off twin
faith always acquire host amused mercy horn service series stove off undo
faith always acquire host amused mercy horn service series stove off uphold
faith always acquire host amused mercy horn service series stove off utility
faith always acquire host amused mercy horn service series stove off verb
faith always acquire host amused mercy horn service series stove off voice
faith always acquire host amused mercy horn service series stove off waste
faith always acquire host amused mercy horn service series stove off wealth
faith always acquire host amused mercy horn service series stove off where
faith always acquire host amused mercy horn service series stove off wonder
faith always acquire host amused mercy horn service series stove off wreck |
|
|
|
|
Yes.
The best would be to export private keys and import into other client (I would suggest Electrum), to have fully functional wallet.
You may also import only addresses (no priv keys), to create read-only wallet - that way you will see balance, but you will not be able to spend.
|
|
|
|
Did not you forget to specify which file should be opened?  --datadir=DATADIR wallet directory (defaults to bitcoin default)
--wallet=WALLETFILE wallet filename (defaults to wallet.dat)
Something like: python pywallet.py --dumpwallet --datadir=DATADIR --wallet=WALLETFILE And do not forget about if you have one |
|
|
|
|
Why do you think about USD only? On planet Earth there are hundreds of currencies.
For example: 1 BTC = 7.5 mln Japanse yen, 1 satoshi is less than yen.
So what? Nothing.
|
|
|
|
They don't point to the same private key. The brainwalletx will give you an address whose private key will be the hash of your word and the other will give you private keys whose master private keys' entropy will be the hash of the word.
Yes, right - the difference is how you retrieve address from private key. One way it is "direct", other way "indirect" as you create children using additional algorithm. |
|
|
|
|
I think the question was if user receive the same address using both seed and brainwallet. And then yes, as both point to the same private key.
|
|
|
|
I think the best would be to extract private key and use other client - anyway you will need to do it if you want to get your altcoins (check https://findmycoins.ninja/ for your address) |
|
|
|
I am not an expert in Bitcoin Wallet (for android), but it is possible that something has changed during 7 years, it would be necessary to check release notes. Maybe they by default work now on (Native)Segwit, not on old 1xxxx format? No idea. Did you protect wallet with PIN? Anyway, they say you may manually restore private keys from backup file (scroll to the bottom): https://github.com/bitcoin-wallet/bitcoin-wallet/blob/master/wallet/README.recover.mdYou may try to use their tool (preferably being offline). As you receive WIF, you may probably easily import it to any other client, mobile or desktop. |
|
|
|
When using VanitySearch
What meaning about Base Key: DA12E013325F12D6B68520E327847218128B788E6A9F2247BC104A0EE2818F44 ?
The initial key from which search starts. If the initial key would be always the same, users who search for the same prefix would receive the same results (first key which fulfils criteria). |
|
|
|
Yes, it is doable. You will need a program which in fact not "delete" files, but overwrites the whole disk with a new content - and do it several times. Normal "delete" only removes information about file, but file stays on it's place. It is more like removing plate with your name from the front door - it does not mean you will disappear inside your flat One of options: https://www.howtogeek.com/howto/15037/use-an-ubuntu-live-cd-to-securely-wipe-your-pcs-hard-drive/BTW: Why not sell laptop without HDD? |
|
|
|
|
Show Posts
