forked from filecoin-project/Allocator-Governance
-
Notifications
You must be signed in to change notification settings - Fork 0
[DataCap Refresh] 3rd Review of RKH flow #3
Copy link
Copy link
Open
Description
What type of Audit did you opt into? Choose from dropdown
Public Open Data
What is your JSON hash (starts with 'rec')
rec1aSx8GP4jczIYu
Link to your allocator operations description
1
Compliance Report
1
Previous Reviews
- [1st review] Outcome: PiB
- [2nd review] Outcome: PiB
(Add more review blocks as needed)
Client Allocation Table
| Client ID ("f...") | Client name | DC granted |
|---|---|---|
| f345678 | Client 1 | 0 PiB |
| f456789 | Client 2 | 0 PiB |
| f561234 | Client 3 | 0 PiB |
Client-specific Breakdown
Client 1
I. Client Name
- DC requested:
- DC granted so far:
II. Dataset Completion
(Provide deal(s) containing sample(s) of data)
III. SP Match
(Does the list of SPs provided match the list in the CID report?)
IV. Replica Count
Promised vs delivered:
V. SP Retrieval Performance
| SP ID | % retrieval | Meets >75%? |
|---|---|---|
| f01234 | 83% | YES |
Client 2
I. Client Name
- DC requested:
- DC granted so far:
II. Dataset Completion
(Provide deal(s) containing sample(s) of data)
III. SP Match
(Does the list of SPs provided match the list in the CID report?)
IV. Replica Count
Promised vs delivered:
V. SP Retrieval Performance
| SP ID | % retrieval | Meets >75%? |
|---|---|---|
| f05678 | 91% | YES |
(Add more client blocks as needed)
Notes from the Allocator
1
Issues or discrepancies reported?
1
Steps to minimize unfair or risky practices
1
Value to the Filecoin ecosystem
1
Confirm you maintained your application standards for all client allocations
Yes
Do you understand that a diligence review will follow and require updates to this issue?
Yes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels