Emulvera LLC

David Chapman

Factomize
Thank you for the application. Let's get started:

A. Can you comment on your private data center in NV? In your garage? 1 mile below ground in Area 51? Any specifics you're able to provide would be appreciated.
 

David Chapman

Factomize
B. Based upon your stated Efficiency of 70% (with one server) and your estimated expenses, at what USD price does FCT need to be for your Authority Node operation to break even on a monthly basis with one server?
 

Jason Gregoire

Kompendium
Thank you for the application. Let's get started:

A. Can you comment on your private data center in NV? In your garage? 1 mile below ground in Area 51? Any specifics you're able to provide would be appreciated.
-The private datacenter is located at 4730 S Fort Apache Road, Las Vegas, Nevada 89147. It is a large corporate complex housing several medium to large business. The building contains a private datacenter to host and storage resident corporations' servers, IT, and communications equipment. One of our team members (David Gregoire) is the IT department chief for one of the major building tenants and we intend to lease available rack space to house our physical dedicated servers. The datacenter obviously has dedicated power and back up power systems. Broadband services are available from multiple vendors that support the center. We intend to contract Stimulus Technologies for our bandwidth needs to the physical servers; they offer scalable bandwidth 200Mbps to 1Gbps. If our bandwidth needs increase in the future, there are other vendors that offer greater bandwidth rates. If we need to scale beyond the private data center, there are several very reputable commercial datacenters in near proximity within Las Vegas.
 

Jason Gregoire

Kompendium
B. Based upon your stated Efficiency of 70% (with one server) and your estimated expenses, at what USD price does FCT need to be for your Authority Node operation to break even on a monthly basis with one server?
-With one server, with zero staking, based on our monthly cost estimates, our lowest break even point occurs at a monthly average Factoid sales price of $18.20. At higher average Factoid prices ($25 and more), our costs will increase to support investment in our server infrastructure to handle future scaling needs. We also aim to stake at least +5% per month.

Thank you
 

Jason Gregoire

Kompendium
What happens to your operation if the value of FCT goes down to $10.00 and stays there for a six months due to a broader bear market?
-My team and I have discuss this possibility. We have drafted several contingencies that we are confident will allow us to weather the storm and ensure we maintain professional server services in support of our authority server(s). We have approximately ~$20,000 to help us start up and we expect that the sizable remainder will be escrowed as a "rainy day/month" fund to support future unfunded operating costs. We intend to replenish the "rainy day" fund to always maintain flexibility for crisis management. In a significant and prolonged market Factoid downturn (~$5-10/Factoid), we plan to reduce personnel costs and ultimately decrease efficiency. Our top priority is to maintain our professionally administration of our authority server(s) in support of the protocol. If the Factoid market suffers a prolonged period of average prices of ~$5-$10, only as necessary, we will reduce our server operating efficiency: at sustained average price of $10/Factoid we estimate that we could still operate with an efficiency of 55% and break even under our lower cost model; however, at an average price of $5/Factoid we would need an efficiency level of 25% or lower to breakeven.

Thank you
Jason
 

David Chapman

Factomize
D. Let's say you get an Authority Node. How it performs will be easy to monitor. However, as part of your campaign you also discuss additional development work starting in 2019 which is important despite your efficiency being set at 70%. The Standing Parties will likely want to see what progress you're making since it was part of your campaign. My questions are:

1. How would you communicate with the Standing Parties. Examples would be blog, twitter, Discord, Reddit, etc.
2. What would you communicate and how often?
3. What metrics should be used to gauge your success?
 

Jason Gregoire

Kompendium
C. Do you have any thoughts on what sort of software your company would develop beginning in late 2019?
Thank you for the question. We identified late-2019 to 2020 as a target timeframe where we hope to be in a position to expand our company to further support the growth and maturity of the protocol. If selected, we will work to identify protocol use cases, likely with the use of industry consultants, that have commercial promise for adoption and seek out companies that are willing to partner and refine the use cases to validate their viability. The industry we currently feel that offers several use cases that are potentially well-suited for solutions based on the Factom protocol is the Laboratory Sciences industry (see attached Emulvera_Introduction.pdf). By 2020, we hope to have significant experience managing the protocol, an established positive reputation within the Factom community, established relationships with companies within our use case industry, and a social network of software engineers and application designers knowledgeable with the protocol and the targeted industry that we will be able to leverage to raise funds to expand the company, hire a team of talented software/business professionals, and bring our use cases to life.

To date, our team's use case roundtables and conversations with people that work in biological laboratories currently point to software that would aim to facilitate traceability and proof of process. I've attached an academic paper that discusses some of the challenges that we currently feel could be solved to a great extent through a version of "Factomization." We envision developing software that would be in nearly all aspects invisible to the user that runs in parallel with already existing data management programs that track laboratory specimens, where they came from, where they are stored, the conditions they were stored in, the test required, who ordered them, what/when tests were perform, what machine performed them, when the machine was last calibrated, results of the calibration test, and when the test results were reported and to whom. These are just a sample of the data we would need for proof of process and traceability. Currently, several systems, often without any interoperability, record most of the information above, but these programs often are extremely expensive, are incompatible with each other, and are difficult to operate. If this use case proved to be viable, we would aim to produce software that is compatible and that runs in parallel with the different programs/machines handling the data. Our software would create consolidated audit histories of specimen life cycle within the laboratory, and automatically transmit a proof of the audit and completeness of process to our company, which would automatically hash the proof into the blockchain. Audit, traceability, and proof of process reports would be tailorable to be sufficiently meet federal and state regulatory compliance. Emulvera would maintain the back end of the software that actually interacts with the blockchain and buy and spend entry credits. For these services, as well as an ability to conduct analytics of company processes/data etc. and produce reports, we envision companies paying a simple subscription service.

The above is only our initial ideas/planning. These things unfortunately take a long time, and rarely come out the way we intend in the beginning. The true work will be in working closely with industry consultants in every step of developing use cases and eventually, if viable, coordinating the development of the products to ensure they are actually bringing value to the customers. We have other use case ideas, but they are not as refined, and are very similar in the service ultimately performed. We envision that the software back end residing with the company interacting with the Factom protocol would be the same for all the use cases, the difference will be in the front end, that will be industry specific, and tailored for broad integration and compatibility with industry used data management programs.

Thank you
 

Attachments

Jason Gregoire

Kompendium
D. Let's say you get an Authority Node. How it performs will be easy to monitor. However, as part of your campaign you also discuss additional development work starting in 2019 which is important despite your efficiency being set at 70%. The Standing Parties will likely want to see what progress you're making since it was part of your campaign. My questions are:

1. How would you communicate with the Standing Parties. Examples would be blog, twitter, Discord, Reddit, etc.
2. What would you communicate and how often?
3. What metrics should be used to gauge your success?
Thanks for the questions. Its great to talk through this processes - there are so many exciting things happening with Factom.
1. How would you communicate with the Standing Parties. Examples would be blog, twitter, Discord, Reddit, etc.

-We currently have secured two web domains, www.emulvera.com and www.factomal.com. It is our intent to use the website(s) to facilitate our interaction with the public, community stakeholders, and industry partners. We aim to have a blog of sorts to log/promote developments regarding Factom, and efforts my the greater Factom community and other authority set companies Emulvera, as well as select news within industries related to our development of protocol use cases. We envision also leveraging Reddit and other media outlets to publish and link to our website blog/forums.

2. What would you communicate and how often?

Regarding the what, please see our response above. For the frequency of our reporting, we feel it would likely be driven by progress, events, and/or milestones driven. That being said, if the greater M3 authority set an established expectation of a "state of the community" report produced and published periodically (biannually or maybe quarterly), we would be happy to detail our activities, progress, projects, and forecasts to the greater community. We value transparency (hence Emulvera=pursuit of truth) and to ensure good stewardship of the present and future protocol; therefore, we feel a consolidated an comprehensive means to communicate what those charged with hosting the protocol are doing valuable.

3. What metrics should be used to gauge your success?[/QUOTE]

We feel that our number one priority is the responsible and professional hosting and stewardship of the Factom protocol. We will judge ourselves by our ability to maintain our high efficiency rates while keeping our promise of high reliability and professionalism. (Our prioritization of our efficiency is to ensure there are significant resources available for those that posses the technical means and capabilities to best and rapidly develop and improve the protocol for everyone.) We also agree we should eventually be held accountable to meet some minimum of industry engagement or use case exploration as well as development of a website with a mechanism to promote to the greater Factom community all things Factom and to include what we are working.

Thanks for taking this seriously, you all are doing such a great job.
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
Thank you for your application.

NK01)
Will the 3 of you be working full time from the start? If no could you give us a rough overview of the amount of hours each will be dedicating?
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
NK02)
-The private datacenter is located at 4730 S Fort Apache Road, Las Vegas, Nevada 89147. It is a large corporate complex housing several medium to large business. The building contains a private datacenter to host and storage resident corporations' servers, IT, and communications equipment. One of our team members (David Gregoire) is the IT department chief for one of the major building tenants and we intend to lease available rack space to house our physical dedicated servers. The datacenter obviously has dedicated power and back up power systems. Broadband services are available from multiple vendors that support the center. We intend to contract Stimulus Technologies for our bandwidth needs to the physical servers; they offer scalable bandwidth 200Mbps to 1Gbps. If our bandwidth needs increase in the future, there are other vendors that offer greater bandwidth rates. If we need to scale beyond the private data center, there are several very reputable commercial datacenters in near proximity within Las Vegas.
Could you elaborate on the backup power systems? Is the power redundant? If you were to rate the datacenter from Tier 1 to Tier 4, which one would it be?
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
NK03)
You have a dedicated server for node 1. Could you give us some insight on the number of disks this server hosts?
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
NK04)
In this thread you talk about scalable bandwidth from 200 Mbit to 1 Gbit. In your application you state 1 Gbit. What is the exact bandwidth you will be buying?
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
NK05)
If selected will hire a company that monitors all servers for security threats/DDOS attacks and that will be able to proactively take measure (surge available bandwidth, etc.) to ensure all servers remain fully operational.
I read several times that you will be relying on an outside security company for monitoring security threads.
Will you be relying on this outside company for this type of monitoring? Could you elaborate on a yes or no answer?
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
NK06)
We’ll leverage server monitoring applications to alert all team members (24/7) of emergent issues with our servers (stalling/offline/connectivity loss, critical error, cyber-attack, etc.).
Could you elaborate how you will detect these issues and include at least the "stalling"?

How would the team members be alerted?
 

Niels Klomp

BI Foundation
Core Committee
Governance Working Group
NK07)
Could you supply us with some information about redundancy in the dedicated server components, it's network and power supply?
 

Jason Gregoire

Kompendium
NK02)

Could you elaborate on the backup power systems? Is the power redundant? If you were to rate the datacenter from Tier 1 to Tier 4, which one would it be?
Hello Niels,
The datacenter for Node 1 would be rated a Tier 2. Power is non-redundant. Server tower would sit on a dedicated circuit, with short term back power - (hours-battery power supply system). Our contingency plan is for a long-term power disruption, we plan to transfer the authority server virtual identity to a VPS. We will run a combination of dedicated serves as well as VPS to offer us redundancy to ensure continuous uptime.

Thank you
 

Jason Gregoire

Kompendium
NK04)
In this thread you talk about scalable bandwidth from 200 Mbit to 1 Gbit. In your application you state 1 Gbit. What is the exact bandwidth you will be buying?
We will be subscribing to 1Gbps service. For future scalability of rates greater than 1Gbps, we'll need an alternative provider.
 

Jason Gregoire

Kompendium
Thank you for your application.

NK01)
Will the 3 of you be working full time from the start? If no could you give us a rough overview of the amount of hours each will be dedicating?
Niels,
Of the three of us, the majority of the tech work will be done by one member (David). He is collocated with the physical servers and runs an IT department of one of the companies resident in the building. He is the network/server lead for our team. He will also be the one who will chiefly monitors both virtual and physical server performance. He will be on call 24/7 to either remote in, or physically work with the servers. He will be full time. I would estimate that in addition to being on call, he will be working ~30-40 hours per week in some capacity with our authority server responsibilities.

For Tommy and myself, I anticipate our weekly hourly work totals to be 15-30 hours per week. We'll be handling all corporate matters, accounting, finances, administration, contracts, services, payroll, website content, testnet presence, and our primary discord presence. While I believe only the guides have the superhuman capacity to read everything on the Factom Discord Community, we will attempt to keep up and continue involvement in the governance, administration, and functioning of the community testnet. Tommy and I also will have sufficient technology and capability to remote into our servers 24/7 when required to ensure rapid response/updating etc.; however, David has the lead as he is our team's technical subject matter expert.
 

Jason Gregoire

Kompendium
NK07)
Could you supply us with some information about redundancy in the dedicated server components, it's network and power supply?
Hello Niels,

This is David. Power supply redundancy is handled by 2 460w power supplies hooked up to separate UPS systems. Network redundancy is handled by the host having 4 1gb uplinks divided into 2 groups over 2 switches.
 

Jason Gregoire

Kompendium
NK05)

I read several times that you will be relying on an outside security company for monitoring security threads.
Will you be relying on this outside company for this type of monitoring? Could you elaborate on a yes or no answer?
Niels,

David again. We've contacted a few DDoS protection companies that are specialized in being able to monitor traffic and provide real time bandwidth to absorb up to a 1tbps DDoS attack. They also employ other tactics to analyze and distinguish incoming traffic. So yes, we would ideally hire the company to monitor our servers, which would provide us with redundancy to our own organic monitoring tools. We believe in the planning stage that two is likely better than one watching the servers especially since we are not yet sure how hostile the environment will be operating Mainnet Authority Servers.
 
Last edited:

Jason Gregoire

Kompendium
NK06)

Could you elaborate how you will detect these issues and include at least the "stalling"?

How would the team members be alerted?

Hello Niels,

David again. I don't think stalling was particularly well defined but methods to detect "stalling" would include latency alerts and disk alerts on the host. These type of alerts, along with several others, relating to our server would be coming from a monitoring server that has access to the host hardware. The team will be notified by Email and SMS.
 
Last edited:
Top