/**
* This API will take a partially signed transaction and a set of public keys that the owner has the ability to sign for
* and return the minimal subset of public keys that should add signatures to the transaction.
*/
set<public_key_type> get_required_signatures( const signed_transaction& trx, const flat_set<public_key_type>& available_keys )const;
If I understood correctly, when an unsigned transaction requires a signature of key A only, sign it with A, then call this API with the signed transaction as trx and A as available_keys, it should return an empty set. However, with latest version (2.0.160316b), the API returns a set contains A. Same behavior is found with earlier versions.
The in-code document of
get_required_signatures
API says:If I understood correctly, when an unsigned transaction requires a signature of key
A
only, sign it withA
, then call this API with the signed transaction astrx
andA
asavailable_keys
, it should return an empty set. However, with latest version (2.0.160316b
), the API returns a set containsA
. Same behavior is found with earlier versions.Log of a test on live BTS chain: