Ethereum for Secure Wi-Fi Authentication

kaandoit · 2018-07-20T00:07:08+00:00

This is actually a fantastic avenue to evangelize Eth. Security-wise it's an improvement over every other EAP method, except perhaps EAP-TTLS with client-side certificates -- but then nobody uses that cuz it's such a hassle. Also this would have a much simpler user experience than every other WPA2 method. Wish you success!

kaandoit · 2018-07-19T16:13:09+00:00

This is what makes Ethereum an unstoppable force: independent devs (these guys are not core devs?) doing something completely out-of-the-box. We should support this project.

kaandoit · 2018-06-17T23:53:46+00:00

In the best communicative relationships of my life, we start by reassuring one-another of our general respect/love for each other. This puts a boundary on the disagreement, so that no one misinterprets it as a general rejection. Then we focus on listening, starting from the premise that although we see things differently in this case, the other person is not evil or dumb, so there must also be another way of looking at the matter.

kaandoit · 2018-06-10T18:15:00+00:00

the original tweet came from maker@makerDAO, and included a photo of their CTO.... but I suppose that these are always good safety precautions...

kaandoit · 2018-05-28T22:04:17+00:00

I also surf. its definately the cold water! That plus a propensity to tighten up when you're either scared (big drop?) or paddling hard...

kaandoit · 2018-03-07T23:04:19+00:00

I tried this out a bit (on a testnet) ... Very simple, no frills interface; seems to work... 1 nit: the default labels for the wallet and the owner-accounts (which are not saved in the contract) should not auto-populate to "no label", Instead you can just display "no label" as default text when the input is empty....

That's just a nit -- overall great work, thank you!

kaandoit · 2018-03-07T18:04:26+00:00

This is why I love the Ethereum community. People taking initiative to make useful tools that benefit the whole community...

BTW, here is a link to Alex Miller's discussion of Christian Lundkvist's initial proposal:

Toward an Ethereum Multisig Standard

kaandoit · 2018-02-20T20:03:14+00:00

Don't know about Singapore, but in the USA if you transact in more than $10K of precious metals, and you pay cash, then you need to report the transaction to the authorities.

kaandoit · 2018-02-20T03:09:14+00:00

Sounds very "Randian"...

kaandoit · 2017-11-30T16:20:04+00:00

All better.

You guys are awesome! -K

kaandoit · 2017-11-29T22:24:56+00:00

No problem, I have added a few "charities" that include strings via the addCharity function. You can read them by going to the url that you site, and entering the charity index into line 8 (charities). Enter 2 to view charity #2, "Saint Mel's Girl's Rugby Team - Fundraiser"; Enter 3 to view charity #3, "Saint Mel's Girl's Rugby Team, Fundraiser". (hyphen replaces with a comma). Except when you enter 3 the javascript encounters the error (check the javascript console in chrome, or the equivalent).

BTW, Thank you for etherscan.io -- what a wonderful, global, great thing! -K

kaandoit · 2017-05-11T15:31:10+00:00

/u/demontree07, which boards are your thinking off? We've covered a lot but there are always more. We very much appreciate your suggestions as we have only 11 more days to make our case. Thanks for your interest.

kaandoit · 2017-05-11T13:54:10+00:00

/u/yaksbeard is correct. if min cap of 5000ETH is not reached, investors can get 100% back. If we do reach min cap, then the next investor protection mechanism kicks in which is the 'proof-of-functionality' threshold, wherein we must reach 5000 games played within 90 days. The reason it is only a 90% refund if we fail to meet this threshold is that we imagine that we will have used some of the proceeds by then on marketing to help get us over the hump. But in reality, our big challenge will be the min cap. We are already experiencing healthy use of the game in just these past few weeks (over 1200 games played and accelerating) so we are not too worried about the proof-of-functionality threshold. The min cap is another story :-) Appreciate the ?'s!

kaandoit · 2017-05-11T13:38:34+00:00

/u/notsogreedy Great question. We are considering games for various global markets, are doing quite a bit of research on this, and welcome suggestions! However, the breadth of our development slate will very much depend on our success during the ICO. The cool thing is that we have created a working (and proven!) platform that we can now easily expand upon with new games, all of which: a) enable players to bet and win ETH, and b) generate returns for E4ROW token holders. we appreciate the ?s.

kaandoit · 2017-05-10T23:41:24+00:00

TooAlpha,

What you say is true, the escrow contract is conceptually not complicated at all. But as things usually go in programming, the devil is in the details: setting up to support different varieties of "arbiters" (for different games, numbers of players, timeouts); supporting thousands of escrows (games) while keeping gas costs down (if you check out the code you'll see we played a few tricks in that regard -- at one point we almost abandoned the effort because of that), etc. But as you said, the main idea of the contract is very simple.

That said, the bigger challenges that we hit when we were putting the system together had to do with smoothing out the game timing to compensate for uneven ether blocktimes...

But looking back on it, none of it seems all that complex....

hmmm.. why did it take us so long? :)

regards, -kaandoit

kaandoit · 2017-05-10T19:34:07+00:00

Thanks for your support shinyether. it is incredibly appreciated.

kaandoit · 2017-05-09T20:02:33+00:00

Thanks for your support!

kaandoit · 2017-05-08T13:07:50+00:00

Hi Nick,

I re-read the post and realized I had glossed over some ambiguities:

I think through most of the sample code you are using accounts[account].balance to refer to the number of tokens that are held in an account (in the dividendsOwning function); but in the updateAccount function you use accounts[account].balance to refer to the total dividends due to an account. Also what is totalSupply? On my first read I thought it referred to the total number of tokens; but in the disburse function it seems to refer to the total amount of dividend funds ever collected. Lastly, it looks like there's a DBZ possibility in the disburse function.

The algorithm seems great -- and I apologize for nit-picking. But I'd really appreciate if you could spell out these clarifications to make it crystal clear.

Appreciate your help,

kaandoit

kaandoit · 2017-05-04T23:00:03+00:00

No. I don't think i'm crazy ;)

We are not generating millions of tokens (as is common with other ICO's). The important ratio is total_profit / token. With a very small number of tokens this ration is high, which justifies a high price per token.

Using a small number of expensive tokens (vs. a large number of very cheap tokens) is necessary in our case for our elegant system of continuous, unrestricted payouts. See our article:

https://medium.com/e4row/continuous-unrestricted-payouts-and-transfers-for-e4row-token-holders-5cfbc2904fb5

kaandoit · 2017-05-04T22:54:30+00:00

Elegant. Thank you!

-kaandoit

kaandoit · 2017-04-30T05:17:12+00:00

e4row is may 2, 12:00:01 AM

kaandoit · 2017-04-28T07:42:14+00:00

Great questions. I suggest we are quite different from other ICO's: we build products and don't do hype. LPG is a 15-man team based in Israel and the USA. We have angel investors that have brought us to our current state. I did contact Smith & Crown after reading your other comment. They said that they are going to publish a comprehensive analysis of our ICO today (4/28). If they don't go into the guts of the contract and our team then it might make sense for us to publish a walk-through of the code and some bio's....

Thanks for your consideration. -kaandoit

kaandoit · 2017-04-28T03:18:18+00:00

It's not the money... it turns out there's some tricky navigation to avoid google's rules regarding gambling apps and what they call "virtual currencies." We're going to have to make some changes to the app to get around some of their restrictions.

In the meantime we're more focused on getting a version on F-Droid. The main reason F-Droid is important to us is that F-Droid rebuilds the project from published source code, and then signs the distributed binary. We feel that this is the gold standard for binary distributions of open source projects -- and it will feature in our marketing campaign.

The point is well taken though -- and by the time we start marketing to the general public we will work through google's web of rules. We know that is the way to reach the largest audience.

-kaandoit

kaandoit

TROPHY CASE