dash/doc/release-notes-5164.md

Updated RPCs
--------

- `bls generate` and `bls fromsecret`: The new `scheme` field will be returned indicating which scheme was used to serialise the public key. Valid returned values are `legacy` and`basic`.
- `bls generate` and `bls fromsecret`: Both RPCs accept an incoming optional boolean argument `legacy` that enforces the use of legacy BLS scheme for the serialisation of the reply even if v19 is active.
feat(rpc): added scheme in bls generate rpc + aligned changes for bls fromsecret rpc (#5164) ## Issue being fixed or feature implemented ## What was done? <!--- Describe your changes in detail --> - `bls generate` and `bls fromsecret` rpcs will return `scheme` used to serialise the public key. Valid returned values are `legacy` and`basic`. - `bls generate` and `bls fromsecret`rpcs accept an incoming optional boolean argument `legacy` that enforces the use of legacy BLS scheme for the serialisation of the reply even if v19 is active. ## How Has This Been Tested? ## Breaking Changes ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [x] I have made corresponding changes to the documentation For repository code-owners and collaborators only - [x] I have assigned this pull request to a milestone 2023-01-20 06:30:17 +01:00			`Updated RPCs`
			`--------`

			- `bls generate` and `bls fromsecret`: The new `scheme` field will be returned indicating which scheme was used to serialise the public key. Valid returned values are `legacy` and`basic`.
			- `bls generate` and `bls fromsecret`: Both RPCs accept an incoming optional boolean argument `legacy` that enforces the use of legacy BLS scheme for the serialisation of the reply even if v19 is active.