Kompendium

Standing Parties: Please score this ANO Candidate from 0 - 60


Have not voted

Authority Nodes Consensus Networks Consensus Networks Innovative Secured Connection (ISC) Kompendium Kompendium

  • Total voters
    28
  • Poll closed .
Hi Kompendium team. Thanks for your application and good luck in the ANO round selection.

Some first question from me:

NK01
Until our staff expands, two Kompendium personnel are available to manage and operate our Factom Protocol nodes an average of 30 hours per week and 24/7 on-call.
30 hours a week equals roughly 130 hours a month. Given the infra itself also costs money and you would be operating at an infra level efficiency of at least 60 percent, you have obviously done the calculations as your document shows. With only a few dollars to spare on net income and your reserve fund, how do you envision the short term future? What happens if your reserve fund depletes rapidly? What factors would mean you would reconsider your efficiency level?

NK02
We will publish the first Factom Protocol book, introducing the Protocol, providing detailed instructions on how to get involved, operate a node, operate within the Testnet and Mainnet, get data uploaded onto the Factom Protocol blockchain, how to get involved in the community behind the movement and much more. The book will offer information for technical experts, business owners, data managers, and general blockchain enthusiasts.
I applaud the initiative. As a startup how are you going to fund and make time for this endeavour? Do you have any timelines associated with that initiative?

NK03
If elected, we will work with the ANO collective and the greater Factom Protocol community to achieve these and other goals.
<snip>
That is quite an impressive list. Basically the same question as above, but worded a bit differently. You mention a lot of initiatives, most which sound great. How hard are these commitments? Can we hold you accountable to these initiatives once elected? So can we regard them as pledges?
 
Thank you for applying to be an ANO! I'll likely have some specific questions later, these are simply questions I am asking all applicants.

1. Will you commit to, if elected, having, at the very least, the executives who will play a role in this ecosystem:
A. Signup for this forum with their username being First Name Last Name
B. Have a personal picture as their avatar.

It's not a requirement that this happen and some won't care but I personally will score those who won't commit to this a little lower and I want to be transparent about that.

2. Will you commit to having a logo created and/or submitted to this area within 30 days of your election (I would provide directions).

3. Will you commit to keeping this area updated for your team (it's easy).

4. Will you commit to providing at least a quarterly update on the progress your team is making in this area.

5. If you haven't already posted them within this thread, please provide the LinkedIn of anyone you mention as part of your team.

Thank you!
 
Thank you for applying to be an ANO! I'll likely have some specific questions later, these are simply questions I am asking all applicants.

1. Will you commit to, if elected, having, at the very least, the executives who will play a role in this ecosystem:
A. Signup for this forum with their username being First Name Last Name
B. Have a personal picture as their avatar.

It's not a requirement that this happen and some won't care but I personally will score those who won't commit to this a little lower and I want to be transparent about that.

2. Will you commit to having a logo created and/or submitted to this area within 30 days of your election (I would provide directions).

3. Will you commit to keeping this area updated for your team (it's easy).

4. Will you commit to providing at least a quarterly update on the progress your team is making in this area.

5. If you haven't already posted them within this thread, please provide the LinkedIn of anyone you mention as part of your team.

Thank you!
1. Will you commit to, if elected, having, at the very least, the executives who will play a role in this ecosystem:
A. Signup for this forum with their username being First Name Last Name. Yes
B. Have a personal picture as their avatar. Yes
2. Will you commit to having a logo created and/or submitted to this area within 30 days of your election. Yes
3. Will you commit to keeping this area updated for your team (it's easy). Yes and working.
4. Will you commit to providing at least a quarterly update on the progress your team is making in this area. Yes.
5. If you haven't already posted them within this thread, please provide the LinkedIn of anyone you mention as part of your team.
 
Hi Kompendium team. Thanks for your application and good luck in the ANO round selection.

Some first question from me:

NK01

30 hours a week equals roughly 130 hours a month. Given the infra itself also costs money and you would be operating at an infra level efficiency of at least 60 percent, you have obviously done the calculations as your document shows. With only a few dollars to spare on net income and your reserve fund, how do you envision the short term future? What happens if your reserve fund depletes rapidly? What factors would mean you would reconsider your efficiency level?

NK02

I applaud the initiative. As a startup how are you going to fund and make time for this endeavour? Do you have any timelines associated with that initiative?

NK03

That is quite an impressive list. Basically the same question as above, but worded a bit differently. You mention a lot of initiatives, most which sound great. How hard are these commitments? Can we hold you accountable to these initiatives once elected? So can we regard them as pledges?
NK01: With only a few dollars to spare on net income and your reserve fund, how do you envision the short term future? In the short term we anticipate drawing on our reserves to fund: incorporating expenses, contract expenses for server and support services infrastructure, branding expenses (e.g., website development), select professional memberships, and marketing activities foreseen to benefit the Factom Protocol community. During this period, we intend to forego drawing a salary from operations to more rapidly reconstitute our reserve fund.
What happens if your reserve fund depletes rapidly? While a rapid depletion of our reserve fund is possible, our dual-node financial Monte Carlo simulations suggests this is unlikely. Kompendium’s operating plan includes strategic reviews at different FCT/USD levels and reserve fund redlines (80%, 60%, 50%, 45%, 40%, 30%, 20%, 10%) to assess our expenses and operations. This strategic review ensures Kompendium services remain viable and sustainable. In the unlikely event reserves fall below 40% or otherwise unsustainable levels, we intend to simply add capital from personal funds as necessary until the reserve fund stabilizes.
What factors would mean you would reconsider your efficiency level? As an Infrastructure Node, we pledge to maintain our efficiency levels at a minimum of 60% as per our campaign document.
** As Infrastructure Node: If circumstances such as a prolonged downturn in the FCT/USD ratio forced hard choices, we would resolve to maintain our pledged efficiency levels. We would temporarily conduct only Infrastructure Node operations (i.e., suspend non-Infra activities and initiatives) until the financial emergency is mitigated or resolved. Prior to any decision or action, Kompendium would discuss/negotiate this recommended course of action with the Protocol Standing Parties.

** If Beyond Infrastructure Node Activities: If Kompendium evolves in its roles, responsibilities, and operations SIGNIFNCANTLY beyond infrastructure ANO activities such as dedicated core Protocol development, we would negotiate with the Standing Parties to consider decreasing our efficiency level to align compensation to the level of value and efforts surpassing our initial infrastructure ANO pledges.

NK02: As a startup how are you going to fund and make time for this endeavour? Do you have any timelines associated with that initiative? As officers in the United States Navy, we are paid full-time salaries. Our assessment is that Kompendium’s reserve funds and modest ANO income will be sufficient to complete the first draft. The research required to write this book will expand our knowledge and educate others. We believe the book should be around 300-400 pages long. Our calculations are based on goals of writing 15-20 pages per week for approximately 20-30 weeks for a first full draft. Absent unforeseen circumstances, and factoring time for revisions, we believe the first draft will be possible by October/November 2019.

NK03: How hard are these commitments? Can we hold you accountable to these initiatives once elected? So can we regard them as pledges?
In addition to running an infrastructure node, the items listed are specific examples of the KINDS of initiatives we are pledging to pursue. We do not want to be held to any individual item on the list as a formal pledge. Rather, we are pledging to pursue multiple initiatives that will provide benefit to the Factom Protocol and our community, of which these would be representative. We believe these efforts will grow the Community, add value to the Factom Protocol, and evangelize the benefits of blockchain technology.
 
Hi Kompendium - thanks for your application!

You narrowly missed out on election in 2018 - what has your team been doing since then? What are some examples of your governance contributions as a long-term token holder?

Kind Regards!
Although we have not significantly contributed to governance as non Standing Parties, we have nevertheless been busy over the last year. In addition to the work culminating in our Campaign Document, we have
  • Advanced our education in current relevant technologies (e.g., Linux, Docker, DB tools, sysadmin, programming, etc)
  • Maintained multiple Testent nodes continuously
  • Applied as Testnet Administrator for the community
  • Brought on two other members to the Kompendium team
  • Recruited and learned from top advisors and mentors on paths to success
  • Researched market trends and academic papers for Protocol use-cases
  • Evangelized the utility and benefits of the Protocol within our professional spheres of influence
These activities represent a sample of our interests and loyalty to the Factom Protocol, it’s community, and it’s potential. Most importantly, we have refined our understanding of exactly what Kompendium is and should do. We have forged a culture, "why", and raison d'être rooted deeply in our passion for finding, building, and appraising trustworthy and reliable data.
 
Last edited:
Kompendium is excited to announce that Mitchell Berry (@Mitchell) has joined the Kompendium team as its lead developer! Mitchell is a seasoned developer and Sysadmin formerly of the prospective ANO Evident Technologies.

As stated within our ANO campaign document, we have been aggressively pursuing technical talent to join Kompendium. On top of our infrastructure, marketing, and educational campaign pledges, Mitchell’s addition will also enable Kompendium to immediately begin contributing to core protocol development, creating Protocol-leveraging applications, and building and enhancing developer tools for the Community. Mitchell has the technical skills, experience, and a passion for the Protocol making him a perfect fit in the Kompendium team and will help Kompendium optimally serve the Community’s needs.

Mitchell enhances Kompendium’s ability to expand and efficiently accomplish campaign pledges as well as ambitious technical initiatives for the Community. We feel very fortunate he believes in Kompendium’s vision. With the addition of a lead developer, we believe Kompendium is optimally positioned to enhance the Protocol. Kompendium is campaigning to provide top-quality network infrastructure, a wide-variety of value-adding key-enabler services (see ANO campaign document), as well as core and commercially-viable technical development, all at very low costs (high efficiency) to the Protocol and Community Grant Pool.

Kompendium remains devoted to running high efficiency infrastructure Authority Nodes while robustly supporting the Community Grant Pool. Moreover, hiring a lead software developer supports our complimentary initiatives to develop tools, applications, education, and marketing strategies for the Protocol. Kompendium will pursue community grants to finance these ambitious technical projects. This approach allows us to maximize our contributions to the Community Grant Pool and leverage the Standing Parties’ grant voting process to ensure our initiatives are fully aligned, supported, and endorsed by the Community.

Attachment -- Kompendium: Draft List for Community Grant Proposals
 

Attachments

Hello, Kompendium, thank you for application.
I ask this questions all ANO candidates:

1. With what efficiency are you going to operate?

2. If your efficiency is lower, than 60%:
2.1. What have you already pledged to the Factom? It's a good practice, when ANO candidates pledge works in advance before being elected.
2.2. Do you have an experience in running business? What kind of businesses it were? Please tell us more about it, so we can understand your strengths and what expect from your ANO if it will be elected.
2.3. What a minimum number of hours per week are you going to work for Factom? Do you commit it?

3. Do you participate in any other cryptocurrency projects? If yes, please reveal details.
 
Hello, Kompendium, thank you for application.
I ask this questions all ANO candidates:

1. With what efficiency are you going to operate?
Hello Anton, thank you for your questions.

As stated in our ANO Campaign Document, Kompendium will use a FCT/USD-dependent schedule for node efficiency determination. We feel a scaled approach will better allow Kompendium to maximize its contribution to the Community grant pool.

At each of the following FCT price points, Kompendium will run two nodes at the corresponding efficiency percentages:

FCT Efficiency (Deferred)
$5 60%
$10 60%
$20 70%
$30 75%
$40 80%

2. If your efficiency is lower, than 60%:
We are campaigning to operate at efficiency levels of 60% or above. However, we appreciate the opportunity to answer following questions.

2.1. What have you already pledged to the Factom? It's a good practice, when ANO candidates pledge works in advance before being elected.
Within the Kompendium ANO Campaign document, we pledged:

As an INFRASTRUCTURE ANO:
  • Maintain scalable technology, at 99.99%+ uptime, to support operations and the growth of the Factom Protocol
  • Operate high-end equipment and processors, RAM, and ultrafast (NVMe) storage
  • Adhere to best practices for security, network and node monitoring, incident response, and latest updates
  • Participate in community engagement, governance, and committees
  • Uphold professionalism, dignity, and respect as public representatives of the Factom Protocol, and conduct ourselves honorably during all community and ANO interactions
  • Use broadband providers that prioritize network and data center security, on-site technicians for emergencies, pledge high availability, and regularly integrate the latest technology
  • Defer majority of FCTs to the grant pool for development priority
  • Maintain a contingency fund to ensure infrastructure in support of the network
  • Support improving the Protocol’s capability, reputation, and use
Additional pledges include:
  • High Performing and Dependable Infrastructure
  • High-performing systems stably operating over a secure, and reliable network.
  • Active Participation in Factom Protocol Governance;
  • Committee Involvement
  • Participate, advance, and contribute to Factom Protocol governance and will campaign to join Factom Protocol committees.
  • Advocacy & Education: Introducing the Public to the Protocol and Community!
  • We will publish the first Factom Protocol book. We will present ANOs opportunities to review drafts then apply for a grant to send our final draft to an editor and have it published.
  • Robust Contribution to the Community Grant Pool
  • Defer at least 60% of ANO protocol-allotted Factoids to the grant pool;
  • As FCT prices rise, defer higher percentages to the grant pool
  • Continued Participation and Support to the Community Testnet
  • Kompendium runs a leader and three follower nodes on the community Testnet;
  • If elected, continue to run Testnet nodes.
  • Leverage the Testnet for spiral development of data management services
  • Seek to incorporate the Factom Protocol as a data integrity back-end solution for our data appraisal services.
With the election of Andrew Young (Team Lead) as the Testnet Administrator, we will enhance and increase participation, standards, utility, and value of the Testnet for the Protocol and Community. We believe the Testnet has untapped potential for the Community and we want to lead its resurgence and enhancement.

We also pledged to deliver value to beyond Infrastructure-ANO expectations and provide several key-enabler and value-adding services for the community, including:
  • Going Beyond Infrastructure ANO Minimums: Marketing, Education, Outreach
  • Work with Linux Academy, serving thousands of tech professionals, to create blockchain instructional courses featuring the Factom Protocol.
  • Coordinate with universities to integrate the Factom Protocol into education and research.
  • Integrate the Protocol into developer curriculums and ANO-led instruction with Hack Reactor (Kompendium advisor)
  • Participate in interviews on popular technology podcasts, including use-case associated Podcasts (digital identity, mortgages, IoT, etc.).
  • Improving the Factom Telegram channel to reduce spam and foster community growth.
  • Market and promote DApp development, GoLang programming, and educating targeted use-case and Meet Up groups co-located with ANOs.
  • Join memberships of non-profit blockchain/technology advocacy groups such as Blockchain Industry Group (BIG) for the promotion of blockchain standards, education, and collaboration.
  • Participate in conference presentation opportunities with BlockchainNW in Seattle, WA
  • Leverage freelance experts (e.g., Fiverr) for blogging, articles, tech reviews, etc. to enhance marketing and promotion of the Factom Protocol.
With the addition of our lead developer, we will strive to enhance the Protocol and bring improved to the Community. We aim to:
  • Develop a “Truffle-like” End-To-End Open Source Development Environment, Testing Framework, and Deployment Pipeline for Factom Protocol Applications
  • Consolidated Development Environment Combining:
  • Existing language libraries supporting Factom
  • Existing developer tools built by the Factom Community
  • Integrates testing/deployment options to Mainnet, Testnet, or private Factom Protocol blockchain
  • Contains Self-Paced Development and Tool Tutorials for Applications and Smart Contracts, Full Documentation
  • Features CLI or full-fledged sleek GUI work environments
  • A catalog of pre-built boilerplate application templates to bootstrap development
  • Integration of front-end development tools, packages, and templates
  • Community-built “Flagship” Factom Protocol Developer Suite
  • Develop Factom Protocol Applications that Nest and Integrate into Widely-Used Services such as: Social Media (Twitter, Facebook, WhatsApp, Instagram, etc.); Other Blockchain Projects; Web Browsers; Email Applications (outlook, Gmail, yahoo mail); Microsoft Office Suite Products
  • Expand and Enhance Available Language Libraries for the Factom Protocol
  • Develop Mobile and Desktop Applications Leveraging the Factom Protocol
  • Join Core Protocol Development Initiatives
  • Educational/Training Projects
  • Professional Factom Protocol Technical Training (tech) Exercises/Lessons
  • Technical education training materials and exercises marketable to instruct students and programmers on how and why to use the Factom Protocol
  • YouTube: Factom Protocol Education and Instructional Channel
  • Weekly/biweekly lessons for Novice-to-Advanced Developers
  • Content steered by Community
  • Instruction features rotation of ANOs leading lessons to
  • develop applications
  • demonstrate Protocol capabilities and features
  • highlight/demo ANO developed capabilities and tools
Open communication and transparency are essential for maintaining a strong, inviting, and cohesive community. We will provide feedback to the community and Standing Parties using the Factomize.com forum and Discord for visibility. We will participate in community discussions and online forums when available. Finally, we strive for transparency of our ANO activities.

Finally, if elected as an ANO, Kompendium will work with talented companies who were not elected to ANO, to contribute to the Community and Protocol. We appreciate and respect all who share our passion and belief in the Factom Protocol and who are driven by the same call to action to deliver value to the Community and ensure the long and prosperous life of the Factom Protocol project.

2.2. Do you have an experience in running business? What kind of businesses it were? Please tell us more about it, so we can understand your strengths and what expect from your ANO if it will be elected.
Yes, individuals within Kompendium have experience running businesses, including:
  • Property management company overseeing three privately-owned rental proprieties.
  • Company managing privately held crypto-assets and the administration of cryptocurrency master nodes as a form of income generation.
  • Technical development consultancy focused on SME sector, maintaining and upgrading C#/DotNet backend codebases, building desktop applications, and automating business logic tasks.

2.3. What a minimum number of hours per week are you going to work for Factom? Do you commit it?
Within our ANO Campaign document, we pledged an average of 30 hours per week and 24/7 on-call. With the addition of Mitchell Berry as our lead developer, these hours will increase. We will seek community grants for technical work on and for the Protocol. If successful, our lead developer could work full time on behalf of the Community. We will also seek additional developers if required to meet our and the Community’s’ ambitious requirements.

Yes. We excitedly and enthusiastically commit to that!

3. Do you participate in any other cryptocurrency projects? If yes, please reveal details.
Although we are not involved in other cryptocurrency projects, we hold non-FCT tokens such as BTC, ETH, GIC, MON, POLY, CVC, and BLT. We stay current on the latest cryptocurrency projects, motivated by a desire to push Factom to the latest, cutting edge technologies.
 
Within our ANO Campaign document, we pledged an average of 30 hours per week and 24/7 on-call. With the addition of Mitchell Berry as our lead developer, these hours will increase. We will seek community grants for technical work on and for the Protocol. If successful, our lead developer could work full time on behalf of the Community. We will also seek additional developers if required to meet our and the Community’s’ ambitious requirements.
At 60% efficiency you will receive approximately 900 FCT a month. At a price point of $5 (which is not unlikely) this amounts to $4500 per month before taxes, company expenses and other overhead.

Will you still pledge to execute on your promises in your campaign document and this thread, including spending 30+ hours a week?

How long could you operate under those conditions? Have you prepared comprehensive budgets to base these pledges on?
 
At 60% efficiency you will receive approximately 900 FCT a month. At a price point of $5 (which is not unlikely) this amounts to $4500 per month before taxes, company expenses and other overhead.

Will you still pledge to execute on your promises in your campaign document and this thread, including spending 30+ hours a week?
Tor, thank you for your questions.

Yes, we emphatically pledge to execute our campaign promises including infrastructure node duties, governance and committee involvement, advocacy and education initiatives, Testnet leadership, and technical development work with the Protocol.

We also pledge to work on the Protocol a minimum of 30 hours a week. This pledge was made when only two Kompendium personnel were available. Now that Mitchell has joined Kompendium, we will be able to dedicate even more manhours elevating and enhancing the Protocol and Community.

How long could you operate under those conditions?
Niels asked a similar question earlier in our campaign. We mentioned that we will conduct strategic reviews at different FCT/USD levels and reserve fund redlines (80%, 60%, 50%, 45%, 40%, 30%, 20%, and 10%) to assess sustainable expenses and operations. During prolonged periods of extremely low FCT/USD ratios, Kompendium will draw on contingency funds to sustain operations.

If operating costs exceed FCT revenue, we will maintain our efficiency levels by temporarily suspending non-Infrastructure initiatives, reducing personal salaries, and focusing on sustaining infrastructure operations. We will fully disclose the situation and negotiate our intended preplanned actions with the Protocol Standing Parties prior to any drastic decision. Once the crisis has passed, we will continue our pledge-aligned operations in support of the Protocol.

If these cost saving measures fail to slow the rate of contingency fund withdrawals, our back up plan is to use personal funds as needed until the operational costs are stabilized.

How long could you operate under those conditions?
Employing the measures above, we should be able sustain operations for an extended period time. If forced to endure low FCT/USD levels for too long, we would reduce our costs and continue making Community and Protocol improvements using community grants. We will always strive to deliver the promises in our campaign document.

Have you prepared comprehensive budgets to base these pledges on?
Yes. We have prepared detailed budgets at various price levels. If stressed, we would seek to sustain our Community pledges by balancing expenses and revenue. Our contingency fund of $30,000 is designed to sustain our core ANO infrastructure pledges for up to one year, assuming extremely low FCT/USD levels.
 

Jay Cheroske

Bedrock Solutions
I've decided to ask all prospective ANOs the following:
  • What experiences do you have running dockerized applications?
  • What are some things you learned while running your testnet servers?
  • How have your ideas about mainnet infrastructure changed as you have become more familiar with running factomd?
Apologies if you have already answered one or more of these somewhere else.
 
Thank you Jay for the question.

What experiences do you have running dockerized applications?
Docker applications with Factom for over a year, we have received multiple training certificates from LinuxAcademy ranging from introductory to advanced Docker applications. Our efforts to increase our familiarity and skills with docker also include reading a number of books including Docker Cookbook by Sébastien Goasguen, Using Docker by Adrian Mouat, Docker: Up & Running by Sean Kane, and Kubernetes: Up & Running by Kelsey Hightower. Mitchell, our newest member and Lead Developer, has the majority of hands-on learning and work experience with containers for our team. In addition to the Factom Protocol, he has significant experience using Docker within his DevOps work responsibilities as well as regular responsibilities in setting up a variety of Docker microservices for past clients. Our education and experience with Docker and containerization is extensive.

What are some things you learned while running your testnet servers?
Docker provides a variety of benefits that allows for rapid and simple management of applications. We have learned there are several techniques leveraging the power of containers. We are exploring ways to automate the set up, troubleshooting, and maintaining of our node containers. Docker has its own idiosyncrasies, and the containers have occasionally inconsistent or unstable. We’ve learned that attention to detail and robust practiced procedures are critical to successfully ensuring zero-error brainswaps and node maintenance. Running an Authority Node on the Mainnet comes with significant responsibility and requires time to both secure our nodes and administer them to maximize stability and security. Kompendium aims to increase utility of the Testnet for the Community, its participants, and ultimately for the improvement of the Mainnet.

How have your ideas about mainnet infrastructure changed as you have become more familiar with running factomd?
We’ve been thinking though our infrastructure for some time, and while selecting virtual servers from the largest cloud providers has appeal, the more familiar we became with running nodes the more we understood the value of geographic and provider diversification. We have therefore designed our node infrastructure to maximize network resiliency. We sought professional and reliable network providers who run top-quality, high performing systems, and selected those who prioritize physical and network security. We ensured our providers were unique within the existing Mainnet Authority Set to maximize network diversity and enhance resiliency, minimizing datacenter outages. Bottom Line: Our infrastructure uses dedicated and virtualized servers, spread over multiple service providers, in geographically diverse datacenters, each with redundant power and broadband providers in order to support and reinforce network resiliency.
 
Thank you for your application and your obvious enthusiasm for the Factom protocol. Thank you too for undertaking the testnet coordination role.
I have two questions:
1) You have undertaken to do a lot and impressively have already been active and also recently increased your resources, nonetheless things are generally easier said than done. When the going gets tough, how will you prioritize what you actually do?
2) What 2 or 3 strategic priorities would you set for the testnet and its use?
 
Thank you for the questions Mike! These are both great questions which we have been thinking about for months and have come to some conclusions.

1) You have undertaken to do a lot and impressively have already been active and also recently increased your resources, nonetheless things are generally easier said than done. When the going gets tough, how will you prioritize what you actually do?
Our core responsibility is the security and stability of the network. This will always be our top priority, particularly when things get tough. We will carry out these responsibilities by optimizing node management and emphasizing thorough node functionality, monitoring, updates, and security in accordance with community best practices. We have detailed response plans for events such as crashes, disasters, and financial hardship to quickly and safely get back online.

Our corporate instructions also include financial redline reviews and reserve capital levels needed to sustain operations. During challenging times, we will remain flexible in our priorities, timelines, and activities until finances improve. If forced to reduce expenses, our non-infrastructure activities (e.g., salaries, marketing, education, advocacy, technical training, etc.) are subject to change. Depending on the situation and severity, we will work with Standing Parties to determine the best sustainable way forward.

Kompendium manages projects and tasks by grouping each member's tasks into 3-week segments. This method maximizes productivity by focusing on complementary and parallel work vice sequential work. We will share with the Community our clearly defined and obtainable project objectives, document issues, goals, and project scopes, while adjusting to cost and time constraints. Our team employs constant, open communication which is critical to defining project parameters, risks, and obstacles. As these projects come to completion, they will be integrated or automated into normal operations and business as usual (BAU). We are also pursuing additional talent and forming relationships with developers to sub-contract work to accelerate objectives and expand services.

Finally, the Factom Community is a critical part of our team, facilitating the completion of our projects and tasks. As we grow and expand, we will seek the counsel and wisdom of the guides and fellow ANOs on recommended priorities and practices. The ANO's, while independent, are bound by a common cause. The strength of the Protocol is directly related to the strength of those bonds. We will join that cause as professional and diligent stewards of the Protocol, seeking the counsel of our fellow ANOs and guides as needed.

2) What 2 or 3 strategic priorities would you set for the testnet and its use?
We have attached a revised list of our Testnet priorities, listed in Milestone order of short, medium, and long-range goals. We are open to discussing these ideas with the Community and Guides to obtain consensus of their prioritization, modification, recommended timelines, and optimum implementation.
 

Attachments

Last edited:
Top