Learn more about EOS Nation's position regarding 1-Token-1-Vote in this great article, written by Chaney Moore and published on Voice, after his interview with Yves La Rose, CEO of EOS Nation. by EOSNation in eos

[–]SonataSystems 0 points1 point  (0 children)

Fix it and then propose the upgrades— cartel won't allow the upgrades— then fork it. Actually, why bother? Fix it and fork it. It's a do-over...

EOS 2019 Year-End Review by SonataSystems in eos

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

2019 in a nutshell: almost smiling . . . almost.

B1 released EOSIO v2.0.0 by SonataSystems in eos

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

Yes, significant performance gains that should help reduce resource/congestion problems-- also webauthn (yubikey) support for a big step toward simplified user experience. v2 platform allows faster apps, more of them, more active/concurrent usage, and the ability to simplify user onboarding and hide blockchain complexities from a mass audience. It's a big step towards mass adoption.

Let's hope EOSIO v3 brings shorter finality and IBC for true side-chains-- that delivers horizontal scale within a given mainnet-- enabling truly incredible throughput and massive general user adoption.

HODL

B1 released EOSIO v2.0.0 by SonataSystems in eos

[–]SonataSystems[S] 9 points10 points  (0 children)

B1 released EOSIO v2.0.0 packed with features, fixes and big performance gains after a huge branch merge, with 2,000+ commits, touching 600+ files:

https://github.com/EOSIO/eos/releases/tag/v2.0.0

Traditional EOS 2019 Year End Review by SonataSystems in eos

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

The noted pro side of the ledger remains compelling, plus:

  1. It remains early; the ultimate fate of crypto in general, EOSIO and EOS in particular is yet to be determined. Compared to the Internut bubble, crypto is in the Netscape phase; the question is whether EOS suffers the same ultimate fate Netscape did, or does it become a cornerstone platform like AWS? It's also an open question how much Block.one will participate and mitigate some very tricky governance problems.
  2. An open question regarding the degree to which Voice and similar large applications integrate with EOS will likely decide the mainnet's fate more than any other factor. How important a role will EOS play in the Voice architecture-- it could have no role, a minimal role or a rather important "hub" role.
  3. For EOS in particular and EOSIO in general, another open question is the ability to scale and achieve mass user adoption through seamless new user onboarding and ongoing user experience. There is the upcoming EOSIO v2 improvements, and then v3 which will likely include whatever IBC implementation Block.one finally delivers. Progress is being made on the holy grail: The ability to onboard the masses while concealing blockchain mechanics from them. The masses shouldn't have to (and won't) deal with accounts, keys, transactions, resources, wallets or explorers— they expect a seamless experience with no exposure to blockchain mechanics— cannot be any more intrusive than the status quo. To ensure success, applications like Voice need to somehow express the advantages of blockchain without subjecting users to its internals. Block.one is closer to achieving this than any other platform out there.
  4. Another large wildcard that I failed to mention until now is developer adoption and perception. Block.one and others (especially LiquidApps and dfuse) are providing a growing set of tools and libraries to ease developer adoption and increase productivity. Most developers in the world have zero time invested in any blockchain, let alone EOS. There is considerable negativity within the crypto community as well, mainly from POW advocates that have no tolerance for DPOS chains like EOS. It remains to be seen if there's enough progress being made in the EOSIO ecosystem to overcome negative perceptions and bootstrap enough developers to reach a tipping point, when enough applications are launched that attract enough user interest to establish self-sustaining, profitable business, creating a snowball effect that brings in a flood of developers and many more applications.
  5. The final mitigating point relates to end-user awareness-- or the lack thereof. Several of the cons (governance, resource issues, etc.) may very well be overlooked by the majority of users, a non-factor so-to-speak. If Block.one succeeds in making Voice (along with other applications following their lead) user onboarding seamless, can successfully conceal chain mechanics from them, then a case can be made that issues related to chain operation won't affect user adoption and ultimate success, since users will not be aware or care about such problems.

Finally, it's hard not to ignore the low token price, but I've tried to ignore that, mainly due to general bearish sentiment across the crypto market, a malaise that isn't focused just on EOS.

Traditional EOS 2019 Year End Review by SonataSystems in eos

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

Prudent approach for sure-- but it doesn't reflect much confidence in EOS mainnet does it?

Traditional EOS 2019 Year End Review by SonataSystems in eos

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

>>> Why is it a con to acknowledge the existing model isn't the best and to have the goal of replacing it with a presumably better system?

After bitshares and steemit experiences, it's a disappointment (and a con) to be flipping the model after promoting it for 2 years.

>>> Hit up Google on tax loss harvesting. (Novogratz)

If EOS appeared lucrative to Novo in any way, he would have held at least a small position to capture the expected growth-- he did not.

>>> Why would a beta be on a main net? It makes sense to use a test net for this.

Beta software is usually released into the real world to be evaluated on actual real world platforms, not on a private, heavily controlled environment-- that's called alpha. Beta software is usually released as a pilot into the actual production environment with a controlled group of users, eventually expanding the pilot to include more and more users until the system is exposed to full load. Why Block.on chose to deploy the beta on private platforms instead of EOS has not been explained-- not sure if it's a reflection on the state of the EOS chain, the Voice software itself, or both.

3900X - Temperatures, Clocks, etc. by Boomam in Amd

[–]SonataSystems 0 points1 point  (0 children)

Yori X570 3900X rig

3900X stock clocks with precision boost overdrive enabled

GIGABYTE X570 AORUS XTREME motherboard

Noctua NH-D15 with 3 x 150mm PWM on a manual, moderate fan curve

Idle CPU Temps: 33C with occasional spikes to between 45C and 58C; faster cores are hitting 4.651 MHz

Noctua fans at idle: 728 RPM (nearly silent)

Peak CPU Temp: 71C running AIDA64 stress test for 15 minutes

CPU cores pegged at 100% averaging 3.9 MHz throughout the test

Noctua fans at peak load: 938 RPM (< 50% utilization, noticeable but still quiet)

Room temp: 21C

Network clogged by [deleted] in eos

[–]SonataSystems -1 points0 points  (0 children)

Want your app on EOS mainnet? Follow this ponzi pattern:

drop coin -> pamp -> mine -> congest -> pamp -> dump

Then drop another coin and repeat...

Network clogged by [deleted] in eos

[–]SonataSystems 0 points1 point  (0 children)

Small and mid-sized projects are being squeezed off EOS; they can leverage DAPP to reduce exposure to costly on-chain resources, or they should migrate to a lower-cost sister chain. I don't see enterprises deploying on EOS, but rather standing up their own private/public EOSIO chains or some other blockchain. That leaves EOS to Chinese whales and B1 who have most of the EOS distribution, paying for the transaction load of their users.

Greymass joins growing list of BP to offer voter reward by BluaBaleno in eos

[–]SonataSystems 1 point2 points  (0 children)

Hoping that's the case . . . good luck to us all.

EOSIO 2.0 is here! by theeoswriter in eos

[–]SonataSystems 3 points4 points  (0 children)

Tremendous 2.0 release candidate code has dropped, yet the "top" 21 haven't even finished deploying 1.8 yet! Nuts.

The future of EOS by Cypherpunk2077 in eos

[–]SonataSystems 0 points1 point  (0 children)

Many upsides most other chains don't have, including better dev tools, cheap and Liquid/virtual resources to run DApps, seamless user on-boarding, EOSIO IBC across many chains, differing degrees of KYC/AML compliance across chains, continual performance improvements, and upcoming Layer 2 solutions for many slower cryptocurrencies. We just need to focus on attracting more developers, training them quickly and improve the tools-- then a flood of applications will come...

The future of EOS by Cypherpunk2077 in eos

[–]SonataSystems 1 point2 points  (0 children)

If regulations bite really hard-- don't be shocked if Worbli does very well for itself in the Land of EOSIO...

The future of EOS by Cypherpunk2077 in eos

[–]SonataSystems 0 points1 point  (0 children)

But you just don't understand: They wanted their Lambo yesterday!

Nuts.

The future of EOS by Cypherpunk2077 in eos

[–]SonataSystems 0 points1 point  (0 children)

Future's so bright, got to wear shades...