ben

Rust enjoyer
DeFi engineer @flint_trade_

[Flint Trade @flint_trade_]

https://t.co/B6gJtftrIg

[ben @_datben]

RT @_rustopian: Most Solana programs are one typo - or one agent mistake - away from disaster.

Security pros warned us 5 years ago to not…

[Flint Trade @flint_trade_]

https://t.co/bkq2lk0FVV

[ben @_datben]

@PierreArowana Just use @flint_trade_

[Roger Wattenhofer @TheWattenhofer]

We separated church and state because a king who spoke for god never had to ask.

Now let's separate money and state.
The printer funds wars nobody wants.
It buys elections with money that doesn't exist.
It taxes you forever through inflation.

A state that can't print money must ask.

[Flint Trade @flint_trade_]

How Flint works

The book lives on-chain. Matching and settlement both happen in the Solana program; no off-chain engine holding the real state. The server is an edge, not a sequencer: landing, market data streams, analytics.

@thedavidgorski on the full system 👇

[ben @_datben]

Just started MEV on slack, DM me if you want alpha

[dgski @thedavidgorski]

Many firms have pricing models. ~Five have the Solana engineering.

Right now, it's not easy or cheap to provide active liquidity on this chain.

I want a big, beautiful, ergonomic on-ramp for new blood and that's what I'm focused on.

Soon.

[ben @_datben]

@toly @moonshiesty @atarashi @defido something sweet is being cooked atm

[Titan @Titan_Exchange]

https://t.co/pkgRYKXPeD

[ben @_datben]

@thedavidgorski Big if true

[π* | ¤ @totlsota]

worth mentioning re this Solana PERP DEX: Superis Labs project:
- this is already well advanced
- there are some very smart people working on this
- this will be good

[ben @_datben]

@mmdhrumil @ArcherExchange_ do you handle SOL -> BTC if there are SOL/USDC BTC/USDC markets ?

[dgski @thedavidgorski]

Solana Transaction Execution Lock Relaxation Proposal

A scheduler (both leader and replay) change that has a theoretical improvement of less than ~2x. No protocol changes needed.

Idea: Drop transaction read locks right away after loading the account state.

Why? This allows upcoming transactions that write-lock the same account to start executing immediately. Pipeline efficiency potential increases significantly (depending on shape).

How? Enforce linearizability requirements. While sub-sequent transactions write locking the same account can start execution, they cannot be recorded as before the reading transaction.

All account states are locked, read and frozen at the start of the transaction; this keeps things consistent throughout execution of the reading transaction.

The linearizability concept happens at the commit/record level; even though the reading and writing transactions might be happening at the same time; the read will always be recorded before the write.

In the case of failure; write transaction is unblocked from commit.

Now that transaction batches can be conflicting (recent change), the trade off here would be the savings of locking and loading the account in one thread and then execute sequentially versus finding an optimized boundary in the graph to split and put into another thread (paying the price for the cross-thread communication). For 'heavy' transactions this could exceed the cross-core optimization.

Generally the less restrictions for ordering, the more flexibility the execution pipeline has and the more efficiently it can schedule.

[ben @_datben]

@bunjil @redacted_noah We are so cooked

[ben @_datben]

@xpmaxxer Luna ponzi was running on unsustainable. If that model had grown bigger, the eventual collapse would’ve been even worse for crypto

[ben @_datben]

Unpopular opinion : Jane Street saved crypto

[ben @_datben]

@thedavidgorski wen perp on btc

[dgski @thedavidgorski]

Flow of Value > Store of Value

Technologies, systems and protocols that enable compute, dynamic state changes, and real transactions are far more interesting than static, HODL til you die, sinks for capital.

Holding has it's place; but it is inherently stagnating on it's own.