This will get you to a shared Neighbourhood on Holochain in less than 20 minutes! The code assumes an ad4m variable was setup as described in Getting Started.

1. Create a Perspective and add content

Adding a new perspective is as easy as

const myPerspective = await ad4m.perspective.add("My new perspective")

The returned object is of type PerspectiveProxy, which hides all the remote calls to the AD4M executor and can be treated like a local database object.

Perspectives are basically local graph databases. We can query all links on that proxy object with get:

const allLinks = await myPerspective.get(new LinkQuery({})) // => []

In this case it should return an empty array since we just created that perspective.

So let's add something! With the following code I'm creating an adhoc semantic statement representing what I think about AD4M...

import { Literal } from '@perspect3vism/ad4m'

const me = await ad4m.agent.me()
const source = me.did
const predicate = Literal.from("thinks").toUrl()
const target = Literal.from("AD4M will be the last social network").toUrl()

const linkExpresion = await myPerspective.add({source, predicate, target})

Links consist of 3 URIs pointing to Expressions of Languages. For this example, we made life easy by using the agent's DID and AD4M's Literal Language.

Agent DID

For the source of our link, we got the user's DID URI by first getting the users Agent object with ad4m.agent.me(). That has a DID property and DID URIs are considered valid URIs in AD4M (they can be looked-up using the Agent bootstrap language which resolves to the same Agent object we got through ad4m.agent.me() - just even if that agent behind the resolved DID isn't me).


The Literal Language is an AD4M Language without back-end. It stores JavaScript literals (i.e. strings, numbers and objects) by encoding them into the Expression URL. So,


returns literal://string:thinks - which is a valid URI - and

Literal.from("AD4M will be the last social network").toUrl()

returns literal://string:AD4M%20will%20be%20the%20last%20social%20network. This is basically like URL parameters and let's us get around introducing Languages before using Perspectives and Links.

We can decode the URL into a JavaScript literal like so:

const string = Literal.fromUrl('literal://string:thinks').get()
// string == 'thinks'


We have put in a Link object into myPerspective.add() ({source, predicate, target}), but what this function returns is a LinkExpression.

Even though this Perspective is not shared (yet) but just our private, local graph database, we might want to share it later as Neighbourhood. Then, all links added by some agent to their local Perspective will be shared with the other agents using a LinkLanguage - a Language which defines Expressions representing Links. That is LinkExpressions.

Using the generic Expression template, LinkExpressions wrap Links with author, timestamp and signature:

    author: "did:key:zQ3shNWd4bg67ktTVg9EMnnrsRjhkH6cRNCjRRxfTaTqBniAf",
    timestamp: "Sun Oct 23 2022 15:31:52 GMT+0200 (Central European Summer Time)",
    data: {
        source: "did:key:zQ3shNWd4bg67ktTVg9EMnnrsRjhkH6cRNCjRRxfTaTqBniAf",
        predicate: "literal://string:thinks",
        target: "literal://string:AD4M%20will%20be%20the%20last%20social%20network",
    proof: {
        key: "#zQ3shNWd4bg67ktTVg9EMnnrsRjhkH6cRNCjRRxfTaTqBniAf",
        signature: "xxxx",

2. Publish Perspective as Neighbourhood

The back-bone of a Neighbourhood is a LinkLanguage - a Language that enables the sharing and thus synchronizing of links (see LinksAdapter). While there can and will be many different implementations with different trade-offs and features (like membranes etc.), there currently is one fully implemented and Holochain based LinkLanguage with the name Perspective Diff Sync.

It is deployed on the current test network (Language Language v0.0.15, included in current network seed) under the address: QmeBD9n9Z5yZsegxArToww5zmwtPpojXN6zXJsi7WwMUa8.

Creating our unique LinkLanguage clone through templating

But we should not just use this publicly known Language as the back-bone for our new Neighbourhood, if we don't want to have everybody following this guide end up in the same network.

So what we want is to use this existing Language as a template and create a new copy with the same code but different UUID and/name in order to create a fresh space for our new Neighbourhood.

What parameters can we adjust when using it as template? Let's have a look at the Language's meta information:

const socialContextMeta = await ad4m.languages.meta(

Which should yield something like this:

  name: 'Perspective Diff Sync',
  address: 'QmeBD9n9Z5yZsegxArToww5zmwtPpojXN6zXJsi7WwMUa8',
  description: 'Holochain based LinkLanguage. First full implementation of a LinkLanguage, for collaborative Neighbourhoods where every agent can add links. No membrane. Basic template for all custom Neighbourhoods in this first iteration of the Perspect3vism test network.',
  author: 'did:key:zQ3shkkuZLvqeFgHdgZgFMUx8VGkgVWsLA83w2oekhZxoCW2n',
  templated: false,
  templateSourceLanguageAddress: null,
  templateAppliedParams: null,
  possibleTemplateParams: [ 'uuid', 'name', 'description' ],
  sourceCodeLink: 'https://github.com/perspect3vism/perspective-diff-sync'

The field possibleTemplateParams tells us that we can set a UUID and override name and description. Let's leave description but change the name. The function languages.applyTemplateAndPublish() takes an object as JSON as second parameter like so:

const uniqueLinkLanguage = await ad4m.languages.applyTemplateAndPublish(
        "uuid": "84a329-77384c-1510fb", 
        "name": "Perspective Diff Sync clone for demo Neighbourhood"

This function call has done a lot for us:

  1. It took the source language (first parameter) and made sure we got the code, i.e. potentially downloading it from the Language of Languages.
  2. The provided template parameters have been applied. In the case of a Language using Holochain, it has unpacked the Holochain DNA, changed the DNA variables according to the values given as template parameters and packed the DNA again (not touching the WASM code)
  3. The resulting Language was published with meta information showing that it was templated, providing the source hash and template parameters.

So the new templated Language is ready to be used.

Creating the Neighbourhood

With that new LinkLanguage, actually creating the Neighbourhood is simple. We just have to provide the id of the perspective we want to upgrade to a Neighbourhood and the address of the LinkLanguage used for that:

const meta = new Perspective()
const neighbourhoodUrl = await ad4m.neighbourhood.publishFromPerspective(
console.log(neighbourhoodUrl) // => neighbourhood://Qm123456789abcdef

The meta field a (static/snapshotted) Perspective that is immutably stored with the Neighbourhood. It can hold arbitrary/semantic meta information about the Neighbourhood but can technically stay empty, just like we did here.

3. Joining a Neighbourhood (on another node/agent)

Assume everything above happened on Alice's agent. Alice now shares the Neighbourhood's URL with Bob. This is what Bob does to join the Neigbourhood, access it as a (local) Perspective and retrieve the Expression Alice created and linked there:

const joinedNeighbourhood = await ad4m.neighbourhood.joinFromUrl(neighbourhoodUrl)
const myPerspective = await ad4m.perspective.byUUID(joinedNeighbourhood.uuid)
const links = await myPerspective.get(new LinkQuery({
    predicate: Literal.from("thinks").toUrl()
links.forEach(async link => {
    const who = link.data.source
    const what = Literal.fromUrl(link.data.target).get()
    console.log(who, " thinks that ", what)

4. Listening to Perspective changes

Perspectives that have been turned into Neighbourhoods are like entangled particles. Every agent still has their local copy of the Perspective, but a change from any agent will be shared with all other agents immediately, resulting in AD4M automatically updating the local Perspective with the changes by the others.

Even with Perspectives that are not shared as Neighbourhood, a different UI could have access to the same Perspective and cause mutations on it.

Apps/UIs can simply register a listener function on that PerspectiveProxy object:

myPerspective.addListener('link-added', (addedLink: LinkExpression) => {
    console.log("Got a new link:", addedLink)

myPerspective.addListener('link-removed', (removedLink: LinkExpression) => {
    console.log("A link was removed:", removedLink)