Post #31915

d71f7c6d72b75d99eed18e7423636635c4957c5b04b8d2c6f973021259014686
bbbb20ce08e14026ec0c1cebc7b0154ff7b5215fbc67929dd63f3217838f33dc
e2c61429397da55a5ee7749088023feb12e0e8e261dfeba32ee7c0794f9a12f8
Signature verified

The signature from the blockchain entry has been verified against an identity on this server.

{"entry_date":1616194026,"post_data":{"edit_count":0,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"cb02ec39b4567e5ea2df28dca03651f18e7661d2fcd134887e9dacc637d4c4061c50c4fd8cf89f9f3e325cf2338d1bf59a27bf64e60aae543870000bb34975ee","node_id":59,"post_date":1616194027,"thread_id":5705,"title_sha512":"cb34bcec8f0288199b4a3d954bca7dd625a557b97422ebca987aef13214ab33c27307f5e11835626b75b591546ac7e07770af2d0c06d5e9418db47177099ce82","user_id":17},"post_link":"https:\/\/forum.factomprotocol.org\/threads\/ano-application.5705\/post-31915"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
ANO Application
This is the initial application for Innovative Secured Connection (ISC) and they will use this area for updating the Standing Parties regarding their contributions to the Factom ecosystem. The following are their answers to the application questions:

[SIZE=6][B]Provide an overview of your entity or company.[/B][/SIZE]
ISC works in the transportation industry to deliver verifiable data to stakeholders that may not have access at present.

[SIZE=6][B]Bios for your workers who will be working on Factom[/B][/SIZE]
[B]Name:[/B] Matthew Whittington
[B]Info:[/B] [URL]https://www.linkedin.com/in/matt-whittington-320a461a/[/URL]

[B]Name:[/B] Jim Luciano
[B]Info:[/B] [URL]https://www.linkedin.com/in/jim-luciano-b745ab10/[/URL]

[SIZE=6][B]Is your company currently incorporated?[/B][/SIZE]
No

[SIZE=6][B]If you are incorporated, what is your legal structure. e.g. Inc, LLC, etc?[/B][/SIZE]
Delaware LLC

[SIZE=6][B]If you are not incorporated, when do you plan to do so and what legal structure will you use?[/B][/SIZE]
In Process

[SIZE=6][B]Are any shareholders with a 10% or higher stake in any way involved with an existing Authority Node Operator. If so, please state who and describe the relationship.[/B][/SIZE]
Matt Whittington worked at Factom, Inc from 2015-2019

[SIZE=6][B]Explain what proactive approach you will take to manage the financial aspects of your business[/B][/SIZE]
Funding to move from POC to pilot is expected to close in the next week. Funding for the required servers is a small step up from what we are already going to be maintaining.

[SIZE=6][B]What is your motivation for becoming an ANO?[/B][/SIZE]
Factom entries are part of our process. Because of this, the health of the Factom network is a going concern. Being an ANO gives us official standing with an integral part of our system. Being an ANO also gives us access to Factoids that we can convert into Entry Credits. FCT availability is occasionally spotty in US markets and we would like to be confident in our access to them.

[SIZE=6][B]What vision do you have of the future of Factom?[/B][/SIZE]
We believe in the original vision of the Factom Blockchain for a public, low-cost, censorship-resistant, store of proof that was the ethos as early as Milestone 1 of the Factom Blockchain.

[SIZE=6][B]What is your commitment to the Factom protocol; what have you brought to the table already?[/B][/SIZE]
Our process is bringing transaction volume to the blockchain as well as another real project built upon it. We will also be a responsive ANO at a time when a few are losing confidence. We are not currently planning on Core or Grant work, we will be active in the discord, forum, and governance activities.

[SIZE=6][B]What is your future commitment to the Factom protocol; what will you bring in the future?[/B][/SIZE]
When our business expands to need them, we plan on pushing and funding beneficial FIPs. It has been a while since we have seen a pause in the blockchain, we would like to see a less fragile restart and update process. We would also like to contribute to a sharding implementation.

[SIZE=6][B]Are you running servers on Testnet?[/B][/SIZE]
No

[SIZE=6][B]If you are running servers on Testnet, approximately when did this start?[/B][/SIZE]
2021-03-31

[SIZE=6][B]How many servers do you plan to run on Testnet?[/B][/SIZE]
0

[SIZE=6][B]For mainnet server 1, what country will the server be located in, what city, and what data center or VPS provider/region will you utilize?[/B][/SIZE]
Some of our business services are Microsoft-based, so we are currently planning on Azure South Central and North Central Virtual servers. We are not married to this. If the US ANOs are already Azure heavy, we can change that determination to contribute to Factom stability.

[SIZE=6][B]For mainnet server 2, what country will the server be located in, what city, and what data center or VPS provider/region will you utilize?[/B][/SIZE]
Some of our business services are Microsoft-based, so we are currently planning on Azure South Central and North Central Virtual servers. We are not married to this. If the US ANOs are already Azure heavy, we can change that determination to contribute to Factom stability.

[SIZE=6][B]Are your mainnet servers currently online?[/B][/SIZE]
No

[SIZE=6][B]Confirm that, if elected ANO, your servers will adhere to the minimum specifications (level 1) described in Doc 202.[/B][/SIZE]
Agree

[SIZE=6][B]Do you intend to surpass the minimum specifications (level 1) listed in Doc 202? If yes, describe the specifications of your servers in detail.[/B][/SIZE]
We are looking at 8 processors, 32 GB Ram, and 64GB drives. These are a little over the minimums but look acceptable.

[SIZE=6][B]Who on your team are able to admin the servers?[/B][/SIZE]
Matt Whittington will be the primary administrator for the time being. As our company expands, others may take on that role.

[SIZE=6][B]How many combined years of experience do you have of running production servers?[/B][/SIZE]
10

[SIZE=6][B]Describe production servers you have managed.[/B][/SIZE]
10 is a loose estimate.
2018-2020 - Recycling points network comprised of the company website, API servers, database servers, and multiple devices acting as collection and advertising hubs.
2014 digital currency exchange
The late 90s to 2012 multiple production-grade systems responsible for tens of millions in revenue.
These were not 'modern cloud-based enterprise networks', but running a handful of ANO and follower servers is not either.

[SIZE=6][B]Have you run any servers for any other protocol, if so, which?[/B][/SIZE]
Occasional nodes for other blockchain projects, but nothing at enterprise scale.

[SIZE=6][B]Have you run follower nodes outside of the Authority Set on testnet?[/B][/SIZE]
Yes

[SIZE=6][B]How will the team administer the Authority Nodes?[/B][/SIZE]
No

[SIZE=6][B]How would you handle an unscheduled restart of an Authority Node?[/B][/SIZE]
There are two types of unscheduled restarts. The first is an unplanned outage. In that case, we will go to the discord server and notify the other ANOs of the situation. We will then ensure that bringing them back up is in a safe manner for the network that will not disrupt elections. The second is a 'planned' unscheduled restart. In this case, we will use discord to notify the other ANOs and ensure that a restart will not conflict with any other ANOs. We understand that elections can be fragile sometimes.

[SIZE=6][B]How are you going to make sure your Authority Nodes operate securely?[/B][/SIZE]
Authority nodes should only be open to access for Factom specific connections. System software will be kept up to date to avoid known system vulnerabilities. Limited access via ssh will be used to access the servers. Federated or Audit servers will not be exposed for transactional uses. Followers will be maintained for that.

[SIZE=6][B]How are you going to make sure you respond quickly to unscheduled downtime?[/B][/SIZE]
Downtime response will be based around the discord server. There will be internal and external monitoring of the Factom services on our concerned machine(s). Any notification from them will cause a visit to the Discord server to see if coordination is needed for a response. Technical staff will be added as we move through our pilot rollout.

[SIZE=6][B]Could you describe how you would see your ideal Authority Node infrastructure?[/B][/SIZE]
Ideally, for each Authority Server, there will be one or more followers. The Authority node is locked down while the followers act as the outside interface and possible failover servers for the Authority node. As followers, they should have an up-to-date blockchain on hand to be able to quickly switch roles. At one time, guard servers were planned, but I do not think they were implemented.

[SIZE=6][B]What is the planned availability of the maintenance team?[/B][/SIZE]
Currently:
Matthew Whittington is primary. On-call 24x7
Jim Luciano is backup for Matthews's unavailability, either planned or unplanned. BOTH should be notified of issues as they happen with Matthew being the one expected to respond.

[SIZE=6][B]What efficiency will you operate at?[/B][/SIZE]
50%
This is the raw content, without BBCode parsing.
Top