AT : Rust & TS Examples#242
Merged
itsyaasir merged 27 commits intofeat/audit-trails-devfrom Apr 13, 2026
Merged
Conversation
…ties` sections Both sections need to be reviewed though
…nd-docs' into feat/audit-trails-dev-examples-and-docs
…ng Revoked Capabilities` sections
chrisgitiota
reviewed
Apr 9, 2026
chrisgitiota
reviewed
Apr 9, 2026
chrisgitiota
reviewed
Apr 9, 2026
chrisgitiota
reviewed
Apr 9, 2026
chrisgitiota
reviewed
Apr 9, 2026
chrisgitiota
reviewed
Apr 9, 2026
Contributor
There was a problem hiding this comment.
As I have very little knowledge regarding customs-clearance processes, I have been struggling to understand which purpose the different roles in this example have.
Would be awesome to have an explanation of the involved actors/roles.
Did some research on this but still have no clue what i.e. the Docs operator is.
chrisgitiota
reviewed
Apr 9, 2026
| npm run example:node -- 01_create_trail | ||
| npm run example:node -- 01_create_audit_trail | ||
| ``` | ||
|
|
Contributor
There was a problem hiding this comment.
We could also add a section for localnet users here:
Using `locanet`, the publish script prints the required `export` statements, so use `eval` to set the variables in one step:
```bash
// In the `bindings/wasm/audit_trail_wasm/examples` folder
eval $(../../../audit-trail-move/scripts/publish_package.sh)
npm run example:node -- 01_create_audit_trail
```
chrisgitiota
reviewed
Apr 9, 2026
| .output; | ||
|
|
||
| let trail = client.trail(created.trail_id); | ||
| let records = trail.records(); |
Contributor
There was a problem hiding this comment.
Defining accessor variables (like records, role, trailHandle, ...) should be done as late as possible (ALAP). Otherwise the definition of those accessor variables will be not known in the example snippets of the wiki docs that reference this example code.
- Introduce named actor clients across all audit trail examples so each client signs with its own key and capabilities are bound to specific addresses (issued_to) rather than left unrestricted - Add //! ## Actors module-level doc to every example describing each actor's role and permissions - Refactor 01_customs_clearance and 02_clinical_trial to use fully distinct clients per operational role (DocsOperator, ExportBroker, Inspector, Monitor, DataSafetyBoard, etc.) - Replace plain-text document data with SHA-256 hash in customs clearance; add comment about off-chain TWIN node storage - Add section-title comments to customs clearance for easier navigation - Add capability auto-lookup comment to 09_tagged_records - Move records accessor definition ALAP in 06_delete_records - Add localnet eval-based quickstart section to WASM examples README
…amples Each actor now uses its own funded client with a distinct keypair, so capability objects are bound to per-actor addresses and the Move-level access-control is exercised as intended. All examples have structured JSDoc ## Actors sections. The issueTaggedRecordRole helper accepts an explicit issuedTo address parameter.
…t-trail-explicit-capability-selection
Node's crypto.createHash is not available in the browser. The Web Crypto API (crypto.subtle.digest) works in both environments.
…ability-selection feat: add explicit audit trail capability selection
chrisgitiota
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of change
Links to any relevant issues
Type of change
How the change has been tested
Change checklist