Martin Lang

ok, so the output seems to be wrong when doing an author-signature. thx, will check. the output from verify should be ok.

hmm, ok, strange. when i sign the metadata like `./cardano-signer sign --cip100 --data-file ktorz.json --secret-key MartinLang.drep.skey --author-name "Martin Lang" --out-file ktorz2.json` ```json { "workMode": "sign-cip100", "outFile": "ktorz2.json", "anchorHash": "13c4ede0869b8582ddf1908659c0638cc120beea91502c217b51def5f9f15cbd" }...

the hash `7d2f344f3651a8372ad603abf11fcb310fb3c5154a6592591d1ff97d951156e3` should be ok for your file, so you can at least submit it. but that is strange that you get a different output during the signing, but...

@KtorZ could you try it with this binary? https://my-ip.at/test/cardano-signer-1.24.3_linux-x64.tar.gz

@KtorZ did you find the time yet to re-try?

Sorry, i thought you were using linux 😄 I can't follow you. I have the ktorz.json metadata file here without a linefeed at the end. `hexyl ktorz.json` ``` │00004b50│ 75...

I have tried to reproduce the issue with rick, he is running an M4pro. No issue at all. 🤔

yea the `verify` function was always ok. but you said you had the issue with the `sign --cip100` function. that this function returned the hash `615380...` while the `verify` function...

Ah ok, now i got you. Ok so the actual issue is a "maybe" re-edit after the file was written out. Hmm. Ok so you suggest that if the input...

I think i see the "issue". Using JSON.stringify to generate the final content does not add any LF at the end. So there is also no LF written out to...