yeah, I am having exactly the same problems as Sam on Telegram Hush:Support.
I tested with 0 fee.
I sent many different sizes.
I disabled the shield change from t-addrs to your sapling address and received this error.
16: bad-txns-acprivacy-chain
On terminal output:
CheckTransactionWithoutProofVerification: invalid taddr RGsMk4MmeDLm1xVTL3bi9SwDE17WZBNtf9 on private chain!
found taddr in private chain: z_z.0 z_t.0 t_z.0 vinsize.80
debug.log
2021-08-18 20:04:33 Build: Created spendAuth and binding sigs
2021-08-18 20:04:34 sendrawtransaction: Submitting to mempool
2021-08-18 20:04:34 ERROR: CheckTransaction(): this is a private chain, sending to taddrs not allowed
2021-08-18 20:04:34 ERROR: AcceptToMemoryPool: CheckTransaction failed
2021-08-18 20:04:34 opid-b35e53f1-e52c-4029-b69d-2ea3c9858b20: z_sendmany finished (status=failed, error=16: bad-txns-acprivacy-chain)
yeah, I am having exactly the same problems as Sam on Telegram Hush:Support.
I tested with 0 fee.
I sent many different sizes.
I disabled the shield change from t-addrs to your sapling address and received this error.
`16: bad-txns-acprivacy-chain`
**On terminal output:**
```
CheckTransactionWithoutProofVerification: invalid taddr RGsMk4MmeDLm1xVTL3bi9SwDE17WZBNtf9 on private chain!
found taddr in private chain: z_z.0 z_t.0 t_z.0 vinsize.80
```
**debug.log**
```
2021-08-18 20:04:33 Build: Created spendAuth and binding sigs
2021-08-18 20:04:34 sendrawtransaction: Submitting to mempool
2021-08-18 20:04:34 ERROR: CheckTransaction(): this is a private chain, sending to taddrs not allowed
2021-08-18 20:04:34 ERROR: AcceptToMemoryPool: CheckTransaction failed
2021-08-18 20:04:34 opid-b35e53f1-e52c-4029-b69d-2ea3c9858b20: z_sendmany finished (status=failed, error=16: bad-txns-acprivacy-chain)
```
I was reading this article last night before I went to sleep; it is where I got the idea to test this...then I woke up in the morning and walla! someone else discovered it. https://github.com/zcash/zcash/pull/2797
```
hush-cli z_mergetoaddress '["RFJ6Hy48EvEjt-addrqDChxqtqsfyF"]' zs1hm0fgfkf7n4wv9ytce6rdvu7ewrzm0zgr3fq3azaddr 0 0
```
Works for me. ANY_TADDR probably a more notable solution for the GUI #23.
Adding the **0** **transparent_limit** is quicker because it doesn't limit to only 50 transactions.
The 0 fee probably shouldn't be used if we don't need to; when using 0 fee it transmits more metadata.
This is great information; we have solved a challenging bug.
More details here: https://faq.hush.is/rpc/z_mergetoaddress.html
I was reading this article last night before I went to sleep; it is where I got the idea to test this...then I woke up in the morning and walla! someone else discovered it. https://github.com/zcash/zcash/pull/2797
I tested with .1, 1 and 10 Hush.
more details about it on zcash github
/zcash/zcash/issues/1970yeah, I am having exactly the same problems as Sam on Telegram Hush:Support.
I tested with 0 fee.
I sent many different sizes.
I disabled the shield change from t-addrs to your sapling address and received this error.
16: bad-txns-acprivacy-chainOn terminal output:
debug.log
@oDinZu have you tried sending the total amount of funds that are in the address, with 0 fee?
@odinzu
z_mergetoaddressfromANY_TADDRshould workWorks for me. ANY_TADDR probably a more notable solution for the GUI #23.
Adding the 0 transparent_limit is quicker because it doesn't limit to only 50 transactions.
The 0 fee probably shouldn't be used if we don't need to; when using 0 fee it transmits more metadata.
This is great information; we have solved a challenging bug.
More details here: https://faq.hush.is/rpc/z_mergetoaddress.html
I was reading this article last night before I went to sleep; it is where I got the idea to test this...then I woke up in the morning and walla! someone else discovered it. https://github.com/zcash/zcash/pull/2797