White label platform
Use your own branding and customer interface. RubySDK provides the asset tokenisation, holder register and smart contracts.
Choose which assets to tokenise, approve participants and set their permissions.
Platform functions
The software covers asset setup, holder permissions, transfers and the records needed to manage them.
Create asset tokens
Define the asset, the quantity represented and the number of tokens. Set who may create them and change their details.
Manage holders
Maintain a register of approved participants. Add or remove permissions to hold and receive an asset’s tokens.
Control transfers
Apply the project’s rules when a holder requests a transfer. Check the recipient’s permissions and any required approvals.
Attach documents
Connect certificates, condition reports and other evidence to the relevant asset. Set who may read or update each document.
Record redemption
Record when tokens are returned in exchange for the asset. Connect that request to the operator’s approval and delivery process.
Receive updates
Notify the application when a contract records a change. Use those updates in customer accounts, operating records and reports.
Use cases
A watch dealer’s customer platform
Connect each watch to its serial number, service history and condition report. Record its holder and apply approval rules when it changes hands.
A wine merchant’s stored inventory
Represent bottles, cases or lots held in storage. Let approved customers transfer their holdings or request collection through the merchant’s application.
A platform for physical commodities
Represent defined quantities of a recorded batch. Link the records to certificates, inspections and delivery requests, with quantities checked against the supporting stock records.
An art or collectibles platform
Link an object to its history, condition and ownership documents. Give approved participants access to the evidence and record changes of holder.
How the smart contracts work
A smart contract is a program on a blockchain. It applies the rules for creating, holding and transferring an asset’s tokens.
For example, a transfer request can be rejected if the recipient is not on the approved holder list. Required approvals must be recorded before the change proceeds.
The accepted change updates the holder record. The application can then display the result and notify the relevant users.
Privacy
Owners should not have to publish their holdings or transaction history to use the platform. RubySDK’s emphasis is on protecting those details in the underlying system, not just hiding them in the application.
Access can differ by role. A buyer may need an asset’s condition report, while a storage provider needs release instructions. Neither needs the full owner register.
The network and encryption are selected against these requirements. Owner identities, holdings and transfers need protection, as do documents and the information sent to connected systems.