Https://Twitter.Com/Trim_bot/Status/1669733696130129920?S=46&T=JqogORbOoFQrRouzPj6Mgg

Is it relative to EOS token or there will be other coin to Taurus? Help to understand this news please 🙂

have they updated the code or forked it?

B1 can never issue new tokens for fear of the SEC

no code updates since 2021, they just open sourced it. All of the contributors are the current ENF engineers https://github.com/EOSIO/taurus-node/graphs/contributors

So the EOS token will not get any pluses from this news?

This has absolutely nothing to do with the EOS token

before I go and get caught up...you're too funny Trim...do you honestly believe B1 put EOSIO Taurus together because they were scared of...what, your and Yves' legal prowess. To think had the ENF actually tried to work with B1, this would likely be great news for EOS. We could've been at the forefront of this news and helping to onboard enterprise partners and tie them into EOS via IBC.

The way the intentionally mangled the commit history and has all changes merged/pushed in a single commit certainly raises suspicion. They went out of their way to obfuscate the history of the code, timeline, and contributors.

Going through it is annoying af too. There's a huge amount of linting

Yeah… I’m on mobile still and can’t make heads or tails of it from here. It’s going to be a nightmare on desktop, and it’s impossible on mobile.

ooooof

do you think the code is from before Sept 2021, or is some of it post that date? I would think that will have an impact on the class action that has been suggested.

There’s code individually committed up until early 2021, which I assume is the fork point for that codebase. Then anything that happened afterwards was all merged into one massive commit, obscuring any kind of timeline or author.

ok thanks. Definitely doesn't help the class action then by the sounds of it...shocker...lol

Really ? 😂😂😂

looking a lot like maybe we don't know what we don't know, and the $1B commitment was indeed reached (whether we like it or not). But ya scared of being sued...meanwhile EOS could've benefited from the release of EOSIO-Taurus and not approaching all time lows 🤦🏻‍♂️ https://twitter.com/BrendanBlumer/status/1669769890063077376

How could EOS be benefitted from EOSIO Taurus ? It seems like just another software from b1.

What does Taurus bring to the table? Its a private-blockchain. Multithreaded queries kind of stand out. Otherwise, don't see any real innovation tbh.

if you look at previous announcements from B1 (prior to us giving them the boot) the EOS price always responded favourably. In this case, if the ENF were working with vs against B1, we could've been involved with their plans and even prepared for this announcement with one of our own that we'd be setting up a new SAAS service to bring in enterprise adoption and help tie private blockchains into a trusted one via IBC. So now a private chain can have users, with assets (say gaming related) that can allow users to migrate their earned tokens, NFTs, etc...back to a public L1 blockchain. I'm just spitballing here, but there are lots of ways a talented marketing team could've used this to our advantage.

If B1 didn’t dump on us we would be higher too

except what they dumped they previously bought...

I think we’ve had that for a while now, with some improvements recently in 4.0.

A lot of what they mention is old stuff, and the blog post reads like it’s pitching the software in general as opposed to anything new.

Aaah, right! Should take some time to go into the entire update log/code stack again. (If I ever find the time)

Right. So I dont think Taurus has much to offer that EOS does not already have. Makes sense that great institutions actually prefer a private chain tho (to obscure transparency).

Or are there things in Taurus that makes you say:"We could/should probably adopt that"?

obscuring transparency has likely very little to do with it. If that were the goal why run a private blockchain instance at all.

So its auditable, and can be regulated as if it were the old internet, but logged like a blockchain. Tho not visible what the holdings of one's address are to the outside.

it could be visible is the point. Did you read the opening of the press release: - Cryptographic security for customers’ funds (all transactions require private keys). - Non-repudiation for transactions (no super user and only customers can transact). - Immutability & auditability of exchange operations for regulator inspections. - The capacity to enforce that customer balances square up after every transaction.

it was a bit new to me, and definitely the features listed later in the article.

One's holdings would not be (per definition) publicly visible on a private chain, whereas they would be on a public chain (although can be obscured to by spreaded holdings over multiple addresses).

Okido, such a b1 fanboy 😉😇. (immutability or usage of private keys are not at all new, lol)

from an auditing POV individual holding's could be determined. And I don't think its impossible to also tie in IBC from a private chain to a public one...there are many uses cases here.

did you read the press release?

Yea, scanned through most of the article

and you see nothing new in there...all old news, stuff you already had access too and knew about? It looked quite new and useful to me.

This is FUD did you see what ENF was able to deliver with only 49M$ and you say that B1 invested 1B$ lol. Dan said that eosio was only 10M$/year this is far from even 100M$. Also nobody gave them 3B$ to put it in their poket. You seem to be happy by the fact that they could keep all the 3B$ for themselves.

Are you ever programming, Chris? (I'm personally not programming anything on chain. I'm programming as a bioinformatician, so that fills my schedule already). I do try to keep up-to-date on the codebase of several chains (Tho @jestagram actually pointed out EOS has a feature I didn't know it already has: multithreaded queries (read-only).) So the only other thing I was able to see in there that I thought: "That could be potentially something useful, sometime" are transactions with a longer execution time. In EOS transactions have time cut-off before they should either be finalized or aborted, right? Please correct me if I am mistaken.

The vast majority of it is old stuff. We knew about most of these features already existing, most of which only benefited Bullish, some of which were rejected by all the public networks. There’s probably a few minor improvements that could be pulled out, but nothing I’ve seen that anyone from the development/infrastructure side is excited for (so far).

Is it really true that B1 has invested 340M$ on projects on EOS ? If this is true why they didn't publish those projects a long time ago ?

@ChrisBarnes1 it seems there is nothing new in torus

there seems to be a couple of good items that could be taken into the Leap, but it needs time to analyze

Are you a dev ? It seems devs here said that there is nothing new.

Like @cc32d9 said above, there might be a few things worth pulling out and implementing into Antelope/Leap - but it’s nothing to get excited about at yet. It’s going to take time for developers review the mess they created in this new codebase and determine what’s actually valuable. I’m also guessing that most of the code of value in there may have been written years ago, by the engineers who left B1 and now work at the ENF. They’ll probably be the best to judge what of that prior work is valuable. There isn’t a binary yes or no answer yet to “is there value?”. It’s just something I don’t think anyone has reason to be super excited about.

Temper expectations, and be excited if anything of value actually comes of it.

there's some value, maybe :)

So far the value we've found is in the (previously proprietary) code written by engineers who now work for/with the ENF. Some of the potential value is moot as we had already addressed it in other ways (we had the talent but not the code). What remains will be a win for our tech debt initiatives but we haven't found anything that's a good candidate for feature-level adoption yet. Still looking. I will say it would have been nice to have had this in the open 12 months ago.

@ChrisBarnes1

Thanks for confirming, and I’m glad you folks are already evaluating it. I’m also very grateful the talent still exists to do this sort of work for EOS and Antelope as a whole 🙏 And yeah, it certainly would have been nice if this was open source all along. A number of things I noticed had already been reimplemented, which sadly came at an extra cost to the network… all because that prior work was proprietary for so long.

@rektkid

I guess the proof will be on whether or not this is continually updated

I only know what that tweet said...so not sure other than its rather self explanatory.

did you not see the reply from CC32d9 to your comment? "there seems to be a couple of good items that could be taken into the Leap, but it needs time to analyze" For me, I'm not a dev, but I have spun up a node and am producing blocks on an Antelope chain.