Hot answers tagged

7

The passphrase set during the fundraiser can not be changed. After you have entered the fundraiser details, some wallets will store your private key in a keystore file encrypted with a password. In this case the password can always be changed. If there is no built-in function for this you can always enter your fundraiser details again and create a new ...


5

Why can I convert between address and contract. But not between address and key_hash? There is the (IMPLICIT_ACCOUNT) instruction to go from key_hash to address. For the other direction, there was (a feature request) but it was closed because no use case has been presented to motivate it.


5

key_hash is blake2b hash of a public key, in the base58 encoded form it can start only with tz, but address is more general, it can also hold KT accounts; There are no instructions for that, probably because it's a rare and arguable case; EDIT: as pointed out by Raphaël, you can convert key_hash to contract and then to address using IMPLICIT_ACCOUNT ; ...


5

Try https://github.com/murbard/pytezos/blob/master/pytezos/crypto.py from pytezos.crypto import Key key = Key(key='mnemonic', passphrase='******', email='foo@bar.com') key.public_key_hash() >>> edpk...


5

With pytezos import pytezos print(pytezos.Key('edesk...', passphrase='yourpassword').secret_key()) UPD >>> from pytezos import Key >>> key = Key.generate() >>> key.public_key_hash() 'tz1hQbcSWjcWLdcRjMDqpJVuTaaj9m2wMtwk' >>> esk = key.secret_key(passphrase='12345'.encode()) >>> esk '...


4

You can not derive Ed25519 keys in a way that is compatible with bip32 or bip44. Bip32 only defines a derivation scheme for secp256k1, and bip44 depends on bip32. To get around this problem there's a SLIP-10 specification that adapt bip32 in a way that makes it possible to derive keys for other signature schemes than secp256k1. The most important takeaways ...


3

You can find those bytes at the bottom of this file https://gitlab.com/tezos/tezos/blob/master/src/lib_crypto/base58.ml In your case, "\013\015\037\217"


3

You may want to read this guide. There is some Python code inside.


2

With regards to the difference between public key (pk), secret key (sk) and public key hash (pkh). The public key is used by other people to send encrypted messages to you, and it is also used by other people to verify that messages you send actually are from you The secret key is used by you to send messages The public key hash is used to identify your ...


2

You can use any signature in place of that parameter. For example, you can use edsigtXomBKi5CTRf5cjATJWSyaRvhfYNHqSUGrn4SdbYRcGwQrUGjzEfQDTuqHhuA8b2d8NarZjz8TRf65WkpQmo423BtomS8Q and it should return the RPC call.


2

Ledger Live, Temple, Kukai, and other wallets use HD key generation which allows for an infinite number of cryptographic secrets to be generated from a single master seed. The master seed is the 12-24 word mnemonic you generated during the setup of your Ledger Nano S/X which should be written down and safely stored. All Tezos accounts on Ledger start with a ...


2

I haven't found a solution myself using what is provided by Truffle to do what you want, so here is what I do. I guess you must be using Taquito. In this case, you can use this function to change the signer whenever you need: const signerFactory = async pk => { await Tezos.setProvider({ signer: new InMemorySigner(pk) }); return Tezos; }; However, ...


1

I think we are in the third case: Maybe useful but none has yet proposed it with convincing use cases? It is true that the keys must be given from the outside but so are the signatures so if one needs to combine signature checking and address-based authentication it is always possible to replace all occurrences of signature with pair key signature and ...


1

Have a look at this library for Tezos, written in Go. This function in particular generates a new wallet from random bytes (mnemonic and password can both be considered as random bytes) and creates an unencrypted secret key, public key, and public address.


1

The passphrase used for fundraiser wallets contribute to the makeup of the secret key, so it's impossible to change it (these passwords aren't actually used for encryption). If you believe your wallet details may have been compromised, you should create a new key and transfer your XTZ.


Only top voted, non community-wiki answers of a minimum length are eligible