Current Update: Kompendium Community Update: April 2021

You are viewing an older update. There is a newer update available.
Previous Update: Current Update: Kompendium Community Update: April 2021
This is an update for February 2021. Activity described occurred over February, March, and early April.


Infrastructure:
  • Client Libraries: Updates and Maintenance were conducted on the Haskell and Rust Libraries
  • Current Servers: 2 Application-support Servers, 2 Factom Authority Servers, 2 Backup Servers, 1 Factom testnet server, and 2 additional servers (7VMs) for a localized FATd testnet
Personnel:
  • We are currently operating at 2.5 FTE spread across four projects.
    • The part-time FATd developer onboarded to support FAE Bridge development is no longer with Kompendium.
Current Projects:
  • Tasset Mobile: Mobile wallets (iOS & Android) supporting Factom, PegNet, FAT, and Ethereum
    • We recently redesigned app organization and integrated Flutter 2.0 library; with over a year in this project we are eager to get it out to the community.
  • Chainview: Asset Explorer supporting the Factom, PegNet, FAT, and Ethereum
    • Like Tasset, this project was recently redesigned to provide greater flexibility and an ability to more easily incorporate additional features and blockchains in the future. With over a year in this project as well, we are eager to get it out to the community.
  • FAE: Factom <> Ethereum bidirectional bridge connecting the two networks
    • We’ve encountered two significant obstacles which have slowed our progress; we are now late on delivering it to the community.
      • Our assumptions of the state of FATd were not accurate. We’ve spent an enormous amount of time and effort in trying to discover and update unaligned FATd dependencies. FATd used numerous libraries that were forked and customized long ago; however, these were not maintained. The upstream community-maintained libraries from which they were forked have undergone generational modifications and changes and those charges are not easy to rectify. In order to integrate into FATd the advanced smart contract capabilities we designed (FATIPs-109-110) and finalize the bridge, we need to realign these dependencies and/or modify FATd to function with the current upstream maintained libraries that contain the needed state-of-the-art functionalities. We are making our way through them, but progress painful and slow.
      • Second, the part-time developer we onboarded to work on FATd and bridge development has moved on. We have pulled a developer from another project and FAE work continues.
  • Customer Engagement
    • We continue to engage external companies to promote Factom-enabled services.
Future Planning:
  • We have continued design/planning work on multiple future projects
    • We’ve conducted multiple developer interviews for potential future additions
    • Consulting with Cube3 on planned project scope, feature design, and services
 
You are viewing an older update. There is a newer update available.
Top