> For the complete documentation index, see [llms.txt](https://hypatia-ai.gitbook.io/hypatia-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypatia-ai.gitbook.io/hypatia-protocol/administration/application.md).

# Application

We have a core team that is currently assembling and are actively seeking out talented developers to fill various positions within our organization. Our team is composed of experts in blockchain technology, distributed systems, and AI, who are committed to bringing this innovative project to life. To ensure the success of our project, we are looking for individuals with specific skill sets and experience in areas such as smart contract development, distributed storage systems, and cryptography. Additionally, we are searching for individuals with a strong understanding of market dynamics and the ability to work in a fast-paced, collaborative environment. We believe that by assembling a team of the best and brightest in their respective fields, we will be able to develop a truly revolutionary proof of storage protocol that will help solve the issues of IP rights and copyright in the NFTs space.

## Blockchain Developers

These developers will be responsible for building the core blockchain infrastructure and implementing the consensus mechanism (in this case, the hybrid proof of storage consensus). They should have a strong understanding of blockchain technology and distributed systems, as well as experience with programming languages like Go, Rust, and C++.

## AI Developers

These developers will be responsible for building the AI algorithms that will be used to regulate the storage of data on the blockchain. They should have a strong understanding of machine learning, computer vision, and natural language processing, as well as experience with programming languages like Python and Java.

## Storage Developers

These developers will be responsible for building the distributed file system that will be used to store the data on the blockchain. They should have a strong understanding of distributed systems, IPFS, and the BitSwap protocol, as well as experience with programming languages like Go.

## Smart Contract Developers

These developers will be responsible for building the smart contracts that will be used to govern the storage and retrieval of data on the blockchain. They should have a strong understanding of solidity, smart contract development and experience with Ethereum and Solana.

## Security Developers

These developers will be responsible for ensuring the security of the blockchain, including the encryption of data, key management, and access control. They should have a strong understanding of cryptography, network security, and smart contract security.

## DevOps Engineers

These engineers will be responsible for maintaining the infrastructure and deploying the blockchain to testnet and mainnet. They should have experience with cloud infrastructure, Linux, and containerization.

## QA Engineers

These engineers will be responsible for testing the code, creating test cases and finding bugs in the code. They should have experience with auto

{% embed url="<https://form.jotform.com/230277350240143>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hypatia-ai.gitbook.io/hypatia-protocol/administration/application.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.