Timeline for How should I store user's password in a smart contract?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 24, 2017 at 7:21 | comment | added | Cyberience |
I would suggest storing an approval Mapping with a True/false value and then once someone joins default false, you separately approve them to true, and use this table for authentication. example, require(approved[msg.sender,true); You may need methods for approve, list, suspend of that list. and maybe make it a struc to add things like name or other informtion to identify the member,
|
|
| Jul 20, 2017 at 12:08 | vote | accept | porfavorite | ||
| Jul 5, 2017 at 14:37 | comment | added | Rob Hitchens | Well...anyone can see because anyone can be a verifier. Main takeaway: no secrets on the chain, or encrypt. | |
| Jul 5, 2017 at 10:46 | comment | added | porfavorite | If I got it right, all data from contract is actually not really opened, but only verifiers can really 'see' all data, am I right? So not any passerby can really get contract data just by knowing contract address, right? | |
| Jul 4, 2017 at 23:01 | comment | added | Rob Hitchens | Possibly a little too much information, but ... ethereum.stackexchange.com/questions/765/…. Also, since miners verify all transactions that would change the contract state, it's safe to say that those transactions are witnessed by all verifiers. Transaction payloads are visible to everyone. Jacob's idea using hashes is viable and suitable for some use-cases. In most cases, it's better to use Ethereum's natural way to do authentication. Hope it helps. | |
| Jul 4, 2017 at 21:51 | comment | added | porfavorite | Can you plase thell me the way I can check contract's values? I just read that everybody can watch it, but don't know how. Thank you. | |
| Jul 4, 2017 at 19:17 | comment | added | Rob Hitchens | It takes some time to adjust to the way Ethereum is meant to be used. it will change the way you approach certain problems. | |
| Jul 4, 2017 at 19:10 | comment | added | Ajoy Bhatia | If you are giving a password to "someone" (i.e. a specific person), you could just as well ask that person to give you his/her Ethereum address. On the other hand, if you want to post the password somewhere from where people could look it up without having to contact you, then they are not really being "authorized" by you. | |
| Jul 4, 2017 at 19:00 | comment | added | porfavorite | But what if I don't know who will join my contract? I just want to give someone password so he could easily enter just using it. Because I don't know in advance his Ethereum address to authenticate him. | |
| Jul 4, 2017 at 17:07 | history | answered | Rob Hitchens | CC BY-SA 3.0 |