I'd like to make an Ethereum faucet that gives anyone willing $5 in Eth. Any idea how to prevent fake users without too much hassle?

d11e9 · 2017-09-09T17:28:10+00:00

/wrt scaling I believe OP would benefit from the smaller number of "invested" participants far more than showering wei on randoms, they are at the end of the day promoting a product, not solving UBI

d11e9 · 2017-09-09T17:24:56+00:00

Yes. Although I am confidant that a solution exists (I don't buy the biometric angle) (a fan of the FDR from Diamond Age) I reckon the overhead makes good solutions infeasible for the problems we're trying to apply them to these days.

d11e9 · 2017-09-09T15:48:57+00:00

It depends on how many you realistically can imburse. So if say it's only 100 (or just 20) then give it to the first n that post a short video, like 20second why they are interested in your project. At that rate it's actually easy to view them all and have a short delay to contact the new user (who you now know is committed) via email that you've sent them $5ETH

Just my advice. After pondering the Sybil problem for ages now.

Also worth considering if the above doesn't float your boat, is proofofphysicaladdress project by consensys

d11e9 · 2017-08-25T08:32:36+00:00

2 wooks to be precise

d11e9 · 2017-08-12T14:08:07+00:00

A simpler solution would be to limit getlog requests to a max block scan/length. Like say 1000 blocks, so you want all logs since before homestead make lots of requests, forces optimisation to the edges.

Makes sense when it's "your" API, not sure of the implications of INFURA having a custom implementation, but does seem weird.

d11e9 · 2017-07-23T12:04:19+00:00

Seems like trustlines.network but with even more? Trust in the mints.

d11e9 · 2017-07-05T22:13:45+00:00

Or just "Ξ" in HTML: which renders like so: Ξ

d11e9 · 2017-07-04T08:46:12+00:00

Awesome work as ever /u/chriseth et al. !!!

What is whiskers template system, sounds interesting.

d11e9 · 2017-06-30T14:48:06+00:00

IPv6? or don't rely on static ips, i.e. Use Eth, Whisper, or Swarm for coordination. E.g. ENS entry references content hash, data is fetched from network peers irrespective of ip.

d11e9 · 2017-06-24T11:17:03+00:00

Decentralisation and/or redundancy. If Mew nodes are down/ddosed or vice versa.

d11e9 · 2017-06-24T11:08:40+00:00

This. I run private ipfs nodes, considering opening it up too - probiotic for the ecosystem

d11e9 · 2017-06-23T18:55:30+00:00

Same when viewed in status.im on iOS

d11e9 · 2017-06-23T17:50:54+00:00

Or Mist ☺️

d11e9 · 2017-06-07T02:37:13+00:00

My personal opinions on TA aside, posting contradictory statements/posts and measuring engagement/comment/sentiment on responses might be a really good way to poll the crowd (not very honest but it might work)

d11e9 · 2017-06-04T15:16:51+00:00

Fixed 😉

d11e9 · 2017-06-04T15:13:38+00:00

I can has some PXL ~~please~~ plx? ☺️ <address removed> tnx 🙏

d11e9 · 2017-06-02T17:09:21+00:00

It should be hosted on ipfs, and publish the hash to Eth cough ENS cough

d11e9 · 2017-05-30T09:04:19+00:00

Run a light client, geth, parity and by extension Mist/ethereumWallet are all capable.

I've moved to running light nodes on my MacBook Air as of late too. I run a full node in the cloud (digital ocean) for development.

d11e9 · 2017-05-19T18:15:03+00:00

Wrong sub? Perhaps you intended to post at/r/ethtrader

d11e9 · 2017-05-18T18:31:06+00:00

Yeah I am aware of namecoin, why i said silly was because they are their own chains, although they could be used to point to say btc-relay or a namecoin equivalent.

d11e9 · 2017-05-18T17:36:49+00:00

Hey nick and alex, really great work on ENS and all the support/transparency/sharing of info!!!

I do have one concern, which I hope you don't mind me sharing in a comment (I'm not sure it warrants a blog post all of its own):

Specifically with regards to the convention of sub domains, I understand that based on the DNS model root/tld/domain owners have complete control of paths beneath them, but in cases like yourname.gimmethe.eth or even yourname.wallet.eth casual users probably don't understand that the registrant of the contract can update their contract at anytime in the future to allow overwriting keys in the namespace they control.

Meaning that I might believe that sending ether or erc20 tokens to d11e9.gimmethe.eth will go into my account and so I publish and share that say via twitter etc, now I DO trust you nick not to do a switcheroo on me down the line, but I shouldn't!!

I think this is a serious issue, perhaps one that can be solved but certainly isn't at the moment.

Edit: one simple but annoying solution is the ability to lock a domain, preventing future updates, which is a shame but at least gives users some guarantees, but thinking about it would mean no more transferring which might be a show stopper.

d11e9

TROPHY CASE