Just checking that z_mergetoaddress is considered ‘safe to use’ ? Its disabled by default & marked as experimental but I’m guessing this is due to the Sprout/Sapling turnstile.
I’ll only be using taddrs & sapling zaddrs so hopefully not an issue.
Just checking that z_mergetoaddress is considered ‘safe to use’ ? Its disabled by default & marked as experimental but I’m guessing this is due to the Sprout/Sapling turnstile.
I’ll only be using taddrs & sapling zaddrs so hopefully not an issue.
In case you were not aware, Sapling support for z_mergetoaddress
was only just added a few days ago so you’d either need to build the latest from source, run the 2.0.2 release candidate or wait for 2.0.2 to be released (which will be soon).
It’s always been an experimental feature since it was released and isn’t related to the Sprout/Sapling turnstile. I think it’s fair to say it’s safe to use and it’s more that say the output / format / functionality could change etc… in future releases.
Great, thanks ! (20 chars)
Edit: Just to add it works very nicely - slurping the entire transparent balance to a shielded address in one command & exactly what I wanted. Here’s the command :-
zcash-cli z_mergetoaddress [\“ANY_TADDR\”] “put_your_sapling_z-address_here”