Omise GO (OMG) tokens white-label E-Wallet platform (ethereum)
OmiseGO Update: Fuseki Milestone and Cash In / Cash Out Details
OmiseGO SDK Closed Beta
Today the OmiseGO SDK has officially moved from alpha into closed beta. This is Fuseki on our roadmap.
As a reminder, the OmiseGO SDK is a code framework on which developers can build wallet applications that will eventually interact with the OmiseGO blockchain.
We are also proud to announce the OmiseGO SDK is in the hands of one of our strategic partners, a huge multinational company that will help us develop one of our first live use cases.
Furthermore, we would like to extend an invitation for keen developers to sign up for our OmiseGO SDK closed beta.
We will be accepting applicants based upon their background and their potential to contribute to helping us get the SDK ready for open beta and then release. We are seeking people to provide feedback on all aspects of the development process: documentation, ease of use of the API, code style, code quality, etc.
If you are interested in participating in our closed beta, please apply here https://goo.gl/forms/8WoL31ccf...
The beta version of the OmiseGO SDK contains:
- A self-deployable OmiseGO API service
- Multiple language bindings for interacting with the API
- Demo iOS and Android app that demonstrates how to integrate the OmiseGO SDK
We plan to work closely with our closed beta invitees to gather feedback and get ready for wider adoption. We expect to support them through the SDK development process and expand our documentation to be more self-serve once we enter open beta.
Our next milestone is Sente which will be a full release of the code in an open beta.
Cash In / Cash Out Details
73% of Southeast Asia is unbanked. That means a majority don’t have access to traditional banking infrastructure such as cards, loans, etc and primarily use fiat money for everything from getting paid to buying groceries.
But, everyone has a smartphone and many companies have started building “e-wallet” apps where one can walk into a convenience store, give the teller cash, and it gets loaded onto a siloed utility app to pay the monthly utility bill.
Another well-known example is the Starbucks app, although dealing with cards, it’s an example of a wallet application that money goes into but cannot get out of besides paying for coffee.
These apps all exist on a “closed loop” payment infrastructure. We want to open up these wallet siloes and have wallets exchange with each other. We believe this will make users happy and increase merchant volume.
Our goal with cash in and cash out touch points is to create a network of banking, hardware, and retail partners where users can deposit and withdraw their cash. The cash becomes tokenized on to their wallet application of choice, and is immediately exchangeable for other tokenized currencies and assets via the OmiseGO blockchain.
With integrated merchant mobile wallets, a decentralized exchange on a blockchain, and finally cash in / cash out touch points this fulfills the final part of our mission to unbank the banked. In addition to servicing the unbanked, what this really provides is an alternative to the current banking system. A free and open financial service network to all people, whether or not they have bank accounts.
Our ambitions are global, we are in active discussions with business partners and unfortunately there is not much we can publicly share. These discussions can take a very long time but rest assured, the talks have been very exciting for everyone involved.
OmiseGO (OMG) Release Omise Python Client Version 0.8.0
OmiseGO (OMG) Release swift v0.11.0: API Resilient (#53)
* Resilient the Charge’s payment property * Resilient the Source Types * Resilient the Currency * Code clean up * Added: Resilient Source Fixture Tests * Added: Resilient Charge Fixture Tests * Remove unused code * Added: Unknown cases * Resilient Schedule * Resilient Bank * Fixed: Throw the wrong error type
ETDA Signed MoU with Omise to Boost the New Government Initiative: National Digital ID Project
After the MoU signing ceremony, ETDA is ready to collaborate with experienced companies in the private sector to facilitate the development of trusted digital identities and digital ID ecosystem in Thailand.
On 19 February 2018, Surangkana Wayuparb, Executive Director of Electronic Transactions Development Agency or ETDA, Ministry of Digital Economy and Society said that ETDA is the primary governmental organization responsible for the development and management of the Federation Proxy. Currently, ETDA have established a cooperative partnership with, Omise, a strong player in the online identification and e-payment service field to initiate the National Digital ID project.
Eight parties have already joined the first phase of this project:
- Revenue Department
- Student Loan Fund
- Thailand Securities Depository Company Limited
- Thai Bankers' Association
- Association of Thai Securities Companies
- The Thai Life Assurance Association
- Thai General Insurance Association
- National Credit Bureau
The Federation Proxy, which is part of the Digital ID Platform, is a component that acts as a bridge for connecting the components in digital ID ecosystem together with an interoperable authentication protocol that is designed to be open-standard and offer strong security for integrating and communicating among different components in an ecosystem.
The three major components in a digital ID architecture are:
1. Identity Provider (IdP)
The party that provides subscriber authenticating services in order to process a transaction or grant access to information or a system. The IdP must ensure service conformity to the standard Levels of Assurance (LoA) for identity proofing and authentication.
2. Relying Party (RP)
An entity that relies upon the digital identity issued by an IdP; therefore, RP should assess their own business risk and choose an appropriate set of IdPs, which can provide assurance level corresponding to result of risk assessment.
3. Authoritative Source
An entity that has access to, or verified copies of, accurate information from an issuing source such that IdP can confirm the validity of the identity evidence supplied by a subscriber during identity proofing.
The National Digital ID Platform is an intermediary and open infrastructurethat provides online service providers (Relaying Party) with standardized ways to identify and authenticate their subscribers or customers using existing digital identifications; and then allow them to access a variety of services remotely. Examples of digital identifications include:
- User accounts on the governmental services, such as the Revenue Department (RD) and The Department of Business Development (DBD)
- Internet Banking accounts
- e-Wallet accounts
OmiseGO Town Hall 0x2: Plasma Edition
On April 4th at 3:00 AM UTC, we will be hosting the second OmiseGO virtual town hall to discuss Plasma.
Check your local time here http://everytimezone.com/#2018-4-4,-540,5yid
With all the buzz around Plasma recently we thought we’d take the chance to chat live with the team working on Plasma.
Speaking will be:
- Robin Clart, CTO
- Jeremy Lam, Product Lead
- David Knott, Research Scientist
In addition to general updates, we will also be taking questions in a Reddit thread like last time.
Please ask your question in this Reddit thread: https://www.reddit.com/r/omise...
We kindly ask you to post every question as a single comment (one question = one comment) and upvote others you’d like to see answered.
Dai and OMG: Uniting for a More Decentralized Tomorrow
OmiseGO and MakerDAO are forming an alliance in our crusade for decentralized finance.
OMG’s currency-agnostic decentralized exchange will allow users the freedom to exchange and manage any digitized asset. However, the volatility of many cryptocurrencies makes them less than ideal as a medium for everyday transactions, in which users want to know that the money they are sending will be worth the same amount when it arrives at its destination.
Stablecoins provide a relatively static benchmark (as static as the currency to which they are pegged) within the volatility of the crypto market. But most stablecoins are centralized, backed by reserves held by private entities whose self-assessment of their own trustworthiness often leaves much to be desired.
Dai, on the other hand, is decentralized, its issuance and value transparently linked to assets held in smart contracts — a system that is better aligned with OMG both philosophically and functionally.
OMG and Dai will be coordinating in two ways going forward:
Dai Stablecoin on OMG network
We’re thrilled to say that Dai will be available on the OMG DEX. OMG network users will have the option to hold, send and trade against Dai from day one, gaining the benefits of a stabilized asset without having to rely on a centralized third party to guarantee its viability. With a decentralized stablecoin held on a decentralized exchange, your funds can’t be lost or revoked due to a single third party’s error, fraud or failure to thrive.
OMG Token as Dai Collateral
The Dai coin’s value is stabilized by collateral — valuable assets held in Maker’s smart contract platform. Dai’s initial release was single-collateral, allowing only Ether to be sent to the CDP (collateralized debt position) contract in exchange for Dai issuance. Maker will soon be releasing multi-collateral Dai, which will allow a variety of assets to be used as collateral for CDP creation. The OMG token will be among the first options offered.
From conception both Maker and OmiseGO have been committed to delivering scalable, highly performant tools for disintermediated finance. We’re very much looking forward to playing a part in each other’s respective upcoming milestones: the OMG DEX will launch with a decentralized stablecoin immediately available as a trading pair, while the inclusion of OMG in Maker’s multi-collateral CDP gives users one more way to put their favorite token to work.
Read Maker’s announcement of this partnership on their blog.
Learn more about Maker and Dai:
OmiseGO (OMG) Release Swift v0.13.1
* Relax the requirement of Store ID and Store Name
* Revise the Optional configuration of the StoreInformation’s properties
OmiseGO (OMG) Update woocommerace v 3.2
• Support multi currency (PR #84🚀 Enhancements
There were some functions that we've removed its interfaces out but some part of its code still remains in the core.
If we don't do cleanup, it may confuse other developers that reading the code and also makes code smelly.
👾 Bug Fixes
OmiseGO (OMG) - April Tech Progress Update
Kasima joins us to facilitate the engineering process of Plasma from research to production is robust, safe and reproducible. He has decades of experience shipping software at a wide range of growth stages, from startup to global scale. He’s excited to BUIDL and ship the network!
Pawel joins the dev team and has been building huge systems for global corporations for as long as he can remember. When Pawel heard about blockchain technologies he realized that its broad adoption will change the world like the Internet did. For now, only his cat can stand his blockchain praises ;)
The eWallet SDK moves closer to reaching the Sente milestone and has many exciting features coming up! This month, the eWallet SDK team worked on:
Redesigning the Admin Panel
Following a retrospective on the current state of the existing admin panel, as well as the addition of awesome new team members, we’ve started a complete redesign in order to provide a better user experience. The eWallet is full of complex features that need to be abstracted from the end user, therefore this is one of the main focus of the eWallet team.
Finalized the Transaction Request Flow
The eWallet already contains everything needed to send transactions between accounts and/or users. Transaction requests allow the creation of “future transactions”, generated in an incomplete state that will be finalized once the recipient (or the sender) consumes it. This feature allows providers to set up some interesting new flows such as payment via QR code scanning, barcode giveaways and easy transfers of tokens between users simply by generating a QR code and scanning it.
First Experiments Integrating the eWallet with the Ethereum Blockchain
We started testing the water by integrating some functionality of the eWallet with the Ethereum blockchain. Our goal for now is to create a simple Proof-of-Concept which includes the generation of accounts on the blockchain and the minting of new ERC-20 tokens.
Refactoring the Android SDK
We received some great feedback on the Android SDK from the community, Yannick Badoual in particular, and decided to do a major refactor. It has now been finalized and we have resumed planned work on the SDK.
Improvements to eWallet and SDKs
We are continuously working on improving the eWallet and the SDKs by fixing bugs and doing small refactors.
Released Docker Images
We saw people requesting access to the Docker images for the eWallet on Reddit and we were happy to comply and upload the images!
We have realized Rocket Chat might not be the best place for finding technical questions and answers. To change that, we set up an OmiseGO tag on StackOverflow. We encourage people to post their questions there and we will do our best to provide helpful answers.
Next for the eWallet SDK
In the coming month, we will be focusing on:
- Finishing the first version of the Admin Panel
- Implementing the Ethereum integration PoC
- Designing an exchange mechanism for the eWallet (internal transactions, external, etc.). More info about this soon!
We are in the final stages of review for the Tesuji Plasma design document. Once this is complete, we will share the design on our GitHub repository!
The blockchain team in Warsaw has been making great progress towards an ‘internal testnet’ release.
The goal of the release is to have an operating child chain server and root chain contract that are both deployable by CI (continuous integration), to an Ethereum testnet and can be used for internal testing purposes.
- Watcher database structure and API to get transactions from the Watcher (done)
- Child chain stops accepting transactions for UTXOs that have been exited (done)
- Deposits on the root chain are tracked and recognized (done)
- Transaction signing (in progress)
- Performance baseline for the the child chain (in progress)
- Detection of invalid exits (in progress)
The research team has been focused on to improving and optimizing the Plasma MVP proof of concept. Highlights include:
- Improving deposit exits and challenges
- Optimizing block submissions on the root chain
- Refactoring the RLP library to be Plasma specific
We are working on the final touches before branching off our reference implementation of the Plasma MVP spec, with some additional improvements.
That paves the way to start research on topics for the Tesuji milestone. Next steps will be focused on benchmarking and optimizing the underlying data structures.
We broke ground on the implementation of Plasma Cash proof of concept, thanks to the Plasma team based in Taiwan. Research is underway on merging and splitting tokens and the use of bloom filters in place of Merkle trees.
We’re continuing to improve our engagement with our developer community. The number of Issues and Pull Requests opened by our community on Plasma MVP is growing! We’re working on improving transparency into our research efforts to encourage more collaboration.
OmiseGO Roadmap Update
We heard your confusion about spoons, timelines, parallel developments and milestones and we’ve done our best to address them here. The visual roadmap above is an overview of what we are building and our progress to date. We’ve been through many iterations of this roadmap graphic since embarking on the quest for clearer communications in response to your feedback.
It is important to note that in the graphic, boxes next to each other do not signify milestones being released simultaneously. Roadmap tracks and milestones are being built in parallel and not necessarily in sequence — and of course, in reality, tracks intersect and milestones interact.
We’ll be updating this roadmap as development progresses, milestones are achieved and new features are introduced to the OMG Network. We will maintain a roadmap repository on Github as well, that developers and others who think in terms of actual workflow may find more useful.
We are continuously evaluating the relative priorities of the milestones. Milestones that are more than one release ahead may be subject to change and as new information becomes available, priorities may also shift. It’s a dynamic, evolving process.
COMPLETED Q2, 2017
OmiseGO raised $25 million in Initial Coin Offering (ICO).
COMPLETED Q3, 2017
5% of total OMG supply was airdropped (automatically deposited) at block height 3988888, to all ETH addresses that had a balance greater than 0.1 ETH.
(Please note that this milestone was COMPLETED in September 2017. Other entities such as exchanges or wallet providers may choose to airdrop OMG to their users, or airdrop other tokens to OMG holders as in the case of the Cosmos DEx spoon; but there are no future airdrops of OMG tokens planned by OmiseGO and anyone claiming otherwise is, without exception, trying to steal from you).
Decentralized Exchange (DEx) Infrastructure
The DEx on the OMG network is back-end infrastructure to allow currency-agnostic asset exchange between all integrated wallets.
While we will continue to keep you updated on the progress of the Cosmos DEx, we will no longer be including milestones related to Honte or the Cosmos DEx on the OMG core roadmap since the timeline of the Cosmos DEx will be largelycontingent on the development of Cosmos itself.
Tendermint DEx (Honte)
Eliminated from OMG roadmap — Spooning to Cosmos DEx
Honte was a Tendermint construction which was being developed to provide sufficient throughput and a proof-of-stake (PoS) for early implementation of the OMG network while Plasma was still in the research phase.
As announced in this post, Plasma progressed more quickly than expected. As a result we decided to stop work on Honte to focus on Plasma. All research and code related to Honte is available on our Github, but please note it is for research purposes only.
Removed from OMG roadmap going forward
The OMG token will be “spooned” soon after the Cosmos hub launch. Put simply, a snapshot of all balances will be taken at a given block height, and every address holding OMG at that time will receive an equal quantity of the Cosmos DEx staking token (not to be confused with ATOMs — the Cosmos DEx will have a separate token). As stated will give at least 2 weeks’ notice before the snapshot.
We will continue to work closely together with the Cosmos team to build a parallel DEx on Cosmos. The Cosmos DEx will use a Tendermint PoS construction, and you can start learning today how staking will work on Cosmos! Join the Cosmos validators room on Riot:https://riot.im/app/#/room/#cosmos_validators:matrix.org
Non-custodial Plasma DEx
In progress — ETA Q4 2018
The implementation of the decentralized exchange is split across two phases.This phase will maintain a centralized service to provide order matching, but users will have custody of their funds with non-custodial order settlement on the OMG Plasma chain. Multiple currencies will be supported, including Eth and ERC20.
Full DEx on Plasma
Upcoming — ETA TBD
In the second phase we will fully decentralize the exchange by moving the order book and order matching into the Plasma chains and decentralizing the order matching process.
Ongoing, features will go to production as they become ready
There are use cases where non-fungible tokens are effective, such as ticketing or unique in-game items. We will ensure that users have a wide range of functionalities with non-fungible tokens (e.g., ERC20s), including:
- Exchange of Non-fungible tokens
- Removal of confirmation messages in Tesuji Plasma
- Recurring payments
- Conditional payments — Where payments are only made when a condition such as a date and time has passed, or when multiple signatures are present
- Order blinding
- Front-running protection
The blockchain track encompasses progress on Plasma scaling, proof-of-stake consensus and integration with the Ethereum blockchain.
Increased complexity comes with increased risk, which is why we’ve chosen to start with the simplest possible consensus mechanism: Proof of Authority (PoA), with OmiseGO as operator. Once we have a battle-tested foundation, we will transition into hybrid Proof of Stake (PoS) and ultimately full PoS.
Though in the majority of PoA chains operators profit from transaction fees, we’ve chosen not to. Our intention is that any profits to OmiseGO from the network will come from staking, in the same way as any other stakers. Transaction fees are necessary in order to deter DDoS attacks (intentional overloading of the network with spam transactions). However, profits from fees during the PoA phase will be used to buy OMG tokens which will then be burned (permanently removed from circulation, resulting in a decrease in total supply).
As mentioned above, standard practice is to provide an ETA for one milestone out. So although we are actively developing the PoS mechanism, we will not be assigning an ETA until our initial PoA implementation is closer to release.
Scalable Blockchain Major Milestones:
DELIVERED Q1 2018
The first Plasma Minimum Viable Product (MVP) technical specification wasannounced in January of 2018. Proof of Concept (PoC) has been created and are being iterated upon.
Plasma Cash is a Plasma construction, first proposed in March 2018, which turns fungible assets into unique “coins” on the root chain. This increases security and usability by:
(i) removing the ability for the operator to print money fraudulently,
(ii) reducing time constraints, and
(iii) only requiring users to watch their own assets as opposed to the entire Plasma chain.
We are creating a Proof of Concept to explore the gritty details of how these improvements can be incorporated into the OMG protocol.
Initial Plasma implementation (Tesuji)
In Progress — ETA Q3 2018
The initial implementation of Plasma will enable:
- Proof-of-authority (PoA) consensus with OmiseGO as operator
- Exit to Ethereum for security
- Command Line Interface (CLI) to monitor the child chain
- Atomic swap support
- Support for Eth and ERC20
This milestone will commence the phase-in of staking. Validators and the operator (OmiseGO) will share the responsibility of creating and validating Plasma chain blocks.
In full Proof of Stake, the operator will be removed and stakers will have full responsibility for block creation and validation.
Application Interface (eWallet SDK)
The free, open source eWallet Software Development Kit (SDK) will allow anyone who needs online asset exchange to connect seamlessly to the OMG Network.
The SDK is constructed in anticipation of iterative enhancements, with many being worked on concurrently. Beyond beta and 1.0 releases, we will put things into production once they become ready, although we have grouped feature categories below for ease of interpretation.
The code for the eWallet SDK may be found in our GitHub.
Aji (cash in/cash out support and access points) is considered a separate milestone as it is not only a question of product design and development but requires collaboration with implementers, partners and Omise’s existing front-end operations.
eWallet SDK Major Milestones:
Fuseki — eWallet SDK Beta
DELIVERED Q1 2018
Fuseki is the first step to onboard users: a working eWallet SDK with basic functionalities.
- A server and client SDK for eWallet providers
- A local database ledger that may be used to issue and make transactions using tokens
- A working demo of a mobile shopping application created using the SDK
Sente — eWallet SDK 1.0 release
In progress — expected Q2 2018
Reaching Sente means that the SDK will be considered production ready, meaning wallet providers can begin to build functional apps with it — although we will continue to add features which will allow wallet providers the flexibility to enhance, add, and customize payment solutions for any number of emerging use cases.
We have begun to incorporate feedback from users on the beta of the eWallet SDK, including a re-designed administrative dashboard and transaction request flow (QR codes) to enable peer-to-peer payments between users. Once these enhancements have been made the SDK will leave the beta phase. As always, it will remain open source and free for anyone to build on.
Additional features under development:
Ongoing, features will go to production as they become ready
- Private contracts (eWallet to eWallet direct communication)
- Finalize exchange design (internal and inter-wallet)
- Ethereum Integration
- Key management
- Custody configuration
- Plasma Integration
Cash in/Cash out (Aji)
In progress — expected Q4 2018
The Aji milestone will bring cash-in/cash-out functionalities via the ewallet SDK plugin. Users will be able to withdraw and deposit fiat in the form of cash, debit or credit to and from their wallets. The Omise Payment Gateway can support debit or credit transactions for partners that have built a wallet using our SDK library.
As Jun outlined in Strategy vol. 02, Omise (the parent company, not OmiseGO) is creating a new subsidiary which will build a network of front-end exchange platforms. This effort will be carried out by a team independent from OmiseGO and will not use any funds from the OMG token sale.
The first step, currently underway, is acquiring centralized exchanges. This network of exchanges will then be used to enhance the OMG network with:
- Support for cash in/cash out from user wallets
- Feed liquidity into the DEx layer on the OMG network
- Generate initial transaction volume for stakers to validate
- Equip the DEx with various capabilities, like order-book matching
The Tengen milestone is the “end game” milestone when the OMG network will be able to support sufficient transactions per second to compete with traditional financial services, have a decentralized exchange with cash-in/cash-out capabilities and interoperability with different blockchains.
We want to thank the community again for your support, particularly those who have actively contributed to advancing research on key components of the OMG Network, and for your patience as we worked to get this roadmap right. We will always welcome your feedback on how to make our communications clearer and more useful to our community.
Stay engaged for further updates as they develop.
OmiseGO (OMG) Update v1.0.2 - Allow the merchant store their information with metadata
Omise GO (OMG) Release PrestaShop v1.7.1
1. FIX ISSUES WITH CREDIT CARD AND INTERNET BANKING PAYMENTS ON PRESTASHOP 1.6
A longstanding bug had gone unnoticed. Some payment methods were not working at all in 'one page checkout' mode on PrestaShop 1.6. This is now fixed
Omise GO (OMG) Release Megneto v1.15
- Upgrade Omise-PHP library to v2.9.1. (PR #147#142)
- Updated internet banking fee message to account for changing bank fees (PR #144#143)
- Applied consistent naming conventions in code for
privateclass members (PR #151 Bug Fixes
- Fixed a CSS issue that was causing internet banking bank logos to not appear with some themes (PR #144)
- Fixed an edge case issue where payments were sometimes recorded against an invoice multiple times (PR #150)
Omise GO (OMG) Release Android App version 2.6.5
Updated comment. * Bumped version to 2.6.5 * Updated CHANGELOG.md * Added changing CreditCardActivity result callback note.