简体   繁体   English

使用 Kaleido 的以太坊账户私钥

[英]Private key of Ethereum account using Kaleido

I have set up an Ethereum network an a couple of nodes using Kaleido.我已经使用 Kaleido 建立了一个以太坊网络和几个节点。 For each node an account is created by default.默认情况下为每个节点创建一个帐户。 Is there a way to get the private key of that account?有没有办法获得那个账户的私钥?

The account private keys are stored in the wallet on the Go-ethereum node. 账户私钥存储在Go-ethereum节点上的钱包中。 JSON/RPC and web3 do not provide an API to retrieve that private key, only to perform signing using it. JSON / RPC和web3不提供API来检索该私钥,仅使用该API进行签名。

Kaleido is in the process of introducing a secure backup store, which can be configured at node creation time to point at an AWS S3 storage bucket. Kaleido正在引入安全备份存储,可以在节点创建时对其进行配置以指向AWS S3存储桶。 When a node has this configured, it will be possible to backup the filesystem of the node to the S3 Bucket (which can be encrypted using standard AWS features), including the wallet and access passwords for that wallet. 配置了节点后,就可以将节点的文件系统备份到S3存储桶(可以使用标准AWS功能对其进行加密),包括钱包和该钱包的访问密码。 If you have a KMS configured on the node, those passwords will be further protected by the master key in KMS. 如果在节点上配置了KMS,则这些密码将由KMS中的主密钥进一步保护。

This secure backup facility is coming very soon (the APIs are actually already live, but it's a dark feature as the docs/UI are not published). 这种安全的备份功能即将推出(API实际上已经启用,但是由于未发布docs / UI,所以这是一个黑暗的功能)。 However, this won't allow you to perform a backup of an existing node. 但是,这将不允许您执行现有节点的备份。 The configurations for Backup, Log streaming and KMS needs to be set at node creation time at the moment. 目前需要在节点创建时设置备份,日志流和KMS的配置。 It is on the Kaleido roadmap to allow Backup & Log streaming to be reconfigured on an existing node, but we aren't able to commit to a timeline on that. Kaleido路线图上允许在现有节点上重新配置“备份和日志”流,但是我们无法为此承诺时间。

I hope that helps explain the situation. 我希望这有助于解释情况。 Regards, Peter 问候,彼得

I had a similar issue - contract creation and ownership was reliant on msg.sender address(constructor) but Kaleido only seems to allow contract deployment using the accounts on Kaleido, which I can't find private keys for.我有一个类似的问题 - 合同创建和所有权依赖于msg.sender地址(构造函数),但 Kaleido 似乎只允许使用 Kaleido 上的帐户部署合同,我找不到私钥。

The temporary solution was to change the contract to take the address in param instead of using msg.sender临时解决方案是更改合同以获取param中的地址而不是使用msg.sender

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM