Skip to content

v16.0.0-rc.2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@Ryang-21 Ryang-21 released this 11 Jun 18:08
v16.0.0-rc.2
21c722e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v16.0.0-rc.2

migration guide:

Changed

  • Soroban auth defaults back to the legacy SOROBAN_CREDENTIALS_ADDRESS (V1) credential, with the CAP-71 SOROBAN_CREDENTIALS_ADDRESS_V2 credential now available behind an opt-in instead of forced on. ADDRESS_V2 is only valid on networks that have upgraded to protocol 27, so emitting it before upgrading would fail submission; the opt-in keeps the default safe while letting you exercise V2 against networks that already support it. The default will flip to V2 in protocol 28. (#1450)
    • rpc.Server.simulateTransaction gained a 4th optional argument, authV2 (default false). When true, the authV2 request flag is sent so simulation returns ADDRESS_V2 auth entries; otherwise the flag is omitted and legacy ADDRESS entries are returned.
    • authorizeInvocation gained an optional authV2 field on its params object (default false) selecting between ADDRESS and ADDRESS_V2 credentials.
    • contract.Client / AssembledTransaction accept authV2 in MethodOptions, threaded through to simulation.

Fixed

  • Resolved a performance regression in Keypair.random() #1449.

Note: the rpc.Server.simulateTransaction authV2 argument and theMethodOptions.authV2 option were removed before the v16.0.0 final release — authV2 on authorizeInvocation is the supported opt-in. See v16.0.0 above.

Assets 2
Loading