homakov

Only if you did KYC on every single customer.

250k fine, 15m raised... https://decryptmedia.com/2018/11/29/exclusive-airfox-ceo-say...

>They could have simply kept their assets in stable coins, like Dai, Tether, etc..

To turn into dust?

>They could also sell into USD on exchanges that allow you to trade USD (e.g. Kraken).

And trust Kraken then.

>Another option would have been to open a hedging short position on say, Bitmex.

and trust bitmex then.

There are no scalable options to cash out $10m to a bank and sleep well. You could cash out into some "stable coin" only to wake up to it costing $0.04 (hello nubits). Tether is no safer in that matter.

Well, didn’t happen to me. “I might not deserve it, but thanks”

>Should I donate it?

do you seriously consider this? Sounds crazy to me. Or pretentious.

Why bother with working another job? Do your own thing, fix something in the world.

I have proposed a solution to this: have the snippet self-hashed and verify with multiple sources. eg:

A=$(curl -L https://get.rvm.io);echo "$A" | shasum -a 256 | grep -q 05b6b5f164d4df5aa593f9f925806fc1f48c4517daeeb5da66ee49e8562069e1 && (echo "$A")

Same can be achieved without hardware part.

>I do remember when OpenId+HW 2FA was supposed to have fixed this

HW 2fa can never fix auth because it's hardware, and cannot scale. There are solutions out there, all what's left is to raise awareness to add it. Showing popular passwords will just move us to a new set of popular passwords and so on.

I don't recall any popular website using Basic Auth. FF must implement WebAuthN or whatever was last offered to fix auth. Have i been pwned brings nothing new to the table.

I'd argue there is no "good" auth at the moment, only "poor". And upgrade to authenticator-based "good enough" is much needed.

Instead of actually fixing authentication they are baking "have this password been exposed in plaintext" into the browsers.

What's the deal with WebAuthN? Such a basic functionality still not completed.

If you're desperate, just serve local sdk from http://localhost/sdk.html which will talk to your local app via postMessage proxy. You may even open this proxy with window.open under https:// app

I've done exactly that https://github.com/fairlayer/fair

Single auth_code shared between web session and local app is all you need.

Requires special modules, you can't just take random npm module e.g. sequelize. Deal breaker for me.

Ripple? Mobile payments? How can a bloated ledger with thousands of tps be good for running on mobile. It's more like interbank thing.

Thanks, the blockchain part is recent and isn't relevant. Otherwise it's super simple idea: strong derivation based on something anyone can remember (username + pw) + website origin = strong non-reusable credentials w/o hardware.

It's definitely would be more successful being part of the browser, but Web Auth API is too slow to move so I went out to make a PoC instead. In the end: I hate electron apps now :) Also I now know what kind of effort is needed to change the auth space... I don't believe it will happen short term :/ It's too hard and too little incentive to change things.

The only perk of being outside the browser is being able to auth regular desktop apps like Spotify or Btc wallets. But yes, 99% are web apps so seamless in-browser login would make more sense.

You just described https://github.com/sakurity/securelogin

Minus the worst bug of all time - password reuse and bruteforce. Sounds like fair tradeoff.

It's significantly more secure and more convenient. Magic links rock. See rollcat comment +1

Interestingly Ethereum has hit in a sweet spot: tech crowd that learns EVM quickly and enjoys playing with it (like a new raspbery pi) & has sizable spare cash to invest in ether/erc20. Bitcoin is nowhere as fun to learn, the VM is quite boring. I wonder if any other blockchain can hit into this sweet spot.

1. front running has nothing to do with TOCTOU/race conditions. the real race condition example would be reentry attack actually.

2. #9 has nothing to do with "off-chain issues". Off chain has very clear context and refers to layer 2 solutions for scaling. No need to call a website bug "off chain issue".

There are other incentives beyond most obvious ones. E.g. hijacked miner could attack to pump another currency (crypto/fiat) the miner holds.

Incentives are out of equation when you speak of fault tolerance. Incentives are not calculatable. Only "tolerance" (# of tolerable byzantine nodes) matters. And that's 2 for eth and btc. TWO.

Incentives dont matter, any centralized entity has no incentive to do bad things about their system yet here we are.

True dapps dont exist yet. Now they all rely on some authority or served as a website

A website. Just a website.

10 years after now, it is gonna change nothing. Cumbersome slowly developed standard.

Something is blockchain powered when you use it as full node. Light node the very least. Dtube and steem are just websites you load in your browser. None of blockchain properties are inherited in this case.

Who decided that "BUMP_SEQUENCE operation" should be implemented? Was there onchain governance or it was a authoritarian decision?

A year ago I had $100 balance and my $50 payment to some cafe turned it into $150. They added money instead of deducting it. That was fixed soon but that's how I still feel about N26.

I remember checking this issue. Parity has origin whitelisting to prevent exact. No idea why geth is so stupid.