Client Allocation Request for: Textile

[andrewxhill]

---

Client Allocation Questions

Core Information

• Name: Textile
• Website / Social Media: company is https://twitter.com/textileio on twitter, https://www.linkedin.com/company/textile.io/. my personal, https://twitter.com/andrewxhill
• Region: North America
• DataCap Requested: 9TiB
• Addresses to be Notarized: f3rab4mhsr7f2gdg6ozgj44mtny6bhcy3rvlftc5xyki6t4hvhdkaji3ahfaid6fh2o3wff4yfrzag4lge2r2q
• Notary Requested: ann-shin

[filecoin-on-boarding-bot]

Thanks for your request!
Everything looks good. 👌

    A Filecoin Plus Notary will review the information provided and contact you back pretty soon.

[andrewxhill]

Our first application here appears stalled #211 so trying anew.

[XnMatrixSV]

@andrewxhill
Hi, nice to meet you. Thanks for your request. Can you kindly add more information here.

1.Are you representing for yourself or your company？
2.If you are representing for your company, Please give the following informations, the establishment time, number of employees, business scope, number of registered users, number of social media followers, and storage usage,and so on. Provide links to social media/news mentions etc. If you are representing for yourself , please introduce yourself. Provide links to social media/news mentions, etc.
3.The history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time, etc.
Type, size, and source of the data you will be store on Filecoin,e.g. public data or private data, etc. Is there any sensitive or illegal content?
4.How do you intend to store the data on Filecoin, e.g. redundancy, location/miner preferences, etc
5.Have you already apply for DataCap to another notary, and whether it is accepted or rejected. Is there any reliable DataCap left?
6.Would you like to post real transactions on Github?

[andrewxhill]

1.Are you representing for yourself or your company？

I'm representing Textile, formally We Are Set, Inc.

2.If you are representing for your company, Please give the following informations, the establishment time, number of employees, business scope, number of registered users, number of social media followers, and storage usage,and so on. Provide links to social media/news mentions etc.

• Incorporated November, 2016.
• 7 employees.
• We build developer tools for decentralized protocols, primarily IPFS, Libp2p, and Filecoin.
• Twitter followers: 4000.

Usage

We intend to use this first datacap to store our existing IPFS pins (~a few TiB) in a series of Filecoin deals as part of our routine system backup process. We will make the storage regular, but this initial datacap application is only intended to cover the first couple of runs (including a small replication factor).

News & Media

• Textile participation in Longhash accelerator https://www.longhashventures.com/filecoin/ (see Mentors)
• EthDenver blog post on Textile https://medium.com/ethdenver/buidl-with-textile-at-ethdenver-2021-1792e1831b21
• Textile mention in Coindesk coverage of Mainnet launch: https://www.coindesk.com/filecoin-mainnet-now-live
• Recent community tweets
  • https://twitter.com/Filecoin/status/1367126623699501061
  • https://twitter.com/deplatformer_io/status/1365007031950708738
  • https://twitter.com/FleekHQ/status/1366437861751422977
  • https://twitter.com/Satellite_im/status/1364663682697953282
  • https://twitter.com/KodaDot/status/1364283818102906883

3.The history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time, etc.

Type, size, and source of the data you will be store on Filecoin,e.g. public data or private data, etc. Is there any sensitive or illegal content?

Contributions

• We've built and maintained Powergate, a tool for Filecoin clients building on the network.
• We've hosted and maintained lotus+powergate nodes for dozens of teams since even before mainnet. We've done this for free for all teams to-date to help onboard more projects and ramp up experimentation+adoption.
• We've contributed a lot of hours to testing deal lifecycle on early networks and on mainnet to give feedback and surface issues for core dev teams.
• We've participated in 3 accelerators/incubators to give mentorship to teams building on Filecoin.
• We've sponsored and worked at multiple hackathons to help teams try out Filecoin.
• We've writen blog posts, given online workshops, and shared tutorials about using the network.
• We've integrated Filecoin wallet and deal making support into our hosted platform for developers.
• This list is pretty out-dated, but gives a sense... we try to be very active.
  • Types + tests for existing npm module multibase DefinitelyTyped/DefinitelyTyped#41416
  • Types + tests for existing npm module multiaddr DefinitelyTyped/DefinitelyTyped#41413
  • Adds existing npm lib multicodec + tests DefinitelyTyped/DefinitelyTyped#41404
  • Adds types and tests for lexicographic-integer DefinitelyTyped/DefinitelyTyped#41025
  • Adds datastore-core types and tests (existing npm package) DefinitelyTyped/DefinitelyTyped#41011
  • Adds types for existing npm module datastore-level DefinitelyTyped/DefinitelyTyped#40932
  • Adds types and tests for existing npm package level-ttl DefinitelyTyped/DefinitelyTyped#40931
  • Adds interface-datastore types with tests DefinitelyTyped/DefinitelyTyped#40842
  • Adds clear to levelup + updates tests DefinitelyTyped/DefinitelyTyped#40792
  • Types for existing npm package subleveldown with tests DefinitelyTyped/DefinitelyTyped#40754
  • Optimize prefix search ipfs/js-datastore-level#25 (feat: optimization on querying)
  • Add typescript types multiformats/js-cid#94 (feat: types for CID)
  • fix: more correct type defs + docs multiformats/js-cid#102 (fix: better types)
  • client: make wallet addr be a param in ClientStartDeal lotus#910 (feat)
  • cli: print nicer message when miner hasn't initialized lotus#911 (fix: analysis for fixing was quite complex)
  • cli: fix name of price unit lotus#937 (fix)
  • deps: upgrades badger from 0.0.5 to 0.2.0 hsanjuan/ipfs-lite#8 (fix: update deps)
  • Adds typescript types + linting/tests libp2p/js-libp2p-crypto#161 (feat: types for libp2p-crypto)
  • feat: adds typescript types + type tests libp2p/js-peer-id#110 (feat: types for peer-id)
  • Update dependencies and make linter happy. ipld/js-codec-interface#2 (fix: update deps)
  • https://github.com/ipfs/go-hamt-ipld/pull/39 (PR)
  • api: ChainNotify sometimes freeze, and force close makes the node panic lotus#1122 (bug)
  • new api to calculate arbitrary forks revert and applys lotus#1084 (PR)
  • state type for actor bafkqadlgnfwc6mjpmfrwg33vnz2a not found lotus#1099 (bug)
  • fix issue #127 lotus#1155
  • Dockerfile: fixes lotus#1159
  • Add DealID to DealInfo lotus#1392 (2020-03-10) & Include DealID in DealInfo lotus#1452 (2020-03-26) [same but in testnet/3]
  • Stale link in Quickstart AudiusProject/audius-protocol#313 (QA)
  • testnet/3: TestAPIDealFlow fails for two deals lotus#1455
  • fix ClientRetrieve with CAR exporting & add test coverage lotus#1472 (2020-03-30)
  • Double Deal Flow lotus#1481 (2020-03-31)
  • docker: fix build, upgrade Go lotus#1516 (2020-04-06)
  • mock: add faked post sector-storage#38 (2020-05-19)
  • mock: produce more valid PoSt proof sector-storage#39 (2020-05-20)
  • Allow remote IPFS node support & IPFS for data retrieval & automatic env wiring lotus#1843 (2020-05-27)
  • update client stream to receive and return server response improbable-eng/ts-protoc-gen#231
  • addrbook: fix races libp2p/go-libp2p-peerstore#154 (2020-06-05)
  • Miner QueryOffer API & non local-discovery retrieval CLI support lotus#2040 + Consider QueryOffer Error & Status lotus#2042 (2020-06-16)
  • storagemarket: GetAsk isn't fully context-aware go-fil-markets#292 (2020-06-23, found annoying thing)
  • Use client address, not default address, to sign proposals go-fil-markets#326 (2020-07-16, I found a but about go-fil-markets using the wrong wallet address!)
  • ipfsbstore: offlinemode, and Has() fix lotus#2462 (2020-07-17)
  • Fatal error on close lotus#2945 (2020-08-10)
  • Mocked sectorbuilder with 512Mib sector hangs on retrieval lotus#3297 (2020-08-25, lotus retrieval bug)
  • openStream: avoid time.Sleep in exponential backoff go-fil-markets#429 (2020-10-09, bugfix)
  • update filecoin-ffi in go mod lotus#4584 (2020-10-26)
  • make IPFS online mode configurable lotus#4650 (2020-10-29)
  • Fix panic in FundManager lotus#4808 (2020-11-11 - Lotus panic)
  • Fix: dont crash on startup if funds migration fails lotus#4827 (2020-11-12 - Startup crash on prerelease)

Data info

• IPFS backup data
• 2 TiB to start, with replica and multiple times
• The data is already publically available on the IPFS DHT. However, we will encrypt the content contained in each deal as it isn't inteded for public use, the aim is to add data security to our platform. We have other ways that individual users of our services can store their data in public deals that wont be included in the use of this datacap.
• No illegal or sensitive content.

4.How do you intend to store the data on Filecoin, e.g. redundancy, location/miner preferences, etc

• A mix of existing FIL+ https://github.com/filecoin-project/filecoin-plus-client-onboarding/blob/main/miners.md and members of the MinerX fellowship.
• We'll aim for 2-5x replication across all deals.
• Each storage job will be larger than a single sector, so we will have a preprocessing step that takes the full DAG down to ~32ish GiB deals and storage each with its own set of miners and replication.
• We will test a wide sleection of locations but our data will originate in North America so we will work around any miner connectivity limitations.
• We will be doing all deals as online only, hopefully no offline deal flows.

5.Have you already apply for DataCap to another notary, and whether it is accepted or rejected. Is there any reliable DataCap left?

We have another open application that was our first, but it appears to have gone stale. This application will be our first and we'll close the other.

6.Would you like to post real transactions on Github?

Shouldn't be a problem initally (through the life of this first datacap allotment) though over time as we ramp up deals we may review how useful it is to maintain.

[XnMatrixSV]

Thanks for your answers. Can you kindly add more information?
1.Business scope,such as state, region or world.
2.Number of registered users.
3.Storage requirement in business.

[andrewxhill]

1. Textile serves customers globally. We provide open source tools for developers as well as hosted APIs primarily built around the Libp2p, IPFS, and Filecoin stack. This project will be internal and run by team members in North & South America.
2. Unknown number of users are using our libraries. Our hosted service has ~25,000 accounts.
3. I don't quite follow this last question, but taking a guess. The storage requirement we have is for about 2-3TiB per week for a few weeks while we test some new deal making pipelines from our infrastructure.

[andrewxhill]

Let me know if you need anything else @ann-shin

[andrewxhill]

Hey @ann-shin any update here?

[XnMatrixSV]

Thanks for your answers. According to our rules (filecoin-project/notary-governance#27), you are L3 customer with a score of 3. The first maximum grant is 5TiB, the single maximum grant is 10TiB, the total maximum grant is 50TiB. This time you are granted for 5TiB DataCap. Are you willing to accept it? Please check you Filecoin address to be notarized: f3rab4mhsr7f2gdg6ozgj44mtny6bhcy3rvlftc5xyki6t4hvhdkaji3ahfaid6fh2o3wff4yfrzag4lge2r2q.

[andrewxhill]

Thanks, we can work with that to start.

Confirmed, f3rab4mhsr7f2gdg6ozgj44mtny6bhcy3rvlftc5xyki6t4hvhdkaji3ahfaid6fh2o3wff4yfrzag4lge2r2q is the address we'd like notarized.

[andrewxhill]

hey @ann-shin sorry to bother, just want to unblock this project