Feature Requests - Long-term Storage

Network Name: Story Mainnet Chain ID: 1514 Rpc : https://mainnet.storyrpc.io

Sei V2 is an EVM-compatible L1 and has a flourishing NFT community. We need more providers to support this network. Thank you for considering!

Ever since I got into NFTs, I've been running my own IPFS node and I pin all collections that I own to help. I believe it would be a good idea to introduce a page on nft.storage website to show which NFTs have the smallest amount of nodes that offer their CIDs. Sorting by amount of nodes, trading volume would also be a good idea, to eg. find the most popular NFTs that at the same point are almost extinct on IPFS. There are certain data hoarding communities which have 1PB+ setups at their homelabs and would be willing to help. While outsiders might be hostile to the whole idea, it could be argued that well, there are collections that are legitimate art and not AI slop. In the feature I mentioned above, there could be a toggle to filter verified collections that are 100% human made. Hosting a node can be dangerous on some providers like Hetzner, so a guide on how to setup own IPFS node (that will be cheap to run and won't get your account banned, mentioning that kubo has a server profile is probably the most important thing) would be good. Not sure what the UX would be for selecting NFTs to pin, maybe we could select multiple collections from a grid and there would be a floating block with a bash one liner to pin metadata+imgs of all selected collections? Long term maybe it would be possible to pair the node with a wallet and get paid tokens for pinning? No idea if Kubo does signing/authentication so pinning might be impossible to prove. Since you guys want to decentralize the whole idea about preserving NFTs, I think this would be a good move.

I would appreciate if you add it. thanks

Please add PulseChain support. Thank you for your consideration !!

I have all CAR files of all my CIDs locally on my computer. (downloaded with lassie fetch) I think it would be easier and safer for you if I could provide/upload the ipfs content archive files (CAR archives) of all my CIDs to be imported into nft.storage . This way you don't have to retrieve the CIDs from the nodes that may be down or very slow. The car archives files contain the complete ILPD DAG structure. You will also send these files to Filecoin to get Filecoin deals. After that you can delete this car files from your server.

Will be attractive to the real developers on XRPL / Xahau

I realize the company has built its product targeting what seems like a mainnet solution for 10k PFPs where all of the tokens are generated at once. So the request for a sandbox with this in mind does not make sense. I am working on a project that incrementally mints tokens over time. And in this scenario I was using the classic solution to upload an image and the metadata file to IPFS vis nft.storage one at a time. Therefore, in looking at the new product I was hoping to due some testing on incremental token uploads, one at a time. To do this, I wanted to test the http API to make sure that I was crafting the API call correctly. I am now using the Pinata APIs to store the image and metadata files, then I wanted to persistently store the just minted token id with the metatdata CID to ntf.storage . I am testing all this on the Base Sepolia testnet, hence the inquiry into testnet support. Again, this request doesn't make sense if the primary product is intended for mainnet token launches following the 10k PFP projects. I, however, am looking to use the nft.storage API to incrementally store minted NFTs as customers create them, in which case I would like to test the product against our testnet application, rather than against our mainnet application. From this github request: https://github.com/nftstorage/nft.storage/issues/2711