AuntChel

Crypto native, market adaptive 🌊 | Spot & futures trader 📊 | Looking for the next paradigm shift ⚡

[AuntChel @auntsol]

@0x_Anni look cool sis

[0xAnni @0x_Anni]

Tavus gave me early access to Griffin, their first human interaction model.

The part that got me was the goodbye.

I said I had to go. She didn't just take it. "Wait, really? Already?" Then she wished me luck with the speech, the one I'd brought up earlier in the call and had already forgotten about myself.

Not scripted, and nobody is operating her.

> first model to pass the Turing test: 45% of 120 people thought it was real
> in the control group, 28% thought a real person was the AI
> first on NVIDIA's Video Full-Duplex Benchmark: 3.83 of 5, against a human at 3.92
> the next best system scored 2.80, and took a full second longer to answer

It is a research preview, not something you can build on yet. Which is the part I keep thinking about.

@tavus @hassaanraza
https://t.co/MFotdOUJSI

[AuntChel @auntsol]

@Zdonuk94 banger

[AuntChel @auntsol]

@Zdonuk94 ahaha funny

[ZDNK @Zdonuk94]

The agent gets better at my work every month. A prompt never does.

That is the part people miss about the Picsart marketplace. There are 19 agents in there, and each one trains on your own output the longer you keep it. Month one it is a competent director. Month six it knows what my shots look like.

A prompt starts from zero every single time you paste it.

> research finds a format already beating its own channel
> the director agent in Picsart plans the rebuild scene by scene
> Make publishes it and reports which format held
> $15 Picsart Pro, $20 research, $9 Make. $44 in, $12,900 out

So is anything in your workflow accumulating, or are you starting over on every video?

Both prompts and the whole pipeline 👇

[CZ 🔶 BNB @cz_binance]

At least, the few recent wind-downs during this winter have allowed users to withdraw their assets, a sharp contrast to the "QuadrigaCx styles" in the previous cycles.

[vitalik.eth @VitalikButerin]

A lot of important progress on Frames (EIP-8141) has been quietly happening over the last few months. Highly recommend reading this, also the updated EIP https://t.co/jYqeS55j6P
https://t.co/CPYONKnWZc

[vitalik.eth @VitalikButerin]

Many years of hard work went into the Poseidon family of hashes, and they have provided great real-world value on Ethereum and elsewhere and will continue to do so for several years. They are the reason why it's fast to generate a client-side SNARK for a modern privacy-protocol.

The fact that we have ultra-fast general-purpose STARKs (mid-three-digit overhead for basically any batched computation) and may well soon drop to double-digit or even lower is more amazing than anything that we had been hoping for in the early 2020s.

Big congratulations to all involved in Poseidon, and all involved in STARKs.
https://t.co/cdERDYkj6n

[vitalik.eth @VitalikButerin]

A note on recursive STARK mempools (EIP-8288) https://t.co/XNBuNtkKmi

This is an EIP that I am hoping we can get included in I-star (the fork after Hegota) that you can think of as the next step after Frames, that would unlock extreme amounts of power. Particularly:

* Ultra-cheap quantum-safe signatures (SPHINCS-). Much of the cost savings comes from the fact that the signature data (~3 kB) does not have to go onchain
* Ultra-cheap quantum-safe privacy protocols. Status quo minimum cost for private txs is ~300k if you engineer very well (no one does), status quo quantum-safe is ~10M gas, this could reduce it to low tens of thousands.
* Universal support for your favorite new signature or proof scheme without needing EVM changes. Whatever you use (Falcon, ML-DSA, some other lattice-based thing, something code-based or isogeny-based or even more esoteric), you can just wrap it client-side in a STARK, onchain gas cost low tens of thousands just like privacy protocols. Hopefully, Ethereum will never need "please support my favorite cryptographic algo" politics again.
* Private account abstraction: keep your account logic private, and in a private location onchain. Then you can make one transaction to change the ownership of all your onchain state - accounts, defi positions, privacy protocol notes, everything - without revealing which objects' ownership you're changing.

Here's how it works.

Your transaction can include a type of frame that we call a "dependency frame". The frame is a list of statements, asserting claims like "message hash M was signed by SPHINCS- public key P" and "data hash D was proven to satisfy a statement defined by verification key V".

When you send your transaction, you send it in an envelope, which includes a signature or a STARK for each statement in a dependency frame.

Once the transaction reaches the mempool, nodes aggregate them. Each node runs a loop: wait one tick (eg. 500ms), aggregate all new envelopes (either single-tx or multi-tx) that you've seen, remove any transactions that are expired, generate a STARK recursively proving all dependencies, and send a new multi-tx envelope containing that STARK.

Hence, the bandwidth load is bounded: each node's outbound is one STARK (~100-300 kB) per tick, plus each transaction getting broadcasted through the network once (as happens already).

The block builder acts as "yet another mempool node", receiving envelopes from the mempool (plus any side channels), generates its own STARK covering the subset of transactions it intends to include in the block, and adds that STARK to the block.

Total onchain overhead: one STARK (100-300 kB), plus 96 bytes for each statement being proven.

This is what I've called before ( https://t.co/3jfVkYTZrR ) "The Proof Singularity". Today, we have all the ingredients to actually implement it.

As a developer, this requires a somewhat different workflow than you are used to, but it is conceptually simple. Any signatures or STARKs, you put into a separate frame. Then the main logic that today is verifying a signature or STARK, you replace with checking for the existence of a frame that includes the correct statement as a dependency.

Examples of useful statements:

* [tx sighash] verifies against [the pubkey at sload(0)]
* there exists a secret and a merkle branch such that hashing secret+0 and applying the merkle branch outputs (public) root R, and hashing secret+1 outputs (public) nullifier N
* there exists a secret address A, salt S and signature Z such that sload(0) = hash(A, S) and a merkle proof of address A inside a recent ethereum state contains some pubkey D where [tx sighash] was signed by D [this is private account abstraction; all variables except [tx sighash] and sload(0) are private; you can also make D a STARK verification key]
* there exists an ML-DSA signature signing [tx sighash], that verifies against an ML-DSA pubkey whose hash is sload(0)

At the core, this is moving any compute and data other than bookkeeping "business logic" outside the core path of Ethereum execution, sharding and parallelizing it via the mempool.

Notice also that this requires agreeing on a _language_ (aka. an ISA) for the recursive STARKs to define statements in. The current leading candidate is RISC-V. So this would also de-facto be Ethereum adding RISC-V (or something else we decide on) as a canonical ISA - a big decision that should be done carefully, but that I think will be necessary to drive Ethereum forward.

[Solana @solana]

Toly on Solana as the end state of finance

"A unified financial layer where you can transfer money to anybody anywhere in the world and access any market anywhere in the world in a single atomic transaction that executes in 100 milliseconds. The time it takes to get light around the planet is the settlement and execution of finance."

[AuntChel @auntsol]

I’m trying to record this @delta flight attendant who is actively actually barking “chicken, beef, or fish” at the plane so no one asks her while she is next to them.

She scolded the man for asking her the options

We have to stop sending the rudest ppl on these African flights.

[AuntChel @auntsol]

Give @RuPaul the Emmy for this week’s episode. Tears the whole time. #rupaulsdragrace

[AuntChel @auntsol]

It was so perfect I cried. We are so blessed to be able to witness queer joy in times like this. Thank you #DragRace

[𝔞𝔭𝔦𝔣𝔣𝔞𝔫𝔶 🪩 @dragraceher]

as soon as the song started, i knew EXACTLY what i wanted to see and to say that Kori King & Lydia B. Kollins delievered would definitely be an *understatement* like– 😩 THE KISS?!?! i'm SHOOK. they fucking ATE. #DragRace

[Jaron @mtraininsane]

JAW WAS ON THE FLOOR #DragRace #rpdr

[AuntChel @auntsol]

Ain’t no way there’s an actual Black couple that found love this season on #LoveIsBlind and we still gave this girl’s instagram 15mins of screen time. I’m tired.

[AuntChel @auntsol]

@CallMeSirg Same.

[AuntChel @auntsol]

Her looks are always everything but I thought she would be eating WAY MORE. Staying tuned tho.

[Jaron @mtraininsane]

I’m OBSESSED with the umbrella illusion into the cane #rpdr #DragRace

[AuntChel @auntsol]

Jewels ATE TF DOWN. Suzi was just okay. Sam was just okay.

[Sultan Boushahri @SBoushahri]

Jewels has played an Australian lesbian, a jade/alyssa hybrid, a female big foot, a perky galinda and devoured every single one of those roles, yet she’s still not received a win? This is insanity. She also won week 1’s lip-sync. #dragrace

[AuntChel @auntsol]

Well damn. Before I could hit send.

[AuntChel @auntsol]

Watching Paradise ep 4. They are making me like Billy too much. I know they are about to kill him.