Closed CodeIsLaw0108 closed 1 year ago
Thanks for your request! :exclamation: We have found some problems in the information provided. We could not find any Web site or social media info in the information provided
Please, take a look at the request and edit the body of the issue providing all the required information.
Thanks for your request! :exclamation: We have found some problems in the information provided. We could not find any Web site or social media info in the information provided
Please, take a look at the request and edit the body of the issue providing all the required information.
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
@galen-mcandrew could you help to sign this issue if all the info is correct?
@dkkapur can you verify this slingshot request?
Confirming that this is on the eligible datasets for Slingshot - https://github.com/filecoin-project/slingshot/blob/master/datasets.md.
However - applicants that have received DataCap in the past for Slingshot V2 have met a very high bar in proving the quality of the work they are doing as well as the robustness of the deal distribution mechanism to ensure they work with several SPs and do not self-deal. On behalf of the Slingshot community, I'd love to hear more about @CodeIsLaw0108's plan to identify SPs and fairly distribute deals across them.
Hi Any update ? @dkkapur For "plan to identify SPs and fairly distribute deals across them"
I think there are no reliable methods for doing this. They are no reliable info on-chain for clarifying this unless any miners need to publish their public IP honestly.
Has there been any progress in identifying SP's to work with? I know there are multiple other Slingshot participants that may be able to help provide some more details or starting points for you.
@kernelogic if you have any suggestions here, might be good to get your advice!
I agree there's no reliable methods for identifying without a pre-registration platform. I guess the second best alternative would be SPs (or the entities) registered during the slingshot restore program earlier this year.
Given the short remaining time on the current phase 2.8 and the size of this LDN, if OP could give a planned list of SP and their respective owning entity to prove no self-dealing and following decentralization rules, that would be very convincing.
Given the short remaining time on the current phase 2.8 and the size of this LDN, if OP could give a planned list of SP and their respective owning entity to prove no self-dealing and following decentralization rules, that would be very convincing.
+1. Looking forward to hearing from @CodeIsLaw0108
Hi, Very happy while we know slingshot2.8 will continue up to 7.6 ,Thanks Could you help to give us a list of SPs , and we could contact them directly ? I think there is no necessary for us to proving such issue if our list is from community ?
@CodeIsLaw0108 fair enough. The Slingshot site has information available about every deal uploaded and the SPs involved, e.g., for one of @kernelogic's projects, you can see the recent deal metadata here: https://slingshot.filecoin.io/project/62340a7a7d907fffc878620e/deals.
Additionally, from Slingshot Evergreen, we publish a list of active SP IDs and their relative deal making here: https://api.evergreen.filecoin.io/public/qap.txt.
What do you think?
Yeah Thanks @dkkapur
As for https://api.evergreen.filecoin.io/public/qap.txt. Could you please help to give slack name also ? It's hard for me to find slack name from miner ID ?
So Can i send deal first for f01850141 As time fly, and wenkend again But
The current reward period ends in 19d 11h 30m 31s
Hey Cabrina, does this node f01850141 belong to you? @xingjitansuo https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/312 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/232 As you know, self dealing in LDN is not allowed in our community. In addition,we found another case connected with you ,could you give some clarification about it. https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/354
@Chris00618 I totally understand and follow the community rule on prohibition of seal-dealing. I do not own SP f01850141. I just recommend this node to @CodeIsLaw0108 .
@Chris00618 Thanks for your reply after waiting so long time . Have checked with @xingjitansuo , Sorry my fault ,Just one of their SP before slingshot 2.8 But can I still send deals for this miner ? Could you help to comments this and help us to speed up this procedure ?
We all want to participate slingshot 2.8 and of course want to get reward from this project But , some guys have finished almost all the task about slingshot 2.8 while we are still struggling applying the project, And project is almost end Many SPs have to pay for Datacap as they need deals for sealing but only few client have gotten their datacap
Wish community could handle issues as quickly as possible , And you can closed this issue if there is any issue that will not meet the requirement, then there is no necessary for us to ask for checking this issue again and again.
@CodeIsLaw0108 I recommend you join #slingshot-evergreen channel to find some more SPs to work with. Approving this one for now so you can start to make deals in the final 2 weeks of v2.8.
1 PiB
Expected weekly DataCap usage rate
100 TiB
Client address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
50TiB
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedkgfhztnbjtrujxeq7aksyxjpezrk3dg2zlebiurwcx7b7kkynly
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
50.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedkgfhztnbjtrujxeq7aksyxjpezrk3dg2zlebiurwcx7b7kkynly
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedfuwpyxffdezk2ddmgsf24mftex67gwsr5ke42sw7vwliblszmjw
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
50.00TiB
Signer Address
f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedfuwpyxffdezk2ddmgsf24mftex67gwsr5ke42sw7vwliblszmjw
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
100TiB
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
xingjitansuo & kernelogic
100% of weekly dc amount requested
100TiB
50TiB
974TiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1122 | 4 | 50TiB | 33.07 | 9.90TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedv4j7evy4wbdwo62ld3dbfkazavhsyzzeoxy27p7o3xg22monsik
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
100.00TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedv4j7evy4wbdwo62ld3dbfkazavhsyzzeoxy27p7o3xg22monsik
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacea3gryhu4zkbeksb3yjfcz7yv4czx5wo27xc5nz6ceuqon5a7dzlu
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
100.00TiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacea3gryhu4zkbeksb3yjfcz7yv4czx5wo27xc5nz6ceuqon5a7dzlu
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacec7iowtwost6ury7evnieetnrkf2k3vmmj4pskbivjhd7qdz3m7j4
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
100.00TiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec7iowtwost6ury7evnieetnrkf2k3vmmj4pskbivjhd7qdz3m7j4
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
200TiB
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
psh0691 & psh0691
200% of weekly dc amount requested
200TiB
50TiB
974TiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1567 | 5 | 100TiB | 26.42 | 2.06TiB |
So do you have any idea of who is f01850141? This guy is a major SP in Filecoin and you're cooperating with him/her.
Is this a bug where psh0691 was able to both propose and approve the datacap request?
@jamerduhgamer @Filefly-ph I am not cooperating with this applicant, and I cannot make proposals and approvals at once. In this case, when there was a bug where the proposal request was repeated, I signed the approval, and the proposal was repeated. I remember reporting to Slack's notary channel. https://filecoinproject.slack.com/archives/C01HRNU4VBK/p1661305706567739
Ah that makes sense now. You tried to approve the datacap request and the wrong message was sent. Then you tried to approve it again which went through with the correct message. Thank you for answering my question @psh0691
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceb4iahqcggxwwzmuoqrkcopozakg23jeada535lggedkm2dq333gu
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
100.00TiB
Signer Address
f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb4iahqcggxwwzmuoqrkcopozakg23jeada535lggedkm2dq333gu
@CodeIsLaw0108 Hi! Great to see you have gotten approval for DataCap. 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.
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
400TiB
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
xingjitansuo & psh0691
400% of weekly dc amount requested
400TiB
150TiB
874TiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1567 | 5 | 200TiB | 26.42 | 46.31TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecqz62lvdlyururvosbmjmvex6oajkiwqz6u4ud7osq75qhnhj7h6
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
400.00TiB
Signer Address
f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecqz62lvdlyururvosbmjmvex6oajkiwqz6u4ud7osq75qhnhj7h6
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebbcmchsz2ofwurkw7xxy6tknrgsncxcbdwvskd6woa5jfhmgbr4m
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
400.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebbcmchsz2ofwurkw7xxy6tknrgsncxcbdwvskd6woa5jfhmgbr4m
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
274TiB
5ba40089-e49d-4f9e-821e-44c0bc47cffb
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
kernelogic & newwebgroup
800% of weekly dc amount requested
274TiB
550TiB
474TiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
10859 | 8 | 400TiB | 19.72 | 89.06TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacediwkrbapbdiqqupsvau6rwslwtmvfnb53gmt7jcf2oqfxjcve5za
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
274.00TiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
Id
5ba40089-e49d-4f9e-821e-44c0bc47cffb
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacediwkrbapbdiqqupsvau6rwslwtmvfnb53gmt7jcf2oqfxjcve5za
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacec5om4mrhhx4uamsyqa25kcm35o736quxawscj3clstyjvkktsi32
Address
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
Datacap Allocated
274.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
5ba40089-e49d-4f9e-821e-44c0bc47cffb
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec5om4mrhhx4uamsyqa25kcm35o736quxawscj3clstyjvkktsi32
Haoqian Mx
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
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.
⚠️ f01926698 has unknown IP location.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01969779new |
Clifton, New Jersey, US | 83.13 TiB | 18.40% | 83.13 TiB | 0.00% |
f0143858 | Clifton, New Jersey, US | 80.34 TiB | 17.79% | 80.34 TiB | 0.00% |
f03223 | San Jose, California, US | 79.06 TiB | 17.50% | 79.06 TiB | 0.00% |
f02301 | San Jose, California, US | 77.25 TiB | 17.10% | 77.25 TiB | 0.00% |
f0240185 | Clifton, New Jersey, US | 57.47 TiB | 12.72% | 57.47 TiB | 0.00% |
f0142637 | Chengdu, Sichuan, CN | 41.16 TiB | 9.11% | 41.16 TiB | 0.00% |
f01926698 | Unknown | 27.19 TiB | 6.02% | 27.19 TiB | 0.00% |
f01850141 | Hong Kong, Central and Western, HK | 6.13 TiB | 1.36% | 6.13 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
19.06 TiB | 19.06 TiB | 1 | 4.22% |
19.75 TiB | 39.50 TiB | 2 | 8.74% |
3.69 TiB | 11.06 TiB | 3 | 2.45% |
24.44 TiB | 97.75 TiB | 4 | 21.64% |
35.78 TiB | 178.91 TiB | 5 | 39.61% |
16.41 TiB | 98.44 TiB | 6 | 21.79% |
1.00 TiB | 7.00 TiB | 7 | 1.55% |
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.
⚠️ CID sharing has been observed.
Other Client | Application | Total Deals Affected | Unique CIDs | Verifier |
---|---|---|---|---|
f1o54sve7ede7im4caux3ug7lsyjmbue7ss3zzl6y | FilSwan | 85.25 TiB | 384 | LDN v3 multisig |
f1bstbq5bi72kyovhh7zoo2f6l6uivsjz4ey5dnqq | FilSwan | 33.38 TiB | 258 | LDN v3 multisig |
f14r2jybmccwiu6hze4fu55jyhclktvwacec56hea | FilSwan | 9.16 TiB | 126 | LDN v3 multisig |
f1r3d25hl2y7rqlsu2mgczdethy4qqjmkfdlmibfq | NEXRAD - FilSwan | 6.19 TiB | 198 | LDN v3 multisig |
f13d6zt424jkp55u7kp67azotkzadtlokwnz2ntxa | FilSwan - Slingshot Restore | 1.97 TiB | 63 | LDN v3 multisig |
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
The issue reached the total datacap requested. This should be closed
f01858410
f1eto4dfafkoeukxenoc7vzexrvf6i4yqvhszrq2y
kernelogic & psh0691
total dc reached
0
824TiB
200TiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
24025 | 8 | 274TiB | 26.79 | 65.78TiB |
Hello @CodeIsLaw0108
It seems that the total datacap is reached. Can you close the issue please?
Thanks!
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.
What is the primary source of funding for this project?
What other projects/ecosystem stakeholders is this project associated with?
Use-case details
Describe the data being stored onto Filecoin
Where was the data in this dataset sourced from?
Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.
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).
What is the expected retrieval frequency for this data?
For how long do you plan to keep this dataset stored on Filecoin?
DataCap allocation plan
In which geographies (countries, regions) do you plan on making storage deals?
How will you be distributing your data to storage providers? Is there an offline data transfer process?
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.
How will you be distributing deals across storage providers?
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?