This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
Add support for additional _muxed
and _muxed_id
optional fields in Horizon's JSON responses
#451
Labels
TL;DR
Add support for additional
_muxed
and_muxed_id
optional fields in Horizon's JSON responses (available since Horizon 2.4, following what's described in SEP 23). That is:For instance, here's an
/operations
response with the new fields:Note the:
"source_account_muxed"
and"source_account_muxed_id"
fields."from_muxed"
and"from_muxed_id"
fields.Also, note how, although the XDR destination address of the Payment operation is a Multiplexed Account, there are no
to_muxed
norto_muxed_id
fields in the response. This simply means that the XDR representation of the destination address is of typeKEY_TYPE_ED25519
and notKEY_TYPE_MUXED_ED2551
.Exhaustive list of new fields
"account_muxed"
,"account_muxed_id"
,"fee_account_muxed"
and"fee_account_muxed_id"
.source_account_muxed
andsource_account_muxed_id
. Additional fields depending on the operation type:"create_account"
operation:"funder_muxed"
,"funder_muxed_id"
."payment"
,"path_payment_strict_receive"
and"path_payment_strict_send"
operations:from_muxed
,from_muxed_id
,to_muxed
andto_muxed_id
."change_trust"
operation:"trustor_muxed"
and"trustor_muxed_id"
."allow_trust"
operation:"trustee_muxed"
and"trustee_muxed_id"
."account_merge"
operation:"account_muxed"
,"account_muxed_id"
,"into_muxed"
, and"into_muxed_id"
."claim_claimable_balance"
operation:"claimant_muxed"
and"claimant_muxed_id"
."end_sponsoring_future_reserves"
operation:"begin_sponsor_muxed"
,"begin_sponsor_muxed_id"
."clawback"
operation:"from_muxed"
,"from_muxed_id"
."account_muxed"
,"account_muxed_id"
. Additional fields depending on the effect type:"trade"
effect:"seller_muxed"
and"seller_muxed_id"
.Reference implementation
You can use the Go SDK implementation as a reference:
The text was updated successfully, but these errors were encountered: