Skynet offers several advantages to developers:
Developers don't have to manage or pay for any infrastructure
Once deployed, applications are independent and need no further caretaking by the developer
Application data is user-controlled, available across applications, so your application can utilize pre-existing user information instead of starting from scratch.
You'll be able to monetize your application without the use of advertising
To get started, create a folder with an
This works for static sites, along with client-side rendered Single Page Applications. Check out our Skynet Workshop for a more in-depth walkthrough.
We just release major new features and breaking changes in our
skynet-js SDK. As we get the documentation together for the new features and breaking changes, you can start learning using these resources.
Skynet SDK Docs v4 Update Guide – Documents breaking changes from v3 and outlines the update
Content Record Viewer – Temporary home for sample app that reviews Content Record data.
Content Record Library Repo – When using a DAC, you import their library in your code so make calling the API of the DAC iframe simpler. This repo documents the Content Record DAC methods.
Official Documentation and SDKs
Skynet SDK Docs – Documentation for all the SDKs
Automated Deployments on Skynet – Blog post walking through how to use Github for automated build uploads and HNS updates
skynet-cli – Great tool for uploading directories from the command line.
Upload2Cloud – Windows Explorer integration for sending files and directories to Skynet. Python script available.
Vue CLI Deployment Plugin – Vue UI based tool for site upload with auto Namebase/Handshake updates
SkyDeploy – Command-Line Tool for easily deploying web apps on Skynet and setting the skyns records to point your HNS domain to the new version
py-skydb – Python Wrapper that you can use to interact with SkyDB portals
Skynet SDK for Dart – Use Sia Skynet and SkyDB in your Dart and Flutter projects
Skystandards – a proposal for data standards to be adopted in Skynet applications in such a way that users can share and use their data in different Skynet apps
If your website is structured to be client-side, then hosting it on Skynet is straightforward. If not, it is likely your website will need to reconsider some parts of its architecture to be fully-functional on Skynet.
Many of these will be incorporated into our Developer Guide, but in the meantime, some things to keep in mind:
For skapps, it's best to use and link URLs that are a subdomain of the portal domain. That means either using an HNS name as a subdomain like
<skapp>.hns.siasky.net or a Base32-encoded subdomain.
If linking to code on Skynet, you should use immutable skylinks when possible so that later updates don't risk breaking your code.
To be a proper "skapp," your application shouldn't be relying on external, centralized services to function. This means external requests to APIs for on-network storage or computation that would make your skapp's data not interoperable with other skapps.
Do not hardcode a specific portal domain into your code! This can be helpful for local development, but be sure to remove this before deploying to Skynet, so that the code isn't forced to use a portal other than the one it is being served from.