You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users should have the option to ask for auto reveal their bets.
Should be set by default. Disable should be a non-emphasized option on UI for security conscious users who don't want to trust a 3rd party
How
Encrypt bet + random salt on client side with Oraclize public key (using their API)
Schedule a reveal callback with Oraclize in LupiManager to the bettingPeriodEnds time
On __callback call Lupi.revealBetForAddress
Notes
Only will work with Oraclize when there is no ticketCountLimit set
how to handle costs? ie. callback cost is paid from contract balance
The text was updated successfully, but these errors were encountered:
szerintedmi @szerintedmi 12:39
we store the bid encrypted with user’s secret key. at reveal user sends unencrypted bid and their secret key. we verify it against the stored one.
Marco Giglio @marcogiglio 12:39
ok I understood, I was thinking of something else. That's a bit inefficient.. you could store all the encrypted bids in a string, using strconcat and then make only one oraclize_query and receive only one callback with everything decrypted
you can used the nested datasource for that
and have many decrypt ds query nested inside
Marco Giglio @marcogiglio 12:46
and offcourse, that oraclize_query would be at the end of the bidding process
the only drawback would be that the last bidders will pay a bit more gas because of the cost of executing the function oraclize_query
Users should have the option to ask for auto reveal their bets.
Should be set by default. Disable should be a non-emphasized option on UI for security conscious users who don't want to trust a 3rd party
How
Notes
The text was updated successfully, but these errors were encountered: