Community Review of Ehume Allocator

[Ehume]

Allocator application: filecoin-project/notary-governance#1048

Allocator pathway: https://www.ehume.com/#/DC

Our pathway supports automatic datacap allocation due to we aim to create a convenient and standardized allocator. Our allocator called a smart contract so that all records can be found on chain. Now we have allocated more than 75% datacap. We want to be reviewed and llok for next round datacap refil.

As one of the first allocators to develop an auto-allocator, there may be something we need to improve in our work. Hope to receive suggestions to help make our allocator pathway better!

[filecoin-watchdog]

@Ehume, I visited your website and provided the wallet address. I understand that all I need to do to receive DC is transfer the appropriate amount of FIL. However, I couldn't find any instructions for your clients or further diligence steps, such as a KYC link, redirection to the application, etc.

Please provide some bookkeeping and reports of your actions, but until then, I've got several questions:

• How do you conduct conversations with clients? What is the communication path?
• What is the non-automated claim pipeline that you mention on your website?
• How is KYC conducted? You wrote on the application that you will use 3rd party KYC verifications, but are they conducted? If so, where are their results stored?
• How do you verify SPs (retrieval rate, quantity, regions, duplicates, etc.)?
• How do you check the number of replicas?

After reviewing your allocator application, I have many more questions, but I am hopeful that some will be answered by reporting and bookkeeping.

[filecoin-watchdog]

@Ehume, Have you had a chance to see the above comment?

[Ehume]

Hello @filecoin-watchdog,

Our original goal for designing the allocator was to make an automated one. But as the community's need changes, we are constantly improving our designs. It's an experiment. We had talked to Molly in Singapore about this idea as well and she was very supportive of us doing some contributions to paid storage.

Ehume's allocator will be a completely innovative automated allocator, and there maybe not a similar design in fil+ community today. We have offered to communicate our thoughts on slack, but have not gotten an effective response.

As our understanding, the community would prefer to see more automated allocators

But in any case, we still want to continue our ideas and the community can explore it with us:

1. We're an automated allocator, so it's just as easy for clients to use it as Glif and doesn't require an application to be submitted. But we won't allocate a little amount datacap to sps because it makes little sense to them.
2. We're not a manual allocator, so the maximum amount per round will be limited to 256TiB, not 2PiB or even more.
3. We do not sell datacap, but clients are required to pay a deposit corresponding to our notice on website before storing. Clients can withdraw their deposit from the pledge after fulfilling our basic requirements (at least 5 SPs and retrieval rate of >95%).
4. Clients who do not fulfill the requirements, their deposit will be deducted and sent to the their SPs, which are supposed to get the stored income from them.
5. We plan to execute the above criteria in the following allocations.

We will regularly summarize and publish client allocations and sp's retrievals results in our github repo https://github.com/Ehume/Ehume

We hope to reduce the time that clients spend waiting and getting datacap, and give clients a better experience. We don't think clients who are willing to pay should have to wait for a long time to get datacap.

Hoping to get more advice from Fil+ community on how to build our automated allocator, thanks!

[filecoin-watchdog]

@Ehume Thanks for the context. Could you answer the questions I asked in my first comment? Without answers, any review of your allocator is impossible.

I would also like to know where the regular summarization is posted within the Ehume repo presented. I couldn't find any, so please point me to it.