<aside> ℹ️ Siasky.net has become a victim of its growth. The usage has attracted abuse and censorship by spam filters and even Twitter. By putting engineering efforts into additional portals run by Skynet Labs and aiding community-run portals, we’re excited to provide additional ways to access Skynet. We’re introducing more ways to access Skynet without sharing a portal’s resources with anonymous users. More will be announced next week.
</aside>
You’ll want to use another portal for you’ll need to change which portal your Skynet client connects to. For now, we only recommend this for “server-side” behavior like running Github Actions, proxies, or code where you can store API keys privately.
You need to take these steps:
skynet-jwt
value. This works like an API key.skynet-jwt
values.<aside>
⏱️ Seeing this after 3/8/2022? We probably have working API Keys. This documentation should be updated shortly. (Soon.)
</aside>
You can either signup for a free account (no Stripe information) at skynetfree.net registration, or you can use skynetpro.net registration for a paid tier account. If you don’t have a promo code for skynetpro.net, but think you should, please reach out.
Alternatively, you can try a community-run portal like fileportal.org.
skynet-jwt
value?After logging in to the portal, please follow the instructions here, but using your portal’s domain (not siasky.net, as in the examples).
<aside> ℹ️ Private API keys are being tested, but aren’t implemented into all of our tooling. This should be rolled out well before your skynet-jwt expires in 30 days.
</aside>
If you’re using the Deploy to Skynet Github Action, you can specify a portal url and skynet-jwt value in your yaml file. You’ll want to store your skynet-jwt
as a Github Secret!
See the documentation README or this example script for more info.
<aside>
ℹ️ The value you pass to the skynet-jwt
input of the action should not include the cookie prefix of skynet-jwt=
, only the data after it.
</aside>
Not yet. We have “Public API Keys” on our roadmap, which will let you “sponsor” users accessing your Skynet-hosted site via your traditional domain name, but