From 34512745141d768536cb785fcc1bd6a5b6cf3033 Mon Sep 17 00:00:00 2001 From: Tom Wilson Date: Sat, 4 Feb 2023 09:51:27 -0500 Subject: [PATCH] Update ANS-108.md Include the option for ArNS Subdomain --- ans/ANS-108.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ans/ANS-108.md b/ans/ANS-108.md index aecfb0f..09f543e 100644 --- a/ans/ANS-108.md +++ b/ans/ANS-108.md @@ -18,12 +18,12 @@ The entire specification for a data uploader consists of a simple tag that Arwea | Tag Name | _Optional?_ | Tag Value | |---|---|---| -|Render-With|False|`Renderer-TX-ID`| +|Render-With|False|`Renderer-TX-ID || ArNS Subdomain`| ### Gateways -When serving data stored on Arweave, if a particular Arweave `TX-ID` contains the `Render-With` tag, gateways MUST use the information stored in the `Render-With` tag to redirect from `/{TX-ID}` to `/{Renderer-TX-ID}?tx={TX-ID}`, _unless_ the original transaction came with a `?render=false` query parameter. +When serving data stored on Arweave, if a particular Arweave `TX-ID` contains the `Render-With` tag, gateways MUST use the information stored in the `Render-With` tag to redirect from `/{TX-ID}` to `/{Renderer-TX-ID or ArNS Subdomain}?tx={TX-ID}`, _unless_ the original transaction came with a `?render=false` query parameter. As an example, consider serving [Metaweave](https://metaweave.xyz/) post data via the arweave.net gateway. When any user accesses `https://arweave.net/MetaweavePostID`, they are redirected to `https://arweave.net/MetaweaveRendererID?tx=MetaweavePostID` if the `MetaweavePostID` Arweave transaction contains the tag `Render-With: MetaweaveRendererID`.