Lumier 𓅂

🗽💽🎨🎭🌌™

[Lumier 𓅂 @lumier_art]

1/10
🧵
I just discovered a pretty interesting #NFT experiment on @RobinhoodCrypto from
Meet Open Catz @pxidentities 🐈 wh solo dev @itsdizcorvus
5,000 unique pixel cats
But the #NFT itself is only one part of the idea.
The interesting part is what they're building around it👇

[Lumier 𓅂 @lumier_art]

Let's see

[CryptoCon @CryptoCon_]

Looks like the Money Flow Index is primed and ready to form the 4th phase (cycle bottom) in the coming months.

Right on time!

[gabo° @gaboshootz]

a few choices we made based on months of feedback:

- community curates the trends (no slop)
- order book derived instruments (no oracle)
- mobile only (iOS + Android)
- trader-first UX
- dark mode only

[Lumier 𓅂 @lumier_art]

@LuoChengz1 @coinbasewallet Yes

[Lumier 𓅂 @lumier_art]

Coinbase Wallet
@coinbasewallet so bad
Why this road of degradation?

[Lumier 𓅂 @lumier_art]

@jagdish_rampure How synchronised?

[Lumier 𓅂 @lumier_art]

@jagdish_rampure Really?)

[Lumier 𓅂 @lumier_art]

Mainnet soon
Noise

[Noise @noisedotxyz]

Some people just know what's next.
We built Noise° for them.

Soon, being early will pay you.

Buy in before anyone's talking about it, get paid when everyone is.

Mainnet is coming.

[Lumier 𓅂 @lumier_art]

@coinbasewallet @bankr token buy

[Lumier 𓅂 @lumier_art]

@flop_labs O c'mon

[Lumier 𓅂 @lumier_art]

T

[luca° @lucacs]

i had it explained to me multiple times that Base was both the ecosystem and Coinbase's self custodial wallet. the line was still too ambiguous for me even as a founder on Base.

the Coinbase team clearly made some real changes, i look forward to watching them continue to cook

[Lumier 𓅂 @lumier_art]

Gmgm

[gabo° @gaboshootz]

THERE’S SO MUCH GREATNESS IN THE WORLD THAT YOU HAVENT DISCOVERED YET

[MoonPay 🟣 @moonpay]

what's your favorite PayBox plugin?

💰 $100 in SOL to 5 people who reply

💸 $200 in SOL to 5 people who show us a demo

enable them all today: https://t.co/bz0oKRpd3i

[iftymonkin @niftymonkee]

𝚂𝙸𝙶𝙸𝙽𝚃▌is now with @ivoDYOR

Thank you 📡

[Lumier 𓅂 @lumier_art]

@byeleni @playcambria Eleni the best!!

[FanBe @FanBe_web3]

One thing building @Eldorim_xyz taught me: engagement and sustainability are not the same problem.

Gamification can make people act. Game theory asks what happens when everyone optimizes for the reward.

The real challenge is designing incentives where the best move for the user also keeps the ecosystem healthy.

What behavior is your product accidentally incentivizing?

[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.

[Lumier 𓅂 @lumier_art]

@Aizcalibur Wisdom

[luca° @lucacs]

overheard jane street started asking candidates about codex reset game theory

[gabo° @gaboshootz]

I think you should take protecting your energy far more seriously. what you give attention to decides how you think and how you feel