that's as good a time as any 🙂

I was wondering about the same thing. If the functions have changed, you want to transact them, but if they haven't, you don't want to fill up the tx log for no reason. I thought that maybe I should do a custom tx function that fails if the fn body hasn't changed, but then realised how marginal the overhead probably is

Exactly the same thoughts running through my head

if you re-submit the same document it won't take up any more space in the document store, and the addition to the tx-log will essentially be [[:crux.tx/put <20-byte-document-hash>]] - I suspect the custom tx-function will incur more overhead as invocations of the tx-fn do create a new document each time 🙂

"invocations of the tx-fn do create a new document each time" Each tx function invocation is its own document?

yes - we separate out the arguments passed to the tx-fn as a separate document so that there's no chance of personally-identifiable information being in the transaction log

the tx-log can then be completely immutable, even in the presence of evicts