Update Muxed Accounts Page #1905
Conversation
|
Preview is available here: |
briwylde08
changed the title
|
Preview is available here: |
|
Preview is available here: |
|
Preview is available here: |
|
Preview is available here: |
| At the protocol level: | ||
|
|
||
| - A **muxed account** = `G...` base account + 64-bit muxed ID. | ||
| - A **muxed address** = the `M...` strkey encoding of that pair for use in classic operations. |
There was a problem hiding this comment.
Muxed addresses are usable in soroban operations too. They're not limited to classic.
| You are using **muxed accounts** (concept + IDs) without exposing `M...` addresses to end users. | ||
|
|
||
| #### 2. Full M-address UX (classic payments) |
There was a problem hiding this comment.
What does classic payments mean here?
|
|
||
| When combining pooled accounts with muxed accounts, the typical exchange workflow depends on whether you are dealing with **classic payments** or **contract tokens.** | ||
|
|
||
| ### Classic payments (XLM / classic assets) |
There was a problem hiding this comment.
I'm not sure about the reference to "classic" in all these titles and sections. Stellar assets are available outside of contracts and inside contracts.
|
|
||
| The same `MuxedAccount` object can be passed anywhere an account source or destination is expected when building transactions with `TransactionBuilder`. | ||
|
|
||
| #### Elixir SDK: |
There was a problem hiding this comment.
What's the reason for exampling with the Elixir SDK here? That SDK doesn't appear to have been updated since protocol 18. See https://hexdocs.pm/stellar_sdk/readme.html. It's probably not the best to use in examples. We probably only need one SDK as a general example, and folks really need to go to the SDKs to actually look at their docs.
#2037
https://developers-pr1905.previews.kube001.services.stellar-ops.com/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos