{"action":"created","issue":{"url":"https://api.github.com/repos/bitpay/copay/issues/2998","labels_url":"https://api.github.com/repos/bitpay/copay/issues/2998/labels{/name}","comments_url":"https://api.github.com/repos/bitpay/copay/issues/2998/comments","events_url":"https://api.github.com/repos/bitpay/copay/issues/2998/events","html_url":"https://github.com/bitpay/copay/pull/2998","id":95324732,"number":2998,"title":"export backup without signing capabilities","user":{"login":"matiu","id":98844,"avatar_url":"https://avatars.githubusercontent.com/u/98844?v=3","gravatar_id":"","url":"https://api.github.com/users/matiu","html_url":"https://github.com/matiu","followers_url":"https://api.github.com/users/matiu/followers","following_url":"https://api.github.com/users/matiu/following{/other_user}","gists_url":"https://api.github.com/users/matiu/gists{/gist_id}","starred_url":"https://api.github.com/users/matiu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/matiu/subscriptions","organizations_url":"https://api.github.com/users/matiu/orgs","repos_url":"https://api.github.com/users/matiu/repos","events_url":"https://api.github.com/users/matiu/events{/privacy}","received_events_url":"https://api.github.com/users/matiu/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-07-16T01:13:39Z","updated_at":"2015-08-05T21:03:01Z","closed_at":"2015-07-16T15:01:35Z","pull_request":{"url":"https://api.github.com/repos/bitpay/copay/pulls/2998","html_url":"https://github.com/bitpay/copay/pull/2998","diff_url":"https://github.com/bitpay/copay/pull/2998.diff","patch_url":"https://github.com/bitpay/copay/pull/2998.patch"},"body":"- this add 'no private key' advanced option to backup.\r\n\r\nIt is then possible to export a backup without the wallet's private key.\r\n\r\nA wallet with a imported backup without private key can: see wallet balance, see tx history, create spend proposal, reject spend proposals, BUT CANNOT SIGN (approve) proposals."},"comment":{"url":"https://api.github.com/repos/bitpay/copay/issues/comments/128147671","html_url":"https://github.com/bitpay/copay/pull/2998#issuecomment-128147671","issue_url":"https://api.github.com/repos/bitpay/copay/issues/2998","id":128147671,"user":{"login":"dan-da","id":5110592,"avatar_url":"https://avatars.githubusercontent.com/u/5110592?v=3","gravatar_id":"","url":"https://api.github.com/users/dan-da","html_url":"https://github.com/dan-da","followers_url":"https://api.github.com/users/dan-da/followers","following_url":"https://api.github.com/users/dan-da/following{/other_user}","gists_url":"https://api.github.com/users/dan-da/gists{/gist_id}","starred_url":"https://api.github.com/users/dan-da/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dan-da/subscriptions","organizations_url":"https://api.github.com/users/dan-da/orgs","repos_url":"https://api.github.com/users/dan-da/repos","events_url":"https://api.github.com/users/dan-da/events{/privacy}","received_events_url":"https://api.github.com/users/dan-da/received_events","type":"User","site_admin":false},"created_at":"2015-08-05T21:03:01Z","updated_at":"2015-08-05T21:03:01Z","body":"ok, I just tried this out with a 1 of 1 (personal) wallet.\r\n\r\nThe good:\r\n  + backup and import worked flawlessly.\r\n  + non signing wallet was able to create a spend proposal and signing wallet was able to approve or reject it.\r\n\r\nThe not so good:\r\n + backup/import is a non-intuitive way to add a non-signer ( aka preparer ) user.\r\n + Operations on either side do not cause a notification to appear in the other wallet.  eg after creating spend proposal, the other wallet must exit wallet then re-enter before it appears.   likewise vice-versa after accepting or rejecting.\r\n + When clicking on Payment Proposal, the created by field says \"me\".   This makes some technical sense, however it is not the desired workflow where there would be named user(s) in a preparer role and other named user(s) in a signer role.  anyway, it is odd to see it was \"me\" that created the tx when really it wasn't.\r\n\r\nThis is a great first step, but I think a bit more work is needed to make the non-signer role into a first class wallet participant.\r\n\r\nI can turn these into separate issues if that would be helpful.\r\n\r\n"}}