Development

GitHub metrics:

Developer activity (from Coinlib.io):

Are you ready to upgrade to Samrong?

v0.2 of the OMG Network is now accessible to all!

OmiseGo team has moved on to the next station with the release of the Public Alpha of Samrong. This hard network upgrade required their partners and ODP participants to migrate their tokens from Ari on to the second version of the OmiseGO Network.

This upgrade requires a change to the immutable smart contract on Ari. For this reason, Samrong will eventually replace Ari entirely. If you wish to continue using the OmiseGO Network, you will need to move your Rinkeby ETH (Ethereum) and ERC20 from Ari to Samrong.

Why upgrade?

Samrong includes a number of significant modifications:

Improved Plasma integration and changes to Plasma smart contracts

Ari launched with Minimum Viable Plasma. Samrong builds on Ari’s Minimum Viable Plasma, and runs on More Viable Plasma (MoreVP). Samrong’s Plasma smart contract will thus be MoreVP compliant, but since the written smart contract can’t be modified, Samrong is implemented as a new, separate network, and will replace Ari.

Greater resilience, less downtime

Samrong’s improved monitoring, reliability, and stability is better at handling high network loads.

New transaction signature using EIP 712

Samrong allows you to sign transactions using the EIP-712 standard, which allows signatures to be carried out through wallet integrations, such as Metamask. EIP-712 also allows Ethereum signatures to display in a structured and readable format.

Meta-data field

A new meta-data field allows users or dApps to store any information in their transactions.

Join the ODP and connect to the latest iteration the OmiseGO Network here.

Technical Update

eWallet

In the past few weeks, the OmiseGO Integration Team has been working on delivering everyone’s favorite Admin Panel updates as well as improving account security with Two Factor Authentication for v1.3. They’re also continue to work on Blockchain integration for v2.0, which will be their primary focus in the upcoming weeks.

Completed

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

v1.3

Fix pagination filter for some fields #1066

Implement transaction request cancel #1044

Fix transaction consumption confirmation #1054

Fix internal server error when providing an association as the filter param #1052

User detail page improvement #1049

Wallet detail page improvement #1058

Implement authentication token expiration configuration #1057

Implement Two Factor Authentication #1065 #1068

v2.0

Implement programming interface in preparation for Ethereum transaction #1028

In progress

These tasks are currently being worked on, or are pending review by OmiseGO Integration Team members:

v1.3

Advanced filtering on all overview pages #1064

v2.0

API endpoints for Blockchain transactions

Update tokens to integrate Ethereum compatibility

Secure private key storage with Shamir’s Secret Sharding

As always, you can also follow their progress on the eWallet GitHub project page and on OmiseGo GitHub Milestones page. If contributing code is your thing, the team has a list of issues suitable for first-time contributors. Be sure to check out!

Potterhat

In addition to eWallet Admin Panel updates, OmiseGO Integration Team has also been working on Potterhat, a Blockchain API orchestrator, to improve the reliability of Blockchain API in general. They’re also looking to normalizing API difference of Geth and Parity to be based on EIP-1474.

Completed

Node event listener and logger #20

In progress

CI pipeline #24

You can track Potterhat milestone and progress on the Potterhat repository and read more about it (or add some ideas and make suggestions) on OIP-15.

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26

- eWallet Suite More Resources:

OmiseGO eWallet GitHub repository

Initial public demonstration of the eWallet

​Chat to the eWallet team

Plasma

The production team has been looking at some optimizations this past cycle to improve their resource usage and reliability. Since they started backing the Samrong child chain and watcher with Parity instead of geth, they’ve seen better reliability and needed to do significantly less wrestling to keep things running. However, they were still seeing high resource usage and spent some time reducing the number of RPC calls they make to Parity to see if that would change Parity’s memory footprint. The team continues to work to improve the metrics and monitoring so that they meet production service standards while operating in PoA. The team believes this is critical as they onboard potential projects to use the plasma chain. The team believes that availability is a required feature to projects that are serious about trying to integrate to the OMG Network.

This cycle, OmiseGo team will be putting their availability and reliability work to the test while they prepare the Plasma Dog Arena event that Hoard will be hosting this month. They’ll set up a test environment to conduct a stress test and see how much load they can throw at it. More details on this will be available in coming weeks.

The team has also broken ground on the plasma abstract contracts implementation. If you recall from my How’s OmiseGOing? post, this contract architecture will allow them to perform opt-in feature upgrades without requiring all of their users to exit and re-deposit into a new chain, as they’re doing now with the Ari to Samrong hard network upgrade. This will provide a significantly improved user experience while enabling them to more easily add features in a trustless manner.

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22

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