IPFS server
Overview
In Toolther, IPFS plays a key role in storing token logos and metadata for every SPL token created through the platform. While external services like Pinata, NFT.Storage, or Web3.Storage are useful for testing and small projects, operating your own IPFS gateway brings clear advantages in scalability, performance, and reliability.
This document describes the benefits of using a self-hosted IPFS node for Toolther, how it improves token storage and branding consistency, and outlines the next step toward building a Pinata-like hosted IPFS service under the Toolther ecosystem.
1. Why Self-Hosted IPFS Is Important for Toolther
1.1 Full Data Ownership
By hosting your own IPFS gateway, you control all uploaded metadata, logos, and JSON schemas. This ensures your tokens remain accessible independently of third-party services.
1.2 Stable and Predictable Gateway URLs
Using your own domain (e.g., https://gw.toolther.app/ipfs/...) allows Toolther tokens to reference metadata under a consistent namespace, improving trust and brand recognition.
This is especially valuable when:
Verifying tokens on Solana explorers.
Publishing project pages or whitepapers.
Building a long-term community brand.
1.3 Higher Uptime and Availability
Unlike public gateways that can throttle or rate-limit traffic, your own node guarantees:
Direct control over caching policies.
Optimized delivery speed for token metadata and logos.
No downtime from third-party outages.
1.4 Custom Gateway Behavior
You can configure:
Custom CORS headers for direct app integration.
Compression and long-term caching (Cache-Control headers).
Content whitelisting or private asset handling for pre-launch tokens.
1.5 Integration with Future Toolther Services
Running your own IPFS node is the foundation for the next major Toolther feature: a decentralized, multi-node “Toolther IPFS Cloud”, where users can pay in SOL or USDC to pin and replicate their assets automatically.
2. Benefits for Toolther Token Creators
Feature
Third-Party IPFS (Pinata, NFT.Storage)
Self-Hosted IPFS
Upload Control
API-based (external limits)
Full control via CLI or API
Data Retention
Depends on provider policy
Permanent while node runs
Gateway URL
Shared and public
Custom under your domain
Branding
Generic
Fully branded (e.g., gw.toolther.app)
Performance
Variable
Tuned for Toolther UI/API needs
Security
Shared environment
Private and auditable
3. Roadmap: Building a Pinata-like Service
Phase 1: Internal IPFS Infrastructure
Deploy multiple IPFS nodes under the Toolther domain.
Implement automatic pinning and replication between nodes.
Expose an internal REST API for uploads from Toolther App.
Phase 2: Public Upload API (Toolther Gateway)
Create an authentication layer (API key or connected wallet).
Support uploads directly from the Toolther web interface.
Introduce usage limits and paid pinning plans.
Phase 3: Toolther IPFS Cloud
Multi-region hosting for redundancy.
File deduplication and CDN-level caching.
Billing in SOL, USDC, or project tokens.
Dashboard for upload stats, pin status, and asset management.
Phase 4: Integration with Token Metadata Editor
Allow users to upload logos and metadata directly from Toolther’s token creation form.
Automatically generate and pin JSON metadata to the Toolther IPFS Cloud.
Store permanent IPFS CIDs in on-chain token metadata.
4. Long-Term Vision
The goal is to make Toolther a complete token infrastructure provider — not just for minting tokens, but also for:
Hosting and securing token metadata.
Managing decentralized assets.
Providing high-speed, brand-consistent IPFS gateways.
This approach makes Toolther independent from centralized APIs and positions it as a trustless token creation and hosting platform within the Solana ecosystem.
Last updated