March Update

Previous Updates

Jason Gregoire

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 ( 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 ( 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.

Jason Gregoire

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

Jason Gregoire

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.

Jason Gregoire

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: 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.

Jason Gregoire

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! 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 ( - (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.

Jason Gregoire

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
-Haskell Client Library for PegNet
-Haskell Client Library for Factom Protocol
-Swift Client Library for Factom Protocol
-PHP Client Library for Factom Protocol
-Ruby Client Library for Factom Protocol

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.
Current Update: March Update

Jason Gregoire

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.