nick.sway ⛽️

Can't wait to see something like this in Fuel.

Unlike EVM, Fuel can provide enormous amounts of state writes w/o putting the entire chain into memory.

The advantages of UTXOs become much clearer when you get to high performance use cases like orderbooks.

Vibe at DappCon is great.

Mostly builders, no fluff. Solid.

I'll be speaking soon at DappCon.

The topic will be how Fuel can uniquely support running multiple Hyperliquids onchain and retain composability.

⛽️

Fuel Forge will be an incredibly important moment for us and the eco 2.0 initiative.

Eco 2.0 is about 2 things:
- Bolster, improve, resource, and revamp the strongest ecosystem projects
- Expand the ecosystem to a new wave of builders and founders

The focus: insane blockchain apps.

We spent a long time building the ultimate infra for high performance blockchain, but building an ecosystem on an entirely new stack has been incredibly challenging.

Eco projects hit many head winds, everything was an uphill battle, we were not ready to get extremely hands on with projects to ensure they have the best chances of success.

But that changes with eco 2.0. Fuel is now far more equip to get extremely hands on from planning, strategy, hiring, resourcing, architecture, development and more.

Building on Fuel should only be a benefit to an app and its users, never a negative.

With our new infra on the way for fast bridging, wallet UX, throughput and latency, building an app on Fuel will mean any user from any chain can seamlessly leverage Fuel without ever noticing Fuel at all.

Forge is about unlocking Fuels infra potential to build a new category of blockchain apps never seen in the space.

If you want to go deep, push yourself, and design the next wave of blockchain applications, join us.

⛽️

UTXOs are the only way.

After building a CLOB for the past few months (o2), I would never in my life want to do this on the EVM.

You can see why HL didn't just yolo an EVM contract on a copy-pasta chain.

Sway is a beautiful language.

Here is a liquidity pool which mints/burns a native asset LP token.

No ERC-20 garble.

No approve/transfer from.

Just simplicity.

Hyperliquid has changed crypto forever, and it’s a good thing.

We spent so long dancing around the fact that 99% of the actual real business of crypto is just tokens, exchanges and fees.

This is where people are willing to spend money (both on CEXs and DEXs). It’s where the big revenue actually is, trading fees.

This whole time, people just wanted a CEX with more leverage, no KYC, some level of safety, decentralization, fairness.

Sure, RWAs, stables, identity, and governance all have a place, but those don’t move like trading moves. Not nearly the same velocity of fees.

HL has made crypto somewhat simple now, it’s basically the hygiene factor.

I’m still very excited for all the other vertices in the space, but hats off to HL for simplifying the mess.

Current Perps DEX Watchlist:
- GTE
- Valhalla
- Lighter
- Ostium
- Hyperliquid
- Aptos
- Eclipse

Current Perps OB DEX Watchlist:
- GTE
- Valhalla
- Lighter
- Ostium
- Hyperliquid
- Aptos
- Eclipse

UTXO > state access list

So if Ethereum wanted to improve its execution layer, it will need to do the following:

- better virtual machine
- improve transaction model
- use a tx model conducive to privacy
- focus on minimizing state growth
- focus on bandwidth compression
- single slot finality

All of which we already solved with Fuel and Tendermint, but alas Ethereum must do it “its way”.

Time for a thread on Fuel's transaction model.

... and how it fixes token state bloat we see on Ethereum.

🧵

Some upcoming eco:
- TheRig (stFUEL)
- Ruscet Relaunch (GMX v2+)
- Mira Rebrand/Relaunch
- Bako NFT Marketplace
- Bako global on/off ramp
- 1Delta Points Program
- SwaySwap 2.0
- Fast Bridging (Base <> Fuel)
- [Redacted] Partnership
- [Redacted] Partnership
- Hyperlane integration
- O2 Private Alpha (spot)
- ZAP Ethereum wallet support
- Stork real-time oracle
- M0 treasury backed stablecoin
- ReactorDEX launch

Some upcoming eco:
- TheRig (stFUEL)
- Ruscet Relaunch (GMX v2+)
- Mira Rebrand/Relaunch
- Bako NFT Marketplace
- Bako global on/off ramp
- 1Delta Points Program
- SwaySwap 2.0
- Fast Bridging (Base <> Fuel)
- [Redacted] Partnership
- [Redacted] Partnership
- Hyperlane integration
- O2 Private Beta (spot)
- ZAP Ethereum wallet support
- Stork real-time oracle
- M0 treasury backed stablecoin
- ReactorDEX launch

Some upcoming eco:
- TheRig (stFUEL)
- Ruscet Relaunch (GMX v2+)
- Mira Rebrand/Relaunch
- Bako NFT Marketplace
- Bako global on/off ramp
- 1Delta Points Program
- SwaySwap 2.0
- Fast Bridging (Base <> Fuel)
- [Redacted] Partnership
- [Redacted] Partnership
- Hyperlane integration
- O2 Private Beta (spot)
- Stork real-time oracle
- M0 treasury backed stablecoin
- ReactorDEX launch

Another advantage of building your own VM vs an ISA is you can tailor key aspects for ultimate efficiency.

RISC-V has no built in heap facility and leaves this up to the OS/software level. For normal computing, this makes total sense, who cares how you want to manage the heap. But in a metered environment like a blockchain, this adds a lot of overhead as each operation must be gas metered for every transaction.

The FuelVM, designed for blockchain and metering, has heap facility out of the box for this exact reason, avoiding having to pay for this every transaction.

Sure, in RV you can maybe add this facility in the ecal but then you might as well just use the FuelVM.

We didn't target these numbers at random. They are what's required for Fuel to become the greatest on-chain trading experience ever constructed.

1ms confs
150k tps
400k orders per second
1-4s bridging
any wallet, any chain, any asset

Fuel = real-time. No compromises.

We didn't target these numbers at random. They are what's required for Fuel to become the greatest on-chain trading experience ever constructed.

1ms confs
150k tps
400k orders per second
1-4s bridging
any wallet, any chain, any asset

Fuel = performance. No compromises.

Does anyone have any bls signature verification contract examples to test the new bls opcodes from Pectra?