Peter Broadhurst

Initial finding: In this case, the `pin` being passed into the `attemptContextInit` is the `nonce: 1` pin, not the `nonce: 0` pin. So I need to track back into what...

In the message I can see it's for nonce=1: ```json "pins": [ "80ad901239cc9f914907639fe4e0b19b341a3c03a1da12292f540f8f5fb2859a:0000000000000001" ], ```

There is an earlier message with `nonce:0` so I need to track back to that: ``` [2023-12-11T16:35:30.292Z] DEBUG Assigned pin 'b36848dff6febe7596d8daab9fb220f80165355d2311b2ad485f9e7f7a10e5cb:0000000000000000' to message 5398c6ad-9274-4061-bc35-9b83d0631e2e for topic 'a133547a-d104-46f8-aed2-7911a48d7ae6' d=pinned_private dbtx=wyQUq4Yj ns=org1-ff->mynet...

Ok - the problem here is that we are using different signing addresses for the two messages. The second overtakes the first on-chain - because they are on different signing...

Need to consider what the right answer is to this (code, architectural assurances, programming requirements, or otherwise), given the laws of physics of the blockchain when ordering, and the requirements...

Thanks @chrisbygrave - I think it's worth considering https://github.com/hyperledger/firefly/issues/1450 alongside this when we get an owner, as they're likely to be architecturally in the same place

One thing not on the list, that I'd like your thought on @awrichar: 6. In the case of a `batchOfOne`, if submission fails X times in the retry loop, mark...

Did some 🤔 on the naming independently on prompting from the PR comment on #1261, and came to a pretty identical conclusion.

Confident this is unrelated to https://github.com/hyperledger/firefly/issues/1272, but will look into it under the scope of https://github.com/hyperledger/firefly/pull/1242

@matthew1001 - seems I missed the chance to review. ### Location of the docs I see they got tucked all the way down in the depths of the architecture section,...