{"action":"created","issue":{"url":"https://api.github.com/repos/OmniLayer/omnicore/issues/61","labels_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/61/comments","events_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/61/events","html_url":"https://github.com/OmniLayer/omnicore/issues/61","id":81495457,"number":61,"title":"Commands for creating transactions from non-wallet addresses","user":{"login":"dexX7","id":5836089,"avatar_url":"https://avatars.githubusercontent.com/u/5836089?v=3","gravatar_id":"","url":"https://api.github.com/users/dexX7","html_url":"https://github.com/dexX7","followers_url":"https://api.github.com/users/dexX7/followers","following_url":"https://api.github.com/users/dexX7/following{/other_user}","gists_url":"https://api.github.com/users/dexX7/gists{/gist_id}","starred_url":"https://api.github.com/users/dexX7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dexX7/subscriptions","organizations_url":"https://api.github.com/users/dexX7/orgs","repos_url":"https://api.github.com/users/dexX7/repos","events_url":"https://api.github.com/users/dexX7/events{/privacy}","received_events_url":"https://api.github.com/users/dexX7/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/OmniLayer/omnicore/labels/feature%20discussion","name":"feature discussion","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-27T15:27:09Z","updated_at":"2015-05-30T01:51:23Z","closed_at":null,"body":"> @achamely: once native commands for creating tx's from unknown address is available we'll use it. But at the moment OmniCore needs to have the address added/scanned before it will create tx's. Unfortunately for Omniwallet, this isn't possible. 1: too many addresses, 2: we don't have users private keys to add.\r\n\r\nPlease help me to understand this a bit more. While I can imagine what you may need, it's probably better to clearly define some requirements.\r\n\r\nRight now, we are able to construct and sign any transaction for wallet addresses. Those transactions can be broadcasted, or just signed, but currently, this is limited to wallet keys.\r\n\r\nAs intermediate step, would it help to have an interface to create raw, unsigned transactions, where the caller provides a set of unspent outputs? Would that be possible for OmniWallet?"},"comment":{"url":"https://api.github.com/repos/OmniLayer/omnicore/issues/comments/106972926","html_url":"https://github.com/OmniLayer/omnicore/issues/61#issuecomment-106972926","issue_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/61","id":106972926,"user":{"login":"zathras-crypto","id":5633351,"avatar_url":"https://avatars.githubusercontent.com/u/5633351?v=3","gravatar_id":"","url":"https://api.github.com/users/zathras-crypto","html_url":"https://github.com/zathras-crypto","followers_url":"https://api.github.com/users/zathras-crypto/followers","following_url":"https://api.github.com/users/zathras-crypto/following{/other_user}","gists_url":"https://api.github.com/users/zathras-crypto/gists{/gist_id}","starred_url":"https://api.github.com/users/zathras-crypto/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zathras-crypto/subscriptions","organizations_url":"https://api.github.com/users/zathras-crypto/orgs","repos_url":"https://api.github.com/users/zathras-crypto/repos","events_url":"https://api.github.com/users/zathras-crypto/events{/privacy}","received_events_url":"https://api.github.com/users/zathras-crypto/received_events","type":"User","site_admin":false},"created_at":"2015-05-30T01:51:23Z","updated_at":"2015-05-30T01:51:23Z","body":"Just to add my 2 cents in here:\r\n\r\n* I'm anti including addrindex stuff in OmniCore because I think it bloats the codebase and introduces potential risks and bugs for every potential user to satisfy only a single use-case (web wallets).  Additionally since Sipa (the original author of addrindex) himself didn't want addrindex to be merged into the main code this gives me reservations on scalability etc.\r\n* I do want to help the OmniWallet guys be as successful as possible and that includes giving them the ability to create any transaction via OmniCore for any address, but this needs to be balanced with potential negative impacts to OmniCore \r\n* I don't buy the argument that addrindex is needed for P2SH, I believe use of watch-only functionality can be used to add a P2SH address and obtain UTXOs for constructing sends\r\n* @CraigSellars suggested the possibility of adding addrindex functionality, but disabling it by default - this seems like it could be a potential compromise.\r\n\r\nThanks\r\nZ"}}