Thread created for questions to be asked by guides as detailed in Doc 104 - Authority Server Application Process.
It's very important to note that the proper nomenclature here is that you'll be operating at 50% Efficiency. You won't be deferring any income as you'll never receive that FCT because you're operating so efficiently.Defer a minimum of 50% gross income to the Protocol Grant Pool to foster further development
Could you elaborate how this is "visible" by all team members. What is the mechanism behind it?
Could you explain what you mean with "high availability" in this context? Could you also do the same for the term "highly available server infrastructure" in chapter 3 on the same page?Provide multiple high availability and elastic Authority and Follower nodes while maintaining
What do you mean with "invest back" in this context?In order for this community and project to thrive, all contributing members
should continue to invest back as an act of good faith and belief in the underlying project and platform.
Good Afternoon,TH #1
Could you please expand on this:
Is your monitoring connected to this is well?To answer your questions:
NK01) - We use an enterprise ticketing system called TeamWork Desk. Part of its core functionality is to have designated support personnel alerted and copied on incoming tickets. Whenever a someone sends an email to firstname.lastname@example.org, a ticket is generated within the system and a copy is sent to all agents so that they are able to view, assign a resource, respond, add notes, etc. This keeps us organized with a central channel of communication, and allows for rapid response.
So the public key and it's passphrase is the 2FA you mentioned in your application?To answer your questions:
NK05) - Yes, this is referring to the passphrase connected to the authentication key The key pair was generated on a separate secured host using a long complex passphrase before being imported into AWS. SSH login requires public key and password authentication factors.
Could you confirm. We are talking about systems with high uptime and not about HA systems?To answer your questions:
NK06) - In both cases we have a similar meaning for the term "high availability". In the first case, we are referring to our goal of providing systems with four 9's of uptime (99.99%). In the second case, we are referring particularly to experience managing systems with availability requirements set by upper management. This a key reason we chose to go with a cloud infrastructure vs on-premises for the Factom use case.
Thank you. Could you elaborate on the fail2ban setup. What is monitored for instance?To answer your questions:
NK08) - The shared memory space permissions have been restricted to read-only by default, but can be modified to allow for read/write if needed for the Factom services. The SSH service has been configured to a non-standard port, inbound firewall rules are set to individual source IPs, public key + password authentication required for login. Fail2Ban service installed and configured. ipv6 is disabled.
Niels,Could you use the quote functionality on a individual basis please? Then we have context. Thx
Some follow up questions.
Is your monitoring connected to this is well?
In Section 6 of our team introduction, the intent was not to imply that all teams should strive to meet 50% efficiency, as there are certainly many other ways to invest back into the project and community, such as time or services. In fact, in addition to our efficiency, we plan to also offer ourselves as a cybersecurity resource to other selected teams and the community as a whole. Currently, we work with several prominent blockchain projects, and we have designed a playbook as well as protocols in order to protect crypto holdings by businesses and at the individual level. Given the fact every team chosen to host nodes in the Authority Set will be given FCT, we want to provide our expertise to help them protect their funds.Yes but you suggest that other operators should strive to do it as well (50%). Aren't there other ways to "invest back"?
B. 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 (though not well-defined) which is important as well. 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?
I am a bit confused as to what you mean here, could you please elaborate? Are you referring to HA systems as something like a clustered ESXi environment, a fault-tolerant SAN, or a redundant GLBP routing configuration, as opposed to a high uptime system? If so, then yes we have worked with and managed HA systems and infrastructure.Could you confirm. We are talking about systems with high uptime and not about HA systems?