4 ms·
How hard do you think this would be to implement on top of the Venmo or stripe API?
by wolfram74 9y ago
How hard do you think this would be to implement on top of the Venmo or stripe API?
- DennisP 9y agoI don't know but I'm working on an Ethereum implementation right now, and it's pretty easy.
- tgb 9y agoI don't know anything about this, but how do you make randomness in Ethereum? I assume it has to replicable across any computer and therefore would be pseudo-random and predictable. Do you use something like the NIST randomness beacon at a specified future time?
- zaroth 9y agoGoogle "provably fair bitcoin lottery". They typically are based on a future block's hash value combined with a published random seed. Here's an example: https://github.com/hmel/bitcoin-raffle https://github.com/hmel/bitcoin-raffle
- themadryaner 9y agoIn theory, a miner could try to manipulate the hash of the future block to change the outcome. It is much more difficult with Bitcoin, where valid blocks are more rare and produce a high income, but with Ethereum blocks are so frequent that it might be possible to collude with the mining pools is done on a large scale. Additionally, how does this deal with Proof-of-Stake algorithms? Ethereum is heading there, and as far as I am aware the blocks would no longer publish hashes.
- rrobukef 9y agoA sybill attack would greatly increase the probability. And has cheatingly other gains.
- kobeya 9y agoNo need for a future block. Recipient commits to the hash of a value. Payer signs a value. Hash the preimage (revealed in claim) and the signed value together. If less than a threshold, pass.
- infogulch 9y agoAs long as neither party has any way to manipulate the hash. Should probably add a 0th step where the payer commits to use a specific signature.