- About
- Initiatives we focus on
- @Reliable, decentralized, and verified retrieval of CIDs in browsers
- @Specifications for end-to-end HTTP retrieval and deserialization of popular content-addressed data
- @Welcome pre-existing content addressed data via supporting large blocks
- @IPFS for pioneers - Enable building interoperable IPFS systems using HTTP protocols
- @Self-service tooling for debugging IPFS request handling
- @Deny list primitive
- @Examples showing how to solve problems in user space
About
Below are the list of initiatives we intend to work on in 2024! This work is beyond our continued solid maintainership of various IPFS implementations, tools, services, and specs where we handle bug fixes, security patches, dependency updating, community contribution landing, and releases. Clearer milestones and dates along with public Github issues will be articulated in early 2024 after we complete the initial graduation logistics from Protocol Labs Inc. In the interim, please feel free to Contact Us if you have any questions or consider supporting our efforts to make these a reality.
Initiatives we focus on
Reliable, decentralized, and verified retrieval of CIDs in browsers
Specifications for end-to-end HTTP retrieval and deserialization of popular content-addressed data
Welcome pre-existing content addressed data via supporting large blocks
Popular IPFS implementations like Kubo and Helia support the wide array of data that is already content addressed by developing sufficient specs and tooling to be able to support incrementally verifiable large blocks. The utility of IPFS moves closer new userbases, with content-addressable data from Docker containers to Blockchains state-trees now being viable for distribution with IPFS protocols without requiring any additional or duplicative processing.