{"action":"created","issue":{"url":"https://api.github.com/repos/OmniLayer/omnicore/issues/391","repository_url":"https://api.github.com/repos/OmniLayer/omnicore","labels_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/391/labels{/name}","comments_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/391/comments","events_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/391/events","html_url":"https://github.com/OmniLayer/omnicore/issues/391","id":161331443,"number":391,"title":"BTC in crowdsales","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},"labels":[{"url":"https://api.github.com/repos/OmniLayer/omnicore/labels/consensus","name":"consensus","color":"e11d21"},{"url":"https://api.github.com/repos/OmniLayer/omnicore/labels/feature","name":"feature","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-06-21T01:32:37Z","updated_at":"2016-06-27T07:44:10Z","closed_at":null,"body":"Hey guys,\r\n\r\nAs requested I'm working on allowing BTC in crowdsales.\r\n\r\nI noticed in the spec we have the text:\r\n\r\n> Effective with version 1 of Transaction type 51 and block #(TBD), a single crowdsale is able to accept multiple currencies, including bitcoins (currency id 0), for purchases of a Smart Property in a single crowdsale. \r\n\r\nTwo Q's:\r\n\r\n1) The requirement at the top of roadmap is BTC in crowdsales, but the roadmap doesn't mention multiple properties in crowdsales.  Are we sticking to the roadmap, or do we want to try and do multi-currency crowdsales per spec?\r\n\r\nNote my vote is a resounding 'no' to multiple currency crowdsales, as it means we need to allow multiple crowdsales to run side by side for a single address, and I'm not really sure what the point is (though happy to be educated!).\r\n\r\n2) What exactly does constitute a v1 crowdsale?  We have plenty of valid v1 crowdsales already on-chain, and these certainly don't allow BTC or multiple currencies.\r\n\r\nThanks\r\nZ"},"comment":{"url":"https://api.github.com/repos/OmniLayer/omnicore/issues/comments/228675089","html_url":"https://github.com/OmniLayer/omnicore/issues/391#issuecomment-228675089","issue_url":"https://api.github.com/repos/OmniLayer/omnicore/issues/391","id":228675089,"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":"2016-06-27T07:44:09Z","updated_at":"2016-06-27T07:44:09Z","body":"Perhaps to simplify, instead of having multiple \"Pay Crowdsale\" or \"Pay Accept\" and so forth, we could have a single \"Bitcoin Payment\" payload.  Something like:\r\n\r\nTransaction Type: 80 (Bitcoin Payment)\r\nTransaction Ver: 0\r\nTargetTxType: uint16\r\nvOut: uint16\r\n\r\nThe vOut specifies exactly which output is considered the payment, and to whom (explicit).\r\n\r\nThe TargetTxType allows to specify what the payment is for - if the target tx type is 22 we know the payment is for an accept, if it's 51 we know the payment is for a crowdsale.  This allows BTC payments in other (eg future) tx types without expressly engineering for it each time.\r\n\r\nJust thinking out loud as I'm prototyping :)\r\n"}}
{"actor":{"display_login":"zathras-crypto"}}