Skip to main content
Post Closed as "Duplicate" by niksmac, q9f
Post Reopened by Matthew Schmidt, Tjaden Hess, Badr Bellaj, eth
added 15 characters in body
Source Link
Tjaden Hess
  • 37.3k
  • 11
  • 91
  • 118

I know about the general open / trustless protocol of storing transactiontransactions. How would I approach a scenario here where I want to store some data in a contract on deployment, to later be retrieved by someone else.

E.g. I have a contract which stores secret number and other users cann interact with the Dapp and id on these numbers, only the highest bidder shall receive the true secret number inunknown at the end.time of deployment?

Clarification: TheThe main problem here is that the receiver of the secret data is not known in advance / when providing the secret data. Therefore simply encrypting the data with buyers public key is not a valid approach

E.g. I have a contract which stores secret number and other users can interact with the Dapp and bid on these numbers, only the highest bidder shall receive the true secret number in the end.

I know about the general open / trustless protocol of storing transaction. How would I approach a scenario here where I want to store some data in a contract on deployment, to later be retrieved by someone else.

E.g. I have a contract which stores secret number and other users cann interact with the Dapp and id on these numbers, only the highest bidder shall receive the true secret number in the end.

Clarification: The main problem here is that the receiver of the secret data is not known in advance / when providing the secret data. Therefore simply encrypting the data with buyers public key is not a valid approach

I know about the general open / trustless protocol of storing transactions. How would I approach a scenario here where I want to store some data in a contract on deployment, to later be retrieved by someone unknown at the time of deployment?

The main problem here is that the receiver of the secret data is not known in advance / when providing the secret data. Therefore simply encrypting the data with buyers public key is not a valid approach

E.g. I have a contract which stores secret number and other users can interact with the Dapp and bid on these numbers, only the highest bidder shall receive the true secret number in the end.

added 223 characters in body
Source Link
floAr
  • 181
  • 1
  • 4

I know about the general open / trustless protocol of storing transaction. How would I approach a scenario here where I want to store some data in a contract on deployment, to later be retrieved by someone else.

E.g. I have a contract which stores secret number and other users cann interact with the Dapp and id on these numbers, only the highest bidder shall receive the true secret number in the end.

Clarification: The main problem here is that the receiver of the secret data is not known in advance / when providing the secret data. Therefore simply encrypting the data with buyers public key is not a valid approach

I know about the general open / trustless protocol of storing transaction. How would I approach a scenario here where I want to store some data in a contract on deployment, to later be retrieved by someone else.

E.g. I have a contract which stores secret number and other users cann interact with the Dapp and id on these numbers, only the highest bidder shall receive the true secret number in the end.

I know about the general open / trustless protocol of storing transaction. How would I approach a scenario here where I want to store some data in a contract on deployment, to later be retrieved by someone else.

E.g. I have a contract which stores secret number and other users cann interact with the Dapp and id on these numbers, only the highest bidder shall receive the true secret number in the end.

Clarification: The main problem here is that the receiver of the secret data is not known in advance / when providing the secret data. Therefore simply encrypting the data with buyers public key is not a valid approach

edited tags
Link
eth
  • 86.5k
  • 53
  • 287
  • 411
Post Closed as "Duplicate" by eth
Source Link
floAr
  • 181
  • 1
  • 4
Loading