注册并分享邀请链接,可获得视频播放与邀请奖励。

与「ISA」相关的搜索结果

ISA 贴吧
一个关键词就是一个贴吧,路径全站唯一。
创建贴吧
用户
未找到
包含 ISA 的内容
NFC Players of the Week! (Week 2) @brockpurdy13 | @DevinLloyd_ | @rodgers_isaiah
0
152
7.9K
725
转发到社区
We are so excited to welcome our grandparents and special friends to Isaac Lane!
A note on recursive STARK mempools (EIP-8288) 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 ( ) "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.
显示更多
Wow, TIL that the reason the chess queen is powerful was because when chess reached Spain in the 15th century, Queen Isabella I changed the rules on how the queen moved (previously it was highly restricted) and the new version was called "Mad Queen Chess" - which proved to be so popular (it made the game much more dynamic and exciting) that it became the dominant ruleset.
显示更多
0
21
1.1K
52
转发到社区
It's Over. We just left the Federal Courthouse in Tampa. The California man who threatened the lives of my wife, my 4 children, and myself in explicit detail was just sentenced after pleading guilty: 11 months in federal prison. 2 years probation. Restraining order. Kate and I delivered victim statements to the court. The Judge did a profound job of reasoning through the sentencing and explaining the weight of rising political violence and its effect on our Constitutional freedoms. The Judge wanted this case to be a deterrence for others who would terrorize a family. That is why we’re sharing this today... George Isabell sent a letter to my house a week after Charlie was murdered, threatening to blow my head off in front of my family. This letter, compounded with a multitude of other physical threats at our doorstep had my wife terrified. Our kids were scared. We had to hire security. New cameras. Gates. We had police outside our house for months. My kids were forced to shelter inside out of fear for their safety. This is terrorism. This type of evil has no place in any civil society. Having a different opinion shouldn't put a target on your back. We thank the judge for ruling in favor of our God-given liberties. We thank you deeply for all the prayers and messages you've sent in support of our family. As a Christian, I encourage you all not to harbor hate. Choose forgiveness. We forgive this man. And we leave justice in the hands of righteous men to wield for the terror of evil men. "For the one in authority is God’s servant for your good. But if you do wrong, be afraid, for rulers do not bear the sword for no reason." -- Romans 13
显示更多
0
1.5K
39.2K
5.4K
转发到社区
@isadora288881 这大哥想让你喝醉,然后你就乖乖听话了