- Update how handle risks of outcalls to possibly untrusted canisters.
- Update how to handle traps.
- Add journaling section

…ces.md

Reference the GoldDAO/gldt-swap implementation as an example of journaling.

…y-best-practices.md


Accept Robin's suggestion to fix a typo in the text he wrote.

Co-authored-by: Robin Künzler <[email protected]>

…curity-best-practices.md


Lower the section level of Journaling.

Co-authored-by: Robin Künzler <[email protected]>

Old link was to a branch that had the underlying commit changed. The new tag link is fixed to a commit as long as normal version tag conventions are followed by the project.

…ing in recovery

Apply guaranteed message ordering to simplify example recovery process.

…gers

Emphasize manual recovery. This is because ICP ledger and ICRC ledgers make it difficult to determine whether a particular transaction has succeeded in an automated way.

Add another note on encouraging manual recovery when finding out the result of a call is difficult to automate.

Co-authored-by: Robin Künzler <[email protected]>

Add details on idempotent retries for task flows.

Give more context for journal example structures and flows and clarify the examples.

Fix missing text in callback cleanup section.

Co-authored-by: Roel Storms <[email protected]>

Add clarification that results may be lost if a trap occurs AND there is no self-call to commit it.

Co-authored-by: oggy-dfin <[email protected]>

Co-authored-by: Roel Storms <[email protected]>

Co-authored-by: Roel Storms <[email protected]>

Suggestion from @roelstorms.

Co-authored-by: Roel Storms <[email protected]>

Suggestion from @oggy-dfin.

Co-authored-by: Robin Künzler <[email protected]>

Suggestion from @roelstorms.

Co-authored-by: Roel Storms <[email protected]>

Suggestion from @roelstorms.

Co-authored-by: Roel Storms <[email protected]>

Add uniqueness requirement for transaction hash.

Remove section `Example journaling structures and flows`. Readers should refer to GoldDAO example instead.