July 2021 Community Update

Previous Updates
This is Kompendium’s first ANO Community Update for August, covering from late-May to 31 July.

Following our selection as an ANO (running at 60% efficiency) in late-May, Kompendium diligently set out on two primary tasks. The first effort was to stand up all-things corporate matters. The second effort, in parallel, was to set up our Mainnet node infrastructure. In early June we hired a tax consultant and set up Kompendium, which the US government will treat as a C-Corp. In the end, we chose to incorporate in Nevada vice Washington state due to more favorable tax treatment and flexibility. In addition to incorporating, we set up all corporate banking accounts, cryptocurrency exchange accounts, set up our company accounting system, and a tax cryptocurrency tracking system.

Setting up our node infrastructure was more complicated than expected. As was detailed in our campaign document, we opted to use three providers across four datacenters to best manage security and contingency risks. However, we discovered that dedicated and virtualized servers across different providers vary widely in how they are set up and partitioned. A good bit of time was required to standardize system administration (set up, monitoring methods, alert methods, and access/security protocols). We have had some issues with the reliability of one of the dedicated servers/providers and expect to switch provider in August.

Kompendium’s Testnet role has been more limited than desired over this reporting period. We hoped to get through a good deal of revamping Testnet governance, but this was delayed. The Testnet continues to have limited participation and is underutilized. We continue to endorse a realignment of the Testnet closer to the Mainnet and to revitalize participation and interest. We are working closely with Luciap’s ChockaBlock (https://chocka.luciap.ca/) to support additional feedback on Testnet load testing performance for the monthly updates. The July update will be released on 1 August.

We spent a good amount of time designing and getting our website completed (www.kompendium.co). Kompendium also participated in all Factom Protocol Governance votes and many community discussions.

Since being elected, Kompendium has pursued two major operational focuses, PegNet development and partnership scouting. We have met with multiple organizations in an effort to identify potential partners to expand Kompendium’s capacity to provide value to the Community. We have ambitious plans for the Protocol and we feel we need additional capacity to make our plans viable and a reality. We intend to aggressively pursue this line of effort over the coming months with the goal of securing additional capacity prior to the 2019 fourth quarter Factom Protocol grant round.

We have also been one of the dedicated ANO volunteering daily to work on PegNet. We feel PegNet has tremendous technical, economic, and marketing value for the Protocol. PegNet potentially offers us more opportunities to show the unique and innovative way that the Factom Protocol continues to stand out and lead the pack.

Kompendium is eager to continue to get business operations up to speed, work out our processes, and bring value to the Protocol, the Community, and beyond.
This is Kompendium’s monthly Community Update for September, covering activity in August.

Infrastructure: We refined and improved the management of our node infrastructure. We added log parsing/monitoring tools, refined our infrastructure visualization dashboards, and added PagerDuty to reinforce our notification alert system.

Advocacy: Following our failed Blockchain Industry Group (BIG) grant proposal, we decided to purchase a BIG membership at the individual level for our own team. Although it is a lower tier membership, we will work to find opportunities and take advantage of this network for the betterment of the community and protocol.

Personnel: As previously announced, Sergey Bushnyak joined Kompendium. Sergey has been a tremendous addition to the team adding new energy, experiences, and an expansive skill set. He has rounded out our team nicely and, with our current group, we are in an even better position to bring value to the community.

PegNet: For the latter half of August, Mitchell took a personal vacation and a short break from his PegNet development activities. Refreshed and tanned, expect him to return to making contributions wherever needed.

Grant Work: We have begun working on our approved grant and are enhancing the Factom Rust Client Library. We are thinking through strategies to maximize its exposure to external Rust developer communities to entice greater usage and expand the adoption of the protocol—more to follow on this effort!

Haskell Client Library: We are building a Factom Protocol Haskell client library to facilitate several additional initiatives we are researching, planning, and/or developing. As an initial means to test out the library, we are exploring building out a couple network observation applications—stay tuned.

Independent Research Initiative1: We are conducting independent research on current Smart Contract (SC) implementations on Factom and across several other blockchain platforms. We are also researching development plans for an end-to-end advanced SC Development Suite (i.e., an enhanced IDE). Research areas for SC include high-level SC languages, execution environments (EV), and the potential utility of creating a new “intermediate notation” language for connecting SC to EV–we’re calling it SCIN for now.

Kompendium will use insights from this research, to support a major development initiative, creating a novel SC ecosystem that will include a formally verified core; tools for static analysis; and a set of templates, solutions, and libraries to enable an intermediate and highly secure implementation of SCs. Currently we are working on a standalone server system that allows integration with any IDE by connecting through an API and providing all required development functionality out of the box.

Additional expected design features will allow developers to create or import SCs in their preferred SC language (e.g., Solidity, WASM, etc.) and then the choice to deploy it to one of several blockchain platforms (ETH, FCT, EOS, etc.). Developers will also be able to determine the accurate cost of deploying their SC across these blockchain platform options. With superior tools, capabilities, and lower costs, we envision this enhanced IDE being a vehicle to provide superior tech to developers across the industry as well as a venue to entice developers presently on other platforms (Ethereum, Cardano, Tezos, EOS, etc.) to shift their development and application/SC deployments to Factom. Much more on this to come, but we are super-excited about the potential value this project could provide to grow the protocol and are happy to at least the community know what is in-store for the future–a platform with best-in-class tools showcasing the protocol and making it easier than ever to leverage the power and potential of Factom.

Independent Research Initiative2. Development of Zero-Knowledge Proofs (ZKP) for the Factom Ecosystem. We have already started research and are conducting preliminary building of an implementation of ZKP on the Factom ecosystem in the form of a library. If the community supports it, in 2020 we will design and develop a tailored, potentially novel implementation of ZKP as a security layer on top of the Factom protocol for Factom/3rd party use. Our initial work on a ZKP implementation will include all required primitives to allow further extension of ZKP as well as the operation of use-case specific algorithms, which the community can help guide.

Q4 Grant Round: We are also reviewing additional projects for the next grant round.

Please monitor Kompendium’s company blog and other Factom Protocol community announcement forums for future Kompendium developments and updates.

Thanks for reading and your support
This is Kompendium’s October Community Update (covering activity in September).

We remain a high-efficiency ANO at 60% efficiency, and are conducting aggressive development work for the community – which to support we are entirely reliant on community grants.


Infrastructure: Our team services have been improved, including expanding out our website features (non-public functionalities), and streamlining how we organize and manage our affairs. It’s a slow and methodical process, but it pays significant dividends in meeting objectives and communication. We have also improved our node infrastructure by swapping out the providers for one of our Mainnet nodes.

Advocacy: Mitchell started a PEGNET Meetup Chapter in Australia.

Personnel: We continue to aggressively seek out and identify additional talent to expand our four-person team. We have multiple projects that we intend to submit as grant proposals in the upcoming rounds, which will require additional developers to support.

Testnet: We continue to advance the number and capability of the Testnet webscraping and data analytics algorithms for community reporting. Please let us know what data or statistics you would like to see so we can refine the monthly report. Reach out to @[Kompendium] Andy Young with any feedback.


PEGNET: We provide continued technical support in developing PegNet.

Development of Factom Client Libraries-Backpay Grant 1: We are expanding the number of client libraries available for the Factom protocol: we’re currently developing remote procedure call clients in PHP, Swift, Ruby, and Haskell. We aim to complete all clients prior to the next grant round in November submit them as a back-pay grant. We believe this work is foundational in providing the tools to grow the community and expand its use and application. Note: once finished in November, Kompendium will have built five of the community’s ten client libraries for the protocol!

Development and Expansions of OpenAPI – Possible Backpay Grant 2: We have built an Open API client library in Haskell that allows automatic generation of clients in other programming languages and adds a type-safe layer for the Open API server. We examining options to expand Open API with additional functionality by implementing more REST endpoints that will be useful for enterprise solutions and provide easier integration for web applications.

Development of a Factom/FAT/PEGNET Explorer: Kompendium is in the early stages of developing a universal Factom explorer that functions with Factom and PegNet. We are examining options for FAT integration as well; altogether the explorer will provide newcomers a deeper ability to understand the Factom Protocol network. More to follow.

Zero-Knowledge Proof Research (ZKP) – ZKP Capability on Factom - Backpay Grant 3: We are researching implementation possibilities of Zero-knowledge Proofs, algorithms to make ZKPs functional on Factom. We expect to produce a research paper and an operational library to enable ZKP on Factom that we will make available to the community and seek out a back-pay grant. As part of the research document, we aim to provide a proposal and development road map for native integration of ZKP as a security layer on top of Factom as a Kompendium future project for 2020.

Enhanced Integrated Development Environment (IDE) and End-to-End Developer Tool Suite - (Planned Q4 Grant Proposal): We continue to research and design a smart contract intermediate notation (SCIN) solution that will enable core functionality and define the foundational blocks of what we believe will be a “best in class” IDE for smart-contract development. We believe that SCIN and the enhanced IDE will provide a game-changing ecosystem for developers and will have the ultimate effect of attracting many current developers on other chains such as Ethereum, EOS, Tezos, Cardano, etc. to instead develop and deploy their programs onto the Factom protocol.

For the latest updates, monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s November Community Update (covering activity in October)

Infrastructure: We continue to work through internal infrastructure improvements with the implementation of NextCloud and a number of other service s- the process will likely be enduring as we grow and mature as an organization.

Advocacy: We drafted an article to announce the development of our JSON-rpc Libraries. We intend to coordinate with the marketing committee to ensure the value of these fantastic new client libraries are maximized for community benefit and we can attract as many new developer communities as possible to the Factom ecosystem.

Personnel/Business Relationships: We continue to aggressively seek out and identify additional talent to expand our team. We further developed two business relationships that will allow Kompendium to significantly expand our capacity to take on greater numbers of projects and more complex initiatives.

Testnet: We celebrated the release of the revitalized testnet governance document– thank you for the efforts put into ensuring the testnet remains an integral part of our community.

PegNet: We continue to run dozens of PegNet miners. We have been busy researching and refining our grant proposal to develop a cross-platform, multi-token PegNet/Factom/FAT mobile wallet solution. We hope the community is as excited as we are about this project, and the positive impact we assess it will have for the ecosystem.

Development of Factom Client Libraries-Backpay Grant: We have been working fervently to finalize four new JSON-rpc client libraries for the Factom protocol. We aim to release these libraries prior to the conclusion of the fourth quarter grant round starting on 04 November. These powerful new clients are for PHP, Swift, Ruby, and Haskell, and we believe these libraries will open the door to a far greater number of very active developer communities, and make the Factom protocol more accessible than ever before. We also believe this work is foundational in providing the tools to grow the community and expand its use and application. Note: once finished, Kompendium will have built five of the community’s ten rpc client libraries for the protocol!

Quarter three, 2019, Grant – Rust Client Library
: We decided to pause the public release of the Rust client library—likely early to mid-November—to await the Rust Community’s 1.39 release, which is expected on 07 November. Announcement Link: https://blog.rust-lang.org/2019/09/30/Async-await-hits-beta.html While we recognize the importance of meeting the pledged grant timeline, we decided a short delay would ultimately be to the community’s benefit to ensure we provide a stable and optimized library for the latest Rust release.

A note: while the market value of FCT has recently contracted significantly to 52wk lows, we at Kompendium continue to aggressively develop and plan significant projects to expand the attractiveness and functionality of the Factom protocol. We are very excited about the direction of the Factom protocol and are eager to refine our proposals and begin work on some of our ideas that we hope will propel Factom to new heights.

For the latest updates, monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s January Community Update (covering activity in November and December 2019)

General Activities and Efficiency Update: Kompendium has been extremely active in further developing half a dozen public libraries for the Factom community during the past four months, and during some weeks we have been working on a near full-time status on development work. In a review of the full scope of work we have conducted for the benefit of the Community in the past six months since our election as an ANO, we are formally transitioning status from an infrastructure ANO to a full developer ANO. This should come as no surprise as we have arguably developed and delivered more tangible assets for the benefit of the community than any other ANO during this period. As a full Developer ANO with two very active developers and several project contract developers, we are reducing our efficiency rate to 15% to support our community-benefiting development work. We are really excited about the projects we have under development and hope the community celebrates their release as they as come to completion.

Governance: We participated in nearly every governance discussion and were active in all voting matters. We also proposed governance-related changes during this period: Extending the grant Discussion Period to allow for greater care in selecting grants that align with producing longterm value for the community.

Testnet: In December we reduced the number of testnet nodes (Testnet Auth Servers) from two to one.


PegNet: We continue to be very active in the development of community-benefiting assets relating to PegNet.

1) PegNet Open Node: We are happy to announce the creation of pegnetd.com! This is an Open Node (PegNet) service set up to support PegNet community initiatives. The current version is in BETA and we continue to work to refine and improve this valuable community service.

3) PegTX: An accounting tool that can export transaction data for PegNet traders, miners, and users. This utilizes the open node out of the box, so batteries included. Anyone can download it, put in an address, and get a big list of their data in csv form.

2) RUST PegNet Client Library: We have created and released to the community a PegNet Client Library for Rust.

3) General PegNet DEV work: Mitchell continued PegNet work with a Minor contribution on travis CI

We have several other PegNet-associated initiatives under development. For those that have been asking about the awesome universal mobile Wallet (FCT, EC, PegNet Assets, FAT Assets) we proposed during the last grant round, we have currently suspended work on that effort due to it not being funded. BUT we continue to believe that such a cutting-edge wallet would be a game-changer for FAT/FCT/and PegNet. We intend to again offer the community a low-cost development proposal for the creation of the technology to make such a wallet possible next grant round.


We worked with the Factom Marketing Committee and the community-hired PR firm to draft an article announcing the completion of Kompendium’s five new JSON-rpc full client libraries for the Factom Protocol, as well as our work furthering the Factom Open API initiative. The draft article will be released shortly as will the finished rpc client libraries. We also intend in the future to break up the article into smaller news updates to allow for tailored advertising to the specific, very active developer communities that the client libraries are meant to attract and open the door to the Factom protocol.

In November and December, we delivered the following value to the Community:

1) Full RUST rpc Client Library - (DEC) The RUST Client was entirely redone at a below-market-rate grant for the community’s benefit. We believe it is one of the most powerful clients built for the community to date. Check out all the features. It’s a fantastic client for an extremely effective and powerful language.

2) RUST PegNet Client Library - (DEC) A PegNet library for one of the fastest-growing power languages.

3) PegNet Open Node (pegnetd.com) - (DEC) A universally available, load-balanced, and redundant public PegNet endpoint.

4) PegTX - (DEC) Turnkey PegNet accounting tool to track your DeFi and PegNet accounting needs.

For the latest updates, monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s February Community Update (covering activity in January)

JAN Summary:
-Several long-term projects completed and released to the community
-Governance activities included several community voting matters and policy discussions
-Preparations ongoing for upcoming grant round including 3rd-party consulting, planning, mock-ups, etc.
-End of January-early February: multiple personnel on travel

Assets Delivered:

--PegTrader: for enhanced PegNet user/trader functionalities https://github.com/kompendium-llc/pegtrader
-Haskell Client Library for PegNet https://github.com/kompendium-llc/pegnetd-haskell-client
-Haskell Client Library for Factom Protocol https://github.com/kompendium-llc/factom-haskell-client
-Swift Client Library for Factom Protocol https://github.com/kompendium-llc/factom-swift-client
-PHP Client Library for Factom Protocol https://github.com/kompendium-llc/factom-php-client
-Ruby Client Library for Factom Protocol https://github.com/kompendium-llc/factom-ruby-client

January Initiatives (details):

PegNet: In January, we continued to contribute to core dev of PegNet. Additionally, we had two releases pertaining to PegNet: a comprehensive Haskell client library, and a PegTrader to introduce additional functionalities and basic PegNet trading automation. We remain interested in further advancing PegNet and expect to have additional releases in the coming months.

Released Libraries: We finished one of our major projects in January—the significant expansion of Factom’s JSON-rpc client library collection—with the release of four full-developed client libraries for PHP, Swift, Haskell, and Ruby. These libraries were built over a span of five months with contributions of half a dozen developers and were extensively built out and tested to ensure full coverage. We’ve also built out a Factom Tooling dashboard to organize SDKs for developers. We believe this work is foundational in providing the tools to grow the Factom ecosystem and expand its appeal and use for years to come.

February Forecast:
We expect February to be consumed with personal travel, the community grant round, and research/POC a few early-stage projects. We don’t have any planned community releases for February. For the latest updates, please monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s March Community Update (covering activity in February through mid-March)

Not counting all the challenges and complications with the ongoing global COVID-19 pandemic, the last 1.5 months have been extremely challenging for the Kompendium team.

February: We spent much of February consumed with the community quarterly grant round and community governance matters.

Additionally, in February we began multiple Proof of Concept (PoC) projects to examine the viability of portfolio management-type automated tools for PegNet. We are currently looking to expand the POCs into releasable tools, of which we are targeting a community release of late April/early May.

On the administrative side, we have adopted an internal project release schedule to plan out the life cycle of our projects. We’re hoping this organization tool improves the predictability of our development activities and releases.

March: The great majority of our activities and energy from late February into mid-March has been devoted to an all-out sprint to stand up seamlessly all new node infrastructure, monitoring alert tools, and corporate administration. We adopted such measures do the departure of one of our team members.

Due to irreconcilable differences, Mitchell is no longer part of Kompendium. We wish him the best, and hope he remains involved in the community as he is an extremely talented developer and Factom Protocol subject matter expert.

In the near-term, I will be heavily consumed with Navy responsibilities over much of April and May, but will diligently work to keep the community apprised of our activities. Even with the challenging impacts of COVID-19 on all aspects of our personal and professional lives, we remain resilient and committed to deliver above average value to the Factom community across all aspects of our ANO repsosniblites.
This is Kompendium’s April Community Update (covering activity in mid-March to early April)

Update Summary:
-Rebuilt/New Kompendium GitHub: https://github.com/kompendium-ano
-Changed the Kompendium company logo, revised strategy, scheduled deliverables
-Finished building out new server identities, infrastructure, testnet node, monitoring services, etc.
-Completed corporate accounting, taxes
-Moved our extensive set of community libraries to our new github and we’ve been busy at work rebuilding our client libraries’ CI/test coverage. We’ve also had the SDK links on factomprotocl.org updated with our new github repos and we’re contouring to maintain them
-Began migrating several private repos holding some of our rpc client tests into our public repos, will publish soon
-Governance activities included several community voting matters and policy discussions. There have been unfortunate and destabilizing events in the past few weeks that we had hoped would be avoided.
-We’re not certain our way ahead for the next grant round. The community continues to fund efforts and projects that don’t align with what we believe would bring the community superior value. We’ve spent tens of thousands of dollars building out what we consider community core infrastructure, which remains unfunded. We’ve got a couple larger projects we’re working on, however they will take time to come fruition.

We’re really excited about our new roadmap and new initiatives over the next couple months. We’re hoping other ANOs are able to continue to remain focused on bring and building value with Factom.

What we’re working on the development side:
-Publish, previously private tests for our client libraries
-Zero knowledge proofs research and capabilities development work
-DIDs and corporate solution services
-PegNet trading tooling POCs
-Governance matters

We expect May to be exciting for Kompendium and hope the current raincloud over Factom/governance clears for sunnier skies. For the latest updates, please monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s monthly Community Update for May (covering activity early-to-late April)

Update Summary:
-Governance activities iincluded several community voting matters and community policy discussions.
-ANO Outreach to establish improved cooperative lines of effort with multiple parties
-Completed several PegNet projects for improved 3rd-party integration, etc.
  • Integrated pUSD (ERC20 wrapper) with Trust Wallet, Myetherwallet, MyCrypto, and updated info on Uniswap
-Finished CI/Testing incorporation/updates to community client Repos: PHP, Ruby, Swift, Haskell
-Assuming the responsibility for the community to host the community ANO alert system – node ready awaiting follow-up by CL
-Agreed to join efforts with ANO DBGrow on the further development of FAT as a FAT Editor/Core Dev

What we’re working on…
-FAT Tooling, FAT Protocol Research
-Grant Round Preparation: Proposed Grants
  • Bidirectional Factom-to-Ethereum Bridge (smart contract-based) (exciting proposal incorporating opportunities for FCT staking, etc.), and FAT core improvements
  • Two fuly-developed community client libraries & library maintenance: PHP & Ruby [Back-Pay]
-Website design, further work on our in-development b2b/b2c Auth Services/Identity services
-Design work towards our proposed Factom-to-Ethereum bidirectional bridge platform (Factom community priority)
-Various governance matters
-Spinning up two additional servers
  • Community ANO alert system host
  • FAT playground for FAT development work
For the latest updates, please monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s monthly Community Update for June (covering activity in May)

Update Summary:
- Governance activities included a few voting matters, the grant round, and participation in several technical and non-technical discussions on various Factom, FAT, and PegNet discord server channels.

- We’ve been thinking through and trying to work towards the community using established and logical workflows towards protocol/feature improvements. Many of the project’s goals remain out of reach due to technical limitations within the ecosystem, creating ways to allow people to improve the protocol and greater interest amongst the ANOs to support such efforts would do a lot towards making this project more viable over the long term.

-ANO Outreach: we’re furthering our partnership with DBGrow to deconflict our intended work on FAT and coordinate workflows.

-We continue to be entirely at odds with nearly all other ANOs with regards to the direction/needs of the community and protocol as highlighted by the last 4 grant round votes. We’re trying to figure out where the ANOs are trying to take the ecosystem and how our vision of the ecosystems’ future mesh over time

- We completed maintenance on several of the community libraries (Factom Rust, PegNet Rust and FAT Haskell)

- Research work towards bidirectional Factom <> Ethereum bridge
*Preparing FIPs needed for bridge​
*Preparing FATIP required for light-client implementation​
*Investigating core Factom source code​
-NOTE: efforts to correct lack of established workflows for FIP, coredev onboarding​
- Research & Planning:
*Core Development​
*FAT codebase (WASM, C, Golang refresher, and GoLang WASM integration)​
– Note: FAT has compelling technical hurdles we intend to invest time in resolving. We believe many of the commercially-viable use cases for the Factom ecosystem will stem from FAT; however, the majority of critical functionalities require essential improvements to make the platform ready for commercial integration/use.​
-Finished multiple PegNet integration bounties (AirSwap, MyCrypto wallets)

-Hosting community ANO alert system, awaiting further testing

What we’re working on:
  • DID-related functions and tooling for in-development b2b/b2c Auth/Identity services
  • Design work towards our interoperability, explorer, and DB solutions
- FAT core protocol improvement planning and initiatives​
- FIP/FATIP planning/drafting​
- Factom games + articles in support of our several community libraries and their uses​
- Workflow and developer onboarding documentation​
- Internal websites and tech infrastructure planning​

For the latest updates, please monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s monthly Community Update for July (covering activity in June)

Update Summary:

- Governance: activities included a few voting matters, and participation in several technical and non-technical discussions on various Factom, FAT, and PegNet discord server channels.

We’ve been working heavily with Factom Governance Working Group members (primarily with ANO CUBE3 & FACTOHSI) on a proposed comprehensive overhaul for community governance, which we expect to be released in the near-term to the community for review.

- ANO Outreach: we’ve been attempting to further our partnership with ANO DBGrow in order to deconflict our work on FAT and coordinate workflows. We’ve provided a proposed draft high-level road map for FAT and slowly conducting research to determine a viable way forward. Communication with stakeholders has been slow. Note: given our grant proposal for FAT improvement was not approved by the community, we did not onboard a dedicated FAT coredev; we do believe such work remains necessary if core FAT improvements are to be realized/desired.

- PegNet work: PegNet development work conducted towards version 2.0. Actively participating in internal development. Multiple PRs created in core repositories related to automated rewards to stakers and developers without additional network transactions (PIP 12, 16). Additional integrations for ERC20 version of pUSD into popular platforms.

- Research/work: believing the community’s non-approval of our bidirectional Factom <> Ethereum bridge grant proposal last grant round as a strategic community error, we’re using the few resources we have to continue work towards its realization, albeit slowly.

- Community Infra: ANO alert system; while we continue to host the system, we continue our desire to coordinate system testing with other ANOs more familiar with using it.

In Work:

What we’re working on:
  • AuthDeX: an in-development b2b/b2c Auth/Identity service
  • AuthDeX website and tech infrastructure
  • ChainView: Factom ecosystem asset/block explorer
  • Smart-contract research - FAT, DAML, custom solutions
  • Bidirectional Factom <> Ethereum bridge
  • Factom Community Governance Overhaul
For the latest updates, please monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s monthly Community Update for August (covering activity in July)

Update Summary:

- Governance: efforts in May and June culminated in the GWG Proposal being shared, debated and put up for community vote. We were excited to see broad community support. We’ve also joined the Community Governance Implementation Group and will be working through Factom Community Governance Documents over the next few weeks to prepare them for further community discussion and ratification.

We’ve also begun participating in the weekly developers stand up meeting.

- ANO Outreach: Within the community we conducted several email, phone call, and Discord DM conversations with other ANOs to discuss coordination/collaboration on ideas as well as expected challenges. Internal outreach was also conducted in support of encouraging ANO participation in the GWG Proposal Major Timed Discussion. Externally, we engaged several small companies to examine their current challenges and opportunities where Blockchain-enabled services might provide them value.

- PegNet work: PegNet development work was conducted towards version 2.0. Sergey is actively participating in the system’s internal development. Multiple PRs were created in core repositories related to automated pAsset staking without additional network transactions and developer rewards (PIP 12, 16). Additional work was done for integration of ERC20 version of pUSD into popular platforms.

- Research: Novel smart-contracts generation approaches and methods oriented towards security.

- Infrastructure: Added a large storage-focused dedicated server to better host our infrastructure to support cross-chain applications in development and associated enabling services.

In Work (Next 30 Days):

What we’re working on:
  • ChainView: Factom ecosystem block/asset explorer
    • *Alpha release expected in August
  • AuthDeX: an in-development b2b/b2c Auth/Identity services
    • *Alpha release expected in August
  • AuthDeX website and tech infrastructure
  • Smart-contract research – FAT + custom solutions
  • Talent Scouting
  • Factom <> Ethereum bidirectional bridge grant proposal support (Grant Round)
  • Factom Governance Implementation Group & Draft Documents/Road Map
  • PegNet v2 related work
For the latest updates, please monitor Kompendium’s company blog (Kompendium Blog) and other Factom Protocol community announcements.
This is Kompendium’s monthly Community Update for September (covering activity in August)

Update Summary:

- Governance: We continued work towards creating draft revisions of several Factom Community Governance Documents as part of our work in the Community Governance Implementation Group (GIG). Once complete, the GIG will prepare recommended revisions for further open community discussion and ratification by the standing parties.

- ANO Outreach: Also as part of our work in the GIG, we continue to engage several ANOs to poll for content and ideas for a draft Community Road Map. This Draft Road Map is meant to capture ideas that can be organized into themes to serve as a starting point for the community to come together and discuss, debate, and ultimately agree upon a community road map to provide strategic direction to the Factom community.

- PegNet Work: with increasing time demands towards our recent grant and several additional Kompendium projects Sergey has reduced his level of involvement in PegNet development at this time.

- Research: Verifiable Credentials/Representations, ZKP, and Identity Governance

-Grant Work: One of our grant proposals was recently approved and we’ve been conducting work in support of that project such as drafting technical specifications and FAT improvement proposals. We’ve also been conducting talent scouting and interviews for an additional developer to assist in the project and creating documentation to facilitate new developer onboarding.

In Work (Next 30 Days):

What we’re working on:
  • Factom <> Ethereum bidirectional bridge work
  • Support to Developer Onboarding
  • Factom Governance Implementation Group & Draft Documents/Road Map
  • AuthDeX: an in-development b2b/b2c Auth/Identity service:
    * Expected internal Alpha release delayed, now September​
  • AuthDeX website and tech infrastructure ongoing
  • ChainView: Factom ecosystem block/asset explorer
    *Expected internal Alpha release delayed, now September​
  • Tasset Mobile Wallets - internal Alpha release
  • Prospective Client Engagement
This is Kompendium’s monthly Community Update for November (covering activity in September and October)

Update Summary:

- Grant Work [Factom<>Ethereum Bridge]: Significant progress has been made on the Ethereum<>Factom bridge. The most significant challenge of the first bridge grant was the need to modify core FAT to allow for several advanced smart contract capabilities. Designing and engineering these solutions proved far more time consuming, complicated, and challenging than we anticipated.That being said, Sergey and our recently hired GO dev were successful inventing innovative solutions to these core FAT shortcomings.
  • These engineered FAT improvements will be submitted in the coming week as three separate FATIPs:
    • 1) Improved Contract Storage
    • 2) Cross-contract Calls
    • 3) Use of EC as a gas-mechanism or Fat dApps.
  • We will submit three separate PRs to incorporate each FAT improvement.
  • To support bridge prototyping we are in the process of creating a Kompendium-hosted local FAT Testnet
  • Ethereum-side bridge prototyping was developed in Solidity and deployed to an Ethereum testnet.
With solutions to all three needed FAT technical improvements, we are in good shape and on-schedule in developing the ETH<>Factom bridge. Our FATips and a grant thread update will be published for community review this week. As we described in the grant application, the bridge will be developed over 6 months, with work divided over two 3-month grants. We are submitting the second (two of two) grant application for the Factom<>Ethereum Bridge in the upcoming grant round.

- Personnel: We hired a part-time GoLang-dev to assist in core FAT design improvements, Factom<>Ethereum Bridge, and other projects. He brings with significant experience from past work on several large projects on the IOTA project.

- Mobile Apps: The AuthDeX app and Tasset Wallets (Facotm & PegNet mobile wallets) have been submitted to Google Play and the Apple App Store for initial review and approval.
  • The AuthDeX app is a limited protype that works with our in-development authentication and authorization business platform.
  • Tasset (mobile) are real-time Factom and Pegnet mobile wallets. We are preparing for Mobile Wallet ANO testing on 03NOV, in preparation of a public release 1-2 weeks later. More to follow. We expect regular wallet improvements and expansions as our team capacity allows following the completion of our Factom<>Ethereum bridge work.
- Ecosystem Block & Asset Explorer: Chainview continues limited internal testing. Progress has been limited as we’ve prioritized Bridge work. We aim to conclude internal testing and release the explorer in mid-to-late November. Chainview will be regularly expanded and improved over the next several months to provide a variety of services across the Factom ecosystem.

- Governance: We invested significant time in outreach and an initial drafting of a Community Road Map in July and August, In early September we passed this effort off to another team. With no advancement by mid-October, we resumed work and provided a draft to the GIG for review. We expect the several Community governance documents we revised in July/August will be brought to the community for review, discussion, and ratifications in the coming weeks by the GIG, of which we remain a contributing member.

- PegNet work: Outside our work on the mobile Tasset wallets, we did not complete any meaningful work relating to PegNet in September and October.

- Libraries: Factom Tooling Dashboard: https://github.com/kompendium-ano/factom-tooling
  • Several libraries were updated/started in September. Some remain a WIP, and some are not yet published. Progress on them has been limited to unscheduled work done whenever time is found between other higher/priority projects. We intend to make several updates to our client libraries in November based on Factomd updates.
    • Updates were made to:
      • Factom DiD Lib implemented in Haskell
      • Rust Client Lib
      • Haskell Client Lib
    • Started New Library
      • Factom Verifiable Credentials Lib implemented in Haskell
      • Improved Rust Client Lib
- Website Work: published a new Kompendium.co website, and created websites for two of our soon-to-be-released mobile applications: Tasset, and AuthDeX.

In Work (Next 30 Days):

What we’re working on:
  • Factom<>Ethereum bidirectional bridge work
    • Monitoring Factom Core Dev work to discover impacts to bridge function
    • Finalize prototype and testing
    • Plan/design bridge supporting features, etc.
    • Bridge Grant Application (part two of two)
  • Factom & PegNet Mobile Wallets - ANO Testing 03NOV - alpha release aftwards
  • AuthDeX App prototype release (app store, google play)
  • Ecosystem Block & Asset Explorer (Chainview) publish and release
  • Factom Governance Implementation Group & Draft Documents/Road Map
  • Updates to several Libraries
  • Progress on Factom VC Library
  • Prospective client outreach

Long Term Projects (update):
Next 9 months: Over the next 9 months our focus will be on building out community infrastructure and establishing business clients.
  • Bridge–Infrastructure: The Ethereum<>Factom bridge is progressing well and will enable known and not yet realized opportunities to the Factom and Ethereum communities. The bridge is being built over two 3-month grants. We are submitting the second of two grant applications in the upcoming grant round.
  • Libraries-Infrastructure: Libraries are critical to our ability to integrate Factom features into Kompendium software as well as a significant asset for the community to allow different developer communities access Factom.
    • Clients: We do not plan to develop additional clients at this time.
    • DID: We have published a DID lib in Haskell and have a WIP for a DID lib in Rust. The Haskell lib is the first DID lib in this language. Our DID focus is in support of our AuthDeX platform.
    • VC: We have started a VC lib in Haskell. Once complete, we intend to create a VC lib in Rust. Our VC focus is in support of our AuthDeX platform.
  • Block and Asset Explorer–Infrastructure. Chainview is an ecosystem block and asset explorer. We have big plans for Chainview to include support for multiple chains and a variety of advanced features.
  • Ecosystem wallets–Infrastructure: Tasset wallets will be a mobile, browser, and desktop multi-token wallet; it will support the Factom Ecosystem of tokens. While the current version of the wallet does not include a dApp browser, we expect to include a dApp browser in a future wallet release.
  • Integrated Developer Environment (IDE)–Infrastructure: Katalyst is a planned advanced dApp Integrated Developer Environment (IDE). Katalyst will support multiple languages and provide advanced features that will allow developers to use their preferred language while at the same time deploying dApps on the supported blockchain of their preference. The idea is it will conveniently allow dApp developers the ability to lower cost and improve flexibility. This is a very large project and has not yet been begun. We believe this project could be one of the fastest and most productive approaches to increase Factom usage and the number of developers building on Factom by appealing to existing and active dApp developers on other blockchains such as Ethereum, Tron, EOS, Tezos, Cardano, etc. to deploy their dApps or at least their dApp data stores on Factom.
  • Smart Contract Language–Infrastructure: Covenant is a Smart Contract programming language we are currently developing for the Factom community that will allow safe, verifiable, and precise smart contracts. We believe that covenant will form the community’s next generation platform for developing dApps and tokens atop Factom.
  • Interoperability Platform–Infrastructure: Kommunity is an idea for an interoperability platform atop Factom connecting several independent blockchains with Factom providing a ledger of record and data intermediary for cross-chain data exchange/events. The high-level idea is to use bidirectional bridges to connect other blockchains to Factom, and develop a communication and messaging system to define and manage flexible, safe, and rapid data and communication exchanges across blockchains interconnected via Factom bridges. The DLT space has changed considerably since we originally drew up these plans early in 2019, but we believe the idea is still valid. Kommunity is very large project and is currently not a top priority for us. We plan to further develop this idea as time and funds allow.
  • Authentication and Authorization Platform-business: AuthDeX is an authentication and authorization platform that is being developed to provide decentralized Identity and Access Management (IAM). This service is centered on DID and VC/Verifiable Presentations. This project is ambitious, and one of our top priorities - MTF.

Beyond 9 months: Plans outside a few months are tentative.
  • ZKP–Infrastructure: Zero Knowledge Proofs remain something we feel would be a tremendous capability additional to the Factom ecosystem. Our early efforts to introduce ZKP to Factom were rejected by the community, but we believe there remains strong interest by a select group. Bringing a robust ZKP capability to the Factom ecosystem represents a large and complicated undertaking. This is not currently a priority for us.
  • Crypto-derivative Exchange–Infrastructure: The Synthetic Options Contracts Exchange and Trust (SOCET). SOCET is a decentralized exchange to trade options contract (smart contracts) of financial synthetics (think pAssets). Some tech features needed to build SOCET such as ZKP and advanced smart contracts do not yet exist on Factom. This would be a very large project on par with PegNet. While it’s unclear if strong hype around DeFi will continue, we believe SOCET has the potential for the community to build and operate a high-buzz, highly- appealing, and high-usage platform.
  • Gaming & Adv Data Services-business: We have several underdeveloped ideas for services related to data lineage veracity, DRM, and gaming. These ideas are not yet developed to a point to measure their commercial viability. We do not expect to actively focus on these ideas in the near-term.
This is an update for February 2021. Activity described occurred over December and January.

Community Grant Work:
  • We are currently completing work under two grants. Both grants are for the design, creation, implementation , and support of a bi-directional Bridge between the Ethereum and Factom Blockchains. This project is very timely for Factom as every major blockchain project is striving to establish bridges as cross-chain functionality is becoming an industry top priority.
  • We recently provided a project update here: Factom Grant Tracking Thread
Highlights include:​
  • Design and prototyping of all major bridge system components:
    • -ETH Bridge contract/dApp
      • -Factom Bridge contract/dApp
      • -ETH Relayer application
      • -Factom Relayer application
      • -ETH Prover application
      • -Factom Prover application
  • Submission of three FAT Improvement Proposals (FATIPs) to introduce advanced smart contract capabilities to the FAT network
    • Development and prototyping of the technologies and implementation methods for bringing advanced smart contract capabilities into FAT’s core protocol proved a far larger, more technical, complicated, and time-intensive task than we had originally estimated. We are excited to report that all three FATIPs have been completed and have been submitted for review. These new and exciting features soon available on FAT will significantly open the aperture of what is possible within the ecosystem.
    • FATIP-108- FAT Gas System <FATIP 108 Link>
      • Summary: FATIP-108 defines a FAT gas system: its basic units, dynamic gas functions, and the specifications governing their use. The gas system increases the overall health of the network by improving security; discouraging network spam; and incentivizing the deployment and rapid processing of transactions, smart contracts, and contract calls within the FAT ecosystem.
    • FATIP-109 Stateful Contracts <FATIP 109 Link>
      • Summary: FATIP-109 introduces the characteristic of “state” to FAT smart contracts, which enables stateful composition to in-contract storage. Stateful smart contracts can hold application logic and can store and update on-chain values, which significantly extends the range of contract and decentralized application (dApp) functionalities possible on FAT.
    • FATIP-110 Cross-Contract Calls <FATIP 110 Link>
      • Summary: FATIP-110 adds the ability for FAT smart contracts to conduct external cross-contract calls. The ability for a smart contract to call functions of other contracts and to create and deploy additional contracts opens a large variety of composable use cases and solutions not previously possible with FAT.
  • Remaining Grant Work: The following is a high-level overview of remaining milestones
    • Make fatd and https://github.com/Factom-Asset-Tokens/factom libraries be in sync with upstream Factom library
    • Submit PRs (implementation code) for FATIP-108, 109, and 110
    • Finish design of Bridge Gas/Fee calculator & incorporate into server
    • Finish design of Bridge sufficient funds validator & incorporate into server
    • Deploy Bridge contracts to Ethereum and Facotm public testnets
    • Functionality & Performance Testing & Audit (local)
    • Functionality & Performance Testing (Multi-party (3-5 ANO))
    • Deploy functional Bridge to Factom (FAT) and Ethereum Mainnet
    • Safety/Security Review
    • Complete Bridge documentation
    • Expose Bridge CLI
FEB20 Grant Round: We have decided not to submit any grant requests this round. In addition to having a principle preference for back-pay grants, we decided to forgo any additional grants this round to allow us to:
  • 1) Bridge: remain focused on completing the Ethereum<>Factom bridge on time
  • 2) Mobile Wallets: complete/deliver a set of mobile wallets in FEB/MAR
  • 3) Asset Explorer: complete/deliver an ecosystem asset explorer in FEB
  • 4) DID Libraries: complete/deliver a set of DID libraries in FEB/MAR
  • 5) VC Libraries: complete/deliver a set of Verifiable Credentials Libs in MAR/APR
Products Under Development:
  • We are hard at work on the 5 products listed above!
    • We expect to release Chainview, an asset explorer for the ecosystem in February. We’ve been working on-and-off on this for a year, but we have brought on additional temporary developer support to finish this project.
    • We expect to release Tasset, a set of multi-token mobile wallets starting late February and through March. First release of the wallet will be limited to Factom. Subsequent updates each week will introduce additional features as well as extended support, to PEGNET, then FAT, and likely beyond. We anticipated releasing the wallets in November, but the combination of changes to the UI as well as greater focus being required on the ethereum<:>factom bridge delayed our planned work. We have brought on additional temporary developer support to finish this project.
    • With the addition of temporary developer support for the Chainview explorer and Tasset Mobile Wallets, we are confident that we will be able to deliver the libraries in late February and March.
Governance Work:
  • We’ve been very busy in governance work in the end of 2020 and early part of 2021. We anticipate there is far more governance work to be done and expected continued heavy involvement over the next several months.
Community Update Periodicity:
  • We will be returning to a monthly update report cadence in 2021.
This is an update for February 2021. Activity described occurred over February, March, and early April.

  • 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
  • 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
This is an update for June 2021. Activity described occurred over May, and half of June.

  • Current Servers:
    • 2 Factom Authority Servers
    • 2 Backup Servers
    • 1 Factom testnet server
    • 3 Application Servers
    • 2 additional small servers (7 VMs) for a localized FATd testnet, and an API sandbox for services
  • We are currently operating at 5.5 FTE spread across six projects.
    • Recently hired three non-permanent near-full time Rust Developers
    • We have three non-permanent part time developers (Go, Dart, Haskell) working on various projects
    • Jason and Sergey remain as core members
  • Since the election of a Community Director and Council, Kompendium has ceased all governance-related activity
    • At this time, we have no privileged insight into any effort or planning that may be occurring within the ecosystem outside our own efforts
Current Work
  • Tasset Mobile: Mobile wallets (iOS & Android) for Factom, PegNet, FAT, Ethereum
  • Tasset Web: Full web-version of the Tasset wallets
  • Chainview: Asset explorer supporting Factom, PegNet, FAT, Ethereum,
  • Factom <> Ethereum Bi-directional Bridge (FAE): Bridge connecting the networks
    • Previous development obstacles have been overcome and we are working through safety checks before opening testing to additional ANOs
  • FAT: Progressing with the incorporation of our three FATIPs which introduce a GAS system, stateful contracts, and expanded contract storage for the ecosystem
  • C.A.P.C.I.L: Next Generation Layer 2 Service protocol atop Factom (FAT=first generation)
    • CAPCIL = Contracts, Assets, Proofs, Credentials, and Identities Layer
    • Rust-based protocol to provide more advanced capabilities atop Factom
    • This is a massive undertaking, but we feel that this investment (and others) is needed for Factom to provide reliable production-ready commercial services that rival or exceed what competing blockchain projects can offer
  • Contracted ARknet Support: Press Release Link
    • We have been contracted to provide various support to Tautachrome’s Augmented Reality (AR) Social platform “ARknet
    • First Phase announced services include Ethereum and Factom token wallet integration, asset explorer support, Factom<>Ethereum bridge integration, and a broad range of NFT-related services
    • Current focus (phase 1)
      • Onboarding their existing user base onto Factom and Ethereum (wallets), connecting ARknet to Factom and Ethereum (multi-chain asset explorer feeds and FAE Bridge)
      • Cataloging existing AR virtual objects and users for assignment of Factom-based DIDs
      • Designing a NFT platform for the ARknet AR space and designing an ERC-1155 equivalent token standard for Factom (CAPCIL)
      • Enabling ARknet tokenized objects to move between Ethereum and Factom blockchains (bridge)
Near-term Future Work
  • Future press releases detailing additional efforts of our work on ARknet
  • Research, proposal writing, and development of Phase II efforts for ARknet
  • Finalizing Tasset Mobile, Tasset Web, and Chainview for public release
  • FAE Bridge multi-ANO testing and mainnet release
  • Research relating to prerequisite requirements for additional planned services and capabilities atop Factom
  • Analysis to determine if we should create an additional element within Kompendium for Factom coredev; discussion with community leadership
Current Update: July 2021 Community Update
This is an update for July 2021. The activity described occurred during July.

Infrastructure (No change since June)
  • Current Servers:
    • 2 Factom Authority Servers
    • 2 Backup Servers
    • 1 Factom testnet server
    • 3 Application Servers
    • 2 additional small servers (7 VMs) for a localized FATd testnet, and an API sandbox for services
  • We are currently operating at 5 FTE spread across six projects
    • We lost .5 FTE since last report (june)
    • We’re competing for an opportunity that would require additional hiring
Current Work
  • Tasset Mobile: Mobile wallets (iOS & Android) for Factom, PegNet, FAT, Ethereum
    • ~90% done - we haven’t had the bandwidth to finish our mobile wallets as we’ve been focused on CAPCIL development, wallet UI needs further polishing
  • Tasset Web: Full web-version of the Tasset wallets
    • ~80% done - this effort is advancing and should soon reach an alpha version
  • Chainview: Asset explorer supporting Factom, PegNet, FAT, Ethereum,
    • ~70% done - this effort is advancing, recent efforts have been around restructuring the back end of the app, the app’s UI needs further polishing
  • Factom <> Ethereum Bridge (FAE): Connecting the Ethereum and Factom networks
    • The bridge is 95% done; We need to do some DevOps work to better package all the components of the bridge for easier deployment
  • C.A.P.C.I.L: Next Gen Layer 2 Smart Contract protocol atop Factom (FAT replacement)
    • CAPCIL = Contracts, Assets, Proofs, Credentials, and Identities Layers
    • Rust-based protocol to provide reliable production-ready commercial services that rival or exceed what competing blockchain projects can offer
    • This has been our primary focus with multiple dedicated FTE; We’ve made significant advances on contract, token, and identity features, with a specific focus on NFTs.
  • Contracted ARknet Support: <https://arknet.app/>
    • We continue to provide full-time blockchain-related support to Tautachrome’s Augmented Reality (AR) Social platform “ARknet”
    • We hope to finalize details regarding the second phase of our planned work in the coming days and release more information to the community.
Near-term Future Work
  • Research and development of ARknet Phase II efforts
  • Finalizing Tasset Mobile, Tasset Web, and Chainview public testing
  • FAE Bridge multi-ANO testnet
  • CAPCIL Testnet and expansion
Comment: With the extensive work we’ve been doing for the past 6-8 months and the unclear timeline of community instituting a new community grant system, we intend to submit a few grant proposals in the current ongoing grant round. We eagerly look forward to a future with the planned rolling grant process.