Overview
Asset Tokenization Studio packages regulated-asset workflows — identity registry integrations, partition strategies reminiscent of ERC-1400, and investor onboarding UX — atop Hedera (ATS docs).
When to use this skill
- Launching regulated instruments where raw HTS keys alone are insufficient UX.
- Coordinating corporate actions (dividends, splits, ballots).
Prerequisites
- Infrastructure for hosting ATS components per upstream README (Kubernetes/Docker compose evolve — verify version).
Workflow
Install ATS stack — follow GitHub release referenced from docs.
Configure identity registry connectors — align with your KYC provider.
Model partitions / restrictions — consult references/ats-architecture.md.
Compare vs raw HTS (references/ats-vs-hts-keys.md).
Corporate actions — see references/corporate-actions.md.
Bootstrap transcript: scripts/bootstrap-ats.md.
Examples
Example 1
“Issue regulated equity on Hedera.”
ATS path vs bespoke ERC-3643 deployment — decide based on maintenance bandwidth.
Example 2
“Need shareholder vote.”
Use ATS corporate action modules if version supports; else schedule dedicated vote contracts.
Example 3
“Integrate Salesforce CRM for accredited investors.”
Build webhook bridge → ATS onboarding API — specifics depend on deployment edition.
Troubleshooting
| Issue | Tip |
|---|---|
| Docs mismatch | Pin Git tag |
References
- Local: references/ats-architecture.md, references/ats-vs-hts-keys.md, references/corporate-actions.md