The GramChain transparently digitizes gold, silver, platinum, cobalt, nickel or physical assets stored at reputable storage providers and allows service providers to offer services that require transparent asset collateralization.
The GramChain consist of:
- Custom RFID tags and scanners to record assets, including gold (Storage Provider UI)
- Software to store entries publicly verifiably using immutable blockchain hashes (APIs)
- Software that provides easy access to the public data (Explorer)
- Software to offer services for the assets tracked (ServiceProvider UI) The GramChain provides a very high degree of event transparency, enforces minimum asset quality standards and makes these assets fungible by reducing assets to “pure grams” of the given asset.
- Events are accessible in the Explorer as:
- plain text for public data
- verifiable hashes for sensitive data
- Events are recorded in vaults using RFID scanners which:
- store data and photographs of assets
- are independent of each vault’s IT department
- Events are logged in a public blockchain providing:
- high transparency and immutability
- reliable asset fungibility (grams)
- asset use via service providers
API Interface Groupings
- DropDownValues API (https://GramChain-test.littlebit.sg/API/DropDownValues//) Provide dropdowns values used by the application. Load once on start for scanner and apps.
- Public API (https://GramChain-test.littlebit.sg/API/public/ ) Retrieves GramChain records, either individual bar records, histories, lists or summary information.
- Secured APIs (https://GramChain-test.littlebit.sg/API/secured/) APIs used to write to the GramChain and other sensitive operations such as login. These need to be secured and will not be made available to the public.
Most APIs require 3 default parameters as follows:
languageid = this field is a two-character support for simple multi-language. Default value is 'en' for English, 'cn' for Chinese. An empty string will return all available languages.
entityID = a field for future use which allows for different results to be returned based on caller entity, currently this field can be left blank.
callerid = the userID calling this API. This allows for an audit trail of data access.