APIS Expanded #2 Smart Contract on Canvas Re-explained

Hello, dear APIS supporters!

We would like to give you some information are unique “ Mineral System”

As bitcoin’s simple script is evolving into smart contract with Ethereum, the use of cryptocurrency is also expanding into various areas including ICO funding, token issuance, identity verification, and cloud storage service.

However, most “smart contracts” are not so smart; they are heavily developer focused and often neglect much needed user interface for everyday users. As a result, deployed smart contracts are hardly user friendly, if usable at all.

Smart contract end-users are also forced to utilize the user interface provided by the core program of the respective cryptocurrency or web-based application, so a smart contract may have more than one correct use case, which could further confuse its already perplexed users. As a result, users often have to refer to technical manual for the smart contract they are using or get help from experienced individuals. This is counterintuitive to the whole concept of smart contract, which is to make cryptocurrency accessible to many users.

APIS plans to solve this problem by implementing so-called “smart contract on canvas.”

Smart Contract made smarter

Developers can register UI elements(the canvas)written in HTML when they deploy their coded smart contract on the blockchain. Canvas consists of a single HTML file and can include CSS, javascript, and image. Javascript code included in the contract can be obfuscated, but it is recommended that obfuscation is not conducted in order to provide transparent data processing mechanism to the contract users. Image files can be registered to the document through Base64 encoding. SmartContracts element implemented in javascript can be called within a canvas.

The HTML file that functions as canvas cannot be saved on the blockchain, so developers must provide an environment in which canvas files can be accessed through web addresses. Theses addresses could be allocated through creation of CanvasLocation variable within the smart contract. In addition, the entire canvas code must be hashed with SHA-256 and saved on the CanvasHash variable in its respective smart contract to prevent secretive, unannounced changes. Through these measures, applications can decide on the existence of a canvas, organized a GUI, and verify immutability of the canvas used.

Thank you.

APIS team