Seth-rpc错误"Alias not found in key directory“，即使在seth-cli-go中创建了别名也是如此

Question

我正在尝试解锁我在seth-rpc容器中创建的别名(使用seth-cli-go创建)。我在seth-rpc中使用以下命令：

docker exec -it seth-rpc bash
seth-rpc --connect tcp://validator:4004 --bind 0.0.0.0:3030 --unlock myalias

在运行上面的命令时，我得到了以下错误：‘别名未在密钥目录中找到’

在seth-cli-go中创建帐户：

docker exec -it seth-cli-go bash
openssl ecparam -genkey -name secp256k1 | openssl ec -out key-file.pem -aes128
seth account import key-file.pem myalias
seth account create --nonce=0 --wait myalias
Account created
Transaction Receipt:  {
  "TransactionID": "bfc03a624baf4ac0f7c983057ae8ce7306190f47029f891e92f8b268b6009b9a3982d0c56dc9ebc45f40d9dc058bb36c76e816398f1046ac95ce48b9bc546aab",
  "Address": "29b71fd0c3100d9595cd9daefa9850e16feb2831"
}

有人能指出我做错了什么吗？

Answer 1

我已经找到了解决这个问题的方法。在docker-compose.yaml文件中，在seth-cli-go的"volumes“部分下添加"- sawtooth:/root/.sawroot”。这确保了在seth-cli-go docker容器下创建的别名对seth-rpc容器也是可见的。我们可以使用以下命令从seth-rpc解锁别名。但是，在解锁后，如果我试图使用"eth_sendTransaction“发送事务，它会显示一个内部错误："Account with address not found”。

$ seth-rpc --unlock myalias --connect tcp://validator:4004 --bind 0.0.0.0:3030
02c0b4c855d0e54a7f6dc5635e2aab0714387ba88b678fe2cc264ce0917fab83b6 unlocked: 373ec8d9b7d1814aa4d081ab4241bf618d73f384

$ curl -d '{"jsonrpc": "2.0", "method": "eth_sendTransaction", "id": 2, "params": [{"from": "0x373ec8d9b7d1814aa4d081ab4241bf618d73f384", "data": "0x608060405234801561001057600080fd5b50610271806100206000396000f3fe608060405260043610610062576000357c0100000000000000000000000000000000000000000000000000000000900463ffffffff1680631ab06ee514610067578063812600df146100ac5780639507d39a146100e7578063c20efb9014610136575b600080fd5b34801561007357600080fd5b506100aa6004803603604081101561008a57600080fd5b810190808035906020019092919080359060200190929190505050610171565b005b3480156100b857600080fd5b506100e5600480360360208110156100cf57600080fd5b81019080803590602001909291905050506101cb565b005b3480156100f357600080fd5b506101206004803603602081101561010a57600080fd5b81019080803590602001909291905050506101fa565b6040518082815260200191505060405180910390f35b34801561014257600080fd5b5061016f6004803603602081101561015957600080fd5b8101908080359060200190929190505050610216565b005b80600080848152602001908152602001600020819055507f545b620a3000f6303b158b321f06b4e95e28a27d70aecac8c6bdac4f48a9f6b38282604051808381526020018281526020019250505060405180910390a15050565b600160008083815260200190815260200160002054016000808381526020019081526020016000208190555050565b6000806000838152602001908152602001600020549050919050565b60016000808381526020019081526020016000205403600080838152602001908152602001600020819055505056fea165627a7a723058203b4d5a111ec2d08b1e7c24d98b5021878a6bb192cc2c5a309663b6bf9db18a2d0029"}]}' -H "Content-Type: application/json" localhost:3030
{"jsonrpc":"2.0","error":{"code":-32603,"message":"Internal error"},"id":2}

另一件事是，在我将验证器(端口4004)与seth-rpc(端口3030)绑定的终端中没有记录任何错误消息。但是，在锯齿验证器终端中记录错误。你知道为什么会发生这样的事情吗？

Answer 2

此问题已在PR#49 https://github.com/hyperledger/sawtooth-seth/pull/49/files集成版2018-07-10的锯齿赛斯源代码中修复。所以Seth的最新版本应该不会有这个问题。