Sabitlenmiş Tweet
smstack.eth
2.6K posts
smstack.eth
@StackDigest
engineer @sunnyside_io | @DecipherGlobal | ko @organ_mo
Katılım Ocak 2023
973 Takip Edilen787 Takipçiler
smstack.eth retweetledi
Ethereum Korea
Build the Path, Connect the World, Execute the Future
기여가 인정으로, 기록이 연결로, 펀딩이 공공재로 이어지는 생태계를 만들어나갑니다.
한국어
smstack.eth retweetledi
OP Stack is for institutional adoption!
Optimist Prime@jinglejamOP
We are extremely excited to announce Vision Chain in collaboration with Bitpanda - A regulated European exchange with 7 million users, powered by the OP Stack!
English
smstack.eth retweetledi
We are extremely excited to announce Vision Chain in collaboration with Bitpanda - A regulated European exchange with 7 million users, powered by the OP Stack!
English
smstack.eth retweetledi
@akashneelesh Can I know the name of the PQ safe wallet or where can I use it?
English
native account abstraction since 2021
also what if i told u we have a post quantum wallet on starknet already ?
ladislaus.eth@ladislaus0x
AllCoreDevs plans to make a decision on EIP-8141 (frame transactions) inclusion in Hegota this Thursday. If you care about post-quantum security on the consensus layer (leanCL), you should equally care about it on the execution layer. A PQ-secure CL with quantum-vulnerable (i.e. ECDSA-locked) user transactions is an incomplete migration. EIP-8141 decouples accounts from a fixed signature scheme, providing a native migration path to PQ-secure signature schemes. But it goes beyond PQ. Frame transactions also make account abstraction a first-class protocol feature rather than something bolted on via entry-point contracts, and enable programmable gas payment (in ERC-20s + sponsoring). Ultimately, both layers need to be PQ-ready.
English
English
@ch4r10t33r @ryanberckmans @ben_a_adams @StackDigest It cannot even do blobs or any meaningful AA change without protocol change????
English
Since people have been debating Frame Transactions, I decided to make my own proposal alongside @ben_a_adams
ethereum-magicians.org/t/frame-transa…
Here, I argue that Frame Txs in their current state offer only the illusion of abstraction and are/always going be moat, at least regarding the verification. On top of it, they are really bad at solving PQ unlike people claim they do (have been working on PQ last 2 weeks). OTOH Schemed Transactions (which is what is being introduced) are a reduced version of Tempo Transactions, they leave room to rethink frames later and enshrine what are today the "Verify" frames. With schemed transactions, we might not only get a way to enshrine good login into Ethereum but also immediatelly do PQ, all inside of Hegota with 1/10 of the complexity of Frame Txs.
English
So true, even watching these discussions are so tired... from 3074, 7702, and now 8141
ladislaus.eth@ladislaus0x
@ryanberckmans Account abstraction has been debated in various forms (3074, 4337, 7702, now 8141) for *years* At some point the cost of perpetually deferring the general solution exceeds the cost of shipping it
English
smstack.eth retweetledi
You can build whatever you want, even games.
ethereum.org/gaming
Lily Liu@calilyliu
Also, gaming on a blockchain is not coming back
English
@howydev Gotcha fully understood, agreed that it would not be a huge blocker!
English
@StackDigest Yup, but it’s not a big lift to fork + remove that check. The purpose is anti footgun, similar vibe as to check if transfer recipient is address(0)
English
@StackDigest isTIP20 is mostly just a guardrail, full functionality is possible even without it!
English
smstack.eth retweetledi
smstack.eth retweetledi
I've never understood the argument that Ethereum focusing on these cypherpunk-style values is somehow anathema to stablecoins, DeFi, or other financial applications.
Ethereum is the clear leader in all of those activities because it offers censorship-resistance (aka access), transparency (aka verifiability), and security (aka property rights).
If you study the long history of financial services, the markets and systems that attract the most participants and capital do so because they are widely accessible yet protective of everyone's rights. In TradFi this is done via laws and regulations. In crypto we can do it with cryptography and incentives.
The chains that sell out (or simp out) on these values because of a hack (or because some suit-wearing bank exec who is simultaneously lobbying to kill crypto asked them to) will never succeed with stablecoins, tokenization, or DeFi.
Those chains are even worst than the TradFi alternative.
Off-chain or on, the most reliable financial infrastructure is the one that's least likely to screw you.
A Foundation that focuses on pithy marketing slogans or throws money at every bank doing innovation theater provides zero assurances to future users that they won't get screwed.
A Foundation that embraces a philosophy like CROPS does.
Kudos to the EF for sticking to what matters, in markets and beyond.
Ethereum Foundation@ethereumfndn
Today, the Foundation’s Board released the EF Mandate. This document, which was first intended for EF members, reaffirms the promise of Ethereum, and the role of EF within this ecosystem.
English
smstack.eth retweetledi
Due to EIP-8141 (native AA), I've been deeply engaging with the ACD process, and there's some truth to what Dankrad is saying in that it feels like the people with decision making powers -- the client devs -- are somewhat detached from real-world usage of Ethereum.
However, I found that it's not that those people don't care -- it's just that their day-to-day job as client devs simply don't provide them with the opportunities to interact with application-layer builders and end users as much as, say, someone like me whose job is to build and sell commercial solutions do.
So how do we bridge the gap between 1) Ethereum's major decisions are made by client devs, and 2) client devs don't get to learn much from application builders and users? That's the key question the EF has to solve.
On the other hand, I also feel that application-layer builders need to take matters into their own hands more. You can criticize the ACD process all your want, but it IS open. All the meetings are announced in advance (github.com/ethereum/pm/is…), free for all to join, and recorded for all to watch. When you do engage with the process, like I've been for the past month for native AA, you find that the client devs DO LISTEN. They are not crazy people with evil agendas -- they just don't know what they don't know, just like the rest of us.
So yes, EF should keep improving the process, but before you complain about Ethereum heading in the wrong direction, ask yourself if you have ever TRIED to engage. Ethereum is for all of us and we all share responsibilities for making it better.
Dankrad Feist@dankrad
EF, last year: Hey, we want to listen to you users to make Ethereum better. EF, now: Jk, we looked at the real world. We don't like building for it after all, we'll go back to building cypherpunk stuff only. This is the EF going back to its old ways, undoing the changes from last year. I have feared this would happen because Vitalik clearly wasn't in with his heart. But whatever they say about the "ecosystem" being able to take care of this, the fundamental problems remain: - there are very few voices in ACD caring about real world Ethereum usage - there is nobody doing Ethereum BD (everyone else who is doing this also has their own separate interests)
English
You mean how to make an account to be fully PQ without deployment, right? I think this needs a change on default code behavior of 8141; adding PQ sig verification support on the flow.
But not sure it's a right approach, since basically the end goal of EIP-8141 seems to be removing the signature / tx types out of the protocol. Changing protocol at every time we need a new signature scheme does not fit for the flexibility of EIP-8141 - if so we can just take Tempo tx approach I guess.
English
Ty for sharing this experimental PoC!!
Qq:
In the case of “Pattern 3: P-256 (Passkey) Signing,” the account is still attached to an EOA, so it’s not really a PQ solution. Is there any case where the account can be fully P256 without deployment?
Since you already solved VERIFY by calling the precompile directly.
WDYT?
English
smstack.eth retweetledi
Mirae Asset, 'Korean BlackRock' managing around $1T assets in Korea, published a report whose title is 'This year belongs to Ethereum'.
And there's a very interesting pharagraph...
"The institutional gold standard is the Stage 2 Rollup. Within the six-tier risk matrix, only Stage 2 Rollups meet the minimum trust requirements necessary for institutional capital. And because Stage 2 Rollups inherit 100% of Ethereum L1’s security, institutional capital will inevitably flow into the Ethereum ecosystem."
Long live Stage 2 L2s
securities.miraeasset.com/bbs/download/2…
English