SRE/Devops @Luganodes | contributor @hyperliquidX Rust SDK | @peripairbot dev
Shell
Joined July 2015
- Tweets8.5K
- Following1.5K
- Followers858
- Likes7.5K
Pinned Tweet
dudes using @peripairbot literally got 2x-3x more points by pair trading and you're trying to fade us anon 😮💨😮💨😮💨
Holy shit
xitter.cf/marionawfal/status/211…
managing infrastructure for validators ruins your patience for pretty rust code.
low-level shortcuts and clean abstractions quietly eat latency right when the validator needs to keep up.
clean code still pays hardware taxes.
managing infrastructure for validators means fast hardware cannot outrun bad peers.
someone treats a rollout as normal, but the gap between stable and degraded is razor thin.
the margin for error is razor thin.
shipping peripairbot in the open left nowhere to hide sloppy code.
real traffic made edge cases impossible to ignore, and people broke things in ways you never thought to test.
public accountability fixed code fast.
then the cyber sec firms swoop in to sell the companies on these "cyber defenders"
programs that will monitor and actively patch CVEs across your fleet.
timing should be near the next local top of the market.
the compiler will happily let you allocate dynamic vectors inside hot block loops.
then peak throughput hits and tail latency spikes off allocator locks. pre-allocating fixed static buffers avoids the entire mess.
heap churn kills performance.
running staking validators across 40+ networks means slashing risk is constant.
silent failures do the damage while dashboards look green. nobody notices your work when everything stays up.
invisible until something breaks.
peripairbot hit 500+ users and $30k revenue with simple trading logic.
the actual work was operational reliability in a solo timezone. optimizing compute, running cheap telemetry, and deploying rapid fixes before users noticed.
reliability was the whole product.
ai coding tools optimize for developer speed at the expense of runtime performance.
generating code faster just creates technical debt that shows up months later.
impact per line is what matters.
managing critical staking infrastructure means validator performance and uptime depend on predictable runtimes.
slashing risk is constant and silent failures never announce themselves.
nobody notices until something breaks.
0xECS ⎊ retweeted
My theory is that everyone who knows you exist— wants you to win relentlessly
- every person you’ve ever met hopes you are likeable
- every job you’ve ever interviewed for hopes you are the perfect candidate
- every date you’ve ever been on has hoped things would work out
Everyone wants you to be a valuable person, the world is in your favor if you choose to wear the shoes.
Ball is already in your court
Goated take
Man's done it again
My theory is that everyone who knows you exist— wants you to win relentlessly
- every person you’ve ever met hopes you are likeable
- every job you’ve ever interviewed for hopes you are the perfect candidate
- every date you’ve ever been on has hoped things would work out
Everyone wants you to be a valuable person, the world is in your favor if you choose to wear the shoes.
Ball is already in your court
they're really going to start cutting your electricity to "save you from super intelligence" aren't they
man oh man
building peripairbot in public changed how i think about shipping code.
running it at ~99% uptime on minimal cost meant optimizing compute so it never had to spawn extra worker threads. bugs got fixed fast, sometimes in the middle of the night, and the telemetry had to stay cheap enough to keep running.
real traffic is completely merciless.