Community Review of LendMi Allocator

[LendMi]

Application Link: (Issues · LendMi-Finance/LendMi-Storage )
Notary Application Form: (https://github.com/LendMi-Finance/LendMi-Storage/issues/1014)
Compliance Report: (https://compliance.allocator.tech/report/f03011025/1728607131/report.md )
Collaborating Client 1: ([DataCap Application] · Issue #10 · LendMi-Finance/LendMi-Stor)
Collaborating Client 2: ([DataCap Application] - <DATA RELEASE 7> · Issue #15 · LendMi-Finance/LendMi-Storage )
Dear FIL+ Governance Team, @galen, @kevin, @filwatchdog,
After onboarding as a V5 notary, we immediately began DataCap allocation. Our first allocation took place on April 30th, but we were not yet familiar with the system at https://allocator.tech/ . During our first round, we intended to approve only 512TiB, but mistakenly allocated 1PiB to [DataCap Application] · Issue #10 · LendMi-Finance/LendMi-Stor .
As a V4 notary, we were accustomed to requesting 1PiB of DataCap, which would then be reduced to 512TiB. However, in the new https://allocator.tech/ system, selecting 1PiB resulted in the entire amount being allocated to the client. This was never our intention; we simply did not yet fully understand the platform.
The Spark system was introduced around May and June, but unfortunately, 80% of our allocations were already completed during April and May, resulting in a low retrieval rate for Spark.
By June, we had fully understood the rules of the https://allocator.tech/ platform and were also familiar with the requirements of Spark. We successfully allocated 512TiB to a new client in June [DataCap Application] - <DATA RELEASE 7> · Issue #15 · LendMi-Finance/LendMi-Storage , and the retrieval rate by the storage provider (SP) reached 50%.
The transition from V4 to V5 brought significant changes in rules, practices, and tools. During this period, our clients were facing high borrowing costs and often urged us via phone calls, emails, and in-person meetings to provide the DataCap they needed. These clients are ones we have known and worked with for over two years, and we have personally assessed their companies and technical capabilities. As a result, we made our allocations more leniently. Unfortunately, we did not provide documentation on our due diligence efforts conducted through other channels like Telegram, email, or in-person meetings on GitHub. We sincerely apologize for this oversight and assure you that we will take greater care in conducting and documenting our due diligence publicly in the future.
We respectfully ask for another chance, and we are committed to showing you our fast progress and diligence.
Our team is based in Singapore, and we are fully capable of communicating in English and traveling internationally. We would be very grateful for an opportunity to hold a call or an in-person meeting to discuss our case further.
Thank you for your time and understanding.