Timeline for Access control of the external resource sold using a DApp?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 12, 2017 at 21:19 | comment | added | user19510 | And no, unfortunately, I don't have a ready example of doing this. | |
| Dec 12, 2017 at 21:18 | comment | added | user19510 | I'm unfamiliar with that example, but yes, I was assuming that when you said "token," you meant an ERC20 token. I was also assuming a second smart contract (the one to receive the tokens), but I suppose you could also just send the request ID as data in a transaction that sends the token directly to an EOA (externally-owned account). | |
| Dec 12, 2017 at 21:14 | comment | added | dc7a9163d9 | Is there any example for this? I'm using to build a token following the truffle example (TutorialToken), is it the ERC20 token? BTW, the business logic will be written in middleware which may not be Javascript. So I think I will create a web service call for "(2) request ID" (access via https). When doing (3), will other users sniffle the "requst ID"? | |
| Dec 12, 2017 at 15:03 | history | answered | user19510 | CC BY-SA 3.0 |