Updated: Feb 6
Textile provides tools to help developers build with IPFS and Filecoin. Textile Hub is a developer API to access the IPFS network and Filecoin network. The Buckets daemon and API provide simple object storage on IPFS & Filecoin, either locally or pinned on the Hub. ThreadDB and Mailboxes allow secure exchange of messages and data between public keys over Libp2p.
Build your app on IPFS and Filecoin with Textile Buckets and Hub APIs.
We are looking for projects that use (1) Textile Buckets (https://docs.textile.io/buckets/) to host and synchronize data over IPFS. Or (2) Textile Mailboxes or ThreadDB to share messages or collaborative databases using the Textile Hub.
Buckets provide local and remote tooling for managing dynamic datasets on IPFS. They off your app the ability to move data over IPFS, IPNS, and HTTP out of the box. Developers can use the Textile Hub (https://docs.textile.io/hub/) to host buckets on remote IPFS nodes.
ThreadDB is a database build on Libp2p and IPFS. Mailboxes are encrypted, anonymous, inboxes for pubkeys. Mailboxes allow apps to store invites (such as Thread invites) and other private messages for recipients even when the recipient is offline. https://docs.textile.io/threads/.
4x$500 for best use of Buckets, ThreadDB, or Mailboxes.
Store your data on Filecoin with Bucket Archives or Powergate
We are looking for innovative uses of Filecoin that store data using Bucket Archives or Powergate. Successful applications should use Filecoin as a core component of their project.
Bucket Archives (https://docs.textile.io/buckets/archiving/) allow developers to easily store snapshots of their data on Filecoin. The Textile Hub has integrated wallets and access control, so developers can move data to Filecoin independently, as a team or organization, or on behalf of app users.
Powergate (https://docs.textile.io/powergate/) is an API-driven backend for building Powergate into your platform or stack. It has support for miner selection, deal pipelines, deal repair, and manages multi-tenet wallets. Powergate has quickly become one of the most popular technologies for building on Filecoin. Get started in under a minute with Localnet (https://docs.textile.io/powergate/localnet/).
Title: Best overall Ceramic X Textile.io integration
With projects exploring how to link data with identity, and especially for use-cases of personal, social, and collaborative apps, there is a lot of opportunity to join Ceramic and Textile.
There are 2 bounties available, one provided by Ceramic and one provided by Textile. Each for $500 for a total possible $1000. Be sure you submit your project to both bounties!
Requirements: In this bounty, we are encouraging developers to experiment and join these two projects in innovative new ways. Use Textile to store data on IPFS with Buckets, distribute events with Threads, or integrate Filecoin over the Hub alongside using Ceramic for smart documents or IDX for identity management.
Judging: The bounty will be paid to the most exciting application that uses Ceramic or IDX and makes use of Textile Buckets, Threads, or Hub to store or relay data on IPFS or Filecoin. Does your project make our jaw drop? Does it look great? Does it use the Ceramic, IDX, and Textile technologies deeply together? Does it use Textile and Ceramic in more than one way?
- Build file-sharing using Buckets to persist and IDX identities to discover, share, and permission.
- Use IDX and Threads to build large-scale group chat.
- Use IDX and Threads to create an embeddable support chat library for your (and other) dapp(s).
- Distribute or sell datasets stored in Buckets and managed in Ceramic documents.
- Textile Buckets — Object storage interface for IPFS, including remote persistence and Filecoin integration: https://docs.textile.io/buckets/
- Bucket Archiving — Store bucket snapshots on Filecoin: https://docs.textile.io/buckets/archiving/
- Textile Threads — Event sourcing and database protocol built on IPFS and Libp2p: https://docs.textile.io/threads/
- Powergate — A backend API manager and client for building on the Filecoin network: https://docs.textile.io/powergate/
- Ceramic — A decentralized network for managing mutable, verifiable information on IPFS, anchored in the Ethereum blockchain for consensus: https://developers.ceramic.network/build/quick-start/
- IDX Identity — A cross-platform identity protocol for managing users and their data, or discovering and importing data from third-party applications: https://developers.idx.xyz/learn/welcome/
- Ceramic and IDX tutorials — Guides, example apps, and demos; including how to use IDX to manage DB keys (ie. Textile): https://blog.ceramic.network/tag/tutorials/
Title: Best overall Near X Textile.io integration
With projects exploring how to link data with smart contracts, and especially for use-cases of data sovereignty, data marketplaces, and NFT assets, there is a lot of opportunity to join Near Protocol with Textile technologies. Interesting combinations of Near+Textile have in the past, included an off-chain Event Indexer for Near developers and community-based data storage for Near users.
There are 2 bounties available, one provided by Near and one provided by Textile. Each for $500 for a total possible $1000. Be sure you submit your project to both bounties!
Requirements: In this bounty, we are encouraging developers to continue the experimentation. Use Textile to store data on IPFS with Buckets, distribute events with Threads, or integrate Filecoin over the Hub from their project deployed to the Near Blockchain.
Judging: The bounty will be paid to the most exciting application deployed to Near that makes use of Textile Buckets, Threads, or Hub to store or relay data on IPFS or Filecoin. Does your project make our jaw drop? Does it look great? Does it use the Near and Textile technologies deeply? Does it use Textile and Near in more than one way? If yes, then you could be our winner!
Use Textile buckets to persist Near NFT assets on IPFS or Filecoin
Use Textile threads to exchange off-chain messages between Near addresses.
Use Textile mailbox API to leave encrypted, off-chain, messages between Near addresses.
Create a Near ↔ Filecoin bridge using Textile Powergate.
Title: Best integration of NuCypher encryption and Textile buckets for content distribution
Controlled access to off-chain data, such as NFT assets, private and/or organizational data, paid subscription content, etc remains difficult for web3 developers. Without centralized control, how do creators monetize their creations?! To address this and similar challenges, there is a lot of opportunity to join NuCypher and Textile technologies. The combination of proxy re-encryption with easy (IPFS-based) content storage and distribution via these two technologies paves the way to truly decentralized content distribution.
There are 2 bounties available, one provided by NuCypher and one provided by Textile. Each for $500 for a total possible $1000. Be sure you submit your project to both bounties!
Requirements: In this bounty, we are encouraging developers to continue the experimentation. Use Textile to store data on IPFS with Buckets, or integrate Filecoin over the Hub from their project, and use NuCypher to provide encryption-based access control to assets within a Bucket.
Judging: The bounty will be paid to the most exciting application that makes use of Textile Buckets to store or relay data on IPFS (or Filecoin), and allocates access to said data via NuCypher. Does your project make our jaw drop? Does it look great? Does it integrate NuCypher and Textile technologies deeply? Does it use Textile and NuCypher in more than one way? If yes, then you could be our winner!
Buckets + NuCypher: Use Textile Buckets as a way to host and distribute content secured and shared via NuCypher. Example, Alice encrypts data using NyCypher’s CLI or Python client. She then pushes that data to a Bucket with the Textile CLI. She grants access to that content to Bob, who can pull the data over IPNS, IPFS, or directly from Textile before accessing.
Filecoin + NyCypher: The same workflow is possible with Filecoin as the primary data storage layer. Developers can achieve this with Bucket Archives or Powergate. In the exchange step, Alice just needs to let Bob know the DealID and miner which they should pull the data from. Bob can pull the encrypted data with a Powergate client or using the Bucket Filecoin retrieval flow over the Textile Hub.
Build a tool where teams can grant or revoke internal documents or data to team members.
Build a paid subscription platform where authors can automatically grant subscribers access to the latest content.
Build a digital goods marketplace, where buyers are granted limited time access to goods.
Powergate Python — https://github.com/pygate/pygate-gRPC
open source. video, blog post, or readme summarizing the effort and explaining use of required technologies.
How vital was the required technology to the solution? Was the idea unexpected, executed in a novel way, or designed beautifully? Does it solve a known problem or have a known user? How difficult is it to start using?