[DataCap Application] XHash - XHash data

[qituo]

Large Dataset Notary Application

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

Core Information

• Organization Name: XHash
• Website / Social Media: https://xhash.com/
• Total amount of DataCap being requested (between 500 TiB and 5 PiB): 5 PiB
• Weekly allocation of DataCap requested (usually between 1-100TiB): 100TiB
• On-chain address for first allocation: f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

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.

XHash is a Web3.0 infrastructure provider, our version is to build a stable, reliable, and secure blockchain infrastructure, provides POS staking service and multichain API to improve Web3.0 development with our customers.

What is the primary source of funding for this project?

Staking service fee & APIs prepaid fee.

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

No

Use-case details

Describe the data being stored onto Filecoin

video,pictures,data,logfile,Blockchain data snapshot ,web3.0 application data ,user valid data.

Where was the data in this dataset sourced from?

Own Servers. 

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/1uMJ7Shgl2b_SnwKygX-sl175jM99hWK1/view?usp=drive_web
https://drive.google.com/file/d/1Aa9Mx80Z94r4Frd6k4ktcgOh8HykcA9_/view?usp=drive_web
https://drive.google.com/file/d/1Ix7xS2JmafrzFctiC8AvMLo_ugBaNnTc/view?usp=drive_web
https://drive.google.com/file/d/1Mz6_9ERwmN5Za5l1hClecdEN7u-zRulj/view?usp=drive_web

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).

Yes.

What is the expected retrieval frequency for this data?

2-3 times a year.

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

Most of data is required to stored permanently. 

DataCap allocation plan

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

Asia.

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

We plan to transfer data offline。

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're selecting the SPs with high reputation on slack  . They have the ability to store deals at a very fast pace and a high success rate.

How will you be distributing deals across storage providers?

We plan to find more than 5 SPs and distribute the deals equally.

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?

We are contacting SPs and don't need community help at this time.

[large-datacap-requests[bot]]

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

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

[qituo]

Is there any problem with my information?

[qituo]

@raghavrmadya @Kevin-FF-USA
Is there any problem with my application? It has been 2 weeks since I was in a hurry to store it. Please help me

[raghavrmadya]

I'm unable to access the data samples. Also please provide more detail on what you are storing exactly

[qituo]

Data samples provided, The first one is some data of the project. The first one needs to be unzipped and opened The second - fourth is some log data, which can be opened with a text editor Please check again Thank you

1: We have made some videos and pictures to help others understand our product operations, including API usage, node building, and staging operations. This data includes

2: We have made many project pictures and publicity pictures

3: There is a lot of log data in the project, because our program extracts all the node data of BTC, ETH, TRON, BSC... chain, which generates more log information

4: We extracted and stored all historical transaction data of BTC, ETH, TRON, BSC, etc., provided API query services, and analyzed the original data to generate a lot of statistical data

5: Some public data of our users

6: Some monitoring data of our project;

[raghavrmadya]

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

100TiB

Client address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

[large-datacap-requests[bot]]

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

DataCap allocation requested

50TiB

Id

a652c7b7-8141-4a32-9a5c-5f3cf29b9eaa

[raghavrmadya]

Triggering as the client has responded to KYC but needs to further determine what is being uploaded. Notaries interested in signing are recommended to conduct their own due diligence and not rely on governance team QA

[YuanHeHK]

The person in charge of this app communicated directly with me and showed some data, which seemed to be fine. This time I'll sign the app once. It is hoped that the application owner will continue to disclose more data samples.

[YuanHeHK]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacec3ze4ary6hwsq6cphe54lmao4smkydicoat76trgv35xkd6kzrv6

Address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

Datacap Allocated

50.00TiB

Signer Address

f1fg6jkxsr3twfnyhdlatmq36xca6sshptscds7xa

Id

a652c7b7-8141-4a32-9a5c-5f3cf29b9eaa

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

[liyunzhi-666]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacea4nqsvic35wyd2ooczzwjoleubij7iwsphfioq56xzks5rp2kd7o

Address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

Datacap Allocated

50.00TiB

Signer Address

f1pszcrsciyixyuxxukkvtazcokexbn54amf7gvoq

Id

a652c7b7-8141-4a32-9a5c-5f3cf29b9eaa

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

[BDE-io]

@qituo Hi! Great to see you have gotten approval for DataCap and advancing the mission of preserving humanity’s most important information. If you are looking for storage providers to store these data or have any questions, please visit #bigdata-exchange on Filecoin Slack or reply here.

We have strong demand from a diverse group of SPs, who are actively looking to onboard more data.

[Sunnyiscoming]

Is there any problem with using datacap?

[qituo]

hi Sunnyiscoming Recently, we are preparing data and contacting SP, and will start soon. Thank you！

[large-datacap-requests[bot]]

DataCap Allocation requested

Request number 2

Multisig Notary address

f02049625

Client address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

DataCap allocation requested

100TiB

Id

89e7e31b-3d07-4cb1-b041-8e6faa066e81

[large-datacap-requests[bot]]

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

Last two approvers

liyunzhi-666 & fireflyHZ

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 (5 PiB)

4.95PiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
78	1	50TiB	100	0B

[filplus-checker-app[bot]]

DataCap and CID Checker Report[^1]

No active deals found for this client.

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

[kernelogic]

The checker bot seems inaccurate about the deals sealed. Another website shows better distribution.

[kernelogic]

[kernelogic]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacebkgn2l43rj54hqdc2grg3ym3whhvhvql7vmismvgvpzzmznayoou

Address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

Datacap Allocated

100.00TiB

Signer Address

f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa

Id

89e7e31b-3d07-4cb1-b041-8e6faa066e81

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

[Tom-OriginStorage]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report[^1]

• Organization: XHash
• Client: f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

  Approvers

  1kernelogic
  1liyunzhi-666
  1YuanHeHK

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 should not exceed 70% of total datacap.
• Storage provider should not be storing duplicate data for more than 20%.
• Storage provider should have published its public IP address.
• All storage providers should be located in different regions.

✔️ Storage provider distribution looks healthy.

Provider	Location	Total Deals Sealed	Percentage	Unique Data	Duplicate Deals
f02029895	Seoul, Seoul, KR QUANTIL NETWORKS INC	16.13 TiB	34.26%	16.13 TiB	0.00%
f01170282new	Hong Kong, Central and Western, HK QUANTIL NETWORKS INC	15.75 TiB	33.47%	15.75 TiB	0.00%
f02030031new	Singapore, Singapore, SG QUANTIL NETWORKS INC	15.19 TiB	32.27%	15.19 TiB	0.00%

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:

• No more than 70% of unique data are stored with less than 3 providers.

✔️ Data replication looks healthy.

Unique Data Size	Total Deals Made	Number of Providers	Deal Percentage
768.00 GiB	768.00 GiB	1	1.59%
3.56 TiB	7.13 TiB	2	15.14%
13.06 TiB	39.19 TiB	3	83.27%

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.[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

[Tom-OriginStorage]

lotus client retrieve --provider f01170282 QmZMkvbHKb9au1ZMWzqVwc6WVQaHXjwS7DGNDVU3JTfoBe aa Recv 0 B, Paid 0 FIL, Open (New), 0s Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 2ms Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 3m2s Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 3m2s Recv 70 B, Paid 0 FIL, BlocksReceived (Ongoing), 3m2.001s Recv 2.162 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m2.002s Recv 50.17 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m2.003s Recv 1.049 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m3.43s Recv 2.049 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m4.906s Recv 3.049 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m6.481s Recv 4.049 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m7.78s Recv 5.049 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m8.901s Recv 6.049 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m10.222s Recv 7.049 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m11.521s

[Tom-OriginStorage]

According to the inspection all conform to the rules

[Tom-OriginStorage]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecejca5ygbjwj2civwocobqds37xjdruadtr5hf74jjoaf7gflvjw

Address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

Datacap Allocated

100.00TiB

Signer Address

f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga

Id

89e7e31b-3d07-4cb1-b041-8e6faa066e81

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

[herrehesse]

@Tom-OriginStorage As stated during multiple governance calls you were asked not to sign any applications, and first do your due diligence on 50 new applications. I am surprised to see you signing this application and would kindly suggest to revert your signature.

Due diligence is not what you performed and your statement "According to the inspection all conform to the rules" is not sufficient.

For transparency tagging: @cryptowhizzard @raghavrmadya @dkkapur @galen-mcandrew @Sunnyiscoming

[Tom-OriginStorage]

@herrehesse For #811 Origin Storage has given a sufficient explanation and has been recognized by everyone. We have confirmed that we can carry out new signatures. Origin Storage has the obligation and responsibility to participate in what the notary should do, just like what we said before Regarding the compliance and inspection of LDN, Origin Storage will continue to conduct inspections according to the rules. Origin Storage also summarizes some inspection methods and tools, which we will share for everyone to use later.

[cryptowhizzard]

All these were set just a few days ago and look exactly the same. These were spinned up for this purpose only

@Tom-OriginStorage : In your R4 application you state :

The following content will include a survey of applicant information prior to approval and a review of DataCap usage after approval.

1. Information survey of applicants (i) Only their identity will be verified for individual users, and the basic verification will be ensured. In contrast, another verification is minimized to promote the use of Filecoin in the general user community. (ii) For web 3.0 developers, we will verify their GitHub registration years and project websites to minimize other verifications and promote the use of Filecoin in decentralized applications. (iii) For corporate entities or organizations, we will verify their entity information (including but not limited to registration number, registration date, registration certificate, board members, and beneficiaries), business type, data source, data samples, detailed usage plans, etc.

2. Review of usage Post-allocation review will be conducted on an ongoing basis to avoid misuse of DataCap, guarantee the original purpose of Filecoin plus, and perform the duties of a notary. The review is based on the principle that it is the responsibility and obligation of the applicant to use the DataCap only for approved purposes. Since DataCap is allocated on the principle of phased distribution, subsequent quotas for applicants who do not pass the review will be delayed and even canceled. The specific review path is as follows (not excluding the continuation of additional review provisions). (i) We require DataCap applicants to provide transaction Cid and minerID. For unencrypted data, we conduct random retrieval spot checks, and if the applicant has any violations of DataCap distribution, we will take measures to stop further distribution. (ii) We verify that the user distributes the requested DataCap to at least three SPs to improve data storage security while reducing the possibility of misuse. (iii) We establish a reputation scoring system to rate the applicant during the usage process, which will affect the applicant's next phase of quota distribution and the next DataCap application, further promoting the applicant's proper use of the quota he/she has received.

During the process of performing due diligence, we will ask the following basic questions to the applicant first: (i) Self-introduction (ii) Knowledge of Filecoin (iii) Business requirements and data format (iv) Data sources and data samples (v) If the application is approved, the minerID that costs DataCap, and the detailed usage plan such as the quota between miners (vi) Data security, any violation of local laws (vii) Profitable or not

We will maintain the principle of conducting reasonable investigations without burdening the applicants with investigations and combine this with a phased distribution mechanism to ensure proper use of DataCap by our customers and do our best to promote Filecoin. What processes will you employ when granting additional DataCap to a client that has previously been verified? This includes confirming that the client is not improperly using the DataCap they were previously granted, i.e., making deals with a single SP entity.

1. Conduct regular and continuous reviews with the help of various statistics from https://filplus.d.interplanetary.one/ and filfox.info to ensure that the assigned DataCap is not abused or misused according to the deal.

2. DataCap will be allocated in stages. If any improper use or misuse of the allocated DataCap is found, the unallocated DataCap may be reduced or even canceled. The score may be penalized to further ensure the proper use of the DataCap.

Applicants with abnormal usage will be contacted and dealt with promptly.

Please provide us with the KYC of Xhash under [ (iii) For corporate entities or organizations, we will verify their entity information (including but not limited to registration number, registration date, registration certificate, board members, and beneficiaries), business type, data source, data samples, detailed usage plans, etc. ]

Secondly :

https://filfox.info/en/address/f02030031 has worker : https://filfox.info/en/address/f3upyhbv2dl7s7ysodxhnldrfso5gylbstoihaej36lqqxhjxyqairt5rgz7xwnpsguqv44ikocqwh2pfddd2q

That wallet got created and 0.3 FIL from https://filfox.info/en/address/f14r6um7ptphe4ecoycjxsv4wf3t5ykxgdq27f2yy

f02029895 has worker https://filfox.info/en/address/f3qsbcoujmw422dupbaulclh7kdhmupwinacunrquyt7iuf4hzgprrf42a4yu7l5kxiroib4trux6577i3nzia

That wallet got created and 0.3 FIL from https://filfox.info/en/address/f14r6um7ptphe4ecoycjxsv4wf3t5ykxgdq27f2yy ( Same wallet ) -> Same organisation.

f01170282 has worker https://filfox.info/en/address/f3vimm34qernd23f6wxcw7ej5wa7mcztvpyq2nd4hsy4wwladwv4j4jlthaposktnuwhruoadtsdr33iaz5v5q

I don't care to trace it... we all know where it ends ;-). .... this is just a 100% self dealing with one organisation exercise and it is simple to prove since the blockchain has everything one wants to know.

Btw :

https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1078 Same set of miners. Same notary signing.

[cryptowhizzard]

Basically 2 questions :

1. @Tom-OriginStorage is xhash a customer of you or chainup?

2. Why did you sign without 4 sp’s and 3 orgs present according to fil+ guidelines and without proper distribution?

[Derek-zd]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

Click here to view the full report.

[Tom-OriginStorage]

Basically 2 questions :

1. @Tom-OriginStorage is xhash a customer of you or chainup?
2. Why did you sign without 4 sp’s and 3 orgs present according to fil+ guidelines and without proper distribution?

1：xhash is a web3 company. They contacted me to sign. After communicating with them, they are a Singapore company. They have worked on ETH mining machines for many years, and now they are starting to incubate web3 projects. I have done my due diligence according to our standards investigation

2：Regarding the issue of 3 SPs, I also communicated with the applicants. The reason they gave was that the quota was only 50T for the first time, and the quota was small, which affected the business negotiations. They are indeed only in 3 SPs at present, but they promised After that, at least 5 SPs will be stored. In this case, many of our LDNs have similar problems. We need to let them run first. The rules also require at least 4 backups at the end. I think this is acceptable for the beginning LDN ; Did I answer your doubts

[cryptowhizzard]

Basically 2 questions :

1. @Tom-OriginStorage is xhash a customer of you or chainup?
2. Why did you sign without 4 sp’s and 3 orgs present according to fil+ guidelines and without proper distribution?

1：xhash is a web3 company. They contacted me to sign. After communicating with them, they are a Singapore company. They have worked on ETH mining machines for many years, and now they are starting to incubate web3 projects. I have done my due diligence according to our standards investigation

2：Regarding the issue of 3 SPs, I also communicated with the applicants. The reason they gave was that the quota was only 50T for the first time, and the quota was small, which affected the business negotiations. They are indeed only in 3 SPs at present, but they promised After that, at least 5 SPs will be stored. In this case, many of our LDNs have similar problems. We need to let them run first. The rules also require at least 4 backups at the end. I think this is acceptable for the beginning LDN ; Did I answer your doubts

Hi Tom,

Thanks for your answer. Regarding 1 it is clear, however i asked if xhash is one of your clients. This can be yes or no. Is Xhash one of your clients?

Regarding 2 , the issue at hand is not that they are 3 sp's . It is only one SP and they are self dealing at the moment. It was not doubt in my question. It was a conclusion with evidence. My evidence showed that there was no due diligence done because the data onboarding plan ( according to the fil+ rules ) is still missing.

[Tom-OriginStorage]

He is not my client, he contacted me on WeChat through some people, because we are all in the blockchain industry, I communicated this issue with them in detail on WeChat, I am completely sure of the authenticity of their company Yes, they are also well-known in the blockchain industry. As for the problem you mentioned that there are currently only 3 SPs, they will solve it in the second round, because the current 50T quota in the first round has been used up. The latest rule for FIL+ is to store 4 copies, but isn’t this just the beginning? The entire LDN just stores 1% of the data. Can you see what I mean?

[cryptowhizzard]

@raghavrmadya @dkkapur

I have tried my best, but we seem to be blocked with a language translation problem or just a lack of tech knowledge in this LDN.

I made a post a few days ago here -> https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1078#issuecomment-1433848806

I am trying to communicate ( and have proven ) that all these machines are owned by one person or organisation with one wallet. We are not talking about 3 different Sp's here .... it is just one provider / organization with 3 machines and a VPN.

Can you give it a try to explain to Tom why this should not have been signed? I would like it to be clear to have an appropiate followup with this LDN according to the FIL+ rules and best practices / guidelines so we all can move on and the customer/applicant knows what is expected from him.

Thanks

[Tom-OriginStorage]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

Click here to view the full report.

[qituo]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

Click here to view the full report.

[qituo]

Hello, I am the applicant for this project. I can guarantee that the SP has not used VPN. We have found a new SP, which has started encapsulation. Now we will find more SPs to complete this project, thank you; If you have resources, you can also introduce to us

[NewHuoPool]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

Click here to view the full report.

[NewHuoPool]

Can you explain the next encapsulation plan? Such as your choice of SPs

[qituo]

Now we have found a new SP (f02044834) to add, which can be seen in the robot list. Below, we will also find 3 more SPs to add. We expect to start packaging next week and hope to support it

[NewHuoPool]

Willing to support，and will continue to pay attention to the new SPs joining situation.

[NewHuoPool]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacebuxpihzqv2gvttkmbh6tieevzthihdjs7tibnxfjzouljbntsxgg

Address

f1r7jgp4cfgnhmcbl2eppbsv5efjnmmccfbchyesq

Datacap Allocated

100.00TiB

Signer Address

f16karfxq7lxdy7izqrzrk75jf3not34k6sg6zvcy

Id

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

[SuperChaiChai]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

Click here to view the full report.

[SuperChaiChai]

What is the packaging plan for the future? There are only 4 SPs in the report.

[qituo]

yes we will also find 3 more SPs to add. We expect to start packaging next week and hope to support it