11–20 of 29 posts
I tend to be pretty skeptical of all things crypto, but this seems pretty cool. It's not very useful, but it seems like a fun concept.
And generate some modest revenue for a side project. It looks like he's made around $1500 so far.
I tend to be pretty skeptical of all things crypto, but this seems pretty cool. It's not very useful, but it seems like a fun concept.
And generate some modest revenue for a side project. It looks like he's made around $1500 so far.
A fun way to get people to donate money to wallets you control. Kind of like Million Dollar Homepage, but without any pesky guarantees.
Agreed. I think it could be a great way to raise money for some kind of cause though.
I'd like to see some proof that the charity-runner isn't going to abscond with the money once it was done, either due to maliciousness, or even something like getting stressed out over success (like some Kickstarters have done.)
(And yeah, I know - it's not like it's a Bitcoin/blockchain only problem - but at least with "real" money, there's typically a system in place where you can at least start trying to get the money back.)
Also, it would be nice that the image at the top is live, something like a gif autogenerated once a minute.
Also, how would you protect against faked transactions? Certainly waiting for confirmations is out of the question.
The niche aspect is something everyone is overlooking. Combining this with the "auctioning" each pixel seems like it would be pretty slow moving. Also, how would you protect against faked transactions? Certainly waiting for confirmations is out of the question.
This is not as dynamic as Reddit Place, the code is waiting for 1 confirmation before the pixel is colored.
The UI for something like that would be great - your client could just constantly generate random hashes and buffer a list of the best values its has come up with. Then the screen could highlight all pixels you can edit. As you wait longer (and generate better and better hashes), you can edit more 'valuable' pixels.
(Of course, that would only work if each hash could only be used once. You could embed the pixel value into the hash's input, but then you'd need to decide which pixels you want to edit before you start generating hashes. And that would be way less fun.)
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[10000][10000] board; modifier onBoard(uint x, uint y) { if (x > 10000 || y > 10000) { throw; } _; } // Accepts funds, if the funds sent are greater than funds for that pixel last, change the color. function colorPi…
IUUC the current code accumulate the payment to each pixel and whatever color has more accumulated money is chosen.
IIUC your code only consider the last payment and to replace the old color you have to outbid it, without any consideration of the previous payments.
Another strategies:
Penny auction: Whatever color received the last payment is the chosen one. This is more similar to /r/place
Generals.io: If someone adds money to the current color, then increase the accumulated money in that color. If someone adds money to another color the amount is discounted. Unless the result is negative and the color changes.
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[10000][10000] board; modifier onBoard(uint x, uint y) { if (x > 10000 || y > 10000) { throw; } _; } // Accepts funds, if the funds sent are greater than funds for that pixel last, change the color. function colorPi…
Is this code equivalent to the current code? IUUC the current code accumulate the payment to each pixel and whatever color has more accumulated money is chosen. IIUC your code only consider the last payment and to replace the old color you have to outbid it, without any consideration of the previous payments. Another strategies: Penny auction: Whatever color received the last payment is the chosen one. This is more s…
The penny auction one is even easier:
bytes3[10000][10000] board;
function colorPixel(uint x, uint y, bytes3 color) onBoard(x, y) {
board[x][y] = color;
}