An asset can represent any physical or digital object. It can be a physical object like a car or a house. Or it can be a digital object like a customer order or an air mile. An asset can have one or multiple owners, but it can also be its own owner. Think of an autonomous car or an IoT sensor that does transactions automatically. An asset always contains data that is immutable. In our example, the registration number of a dolphin is immutable data.
Depending on the context, an asset can represent many different things:
An asset as a claim
An asset can represent an ownership claim for a particular object, e.g. it represents a claim that User ABC owns the bicycle with the number XYZ. This can be valid for any type of ownership.
An asset as a digital currency
An asset can also represent a digital currency. omniChain supports divisible assets. This means, multiple assets can be issued and attributed to one overarching asset. This can for instance be interesting for digital currency launches.
An asset as a versioned document
An asset can also be a versioned document with the version stated in the metadata field. The version of this document can be updated on a continuous basis. Every time there is a new version of the document, it could be reflected in the metadata.
An asset as a time series
An asset can also represent a time series of data. For instance, an IoT sensor records its own data. The IoT sensor is the asset and every submission of its data (e.g. temperature) is represented as an update in the metadata with the latest temperature that the IoT sensor measured.
An asset as a state machine
An asset can also be a state machine where the state transition is represented in the metadata. Each time the machine changes its state, a transaction is triggered to update the metadata to the new state (possibility to listen to it with the WebSocket).
An asset as a permission (RBAC)
Assets could also be: roles, users, messages, (and anything which can have multiple instances in a scenario — vehicles, reports, and so on).
Tip: As you can see, there are almost no limits with respect to what an asset can represent.
You can find all your assets under omniChain \ Blockchain Setup \ Assets Definition. You can create a new asset, edit existing definition or choose one of the templates you created or provided by Omnibasis community. Select Create from action menu at the top right corner to create new asset definition.
Edit Asset Definition
Next to the asset name select option drop down and choose Edit to edit an existing asset definition.
Navigate to Info section.
- Give asset class a Name.
- Choose the way you going to collect the data, via Form or Wizard.
- Give an optional Description.
- If you want cross reference assets with asset linking, select Enable parent and child records linking.
- To enable linking across different asset classes, select Enable parent and child records linking across different types and definitions.
- Use Labels to help you to tag the assets definition.
- If you want to reuse this definition in the future, select Mark as a template.
Navigate to Design section to define your asset form. Our easy to use form building where you can define what information do you want to collect about the asset. It is based on WYSIWYG (what you see is what you get) interface and allows completely customize all data fields.
Navigate to Preview section to see what the forms looks like when it will be used to submit or edit an asset.
Navigate to Permission section to configure and secure access to your asset. You can restrict access with the password or with user permission role.
Roll out your own blockchain network, or let us take care of this for you. You can connect your own blockchain database here. You need to define the database first.
- Select Blockchain network if any. If choose no network, default will be used.
- Select Encrypt data if you want to encrypt all submitted data.
- Choose User will be required to enter paraphrase for blockchain transaction - turn on this feature to require paraphrase with asset submission and transfer.
- If you want user to enter the quantity of initial asset, select Allow to enter the quantity.
Decide what happens when your asset is submitted. You can setup notifications via email, SMS, redirect user to a specific page. You can also embed asset submission into any page. Your asset, your users, you decided who you want them to interact with your data on Blockchain.
Mobile Wallet Pass
Navigate to omniPass section to configure mobile wallet integration.
Mobilize your assets. Deliver your assets updates with Mobile Wallet. Power up your Assets information on your customer Mobile phone with personalized updates and messages just in time, based on their location, time of day and more.
- Select Wallet Pass Design to use.
- Map Wallet Pass fields with fields on the pass design.
Once asset is submitted, customer will be prompted to install mobile wallet pass to keep track with updates.