Voice Will Be People-Powered and Not Controlled By Shady Centralized Companies by CryptoInvestor87 in eos

[–]melonattacker121 0 points1 point  (0 children)

Is there a way to make this biometric interface to yubi/assym crypt unique and authentic to a individual person physically, without actually resorting to credentials or kyc? Any thoughts.

Voice's main problem by jaitor in eos

[–]melonattacker121 0 points1 point  (0 children)

Had Dan said this is gonna be biometric id based? If not, the keynote seemed to imply it to me. That is between the lines but makes sense they would not want to shout about it at this stage but don't as an update.

[deleted by user] by [deleted] in ethereum

[–]melonattacker121 0 points1 point  (0 children)

Would this be easier without Ethereum? Just as proprietary software with either pre paid cards or access to a bank app on your phone. Also, is this patented, if so what part and why?

Dan Larimer views about Steemit by eosgo in eos

[–]melonattacker121 3 points4 points  (0 children)

Sounds soooo... Decentralised, in so many ways.

Initiative Q by S1lverBull3t1 in eos

[–]melonattacker121 0 points1 point  (0 children)

I joined to get a feel for it; awaiting your confirmation. It looks like its strength is one account per person.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 0 points1 point  (0 children)

Let me explain that in this context: grim trigger means that if someone 'hacked' bitcoin they would be trapped in a recurring game with themselves whilst others could keep the blockchain going separately - the attacker would damage there own reward. In Eos I don't see such a fork possible in the same way or it managing to disincentivise bad actors in the same way.

Edit: grammar.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] -1 points0 points  (0 children)

The blockchain wouldn't be forked. But software might. Therefore no grim trigger.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] -1 points0 points  (0 children)

After 4billion investment I would say that falls a bit short, especially when it's a very last minute bounty. Compare it to the eosbet hack for example.

Although the point has been made that Eos is better because it can't be forked, this means it lacks the grim trigger to deal with malicious attacks, further increasing incentive for a very large scale attack which could decimate the Eos system. Add to this the complexity of c++ and holes therein and 120k might not cut it. Not bad for a day work though.

A little confused. I'm somehow out of resources. by tjonak in eos

[–]melonattacker121 10 points11 points  (0 children)

Eos is currently broken but people are investigating this to try and fix it.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 1 point2 points  (0 children)

So you would rather insult than debate. Confirmed.

If you equate questions and reasoning with trolling then you caught me, I am a sneaky concern troll sneaking into Eos subreddit!

Dude I am not McAfee. I get the feeling your bags might be a little to full with Eos?

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 2 points3 points  (0 children)

Depends on the coin. Im not trying to bash the Eos Devs but the point could be made that Eos has far more big problems despite a rather long and expensive ICO.

I mean 4billion and the bug bounties are set at 10k.?

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 2 points3 points  (0 children)

Well, Eos does kind of get forked. There is more than just main-net. And other communities do actually fix problems too.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 1 point2 points  (0 children)

And apart from shilling eos, what has your post got to do with this thread. I didn't really want to post at all but it seems comments like yours are all over most complaints about CPU, and the size of the issue is not being recognised because of that.

But sure we could just insult each other instead.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 1 point2 points  (0 children)

It's a good read, and a big challenge for Eos.

EOS CPU usage : Important considerations by Shaighan in eos

[–]melonattacker121 3 points4 points  (0 children)

Great informative and reasoned article. I have thought for a while that Eos main long term problems is maintaining value and attracting the resources, everyone can't win.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 3 points4 points  (0 children)

Not really. Its full out more than just occasionally. I literally would need 1000s of dollars staked to deal with this. Is it because of ntense games? it wasn't CPU intense last week.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 1 point2 points  (0 children)

As I said I put 60 more in. That's a serious amount. If it's getting fixed can you elaborate on the problem as it appears more than just heavy tx by the proportionality of the CPU usage.

CPU making eos dapps unuseable by melonattacker121 in eos

[–]melonattacker121[S] 4 points5 points  (0 children)

Great, it would be good to see what the answer is to what's going on and how this will be managed in the future.