the Autonomi door

a picture from the network

this picture lives on the Autonomi network, not on our servers. your browser asks for it through the estate's door. nothing to install.
public data, public reads. we hold no keys here.
open it where the door runsrelay.skaists.dev · opens in a new tab
one request, to this address only.

see it where the door runsrelay.skaists.dev · opens in a new tab
public DataMap · mainnet · read same-origin through the estate's GET-only door
keys held by the estate here = nonepublic data, public reads

the request · this page, now

the read · five steps this page sees

    behind the door, by design and not observable from this page: Caddy passes GET /ant/* to a local read-only antd (every other method refused), which reads the DataMap from Autonomi mainnet.

    the receipt on record · not live

    verify · no trust in this page needed

      the whole door

      ⬡ the Autonomi door

      estate page · reads Autonomi bytes same-origin — no plugin, no visitor-side daemon

      public data from the network

      fetching through the estate's door…
      autonomi://711c7e20006ff3e0ac6c1f3063286a0c1a3e4c409642e8c526173fa60bb7078a
      · · ·

      what you are looking at — three audiences

      the neighbor — this image lives on the Autonomi network, not on our servers. Your browser fetched it through the estate's door, in one same-origin request. Nothing to install, nothing to configure.
      the builder — the page calls /ant/v1/data/public/<address> on this origin; Caddy proxies to a local read-only antd gateway (GET-only, all other endpoints refused). Open your network tab: one request, this origin, no third parties.
      the cypherpunk — the door is a bridge, not the destination. Direct browser access — the page itself speaking the network's post-quantum protocol — lands when Autonomi's WASM client ships. When that day comes, this door retires and the fetch goes peer-to-peer. The estate holds no keys here: public data, public reads.