{"action":"opened","issue":{"url":"https://api.github.com/repos/hashgraph/hedera-sdk-java/issues/88","repository_url":"https://api.github.com/repos/hashgraph/hedera-sdk-java","labels_url":"https://api.github.com/repos/hashgraph/hedera-sdk-java/issues/88/labels{/name}","comments_url":"https://api.github.com/repos/hashgraph/hedera-sdk-java/issues/88/comments","events_url":"https://api.github.com/repos/hashgraph/hedera-sdk-java/issues/88/events","html_url":"https://github.com/hashgraph/hedera-sdk-java/issues/88","id":436292927,"node_id":"MDU6SXNzdWU0MzYyOTI5Mjc=","number":88,"title":"Public key reduction on signatures (optional)","user":{"login":"gregscullard","id":9549788,"node_id":"MDQ6VXNlcjk1NDk3ODg=","avatar_url":"https://avatars3.githubusercontent.com/u/9549788?v=4","gravatar_id":"","url":"https://api.github.com/users/gregscullard","html_url":"https://github.com/gregscullard","followers_url":"https://api.github.com/users/gregscullard/followers","following_url":"https://api.github.com/users/gregscullard/following{/other_user}","gists_url":"https://api.github.com/users/gregscullard/gists{/gist_id}","starred_url":"https://api.github.com/users/gregscullard/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gregscullard/subscriptions","organizations_url":"https://api.github.com/users/gregscullard/orgs","repos_url":"https://api.github.com/users/gregscullard/repos","events_url":"https://api.github.com/users/gregscullard/events{/privacy}","received_events_url":"https://api.github.com/users/gregscullard/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-04-23T16:58:20Z","updated_at":"2019-04-23T16:58:20Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"A feature of the next version of HAPI is `signatureMaps` to replace the old method of providing signatures to a transaction.\r\nNot only is the `signatureMap` much easier to use being a flat list of public key + signature compared to the hierarchical lists of old, it is possible to reduce the public keys provided in the map to the bare minimum required to uniquely identify them, it's even possible to leave the public key blank/null if there is only one key on an account/file. This causes a potential problem in multi-signature scenarios.\r\n\r\n-User 1 creates and signs a transaction, sends it to user 2\r\n-User 2 signs the transaction and submits to the network\r\n\r\nIf the transaction created by user 1 has had its public key reduced, it will potentially be null. When user 2 signs the transaction, it's no longer possible to ensure the public key reduction will result in uniquely identifiable keys.\r\n\r\nWhen a transaction payload is created and signed, the full public keys should be included in the signatureMap.\r\nOnly when the transaction is sent to Hedera should the public keys be reduced."}}
{"actor":{"display_login":"gregscullard"}}