Development

GitHub metrics

Developer activity (from Coinlib.io)

Technical Update

Completed

Here are the main items the team has knocked out since the last update:

Improvements:

Get Account members and keys endpoints #869

Release iOS SDK 1.2.0.beta.1

DB connection pool-sharing across database repositories #853

Detach client API keys from accounts and owner_app #870

Get paginated wallet’s balances endpoints #822

Update Android POS Client Wallet dependencies and refactor #822

Improve Key page style for Admin Panel #867

Bug Fixes:

Fixed an issue with the CORS config #871

Fixed a random test error in WalletControllerTest #872

Fix internal server error on missing filter params #873

Skip settings migration if the settings value has not been changed #874

Fix bug on Android POS Merchant Wallet #46

In review

These tasks have been completed, pending review by eWallet team admins:

Improvements:

Add a few new endpoints to retrieve memberships of accounts/admins/keys #898

Normalize ENV values before saving to settings #875

Add the ability to assign Key to Assign #883

In progress

Research and design of Potterhat, a multi-client Ethereum data service OIP-15

Prevent balance leaks with new permission system #861

You can also follow the progress on the eWallet Waffle board and in GitHub Milestones page.

- eWallet Suite More Resources:

OmiseGO eWallet GitHub repository

Initial public demonstration of the eWallet

​Chat to the eWallet team

Plasm

The past two weeks have largely been spent on closing out a bunch of feature work as well as some clean up. For the feature work, the team has finished up development on:

UTXO management: UTXO stands for Unspent Transaction Output. This is the transaction model they employ in the MVP framework (Bitcoin also uses UTXOs, unlike Ethereum which uses an account/balance scheme). UTXO management in the context of OMG means users are able to combine their various UTXOs without paying any fees. This makes the user experience functionally similar to the account/balance model, significantly improving the usability of the child chain.

Support for an arbitrary data field in the transactions: The arbitrary data field allows transactions to be used for additional purposes than just UTXO transfer. The purpose of this feature is to allow transactions to be applicable to a wider range of use cases.

During this validation phase of their internal alpha testnet, the team has learned a lot about how the system runs over a longer period of time. The team has run into some availability issues related to syncing with geth, the first Ethereum client the team integrated with. They’ve spent a lot of effort refactoring the services to be more fault tolerant of geth crashes and have continued to improve syncing. Additionally, in the interest of consistent availability, they’ve added parity support for their services so that they can work towards redundancy in case one node fails. In pursuit of their commitment to providing their integrators and partners a reliable service, the team will be continuing this resiliency and availability work in the upcoming iterations.

Understanding the Generalized Plasma Architecture by Plasma Group:

Plasma Group recently published an article that describes their new work on a more generalized plasma architecture. This post goes into more detail about the architecture for those who are interested in how things work under the hood. Plasma Group goes over how everything fits together at a high level, then they discusses the sample implementation in Python.

- For more on Plasma, see these community-produced resources:

The OmiseGO Developer Program (ODP) is an initiative that is part of the product development process. The objective of the ODP is to systematically and carefully facilitate usage and thorough testing of Proof-of-Concepts (PoCs) and early stage products in order to gain feedback for improvement. The program is aimed towards those who would like to build their own products, such as games, financial service applications, and education platforms on top of the OMG Network. Applicants of the ODP will fall into the developer category and are willing to work with unpolished and early stage codebase.

Early testers and integrators are given early access to the new products OmiseGO rolls out. Those in the program will also have opportunities to interact with each other and with the engineering team.

The ODP is an ongoing program and applications are accepted on a rolling basis. The goal is for ODP participants to participate as Alpha testers for roll-outs before they are released to the public in Beta. What this means is that there is no real definite timeline or start and end dates.

Sign up for the OmiseGO Developer Program.