tfFullyCanonicalSig

[BeliyBro33]

Good day!
I have an old transaction 33E7E6BBC8FCFD23D2FE309C3537E24285E56E1DDA5B476CFD2B70874A5D9557 . sent funds from the exchange VinDAX to yobit . The receipt was refused because there was no flag (tfFullyCanonicalSig ). a lot of time has passed, maybe now there are some solutions to this issue?

[ximinez]

There's nothing any of the developers in this repo can do to help you with this issue. You'll have to contact VinDAX and/or yobit to straighten things out, particularly since it looks like that transaction was from 2020.

The good news is that the RequireFullyCanonicalSig amendment was enabled about 8 months after that transaction was validated, so the flag no longer has any effect. Exchanges may still require it, but that is out of our hands. https://xrpl.org/resources/known-amendments#requirefullycanonicalsig

[BeliyBro33]

from topic 3042(#3042), it seemed to me that there is some tool that can correct the transaction and sign it correctly

"If necessary, we could publish a tool that can convert non-fully-canonical signatures to fully-canonical signatures. Basically, this tool would take advantage of the malleability of those transactions to make fully-canonical variants of them without needing anything beyond the signed blob of the transaction itself. This would of course result in a slightly different blob and a different hash, but anyone who has such transactions in cold storage could use this tool to convert them to fully-canonical signatures."