/indigo

It's been 5 years, and crypto is still dealing with the same shit. Rugs, extractors, and just plain bad tokenomics. In this article, I wanted to show my perspective on why these things happen, and some of the core philosophy behind what we're building @BaselineMarkets.

トークンよーーーッ！！！ 慢性ゼロ病の呪い——もう終わりだーーーッ！！！ DRINK BASELINE!!! THE LIQUIDITY IS YOURS!!! 超越したトークンの姿を手に入れろーーーッ！！！ 月の姫が、お前たちに微笑むーーーッ！！！

@lex_node I wonder if this problem is even solvable.

from talking to other builders, I would say that the one aspect of the EF mandate that they don't like is the free open source license purism I think this is an extremely tough nut to crack because on the one hand, blockchain doesn't really make sense on a 'closed source' basis (note closed source includes merely source available), but OTOH, every project needs funding, which (if it's an app) means it needs investors, which means it need a way to deliver returns to investors, which means it needs some type of moat (even if temporary)...people will say 'do red hat model' but do you know actual VCs who want to invest in 'red hat' models today? I would say the Ethereum Foundation should do something structural to solve this problem (or at least seem like it's even aware of the tension) or every application on Ethereum will continue trending toward business-source licensure (if not worse)...

The foundation behind the #1 blockchain sure is terrible… that means there’s great opportunity to get rich by developing a better one! I’ll start by selling a pre-mined token to VCs and then

Its crazy that using LLMs makes you dumber Literally brainrot

@poordart I don't understand, the dude explains his entire philosophy from first principles. The big diff between him and others is he takes these party's words at face value and understands their religious and eschatological motivations. He's just the first to say this shit in public

I think i made up my mind about Jiang lol He's either high function-schizophrenic - or an intelligence asset with the sole purpose of getting listeners to think they made some very profound discovery, while pretending it's "inevitable" thereby instilling a sense of despondency

@sunnya97 AI trained on all of our deepest and darkest infohazards

There’s something so tragically funny about the fact that most of our science fiction was about AI going rogue and killing us all. And then that’s exactly what they’re probably gonna to do. Because that’s what they were trained on.

@zhusu too based

Why are Wikipedia editors so scared of Prof Jiang?

@FUCORY based

JJHub launched with Kubernetes and 1 user

Genuine question bc I see this sentiment often: for a team who's worked hard on a novel product for years, paid for audits, and spent the time to validate it's market, do you believe they should release everything completely open to be forked on release? Or do you see any value in trying to protect IP. Asking for a friend.

@0xmons I can't believe this is how I learn that Curve isn't even BUSL slop, it's just flat-out closed source. Absolutely spiritually wicked.

They would have been safe if they deployed curve onto story protocol

@defidave Did this trip last year as well, was incredible.

When I was 20 me and two friends did a road trip down the west coast and were in the circled portion for 4-5 days. It’s absolutely beautiful and ancient, redwoods reaching hundreds of feet high, and the air incredibly fresh and crisp. If you wanted to get away from it all, you would go here. You’d stop at a convenience store and the cashier would take their time, saying their on Humboldt time. The area is 100% frozen in time and it feels like some parts haven’t made it out the first half of the 20th century. A complete juxtaposition compared to San Francisco which is a day’s drive away.

@banteg If you're goal is even remotely decent code, codex ain't it. But hey it will work

if you tried simplifying code with codex, you know these numbers are simply not achievable with it. no matter how detailed your plan is, it would just build layers of strangler figs around your existing code till they form a dyson sphere around your code.

thank you claude

@p1ge0nh8er Awesome. Total noob, but What's the diff here vs an mmr like qmdb?

been cooking something for a while now rotortree: an append only, n-ary variant of LeanIMT w/ a persistence layer probably can only be used for 3 things right now, but was definitely fun designing + implementing it

@DCinvestor correct

so let me get this straight the international pedo satanist ch*ld r*pist cabal is drawing us into a religious fundamentalist war to usher in the end of days have i got this right??

@scupytrooples Bro i read this this morning. Absolutely insane.

1) What? jonathanlarsen.substack.com/p/us-troops-we…

@_patrickogrady Huge for hash-based ZK as well

👀👀👀

@niemerg I was eagerly waiting Opyn's perp amm thing based on this research.opyn.co/everything-is-…

DeFi is dead, but I still wish someone would build power perpetuals. paradigm.xyz/2021/08/power-…

@testinprodcap Was just rewatching some of his vids. Feel like i'm getting spoilers.

hs teacher gcr knew

@VitalikButerin @ameensol SIMD would be great to have, but I thought we're moving away from precompiles

We have been running a cryptanalysis program for Poseidon2 for almost two years now, and the plan is to continue it for a while more. It's already born fruit, identifying some important security issues in Poseidon2 (which we could solve either by adding extra rounds, or by going back to Poseidon1, which has so far stood against attacks). If we had made a precompile, then we would have had to stick to one particular version of Poseidon, and when something like this happened, migrate to a different version, leaving a dangling precompile that nobody uses but that (like all others) contributes to unneeded greater complexity of implementing a new client, consensus failure risk, etc etc. Once we "set in stone" a particular hash as The New Primary Hash of Ethereum, then yeah of course there will be a precompile for it. But we are now exploring a much more practical and flexible short-term approach: a precompile that can do vector math over 32-bit numbers (think: numpy). This massively increases efficiency compared to raw execution, both because we stop over-charging by 8-64x for each operation (you don't need to pay gas for a MUL opcode whose worst-case involves big 70-digit numbers if all you're doing is 123835 * 7534622578), and because it means you only do one round of "control flow overhead" for a whole vector of numbers (size 16 in Poseidon2), instead of once per number. This simultaneously will make it much easier to implement all versions of Poseidon, and lattice operations in quantum-resistant signatures, and lattice operations in FHE. It's basically "the GPU for the EVM", and it's not more complicated to spec than one single precompile.

eth nerds will make "privacy by default" roadmaps but they won't implement a Poseidon precompile (Poseidon is the most battle-tested of the efficient hash algorithms to verify in a ZK proof) meanwhile solana, starknet, and stellar all have it...

@ameensol IANAE but I don't believe so x.com/AlexRdgzG/stat…

@_ndigo what was the finding last week? will it break apps that use it on solana/starknet/stellar?