RIP Beeswap - Crypto-Dreamr remembers

3 hours ago

We love(d) Beeswap, I know we did because I did, and I used it almost every day for years. There is a lot of story, a lot of history to remember - and as they say, "to love and have lost, is better than never having loved at all". We can also see some interesting parallels with The Legacy of ARCHON, I have no idea if other people are learning some of these lessons along side of me or not - but I am writing about them and they are meaningful to me (which is my bar for a HIVE post anyway).

Now we have tons of these tutorials, archeological evidence that could be used to reconstruct what we have lost.

Maybe nothing lasts forever, but the durability of what we build is often a more important question that we give it credit for in the moment. It's one of the often forgotten pillars of the open source philosophy, that open source code is more durable "for the community" than non-open source code.

Because someone from the community can pick it up and run with it, regardless of communication levels at the critical moments of teams disbanding and projects ending. Maybe not everything can be saved in all cases and all times, but the bits and pieces we can save are "worth it", if not for the developers themselves then as least as a Pareto Calculation of overall utility across all users aka "the community".

HIVE-Engine

I have been working with Hive-Engine seriously, "developing", for about a year now, along with my brilliant friend and wizard @thecrazygm. I have dug deep, and I have heard all the arguments. When people talk about "hive-engine", they are referencing one or more of the 6 or 7 distinct pieces of what makes up "HIVE-Engine", a consortium of concepts that when taken in it's entirety makes up a crucial part in what it has meant to "play around on HIVE".

Some of those pieces are not at all decentralized. Some are theoretically decentralized with centralized dependencies. Some are truly and utterly decentralized, as the word means. One day hopefully soon I will make the effort to break down these 6 or 7 pieces of what we usually call the hive-engine protocol.

In my mind and in my own legend lore - BeeSwap (run by @gerber and @scriptioner) touched something at the heart of the decentralized guts of hive-engine.

Swaps and Pools

It took me less than 1 day to really come face to face with the fact that I cannot live without some of Beeswaps functionality. Tribaldex is okayyyyyy.... but okay doesn't cut it. Tons of extra clicks into my workflow, losing visibility - which already wasn't great.

I need better tools. I need them, so we build them. Sometimes other people like them as well.

I'm not great at copying, I just want to see my positions in the liquidity pools. It's public information isn't it? Maybe I want to see your positions too.

https://tools.crypto-dreamr.com/beeswap/pools/positions?username=ecoinstant

A moment of silence for Beeswap. You will be missed.

Our beeswap tool isn't really completely ready, although you can click around and see things now. I have no interest in being beeswap. But there is now a pretty big hole of missing functionality in the ecosystem - and I cannot abide that; my own workflows cannot abide by that.

Anybody could probably vibe code up a replacement. A replacement ui, a replacement market, a replacement token protocol, a replacement layer 2. You might vibe code up a replacement nft game or even a replacement blockchain.

I'm not sure the value is in what we "can do".

It's in what we come together to do. And in that vein, I want to end by celebrating the great work of Mantequila with their "HIVE Brain" project, and mention that I have submitted and got accepted by @meno an updated Hive-Engine Skill for agents.

Expect more updates from me in this area. I am not against other layer 2s at all either, and as soon as we start using them we will probably start building tools for them as well.