search

filecoin-project / filecoin-plus-large-datasets

Hub for client applications for DataCap at a large scale
109 stars 62 forks source link

[DataCap Application] <VMERA3> - <Metaverse Project>  #1279

Closed szcoolw closed 1 year ago

szcoolw commented 1 year ago

Large Dataset Notary Application

To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.

Core Information

Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.

Project details

Share a brief history of your project and organization.

A Metaverse in our opinion is the real world in a digital space. That's the experience we want our users to have. 

We are a Metaverse that brings together components of Web 3.0 in a highly efficient and synchronized manner such as our Vmeta3 Wallet, Layer-2 Mining, Cross-Chain NFT Marketplace, and Swap. These modules interlock with each other, forming a profitable Metaverse economy hence helping it grow and prosper. The development of each independent module will ultimately improve the growth of any business that aims to harness the Web 3.0 Technology.

We seamlessly and securely facilitate Cross-Chain transmission of informational data, NFTs, and smart contracts across other chains.

Providing a mechanism to exchange tokens between Ethereum scaling solutions and for transferring tokens over a shared layer 1 network quickly and without trust.

Enabling customers with a two-pronged token bridge for Ethereum’s layer 2 networks.

The solution aims to facilitate the rapid movement of a token between layer 2 and a scaling solution’s governance token. 

Using Key Artistic Standards and Instructions based on the Unity engine, the PBR process and emphasizing the real restoration of resources we can truly achieve the relationship between the metaverse and reality,

We understand the requirements of businesses such as virtual fashion that have rigid requirements for expressiveness.

The application of this standard can also expand the types of NFTs and promote the development of NFTs.

We have a unique set of standards that protect the IPs of artists. The original designs minted on VMeta3 Chain will be marked in encrypted files so that the chain will confirm the owner of the NFTs and protect their copyright.

In VMeta3, Digital Identities (DI) are unique online identifiers. A DI is who you are and how you represent yourself in this virtual space. Your DI will have important information about you, like your habits and skills. Having your DI removes the need for physical documentation to prove your identity in the digital world.

Our advertising solution uses blockchain data, a "Peer-to-Peer" advertising solution for sponsors to choose their audiences, and an open source report that shows the marketing expense on the exact audience, ensuring transparency and fairness between audiences and sponsors.

With our virtual fashion technology, you can try on clothes and accessories from the comfort of your own home. The VMeta3 Metaverse is improving how people shop for clothes and accessories. We're making it easier than ever to find the perfect outfit and experience what it feels like to wear them before deciding to buy.

What is the primary source of funding for this project?

Company's own funds and partners' funds.

What other projects/ecosystem stakeholders is this project associated with?

None.

Use-case details

Describe the data being stored onto Filecoin

Videos, pictures, R&D data.

Where was the data in this dataset sourced from?

The data comes from the data provided by the company's research and development department and publicity department.

Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this. 

https://drive.google.com/file/d/1JT_VpYAMhjQyj34T8lMxpNQz-uXuTWkN/view?usp=sharing
https://drive.google.com/file/d/1LMRfBZstqG7ligNj-VlCeFhZjiHPXj7u/view?usp=share_link
https://drive.google.com/file/d/1W5jCMe2qvnoaciZpEKmMfAhGYHVUQAkj/view?usp=share_lin
https://drive.google.com/file/d/1JWsgkTQ0N96vFKNz5D8iP5B1LQTrFNjc/view?usp=share_linkk
https://drive.google.com/drive/folders/1pS3IodBvhk019PdXGcxLfAbrd2GWWFuw?usp=share_link

Confirm that this is a public dataset that can be retrieved by anyone on the Network (i.e., no specific permissions or access rights are required to view the data).

Confirm.

What is the expected retrieval frequency for this data?

About a year or so.

For how long do you plan to keep this dataset stored on Filecoin?

At least 24 months.

DataCap allocation plan

In which geographies (countries, regions) do you plan on making storage deals?

Asian region.

How will you be distributing your data to storage providers? Is there an offline data transfer process?

Both online and offline transmission.

How do you plan on choosing the storage providers with whom you will be making deals? This should include a plan to ensure the data is retrievable in the future both by you and others.

We need a storage provider that can cooperate for a long time. We will choose a reputable storage provider, check their overall capacity and working hours, screen the overall technical strength of miners, and ensure distributed storage and data security.

How will you be distributing deals across storage providers?

We will choose a stable and secure storage provider, and then allocate according to the allocation rules on this basis.

Do you have the resources/funding to start making deals as soon as you receive DataCap? What support from the community would help you onboard onto Filecoin?

Yes ,we have enough funds.
large-datacap-requests[bot] commented 1 year ago

Thanks for your request! Everything looks good. :ok_hand:

A Governance Team member will review the information provided and contact you back pretty soon.

simonkim0515 commented 1 year ago

Datacap Request Trigger

Total DataCap requested

3PiB

Expected weekly DataCap usage rate

100TiB

Client address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

DataCap allocation requested

50TiB

Id

26655d8b-7631-4a2c-be52-9575ee639bc5

Tom-OriginStorage commented 1 year ago

1：can you send email to [[filplus-app-review@fil.org] 2：Can you tell which nodes should be stored？

szcoolw commented 1 year ago

1.yes,i can 2.f01901351 f01830424 f01776264 f01889668

szcoolw commented 1 year ago

vn I have replied. Please confirm it.

Tom-OriginStorage commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacebnu43zenjlfb53my4prhl5t3lqdfy53kr7mu626b76pexkknqkqq

Address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

Datacap Allocated

50.00TiB

Signer Address

f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga

Id

26655d8b-7631-4a2c-be52-9575ee639bc5

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebnu43zenjlfb53my4prhl5t3lqdfy53kr7mu626b76pexkknqkqq

NDLABS-Leo commented 1 year ago

Checked the customer subject information and data samples, willing to support and keep concerned.

NDLABS-Leo commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecb6267bpkmyf6jq2o5f5iwzpd4z7dtm2m7uqs7syic5tiu7g6wse

Address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

Datacap Allocated

50.00TiB

Signer Address

f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei

Id

26655d8b-7631-4a2c-be52-9575ee639bc5

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecb6267bpkmyf6jq2o5f5iwzpd4z7dtm2m7uqs7syic5tiu7g6wse

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Request number 2

Multisig Notary address

f02049625

Client address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

DataCap allocation requested

100TiB

Id

ea6b9deb-03fc-478b-bab7-3148c78022b4

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

Last two approvers

not found & llifezou

Rule to calculate the allocation request amount

100% of weekly dc amount requested

DataCap allocation requested

100TiB

Total DataCap granted for client so far

50TiB

Datacap to be granted to reach the total amount requested by the client (3PiB)

2.95PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
1235 4 50TiB 32.23 9.40TiB
filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

Since this is the 3rd allocation, the following restrictions have been relaxed:

✔️ Storage provider distribution looks healthy.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f01776264 Hong Kong, Central and Western, HK
Hong Kong Broadband Network Ltd.		 12.44 TiB 33.50% 12.44 TiB 0.00%
f01998447 Moscow, Moscow, RU
PJSC MegaFon		 7.44 TiB 20.03% 7.44 TiB 0.00%
f01996698 Orcas, Washington, US
Unknown		 9.13 TiB 24.58% 9.13 TiB 0.00%
f02001667 Berlin, Berlin, DE
Vodafone GmbH		 8.13 TiB 21.89% 8.13 TiB 0.00%

Provider Distribution

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

Since this is the 3rd allocation, the following restrictions have been relaxed:

⚠️ 100.00% of deals are for data replicated across less than 3 storage providers.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
27.50 TiB 27.50 TiB 1 74.07%
4.81 TiB 9.63 TiB 2 25.93%

Replication Distribution

Deal Data Shared with other Clients

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

mikezli commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceawvfqx5l3zyggp7mg3ewsjntw74zmt5fcvnpzcpku5zz2dckorie

Address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

Datacap Allocated

100.00TiB

Signer Address

f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea

Id

ea6b9deb-03fc-478b-bab7-3148c78022b4

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceawvfqx5l3zyggp7mg3ewsjntw74zmt5fcvnpzcpku5zz2dckorie

mikezli commented 1 year ago

no CID sharing Storage provider distribution looks healthy so i would like to support

newwebgroup commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceahy4seeqspkfcyt7tglpqa2wr5i5srs57d2axnxcgd5luu5xecsg

Address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

Datacap Allocated

100.00TiB

Signer Address

f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq

Id

ea6b9deb-03fc-478b-bab7-3148c78022b4

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceahy4seeqspkfcyt7tglpqa2wr5i5srs57d2axnxcgd5luu5xecsg

herrehesse commented 1 year ago

It seems (given my crowded inbox) that in the past 15 minutes @newwebgroup has approved 10+ datacap requests.

I wonder if this blind approval is allowed?

Would like to see per project what due diligence you did to explain the approval @newwebgroup.

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Request number 3

Multisig Notary address

f02049625

Client address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

DataCap allocation requested

200TiB

Id

9ffe3ae8-8ed3-4d88-b8e2-3eb0abff7a76

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1qttvggw2cpaqidpg5luhqvkxu6qmm6x6rvy6zlq

Last two approvers

newwebgroup & DeFIL123

Rule to calculate the allocation request amount

200% of weekly dc amount requested

DataCap allocation requested

200TiB

Total DataCap granted for client so far

50TiB

Datacap to be granted to reach the total amount requested by the client (3PiB)

2.95PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
1495 4 100TiB 35.12 3.28TiB
filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

⚠️ f02001667 has sealed 32.16% of total datacap.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f01776264 Hong Kong, Central and Western, HK
Hong Kong Broadband Network Ltd.		 12.44 TiB 29.09% 12.44 TiB 0.00%
f01998447 Moscow, Moscow, RU
PJSC MegaFon		 7.44 TiB 17.40% 7.44 TiB 0.00%
f01996698 Orcas, Washington, US
Unknown		 9.13 TiB 21.35% 9.13 TiB 0.00%
f02001667 Berlin, Berlin, DE
Vodafone GmbH		 13.75 TiB 32.16% 13.75 TiB 0.00%

Provider Distribution

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

⚠️ 100.00% of deals are for data replicated across less than 4 storage providers.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
33.13 TiB 33.13 TiB 1 77.49%
4.81 TiB 9.63 TiB 2 22.51%

Replication Distribution

Deal Data Shared with other Clients

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

herrehesse commented 1 year ago

@newwebgroup Asking a bot for numbers is not doing due diligence. Please respond to my original question.

szcoolw commented 1 year ago

I don't think they're online every day, just occasionally processing messages, like you.

herrehesse commented 1 year ago

@szcoolw hello applicant, can you help and explain to my why your data fits the Filecoin+ program rules?

"Videos, pictures, R&D data."

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

⚠️ f01996698 has sealed 30.46% of total datacap.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f0153960 Hong Kong, Central and Western, HK
Alibaba (US) Technology Co., Ltd.		 26.13 TiB 23.78% 26.13 TiB 0.00%
f01776264 Hong Kong, Central and Western, HK
Hong Kong Broadband Network Ltd.		 12.44 TiB 11.32% 12.44 TiB 0.00%
f01998447 Moscow, Moscow, RU
PJSC MegaFon		 7.44 TiB 6.77% 7.44 TiB 0.00%
f01996698 Orcas, Washington, US
Unknown		 33.47 TiB 30.46% 33.47 TiB 0.00%
f02001667 Berlin, Berlin, DE
Vodafone GmbH		 30.41 TiB 27.67% 30.41 TiB 0.00%

Provider Distribution

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

⚠️ 100.00% of deals are for data replicated across less than 4 storage providers.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
71.88 TiB 71.88 TiB 1 65.42%
13.00 TiB 26.00 TiB 2 23.66%
4.00 TiB 12.00 TiB 3 10.92%

Replication Distribution

Deal Data Shared with other Clients

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

cryptowhizzard commented 1 year ago

Feb 13 22:00:52 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:00:52.317+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM:\n [/ip4/47.242.95.98/tcp/62353] dial tcp4 0.0.0.0:38697-\u003e47.242.95.98:62353: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0153960\",\"MinerPeer\":{\"Address\":\"f0153960\",\"ID\":\"12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM\",\"PieceCID\":null}}"} Feb 13 22:00:52 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:00:52.317+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 13 22:01:28 proposals autoretrieve: [addressId] => f01920820 Feb 13 22:01:33 proposals autoretrieve: Working with PSP . f02001667 AND client f01920820 Feb 13 22:02:11 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:02:11.831+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM:\n [/ip4/47.242.95.98/tcp/62353] dial tcp4 0.0.0.0:38697-\u003e47.242.95.98:62353: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0153960\",\"MinerPeer\":{\"Address\":\"f0153960\",\"ID\":\"12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM\",\"PieceCID\":null}}"} Feb 13 22:02:11 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:02:11.831+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 13 22:02:31 proposals autoretrieve: [addressId] => f01920820 Feb 13 22:04:57 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:04:57.448+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM:\n [/ip4/47.242.95.98/tcp/62353] dial tcp4 0.0.0.0:38697-\u003e47.242.95.98:62353: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0153960\",\"MinerPeer\":{\"Address\":\"f0153960\",\"ID\":\"12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM\",\"PieceCID\":null}}"} Feb 13 22:04:57 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:04:57.448+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 13 22:06:58 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:06:58.993+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM:\n [/ip4/47.242.95.98/tcp/62353] dial tcp4 0.0.0.0:38697-\u003e47.242.95.98:62353: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0153960\",\"MinerPeer\":{\"Address\":\"f0153960\",\"ID\":\"12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM\",\"PieceCID\":null}}"} Feb 13 22:06:58 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:06:58.993+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 13 22:07:42 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:07:42.665+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM:\n * [/ip4/47.242.95.98/tcp/62353] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0153960\",\"MinerPeer\":{\"Address\":\"f0153960\",\"ID\":\"12D3KooWRV1adkrcTeenh9pt7MxPmUBdeFWAFEA2JT4sbPipjZEM\",\"PieceCID\":null}}"} Feb 13 22:07:42 proposals dealscanner-f01920820-f0153960: 2023-02-13T22:07:42.665+0100#011ERROR#011retry#011retry/retry.go:29#011Failed after 5 attempts, last error: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 13 22:07:42 proposals dealscanner-f01920820-f0153960: ERROR: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 13 22:07:42 proposals dealscanner-f01920820-f0153960:

cryptowhizzard commented 1 year ago

Seems retrievals are not working. Can you check your side please?

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open.

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you!

aggregation-and-compliance-bot[bot] commented 11 months ago
Client f01920820 does not follow the datacap usage rules. More info here. This application has been failing the requirements for 7 days. Please take appropiate action to fix the following DataCap usage problems. Criteria Treshold Reason
Cid Checker score > 25% The client has a CID checker score of 18%. This should be greater than 25%. To find out more about CID checker score please look at this issue: https://github.com/filecoin-project/notary-governance/issues/986