Amphi is a decentralized intelligent language service marketplace. Solve the translation needs of web3 projects like DAO, Gamefi etc, and become the best choice for Web2 translators to join Web3.
Amphi is a decentralized intelligent language service marketplace, a new model in language service industry. DAO translation weakness and Amphi opportunities
Amphi is made for translators, translation organizations or freelancers can get bounty here. In Amphi, we provide statistical tools and personal IP creation paths in the language industry. Amphi aims to provide one station language service solution, not only settlement in cryptocurrency but also letting translators accept bounty, translation management, and asset transactions.
Web2 language service industry weakness and Amphi opportunities There are 4 characters translator, validator, project manager, and translation buyer in web2.
In Amphi, the validator has the responsibility to control the translator's translation quality, if the translation quality is under standard, it will affect the validator's benefit as well. The final translation quality will decide by the translation buyer. If the translation buyer has a quality problem, they can ask for modification. if there is a different opinion they can propose a vote. In Amphi, we control the whole decision time within one week, and the translator and validator will get paid within one week after completing the task. In Amphi, there is no arrears problem.
The problem we meet has a lot, there is always encrypt files demand in the language industry, and how to encrypt each file and decrypt it to different people smoothly in web3 is very tricky, because the ipfs or filecoin does not have the related function. In the first beginning, we choose pinata, it can encrypt and decrypt a whole task , and can not encrypt each file under a whole task, we spend a very long time discussing this problem, but there is no better way to solve it, until the last 3 days to submit project we saw lighthouse, they can solve this problem better, and when we try to encryption each file we found the string is not supported by encryption node, which means that we can only encrypt and decrypt the entire task, or we change the smart contract, meanwhile, the single file has the risk of leakage. To solve this problem we communicate with lighthouse team, and they responded very quickly and give us a solution that made big progress in our project.