The SAFE Network Primer
Websites on the SAFE Network
can be identied using URLs thus
safe://mysite.alice). Working in a
similar way as the familiar Internet
Domain Name System (DNS), these
human-readable addresses are
translated into network addresses
on SAFE using the Decentralized
Naming System - also abbreviated
On the SAFE Network the DNS takes
a hash of the Public_ID, so ‘alice’
in our example becomes a string
of 256 characters. The browser
takes this hash and uses it as the
address to nd the corresponding
MutableData entity from which it
obtains the address of the site on
the NFS that matches the Service
The browser nds the Services
container for the public ID ‘alice’,
and it retrieves the entry whose key
matches the service name ‘mysite’.
The value stored in this entry contains a reference to the NFS container (a MutableData entity with
type tag set to 15002) where the browser can retrieve the names of the les that make up the
website along with the addresses of the ImmutableData entities where these les’ content is stored.
With this information it can start retrieving the website’s les and rendering them on the UI.
Tell me more
(click on links)
MutableData (MaidSafe RFC)
Distributed network with opportunistic data caching (MaidSafe)
Maidsafe NFS API documentation
File Storage (NFS) –
an API that allows a Client to access
a collection of les stored over the SAFE Network.
Decentralized Naming System (DNS) – analogous to the
Domain Name System on the Internet (also DNS), this is a
system that translates a human-readable web address into
a network XOR address.
Public ID – chosen name for an account (e.g. alice or
maidsafe). An account may register any number of Public
IDs so long as they have not been registered previously.
Service name – the name of a service such as a website,
email or chat app. So if Alice’s website was called mysite the
URL would be mysite.alice.
Data map – a record retained within a User Account which
contains all the information necessary to decrypt a user’s
le stored on the SAFE Network.
Type tag – allows apps to identify the type of data: 15001
Public ID; 15002 Service Name; 15003 Email ID; 15004
Opportunistic caching - automatic creation of more copies
of popular data close to where it is being requested, so
popular websites and other data feeds will actually speed up
as they get more visitors, rather than slow down as they do
on today’s web.