This is a ācore-zcashā error. This article would be helpful to diagnose it: Perhaps you could try to send 2-3 transactions with lower amount eachā¦
Sorry to read that, like radix42, youāre also not being sufficiently rewarded by grateful users. I can appreciate that youād like ZEC donations but can I suggest that you also list other payment addresses?
I should probably go find out from the the github issues page but, when you say that a transactions is too large, do you mean that in terms of bytes or the amount of the transaction?
yes @vaklinov has put a huge amount of effort into the Swing Wallet, which is the only way I know so far to send shielded transactions with a GUI!!! send donation love his way, everyone!
The error message comes from zcashd it is due to technical limitations in transaction size in bytes (not the total value per se). I think this limit is exceeded. It may happen due to too many inputs or outputs that have to be included. However I am not an expert on thisā¦
yeah from the issue someone linked to earlier in this thread, its when there are too many inputs to a JoinSplit (too many notes) or too many recipients, etc.
Thereās some upper limit over which that wonāt helpā¦theyāre going to improve error messages for that and try and move the error generation to BEFORE it generates the proof
This step is very important! To verify that the file ZCashSwingWalletUI.jar is an authentic release, you
need to compute its SHA256 checksum, like this:
If the resulting checksum is not e6b877d0811190f398b6465580ec640808b1ea719a2e7f5838658a938153f72f then something is wrong and you should discard the downloaded wallet!
The page that describes the Windows installation points to the same release as exists for Linux (the JAR is the same across platforms). There are sites like this one that can calculate the SHA256 sum for verification.
Generally I recommend to security conscious users to build the wallet from source code. The JAR that is built from source code on one OS can be used on allā¦