Skip to content

release-notes-7099.md

Latest commit

 

History

History
25 lines (21 loc) · 1.47 KB

release-notes-7099.md

File metadata and controls

25 lines (21 loc) · 1.47 KB
Raw

Updated RPCs

  • Dash RPCs will no longer permit submitting strings to boolean input fields in line with validation enforced on upstream RPCs, where this is already the case. Requests must now use unquoted true or false.

    • The following RPCs are affected, bls generate, bls fromsecret, coinjoinsalt generate, coinjoinsalt set, masternode connect, protx diff, protx list, protx register, protx register_legacy, protx register_evo, protx register_fund, protx register_fund_legacy, protx register_fund_evo, protx revoke, protx update_registrar, protx update_registrar_legacy, protx update_service, protx update_service_evo, quorum info, quorum platformsign, quorum rotationinfo, quorum sign.

    • This restriction can be relaxed by setting -deprecatedrpc=permissive_bool at runtime but is liable to be removed in future versions of Dash Core.

  • Numeric arguments of the Dash-specific RPCs (quorum, protx, gobject, masternode and their sub-commands) must now be passed as JSON numbers. Strings containing a number, which earlier versions accepted, are rejected with a type error (code -3). The only exception is the baseBlock and block arguments of protx diff and protx listdiff, which take a block hash or a height and therefore still accept a height as a string. There is no runtime option to restore the old behaviour; -deprecatedrpc=permissive_bool only applies to booleans.