TezEdge is no more for Kathmandu

https://twitter.com/tezedge/status/1570423910822289408?s=46&t=ORNs_xEhjyfL_xtH-aUZ6w

This looks like an great shame and there is absolutely no information as to reasons why and path forward.

If the reason is that OCaml is enough, someone should make an argument for that. There are some really good points against I want to get into as well as others who share the same view. Why not have this discussion in the open?

Most importantly though, let’s please aim not to have things happen, that affect each and every one of us, in the middle of the night with no explanation from anyone. There are some really shady vibes that come with this kind of reality.

3 Likes

Building a node is a serious technical challenge and a lot of work. I’m not terribly surprised this effort failed, but it doesn’t mean we shouldn’t keep trying - client diversity is valuable, as is supporting a language like Rust with bare-metal speed and a much more vibrant developer community.

The loss of this Rust code is a major blow for Tezos. I have been begging/screaming at core teams for years to split their work up into reusable modules that can run natively on other platforms (e.g. in a language such as rust, C, C++ etc), with no progress so far. I had spoken to TezEdge about them splitting up the client/node into separate repos so I could play around with importing bits and pieces (forging, parsing, michleson/micheline transformations, crypto module that supports all Tezos curves out of the box), directly into apps or providing language specific wrappers around them. They were open to the idea but too busy with protocol work at the time. Now back to square one, painfully hacking away at JS libraries and taking massive performance hits