XPlorer following the chain as its own read-only node

height 23745 of 23745 on the network. 9 peer(s) connected, 77 in its peer directory; 1041 block(s) followed and 865 pulled in by sync since this follower started. Caught up: this follower holds every block any peer has claimed, so every panel below is the whole chain. Genesis 1cf8655125cc1bbb…, producers genesis.

What this follower is, locally

Following 7 seed(s) — their addresses are not published here, for the reason the peer table gives. Its store is held under its own Cerberus lease — no other node’s store is opened, touched or stopped.

Six dimensions. Infinite sovereignty.

HEX, the Hybrid EXchange over the chain. Buy STR with ETH or BNB, register an STR.domain, start a token, or bring a business onto SourceLess.

HEX for business

What SourceLess sets up for an organisation, from a free token to a chain of its own. This page is a catalogue: it takes no payment and collects nothing.

Token

Freeno fee on chain

A ZK13 token on SourceLess Asgard, written in the token wizard and deployed by you with your own key.

The token wizard, with every option checked against this chain
Deployed from your own proved STR.domain
Security inherited from the SourceLess validators

Create a token

Business Suite

$50,000paid in STR

Your organisation on SourceLess, set up with the SourceLess team.

A business STR.domain with its wNFT identity
A ZK13 token
Contracts from the 19 templates
Set up with the SourceLess team

Large fork

$250,000setup, plus annual managed hosting

A chain of your own, run on the SourceLess software and operated for you.

A dedicated Vanaheim chain
Contract execution
Encrypted storage (Oort and Accretion)
STR.talk messaging, built in
Payment options: transfers with memos, delegated spending, escrow and payment-splitter contracts
Custom software, by quote

Coming later

A point-of-sale terminal
A dedicated HEX and DEX on the fork

Plan a fork

What a fork does not get

Stated before what it gets, because this is the assumption that ruins a fork. Managed hosting runs the machines; it adds no shared security, no bridge and no migration path. Fork only if your asset must be native, your data must not sit on a chain other people read, or your regulator requires you to operate the validators.

No shared security. Your blocks are sealed by your seats and by nobody else. The SourceLess validators do not see your chain, hold no key on it, and could not help it if every one of your nodes went down.
No bridge. There is no path for value to move between your chain and SourceLess, or anything else. A fork is created fail-closed: it mints no $TR and refuses every collateral record.
Your own validator set to recruit. The genesis set is your whole producing capacity on day one, and adding a seat afterwards is a governance action at the 30-day delay.
Your own custody to perform. A rehearsal fork's keys can be derived by anyone who knows its name and id, so a fork that carries value has its keys made and held privately before it launches.
No real ZK13 prover. The reference provider refuses to run in production until a real prover is bound.
No migration path. Contract state cannot be moved onto a fork or off it across a genesis boundary.
No endpoint anybody else can reach, out of the box. Every port the fork command opens is loopback; a published endpoint, a domain name, TLS and a seed list are separate work.

Request an order

Write to the SourceLess team with the tier, your organisation and what you want to build:

support@sourceless.net

This page collects and stores nothing. There is no form here and no payment: an order starts with your email and is agreed in writing before any work begins.