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. We’re also continue to work on Blockchain integration for v2.0, which will be our primary focus in the upcoming weeks (sorry, Admin Panel fans!)

Completed

Here are the main items we’ve 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 our progress on the eWallet GitHub project page and on our GitHub Milestones page. If contributing code is your thing, we have 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. We’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.

Best,
The Integration Team

Did this answer your question?