15 reasons to build with Tusky API

Walrus is a decentralized, blockchain-agnostic storage and data availability protocol developed by Mysten Labs. Building on top of this, Tusky introduces a file management system abstraction, end-to-end encryption, fiat payments and access control, ensuring a seamless, edge-optimized solution that meets the needs of both developers looking to leverage Walrus as a storage solution.

In this article we look at the Walrus API and highlight the additional benefits that working with the Tusky API delivers. 

1. Developer experience

Walrus API requires Walrus and Sui experience to set up and run, especially for production use. Users must manage their own SUI wallet with tokens and run the Walrus daemon. Walrus does not have a file system, so users must work directly with file IDs. Additionally, the storage epoch management requires users to keep files alive on their own.

Tusky API is extremely developer-friendly, with a JavaScript SDK and CLI coming in testnet for seamless integration. Users don’t need to handle wallet management, as the API integrates with familiar web2 services (Google, Facebook and Twitch) and uses JWT tokens for authentication. Tusky provides a structured file system with vaults and folders, making it easy to manage and retrieve files. The setup process is streamlined, with no technical complexity regarding file management or re-uploading files after storage epochs expire.

2. File system and structure

Walrus API does not have an integrated file system for managing directories or folders.

Tusky API provides a full file system layer that allows users to organise files in directories, handle trash management, and treat it as if they are working with a local disk.

3. Speed and efficiency

Walrus API users must handle files directly, which can be slower or more complex, especially when managing bulk uploads.

Tusky API is optimized for speed, as it accepts file uploads and stores them asynchronously to Walrus, providing a fast, user-friendly experience. It supports chunked uploads and allows for resumable uploads, so users can pause and resume the process anytime, ensuring efficient handling of large files.

4. End-to-end encryption

Walrus API does not provide built-in encryption features. Users must implement their own encryption layers if they require this level of security.

Tusky API supports end-to-end encryption for vaults. Files are encrypted on the client side before being uploaded, and users control keys, ensuring that only authorized users can access the data.

5. Storage epoch management

Walrus API users must manually declare the storage period for each file and are responsible for extending it to prevent deletion.

Tusky API automatically handles the extension of storage epochs, taking this responsibility off the user's shoulders. Future updates (Epoch Vaults) will give users more granular control over storage periods.

6. Authentication and access control

Walrus API requires users to manage their own SUI wallet and tokens.

Tusky API uses simple web2-based authentication, allowing users to log in via Google and Twitch. Users can also authenticate using a Sui wallet. For developers, Tusky provides the option to authenticate using API keys on the server side, adding flexibility for backend integrations.

Additionally, Tusky's API has vault memberships with customizable permissions (Admin, Contributor, or View only), making access control possible. An admin can also invite other members using magic links.

7. Payments

Walrus API does not have payment features for managing storage or services, requiring users to handle their own SUI tokens and wallets.

Tusky API supports fiat payments for a subscription-based Pro plan, making it easier for users to manage costs. Support for crypto payments at the API level is in the roadmap, as well as the ability to prepay for long term storage as specified periods of time/epochs (Epoch Vaults).

8. File availability and CDN support

Walrus API requires users to manage file availability by maintaining epochs, and it does not offer built-in support for CDN-backed public access.

Tusky API provides access to files through a CDN-backed, edge-optimized caching layer, enhancing speed and reliability for file retrieval.

Additional API features

9. Zip uploads

Tusky supports zip uploads, which can be automatically unpacked and stored in the file system. This simplifies the process of uploading large sets of files at once, offering users a way to efficiently handle bulk data transfers.

10. Event subscriptions/notifications

Tusky's API integrates with HTTP webhooks and websockets, allowing users to subscribe to key events, such as file uploads or transactions. This real-time event handling can automate workflows and improve efficiency for developers building applications on top of Tusky.

11. Multi-purpose usage via SDK & CLI

Tusky's API is mirrored by a JavaScript SDK, making it extremely easy for developers to integrate its features into their applications. For power users, Tusky offers a CLI that provides similar benefits as the SDK but within a console environment.

Roadmap

12. Epoch Vaults, perpetual storage

Tusky plans to introduce Epoch Vaults, designed for long-term storage. Users will be able to define a storage period for each upload, based on the available credits in their account and the maximum duration supported by Walrus.

13. Accepting crypto payments

In the future, Tusky will accept crypto payments, making the platform even more accessible to users. This will complement the fiat payment options already in place and offer more payment flexibility.

14. Minting tokens on Sui

Tusky will allow users to mint tokens on the Sui blockchain, with the underlying assets stored on Walrus.

15. Token-gated access

Tusky is developing token-gated access to private vaults. These vaults will be access controlled by tokens, supporting gating mechanisms across Sui, Ethereum, and Solana.

Get started

Tusky's API offers a much more streamlined and developer-friendly experience, with simplified setup, automated storage management, and support for familiar authentication methods and payments.

Get started with our docs.