scientaster

3 ms·

1. 1.▲
   by scientaster 9y ago

   Unfortunately, since everything is off chain in third parties' hands, bitcoin is slowly becoming what it meant to replace.
2. 2.▲
   by scientaster 9y ago

   Good analysis of the code, and nice correction. Agreed that you should always check your sends' return values, too! In this example you have to send more than the last guy, so I think a recursive call would still put in more ether tha
3. 3.▲
   by scientaster 9y ago

   It's not equivalent to what OP made, the logic is slightly different. It took 5 minutes and it was just to demonstrate how easy it would be to make something similar. If you wanted to mirror OP you could build out the pixel struct to h
4. 4.▲
   by scientaster 9y ago

   Would have been much easier with an ethereum smart contract. No gimmicky address list, it's a crowdsourced picture in the blockchain. contract Place { struct Pixel { bytes3 color; uint lastPayment; } Pixel[
5. 5.▲
   by scientaster 10y ago

   While I haven't read the contract, that is a definite possibility. Most applications that require an 'Oracle' (a trusted source of information i.e the bot) can be written in a way that a deadlock would occur if their service
6. 6.▲
   by scientaster 10y ago

   Basically a github maintainer can add their project to commiteth so that whenever someone posts an issue with a label "bounty" a bot posts an address. That address is an ethereum smart contract. People all around can send ETH to t