Skip to content

SEP-57: Add muxed address event #2013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leighmcculloch merged 2 commits into from
Sep 9, 2026
+21 −2
Merged

SEP-57: Add muxed address event #2013

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e20f7ea
muxed address event for rwa
ozgunozerk Sep 8, 2026
425fa38
Merge branch 'master' into sep-57-muxed-transfer
leighmcculloch Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 21 additions & 2 deletions ecosystem/sep-0057.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ Title: T-REX (Token for Regulated EXchanges)
Author: OpenZeppelin, Boyan Barakov <@brozorec>, Özgün Özerk <@ozgunozerk>, Dennis O'Connell <@droconnel22>
Status: Draft
Created: 2025-11-26
Updated: 2026-06-11
Version: 0.3.0
Updated: 2026-09-08
Version: 0.4.0
Discussion: https://github.com/orgs/stellar/discussions/1814
```

Expand Down Expand Up @@ -501,6 +501,23 @@ pub struct Transfer {
}
```

When `transfer` targets a `MuxedAddress` with a muxed ID, the event data also
carries the ID, as in SEP-41. Identity verification, compliance and freezing
operate on the base address; the ID is only recorded in the event.

```rust
#[contractevent(topics = ["transfer"])]
pub struct MuxedTransfer {
Comment on lines +509 to +510

@leighmcculloch leighmcculloch Sep 9, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heads up that with soroban-sdk v28+ if to_muxed_id: None then the result of the MuxedTransfer event will be identical to the Transfer event and we can start describing events with a single shape.

#[topic]
pub from: Address,
#[topic]
pub to: Address,
/// The muxed ID of the destination
pub to_muxed_id: Option<u64>,
pub amount: i128,
}
```

### Mint Event

The mint event is emitted when tokens are minted to a verified address.
Expand Down Expand Up @@ -1531,3 +1548,5 @@ on-chain.
`TransferKind` (`Standard` / `Delegated(spender)` / `Forced`) parameter to
`transferred`, letting modules exempt privileged (forced/recovery) operations
from policy while still applying bookkeeping.
- `v0.4.0` - Add the muxed layout of the transfer event (`MuxedTransfer`),
emitted when `transfer` targets a `MuxedAddress` with a muxed ID.
Loading