How can I create unencrypted addresses?
In my alphanet tezos-client, tezos-client gen keys <address>
creates an unencrypted address, and requires the --encrypted
flag to create an encrypted address.
But in the mainnet tezos-client, running tezos-client gen keys <address>
asks for a new password and creates an encrypted address.
How can I create unencrypted addresses via in the mainnet tezos-client?
tezos-client
add a comment |
In my alphanet tezos-client, tezos-client gen keys <address>
creates an unencrypted address, and requires the --encrypted
flag to create an encrypted address.
But in the mainnet tezos-client, running tezos-client gen keys <address>
asks for a new password and creates an encrypted address.
How can I create unencrypted addresses via in the mainnet tezos-client?
tezos-client
add a comment |
In my alphanet tezos-client, tezos-client gen keys <address>
creates an unencrypted address, and requires the --encrypted
flag to create an encrypted address.
But in the mainnet tezos-client, running tezos-client gen keys <address>
asks for a new password and creates an encrypted address.
How can I create unencrypted addresses via in the mainnet tezos-client?
tezos-client
In my alphanet tezos-client, tezos-client gen keys <address>
creates an unencrypted address, and requires the --encrypted
flag to create an encrypted address.
But in the mainnet tezos-client, running tezos-client gen keys <address>
asks for a new password and creates an encrypted address.
How can I create unencrypted addresses via in the mainnet tezos-client?
tezos-client
tezos-client
asked Feb 21 at 13:39
SvanteSvante
2927
2927
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
On mainnet, here is how to do it:
- start by creating the key with a non-existent node (here
xxx
does not exist !):
tezos-client -A xxx gen keys for_stackexchange
It will display some error messages and say nothing more. In fact, the key was created.
- call it again:
tezos-client -A xxx gen keys for_stackexchange
Error:
The secret_key alias for_stackexchange already exists.
The current value is unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4.
- display the associated address:
tezos-client show address for_stackexchange -S
Warning:
Failed to acquire the protocol version from the node
Rpc request failed:
- meth: GET
- uri: http://localhost:8732/chains/main/blocks/head/metadata
- error: Unable to connect to the node: "Connection refused"
Hash: tz1Rpm5To3JT8vpqbt681EMuxEaM4tL2MvRi
Public Key: edpkvPpcAmrCFUiwBPZ4SGEsDXQstVmLHJoXKQURE2ANXem7zQH2e9
Secret Key: unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4
Seems kinda hacky. But thank you, it works!
– Svante
Feb 25 at 14:11
add a comment |
You cannot do this with the mainnet client afaik. You need to use third party tools like eztz in order to do so. Actually TezBox creates addresses which you can export unencrypted. There is also a python based tools library available called pytezos and you can look for the secret_key method
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "698"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f538%2fhow-can-i-create-unencrypted-addresses%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
On mainnet, here is how to do it:
- start by creating the key with a non-existent node (here
xxx
does not exist !):
tezos-client -A xxx gen keys for_stackexchange
It will display some error messages and say nothing more. In fact, the key was created.
- call it again:
tezos-client -A xxx gen keys for_stackexchange
Error:
The secret_key alias for_stackexchange already exists.
The current value is unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4.
- display the associated address:
tezos-client show address for_stackexchange -S
Warning:
Failed to acquire the protocol version from the node
Rpc request failed:
- meth: GET
- uri: http://localhost:8732/chains/main/blocks/head/metadata
- error: Unable to connect to the node: "Connection refused"
Hash: tz1Rpm5To3JT8vpqbt681EMuxEaM4tL2MvRi
Public Key: edpkvPpcAmrCFUiwBPZ4SGEsDXQstVmLHJoXKQURE2ANXem7zQH2e9
Secret Key: unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4
Seems kinda hacky. But thank you, it works!
– Svante
Feb 25 at 14:11
add a comment |
On mainnet, here is how to do it:
- start by creating the key with a non-existent node (here
xxx
does not exist !):
tezos-client -A xxx gen keys for_stackexchange
It will display some error messages and say nothing more. In fact, the key was created.
- call it again:
tezos-client -A xxx gen keys for_stackexchange
Error:
The secret_key alias for_stackexchange already exists.
The current value is unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4.
- display the associated address:
tezos-client show address for_stackexchange -S
Warning:
Failed to acquire the protocol version from the node
Rpc request failed:
- meth: GET
- uri: http://localhost:8732/chains/main/blocks/head/metadata
- error: Unable to connect to the node: "Connection refused"
Hash: tz1Rpm5To3JT8vpqbt681EMuxEaM4tL2MvRi
Public Key: edpkvPpcAmrCFUiwBPZ4SGEsDXQstVmLHJoXKQURE2ANXem7zQH2e9
Secret Key: unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4
Seems kinda hacky. But thank you, it works!
– Svante
Feb 25 at 14:11
add a comment |
On mainnet, here is how to do it:
- start by creating the key with a non-existent node (here
xxx
does not exist !):
tezos-client -A xxx gen keys for_stackexchange
It will display some error messages and say nothing more. In fact, the key was created.
- call it again:
tezos-client -A xxx gen keys for_stackexchange
Error:
The secret_key alias for_stackexchange already exists.
The current value is unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4.
- display the associated address:
tezos-client show address for_stackexchange -S
Warning:
Failed to acquire the protocol version from the node
Rpc request failed:
- meth: GET
- uri: http://localhost:8732/chains/main/blocks/head/metadata
- error: Unable to connect to the node: "Connection refused"
Hash: tz1Rpm5To3JT8vpqbt681EMuxEaM4tL2MvRi
Public Key: edpkvPpcAmrCFUiwBPZ4SGEsDXQstVmLHJoXKQURE2ANXem7zQH2e9
Secret Key: unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4
On mainnet, here is how to do it:
- start by creating the key with a non-existent node (here
xxx
does not exist !):
tezos-client -A xxx gen keys for_stackexchange
It will display some error messages and say nothing more. In fact, the key was created.
- call it again:
tezos-client -A xxx gen keys for_stackexchange
Error:
The secret_key alias for_stackexchange already exists.
The current value is unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4.
- display the associated address:
tezos-client show address for_stackexchange -S
Warning:
Failed to acquire the protocol version from the node
Rpc request failed:
- meth: GET
- uri: http://localhost:8732/chains/main/blocks/head/metadata
- error: Unable to connect to the node: "Connection refused"
Hash: tz1Rpm5To3JT8vpqbt681EMuxEaM4tL2MvRi
Public Key: edpkvPpcAmrCFUiwBPZ4SGEsDXQstVmLHJoXKQURE2ANXem7zQH2e9
Secret Key: unencrypted:edsk43pBvh7zPgiGWSG3XSHybCqdQV7XRosqcGPLA9TDBc5ens7oP4
edited Feb 21 at 16:15
answered Feb 21 at 16:09
lefessan♦lefessan
2,982522
2,982522
Seems kinda hacky. But thank you, it works!
– Svante
Feb 25 at 14:11
add a comment |
Seems kinda hacky. But thank you, it works!
– Svante
Feb 25 at 14:11
Seems kinda hacky. But thank you, it works!
– Svante
Feb 25 at 14:11
Seems kinda hacky. But thank you, it works!
– Svante
Feb 25 at 14:11
add a comment |
You cannot do this with the mainnet client afaik. You need to use third party tools like eztz in order to do so. Actually TezBox creates addresses which you can export unencrypted. There is also a python based tools library available called pytezos and you can look for the secret_key method
add a comment |
You cannot do this with the mainnet client afaik. You need to use third party tools like eztz in order to do so. Actually TezBox creates addresses which you can export unencrypted. There is also a python based tools library available called pytezos and you can look for the secret_key method
add a comment |
You cannot do this with the mainnet client afaik. You need to use third party tools like eztz in order to do so. Actually TezBox creates addresses which you can export unencrypted. There is also a python based tools library available called pytezos and you can look for the secret_key method
You cannot do this with the mainnet client afaik. You need to use third party tools like eztz in order to do so. Actually TezBox creates addresses which you can export unencrypted. There is also a python based tools library available called pytezos and you can look for the secret_key method
answered Feb 21 at 13:45
Ezy♦Ezy
2,863632
2,863632
add a comment |
add a comment |
Thanks for contributing an answer to Tezos Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f538%2fhow-can-i-create-unencrypted-addresses%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown