Add migrate_zcashd_wallet command.#152
Conversation
099475d to
86d747e
Compare
e2d4ef6 to
17df195
Compare
2b4d0c7 to
7b2b817
Compare
b55f231 to
b565c41
Compare
b565c41 to
fa843a2
Compare
fa843a2 to
619d100
Compare
7df8b76 to
4c547c3
Compare
Co-authored-by: Jack Grigg <thestr4d@gmail.com>
The primary purpose of the asynchronous operation of `z_sendmany` is to avoid long proving times in a synchronous call. We don't have any reason to believe that proposal construction should be a long-running process, and it's better to report errors to the user synchronously rather than async, so this change moves all of proposal construction into the synchronous phase of the RPC call.
91040f5 to
c013767
Compare
1da8505 to
cb94bf3
Compare
| zcash_protocol = { git = "https://github.com/zcash/librustzcash.git", rev = "10caf455e3f52744b5392af226a408b05721f70f" } | ||
|
|
||
| zewif = { git = "https://github.com/zcash/zewif.git", rev = "f84f80612813ba00a0a8a9a5f060bd217fa981cc" } | ||
| zewif-zcashd = { git = "https://github.com/zcash/zewif-zcashd.git", rev = "02a98d6236e24819904e084180da9ba0f5c9b5d0" } |
There was a problem hiding this comment.
Where is this commit from? I can't find it anywhere.
There was a problem hiding this comment.
The zewif commit is the tip of zcash/zewif#1.
The zewif-zcashd commit does not correspond to either the tip of https://github.com/zcash/zewif-zcashd or any PR opened on it.
There was a problem hiding this comment.
zcash/zewif#1 for zewif
https://github.com/zcash/zewif-zcashd/tree/fix/wallettx_sapling_parsing for zewif-zcashd. It's on PR #1 from my fork; I've also now pushed it to the zcash org repo.
There was a problem hiding this comment.
It is not on zcash/zewif-zcashd#1 which is very confusing to me, because I do now see it on that branch.
| let config = APP.config(); | ||
|
|
||
| // Start monitoring the chain. | ||
| let (chain_view, _chain_indexer_task_handle) = ChainView::new(&config).await?; |
There was a problem hiding this comment.
Non-blocking: if we start any component that fires off a background task, we need to shut it down as well. This particular callsite will be altered by #237 so I will fix this then.
|
|
||
| if !account_exists { | ||
| db_data.import_account_ufvk( | ||
| &format!("zcashd legacy sapling {}", idx), |
There was a problem hiding this comment.
Non-blocking, but for the record this will be incorrect for imported Sapling keys (which are not associated with any legacy account) until #263 is done.
Co-authored-by: Jack Grigg <thestr4d@gmail.com>
f9e3faf to
f53923b
Compare
str4d
left a comment
There was a problem hiding this comment.
utACK f53923b however CI is still failing. The tests now need to have the new features enabled; something like this in zallet/Cargo.toml should work:
[[test]]
name = "cli_tests"
required-features = ["zcashd-import"]Place this between [package.metadata.deb] and [dependencies] (I always try to follow the section order in The Manifest Format for consistency).
f54315a to
61700db
Compare
`CmdRunner` uses `cargo run` under the hood, which can rebuild the main binary. If this runs before `cli_tests` it can alter the features that the latter test expects to be present. We also fix the acceptance tests to tolerate the stderr output maybe containing a rebuild. Co-authored-by: Jack Grigg <jack@electriccoin.co>
61700db to
bb3e630
Compare
This adds support for importing the secret key material from a
zcashdwallet.datfile intozallet.It does not at present support import of wallet history; a wallet initialized using this command will perform recovery via scanning the chain.
Depends on zcash/librustzcash#1768