# My auditor could read what I said it couldn't. Fixed, and you can test it

**URL:** <https://forum.canton.network/t/my-auditor-could-read-what-i-said-it-couldnt-fixed-and-you-can-test-it/9505>\
**Category:** App Development\
**Created:** [November 15, 2026, 12:11pm UTC](https://forum.canton.network/t/my-auditor-could-read-what-i-said-it-couldnt-fixed-and-you-can-test-it/9505 "2026-11-15T12:11:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![orumedominic](https://avatars.discourse-cdn.com/v4/letter/o/3da27b/32.png) [@orumedominic](https://forum.canton.network/u/orumedominic)\
**Post date:** [November 15, 2026, 12:11pm UTC](https://forum.canton.network/t/my-auditor-could-read-what-i-said-it-couldnt-fixed-and-you-can-test-it/9505/1 "2026-11-15T12:11:20Z")

</div>

My README has said since 19 October that an allowed action stays hidden from the auditor. It did not.

I found this on 14 November. The auditor and the guard were sent the action, its details, and the secret meant to hide them. All of it in plain text. My tests could not catch it, because the Daml Script cannot see what a call is given.

It is fixed. This command shows what the auditor is sent now, and a control proves it would catch a leak:

> <https://github.com/dominicrume/cantor8_kya_rails/blob/b4a5f60170559f1098023b316189f9c9535323af/tools/who_sees_the_attempt_arguments.py>

One thing I cannot solve. Before, finishing an action proved it matched what was promised up front. Now it does not. How would you tie the two together without showing the auditor the secret?

Also built since: a test for Georgi Radev’s point of 27 October and a check for tonozzibeverley953’s topology idea of 13 November.

What is still weak:

> <https://github.com/dominicrume/cantor8_kya_rails/blob/b4a5f60170559f1098023b316189f9c9535323af/docs/threat-model.md>