From d157cc8a536187f589531cc9f44f45d730bf2648 Mon Sep 17 00:00:00 2001
From: Philipp Gackstatter <philipp.gackstatter@iota.org>
Date: Fri, 3 Nov 2023 10:22:31 +0100
Subject: [PATCH] Add Anchor Address in Restricted Address

---
 tips/TIP-0050/tip-0050.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tips/TIP-0050/tip-0050.md b/tips/TIP-0050/tip-0050.md
index f9ca70f81..aa915aa57 100644
--- a/tips/TIP-0050/tip-0050.md
+++ b/tips/TIP-0050/tip-0050.md
@@ -91,6 +91,10 @@ The following table shows the serialization of a _Restricted Address_:
         <summary>NFT Address</summary>
         <blockquote>An Address derived from an NFT ID which can be unlocked by unlocking the corresponding NFT. Defined in <a href='../TIP-0038/tip-0038.md#nft-address'>TIP-38 (NFT Address)</a>.</blockquote>
       </details>
+      <details>
+        <summary>Anchor Address</summary>
+        <blockquote>An Address derived from an Anchor ID which can be unlocked by unlocking the corresponding Anchor. Defined in <a href='../TIP-0038/tip-0038.md#anchor-address'>TIP-38 (Anchor Address)</a>.</blockquote>
+      </details>
       <details>
         <summary>Multi Address</summary>
         <blockquote>Defines a Multi Address that consists of addresses with weights and a threshold value. The Multi Address can be unlocked if the cumulative weight of all unlocked addresses is equal to or exceeds the threshold. Defined in <a href='../TIP-0052/tip-0052.md#multi-address'>TIP-52 (Multi Address)</a>.</blockquote>