Introduction
System addons extend your tokenized assets with advanced capabilities like atomic settlements, yield management, and automated distributions. Learn how platform administrators discover and install addons from the on-chain Directory registry.
System addons are optional modules that extend the functionality of your tokenized assets. Each addon provides specialized capabilities that work alongside your core asset operations.
Available addons
The platform automatically discovers available addons from the on-chain Directory registry. This means the addon list is always up-to-date—no manual configuration required. When new addon types are registered to the Directory, they automatically appear in your Add-ons settings.
| Addon | Purpose | Common use cases |
|---|---|---|
| XvP Settlement | Atomic multi-party asset exchanges | Bond-for-cash trades, currency swaps, cross-chain transfers |
| Yield Schedule | Automated distribution of returns | Bond coupons, dividend payments, interest distributions |
| Vault | Multi-signature treasury control | DAO treasuries, corporate custody, maker-checker workflows |
| Airdrop | Token distribution | Community rewards, team vesting, acquisition swaps |
| Feeds | On-chain data feeds with issuer-signed updates | Price feeds, NAV reporting, oracle data |
Feeds: API-only
The Feeds addon does not have a UI workflow. Manage feeds through the API. See the Feeds developer guide for details.
How addon discovery works
Addons are registered in the system's on-chain Directory. The platform queries this registry to build the list of available addons. This approach ensures:
- Always current: New addon types become available automatically when registered to the Directory
- Consistent: All environments use the same addon list from their respective Directory
- Extensible: Platform operators can add new addon types without code changes
When you access the Add-ons settings page, the platform fetches the current list of registered addon types from the Directory. Any addon type listed in the Directory appears as available for installation.
How addons work
Addons are deployed as separate smart contracts registered in the system's addon registry. They operate independently of individual assets, providing platform-wide capabilities that any authorized user can use for their tokenized assets.
Each addon:
- Is registered once at the system level by platform administrators
- Operates independently of other addons
- Has its own role-based access controls
- Provides both UI workflows and API access
- Records all operations on-chain for auditability
Addon deployment vs. instances
System-level deployment (administrators):
- Enables an addon for the entire platform
- Done during initial setup or via platform settings
- Example: "Deploy XvP Settlement addon"
Creating instances (authorized users):
- After deployment, users create specific addon instances for their needs
- Examples: "Create a yield schedule for this bond", "Create an XvP settlement between these parties"
- Each instance operates independently with its own configuration
Enabling addons
Addons are configured at the system level by platform administrators. Once enabled, authorized users can access addon features through the platform UI or API.
To install an addon:
- Go to Settings > Add-ons
- Browse available addons from the Directory registry
- Click Install on the addon you need
- Configure the addon for your organization
You can also install addons during the onboarding wizard when setting up a new asset.
Administrator access
Contact your platform administrator to enable addons for your organization.