From ed419a3e0c7cab21a2684113cb54857f3b741da8 Mon Sep 17 00:00:00 2001
From: Leigh <351529+leighmcculloch@users.noreply.github.com>
Date: Mon, 3 Aug 2026 23:46:40 +1000
Subject: [PATCH 1/5] allow additional topics and optional asset name topic

---
 ecosystem/sep-0041.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/ecosystem/sep-0041.md b/ecosystem/sep-0041.md
index a7b89e6fb..c9e4fa892 100644
--- a/ecosystem/sep-0041.md
+++ b/ecosystem/sep-0041.md
@@ -176,6 +176,10 @@ format and a map data format. The map data format encodes the event data as a
 in this SEP. Event consumers must be able to handle keys they do not recognize,
 and are expected to support both formats.
 
+Implementers may emit additional topics beyond those defined for each event.
+Any event may optionally include the asset name as an additional topic, emitted
+as a `String` after the defined topics.
+
 #### Approve Event
 
 The `approve` event is emitted when the allowance is set.
@@ -309,6 +313,8 @@ and a clawback action that emits a clawback event must reduce total supply.
   no separate burn or transfer event is emitted alongside the clawback event.
 - `v0.5.0` - Document the single-value/vec and map data formats for all events,
   generalizing the form already used by `transfer` and `mint`.
+- `v0.5.1` - Clarify that implementers may emit additional topics, and that any
+  event may optionally include the asset name as an additional topic.
 
 ## Implementations
 

From e4f95a9b18df4decff959c7ba96d30e34a34d6ba Mon Sep 17 00:00:00 2001
From: Leigh <351529+leighmcculloch@users.noreply.github.com>
Date: Mon, 3 Aug 2026 23:53:57 +1000
Subject: [PATCH 2/5] recommend additional topics be documented in a SEP

---
 ecosystem/sep-0041.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ecosystem/sep-0041.md b/ecosystem/sep-0041.md
index c9e4fa892..214417908 100644
--- a/ecosystem/sep-0041.md
+++ b/ecosystem/sep-0041.md
@@ -177,8 +177,8 @@ in this SEP. Event consumers must be able to handle keys they do not recognize,
 and are expected to support both formats.
 
 Implementers may emit additional topics beyond those defined for each event.
-Any event may optionally include the asset name as an additional topic, emitted
-as a `String` after the defined topics.
+To improve interoperability, it is recommended to do so as part of a SEP that
+documents the behavior and when contracts should emit those additional topics.
 
 #### Approve Event
 

From 2090409cfecb976586cf70153d67c26b98faf87f Mon Sep 17 00:00:00 2001
From: Leigh <351529+leighmcculloch@users.noreply.github.com>
Date: Tue, 4 Aug 2026 00:06:51 +1000
Subject: [PATCH 3/5] Fix prettier formatting and bump version to 0.5.1

---
 ecosystem/sep-0041.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/ecosystem/sep-0041.md b/ecosystem/sep-0041.md
index 214417908..04816ad8b 100644
--- a/ecosystem/sep-0041.md
+++ b/ecosystem/sep-0041.md
@@ -6,8 +6,8 @@ Title: Soroban Token Interface
 Authors: Jonathan Jove <@jonjove>, Siddharth Suresh <@sisuresh>, Simon Chow <@chowbao>, Leigh McCulloch <@leighmcculloch>
 Status: Draft
 Created: 2023-09-22
-Updated: 2026-06-08
-Version 0.5.0
+Updated: 2026-08-03
+Version 0.5.1
 Discussion: https://discord.com/channels/897514728459468821/1159937045322547250, https://github.com/stellar/stellar-protocol/discussions/1584
 ```
 
@@ -176,8 +176,8 @@ format and a map data format. The map data format encodes the event data as a
 in this SEP. Event consumers must be able to handle keys they do not recognize,
 and are expected to support both formats.
 
-Implementers may emit additional topics beyond those defined for each event.
-To improve interoperability, it is recommended to do so as part of a SEP that
+Implementers may emit additional topics beyond those defined for each event. To
+improve interoperability, it is recommended to do so as part of a SEP that
 documents the behavior and when contracts should emit those additional topics.
 
 #### Approve Event

From a070f39874b26aeaef0225638c0547b8b911e117 Mon Sep 17 00:00:00 2001
From: Leigh <351529+leighmcculloch@users.noreply.github.com>
Date: Tue, 4 Aug 2026 00:09:04 +1000
Subject: [PATCH 4/5] fix v0.5.1 changelog entry

---
 ecosystem/sep-0041.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ecosystem/sep-0041.md b/ecosystem/sep-0041.md
index 04816ad8b..26385bc16 100644
--- a/ecosystem/sep-0041.md
+++ b/ecosystem/sep-0041.md
@@ -313,8 +313,8 @@ and a clawback action that emits a clawback event must reduce total supply.
   no separate burn or transfer event is emitted alongside the clawback event.
 - `v0.5.0` - Document the single-value/vec and map data formats for all events,
   generalizing the form already used by `transfer` and `mint`.
-- `v0.5.1` - Clarify that implementers may emit additional topics, and that any
-  event may optionally include the asset name as an additional topic.
+- `v0.5.1` - Clarify that implementers may emit additional topics, recommending
+  doing so as part of a SEP that documents the behavior.
 
 ## Implementations
 

From 958300b7e4d7b8ecf69da798a9941998d724e864 Mon Sep 17 00:00:00 2001
From: Leigh <351529+leighmcculloch@users.noreply.github.com>
Date: Tue, 4 Aug 2026 00:09:18 +1000
Subject: [PATCH 5/5] shorten v0.5.1 changelog entry

---
 ecosystem/sep-0041.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/ecosystem/sep-0041.md b/ecosystem/sep-0041.md
index 26385bc16..7bc8cd3d5 100644
--- a/ecosystem/sep-0041.md
+++ b/ecosystem/sep-0041.md
@@ -313,8 +313,7 @@ and a clawback action that emits a clawback event must reduce total supply.
   no separate burn or transfer event is emitted alongside the clawback event.
 - `v0.5.0` - Document the single-value/vec and map data formats for all events,
   generalizing the form already used by `transfer` and `mint`.
-- `v0.5.1` - Clarify that implementers may emit additional topics, recommending
-  doing so as part of a SEP that documents the behavior.
+- `v0.5.1` - Clarify that implementers may emit additional topics.
 
 ## Implementations