You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Payloads have a new meta property: signers. The field can be null or an array containing between one and an arbitrary amount (currently hard capped by our backend at four, client doesn't have to enforce) XRPL account addresses.
When one or more account addresses are entered, XUMM forces signing with one of those accounts.
Impact:
Payload GET types (meta.signers) (null or string[])
Paylost POST types (options.signers) (omit, null or string[])
TL;DR:
Payloads have a new
meta
property:signers
. The field can benull
or an array containing between one and an arbitrary amount (currently hard capped by our backend at four, client doesn't have to enforce) XRPL account addresses.When one or more account addresses are entered, XUMM forces signing with one of those accounts.
Impact:
meta.signers
) (null or string[])options.signers
) (omit, null or string[])Commit to XUMM-SDK:
XRPL-Labs/XUMM-SDK@8b5c484
Based on discussion:
XRPL-Labs/Xaman-Issue-Tracker#384 (comment)
The text was updated successfully, but these errors were encountered: