Open Future Platform & Airdrop
OPEN FUTURE AIRDROP
- OPEN allows developers to use any wallet
- Through the OmiseGo Wallet SDK, the developer can automatically convert any Scaffold transfer into any cryptocurrency they desire or fiat.
- An ERC20 token that will be distributed in the OPEN TGE and allows for developers to create and operate Scaffolds in the OPEN ecosystem.
The OPEN team has years of experience founding, growing, and developing mobile application companies, but instead of making another hardcode blockchain solution to address the issue of in-app payments, we have decided to create a platform that is designed to facilitate the connection between centralized and decentralized systems.
In a sense, the OPEN platform is the foundation for the first decentralized API for centralized applications. Furthermore, OPEN is designed to make it easy for developers to integrate decentralized technologies into their current technology infrastructure. This is meant to facilitate mainstream adoption of decentralized networks. The OPEN Platform’s ability to port its API abstraction layer to other chains provides every developer the opportunity to port their payment schema to a variety of different platforms to capitalize on the different features within chains.
Presently, there exists no easy solution for application developers to integrate blockchain technologies into their core infrastructure. Infrastructure to accommodate an application’s specific pricing scheme and the ability to determine which users on a decentralized platform have met conditions of a specific pricing scheme, i.e paid or have enough in application currency, are lacking. Specifically, developers require a way in which they can integrate a decentralized payment gateway into their application’s custom payment scheme that is able to accept any cryptocurrency and synchronize such transactions with their existing backend.
Moreover, centralized systems display incredible inefficiencies that can easily be eliminated by incorporating aspects of a decentralized stack. Consider an example when using a centralized system to host or operate an application. Often times, developers must go through a long auditing process by a centralized figure in which every single application update is scrutinized. This results in long backlogs for developers to publish their latest update containing a more efficient data structure or pricing model. Further issues with payment verification gateways exist as the current flow of in-app purchases go through countless processes and third-parties, adding unnecessary time and cost before reaching the developer’s account.
OPEN provides a solution to this problem by utilizing systems of sophisticated smart contracts as transaction and verification tools for software applications. Not only do payments come faster, they come at lower transaction costs with the added benefits of a trustless environment. This enables unique benefits for the application developer and its users.
OPEN has created a blockchain agnostic platform with a comprehensive API structured to specifically create ease of access and integration into pre-existing application infrastructure. The OPEN API abstracts away the complexities of the OPEN platform’s decentralized architecture by introducing an application layer developers can connect to with their existing codebases. This makes it easy for a developer to switch out centralized functions, like a payment gateway or a hosting environment, for functions that utilize OPEN’s decentralized application platform. At the moment, the functionality that OPEN seeks to provide with its platform and API primarily deals with payment gateways. The OPEN API will leverage functionalities already present in external libraries like web3.js and ETHJS to develop a secure way to interact with the blockchain. With this implementation, OPEN will unlock the potential within blockchain technology in order to fundamentally alter the way applications are built, hosted, trusted and monetized.
An OPEN Wallet is the storage unit for the user’s cryptocurrencies (e.g. ETH, BTC, etc.) as well as the OPEN States the user has purchased through the OPEN API. These OPEN States provide payment verification for the user on different applications. The OPEN Wallet provides an intuitive user interface that abstracts away having to learn how a blockchain works, and maintains the same user experience as current centralized implementations.
A developer wallet is the wallet (address) where the Scaffold transfers the funds that the user has sent to it for an OPEN_State (see diagram below). While OPEN allows developers to use any wallet, it is recommended that the developer use the OPENWallet, as it leverages the OmiseGO SDK, which has a built-in decentralized cryptocurrency exchange and great community support. Through the OmiseGo Wallet SDK, the developer can automatically convert any Scaffold transfer into any cryptocurrency they desire or fiat.
An ERC20 token that will be distributed in the OPEN TGE and allows for developers to create and operate Scaffolds in the OPEN ecosystem.
Data stored by both, the user and the database, that is stored through IPFS and referenced by the Scaffold. It stores a cryptographically hashed state of a user on an application Copyright © 2018 OPEN. All rights reserved. 8 (implementations for what the OPEN_State can represent are discussed in the “Future Proofing” section). An application’s current database state at the time of purchase can be made private using a cryptographic hash and then anchored to the blockchain. The OPEN_State will include information to allow for verification that the OPEN_State belongs to the specific user and to a Scaffold. This information includes the user’s OpenWallet address and the Scaffold’s address.
Ref link: http://vy.tc/f5BWy89