@Autotunafish in that image those addresses don’t look like testnet addresses.
Were you able to get zecwallet-cli to return utest1XXXX… addresses?
Here are my exact steps…
zcashd part:
1. remove ~./zcash/testnet3 (starting from scratch just to be sure)
2. restart zcashd
3. confirm that ~./zcash/testnet3 is recreated included the files one would expect to see e.g. see wallet.dat. *.log, blocks, etc.
4. wait for syncronization to finish
5. Confirm rpc to zcashd and see the addresses created by zcashd
curl --user XXX:YYY --data-binary ‘{“jsonrpc”: “1.0”, “id”:“curltest1”, “method”: “z_getnewaddress”, “params”: }’ -H ‘content-type: text/plain;’ http://127.0.0.1:18232
curl --user XXX:YYY --data-binary ‘{“jsonrpc”: “1.0”, “id”:“curltest2”, “method”: “z_getnewaccount”, “params”: }’ -H ‘content-type: text/plain;’ http://127.0.0.1:18232
curl --user XXX:YYY --data-binary ‘{“jsonrpc”: “1.0”, “id”:“curltest3”, “method”: “z_getaddressforaccount”, “params”: [0] }’ -H ‘content-type: text/plain;’ http://127.0.0.1:18232
curl --user XXX:YYY --data-binary ‘{“jsonrpc”: “1.0”, “id”:“curltest4”, “method”: “z_getwalletinfo”, “params”: }’ -H ‘content-type: text/plain;’ http://127.0.0.1:18232
curl --user XXX:YYY --data-binary ‘{“jsonrpc”: “1.0”, “id”:“curltest5”, “method”: “listaddresses”, “params”: }’ -H ‘content-type: text/plain;’ http://127.0.0.1:18232
Last RPC call returns…
http://127.0.0.1:18232
{“result”:[{“source”:“mnemonic_seed”,“transparent”:{“addresses”:[“tmAZaBXXWPbUCcwmg5TB5dayk8PavVf5WSQ”]},“sapling”:[{“zip32KeyPath”:“m/32’/1’/2147483647’/0’”,“addresses”:[“ztestsapling1yl2rctrdjj2fgmlalq30karyc59mmgs7fn95fg9wc5549f277fdzpydac5xygy4k9gka28f9xxf”]}],“unified”:[{“account”:0,“seedfp”:“7613e2c79ce72698c650c3dfb0b1a65471e904ccb110ea080781ce31f1585324”,“addresses”:[{“diversifier_index”:4,“receiver_types”:[“p2pkh”,“sapling”,“orchard”],“address”:“utest1ycg5ncs8djy6q7vtkgdmp72k7fsg9eu6xhlfgxxy078fxz0f9kmwr24ptgkyke0wzy2ajwda5k86p354pq0dnrrqatrtycjv5akz7hzlmrl0kjfdepkypc4232uzw75syda4hhr4hxxquehumczacfq9qzc8x4m4dff99s7mr6uqs9humt8gg3teqkkrmkcjeq8ztjsnfjr8umawlzg”}]}]}],“error”:null,“id”:“curltest5”}
This looks normal: tm, ztest, and utest1 accounts returned.
lightwalletd part:
- start lightwalletd
./lightwalletd --no-tls-very-insecure --zcash-conf-path ~/.zcash/zcash.conf --log-file /dev/stdout --rpcuser XXX --rpcpassword YYY
Just let lightwalletd use the default /var/lib/lightwalletd directory
lightwalletd returns logs no errors and as expected there are many many getblock and getbestblockhash entries visible; tail -f ~./zcash/testnet3/debug.log
zecwallet-cli part:
- Create new wallet and addresses
./zecwallet-cli --server 127.0.0.1:9067 addresses;
u1 address is returned NOT utest1 address as expected
Creating a new wallet
{
“ua_addresses”: [
“u1xxxx…” ← expected this to be utest1 ???
],
“z_addresses”: [
“zs1xxx…” ← expected this to be ztest1xxx… ???
],
“t_addresses”: [
“t1Ve15QhKXK2a2WZuLiPCn2caJTcEiEvXF2” ← This to be tmxxx… ???
]
}
- run zecwallet-cli in interactive mode
./zecwallet-cli --server 127.0.0.1:9067
Lightclient connecting to http://127.0.0.1:9067/
status: Unknown, message: “-5: Invalid address”, details: , metadata: MetadataMap { headers: {“content-type”: “application/grpc”} }
Ready!
(test) Block:2223020 (type ‘help’) >>
The prompt indicates “test” which leads me to believe that zecwallet-cli is on testnet and communicating with lightwalletd which is on testnet because lightwalletd is communicating with zcashd which is confirmed to be communicating on testnet.
There is an “Invalid address” error because the newly created zecwallet-light-wallet.dat is populated with mainnet addresses at step 6. In step 6 in this formula testnet address should be expected???
What do you think? Stumbled on a problem?
Dennis
