Vitalik Buterin proposes a new way to handle Ethereum cryptography

cryptonews16:39

Ethereum co-founder Vitalik Buterin has backed EIP-8288 as a proposed way to support complex cryptography without repeatedly adding new verification functions to Ethereum, arguing that most heavy ...

Source Link

Disclaimer: Investing carries risk. This is not financial advice. The above content should not be regarded as an offer, recommendation, or solicitation on acquiring or disposing of any financial products, any associated discussions, comments, or posts by author or other users should not be considered as such either. It is solely for general information purpose only, which does not consider your own investment objectives, financial situations or needs. TTM assumes no responsibility or warranty for the accuracy and completeness of the information, investors should do their own research and may seek professional advice before investing.

Comments

We need your insight to fill this gap

Leave a comment

{"i18n":{"language":"en_US"},"isChannel":false,"data":{"share":"https://ttm.financial/m/news/2676501938?lang=en_US&edition=fundamental","thumbnail":"","is_english":true,"pubTime":"2026-10-19 16:39","share_image_url":"https://static.laohu8.com/e9f99090a1c2ed51c021029395664489","id":"2676501938","market":"other","top_or_hot":-1,"title":"Vitalik Buterin proposes a new way to handle Ethereum cryptography","media":"cryptonews","content":"<div>\n<p>Ethereum co-founder Vitalik Buterin has backed EIP-8288 as a proposed way to support complex cryptography without repeatedly adding new verification functions to Ethereum, arguing that most heavy ...</p>\n\n<a href=\"https://crypto.news/vitalik-buterin-ethereum-eip-8288-cryptography/\">Source Link</a>\n\n</div>\n","source":"crypto_news_highlight","html":"<!DOCTYPE html>\n<html>\n<head>\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\" />\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1.0,minimum-scale=1.0,maximum-scale=1.0,user-scalable=no\"/>\n<meta name=\"format-detection\" content=\"telephone=no,email=no,address=no\" />\n<title>Vitalik Buterin proposes a new way to handle Ethereum cryptography</title>\n<style type=\"text/css\">\na,abbr,acronym,address,applet,article,aside,audio,b,big,blockquote,body,canvas,caption,center,cite,code,dd,del,details,dfn,div,dl,dt,\nem,embed,fieldset,figcaption,figure,footer,form,h1,h2,h3,h4,h5,h6,header,hgroup,html,i,iframe,img,ins,kbd,label,legend,li,mark,menu,nav,\nobject,ol,output,p,pre,q,ruby,s,samp,section,small,span,strike,strong,sub,summary,sup,table,tbody,td,tfoot,th,thead,time,tr,tt,u,ul,var,video{ font:inherit;margin:0;padding:0;vertical-align:baseline;border:0 }\nbody{ font-size:16px; line-height:1.5; color:#999; background:transparent; }\n.wrapper{ overflow:hidden;word-break:break-all;padding:10px; }\nh1,h2{ font-weight:normal; line-height:1.35; margin-bottom:.6em; }\nh3,h4,h5,h6{ line-height:1.35; margin-bottom:1em; }\nh1{ font-size:24px; }\nh2{ font-size:20px; }\nh3{ font-size:18px; }\nh4{ font-size:16px; }\nh5{ font-size:14px; }\nh6{ font-size:12px; }\np,ul,ol,blockquote,dl,table{ margin:1.2em 0; }\nul,ol{ margin-left:2em; }\nul{ list-style:disc; }\nol{ list-style:decimal; }\nli,li p{ margin:10px 0;}\nimg{ max-width:100%;display:block;margin:0 auto 1em; }\nblockquote{ color:#B5B2B1; border-left:3px solid #aaa; padding:1em; }\nstrong,b{font-weight:bold;}\nem,i{font-style:italic;}\ntable{ width:100%;border-collapse:collapse;border-spacing:1px;margin:1em 0;font-size:.9em; }\nth,td{ padding:5px;text-align:left;border:1px solid #aaa; }\nth{ font-weight:bold;background:#5d5d5d; }\n.symbol-link{font-weight:bold;}\n/* header{ border-bottom:1px solid #494756; } */\n.title{ margin:0 0 8px;line-height:1.3;color:#ddd; }\n.meta {color:#5e5c6d;font-size:13px;margin:0 0 .5em; }\na{text-decoration:none; color:#2a4b87;}\n.meta .head { display: inline-block; overflow: hidden}\n.head .h-thumb { width: 30px; height: 30px; margin: 0; padding: 0; border-radius: 50%; float: left;}\n.head .h-content { margin: 0; padding: 0 0 0 9px; float: left;}\n.head .h-name {font-size: 13px; color: #eee; margin: 0;}\n.head .h-time {font-size: 11px; color: #7E829C; margin: 0;line-height: 11px;}\n.small {font-size: 12.5px; display: inline-block; transform: scale(0.9); -webkit-transform: scale(0.9); transform-origin: left; -webkit-transform-origin: left;}\n.smaller {font-size: 12.5px; display: inline-block; transform: scale(0.8); -webkit-transform: scale(0.8); transform-origin: left; -webkit-transform-origin: left;}\n.bt-text {font-size: 12px;margin: 1.5em 0 0 0}\n.bt-text p {margin: 0}\n</style>\n</head>\n<body>\n<div class=\"wrapper\">\n<header>\n<h2 class=\"title\">\nVitalik Buterin proposes a new way to handle Ethereum cryptography\n</h2>\n\n<h4 class=\"meta\">\n\n\n2026-10-19 16:39 GMT+8&nbsp;&nbsp;&nbsp;<a href=https://crypto.news/vitalik-buterin-ethereum-eip-8288-cryptography/><strong>cryptonews</strong></a>\n\n\n</h4>\n\n</header>\n<article>\n<div>\n<p>Ethereum co-founder Vitalik Buterin has backed EIP-8288 as a proposed way to support complex cryptography without repeatedly adding new verification functions to Ethereum, arguing that most heavy ...</p>\n\n<a href=\"https://crypto.news/vitalik-buterin-ethereum-eip-8288-cryptography/\">Source Link</a>\n\n</div>\n\n\n</article>\n</div>\n</body>\n</html>\n","isBrief":false,"type":0,"news_type":1,"symbol":"BETH","symbol_name":"比特币&以太币期货ETF-ProShares","start_time":0,"source_url":"https://crypto.news/vitalik-buterin-ethereum-eip-8288-cryptography/","article_id":"2676501938","we_media_id":null,"thumbnails":[],"rights":{"source":"crypto_news_highlight","url":"https://crypto.news/vitalik-buterin-ethereum-eip-8288-cryptography/","rn_cache_url":null,"directOrigin":true},"url":"https://stock-news.laohu8.com/highlight/detail?id=2676501938","pubTimestamp":1792399189,"columns":[],"sourceInfo":{"source_id":"crypto_news_highlight","name":"Crypto News"},"weMediaInfo":null,"summary":"Ethereum co-founder Vitalik Buterin has backed EIP-8288 as a proposed way to support complex cryptography without repeatedly adding new verification functions to Ethereum, arguing that most heavy cryptographic work should happen outside the network’s main execution process.Vitalik Buterin wants Ethereum to verify complex cryptography through aggregated proofs instead of repeated protocol upgrades.EIP-8288 proposes combining cryptographic signatures and STARK proofs before Ethereum validators verify their collective validity efficiently.The proposal could support quantum-resistant wallet signatures without requiring separate Ethereum precompiles for every signature type.Ethereum developers have not approved EIP-8288, which remains a draft requiring further implementation and network consensus.The proposal, EIP-8288, would allow Ethereum to verify that cryptographic operations were performed correctly without including every original signature or proof in a block.In the October 19 discus","collect":0,"end_time":0,"defaultTopTitle":"crypto.news","property":[],"viewcount":null,"language":"en","relate_stocks":{"BETH":"比特币&以太币期货ETF-ProShares","09009":"博时以太币-U","STCE":"Schwab Crypto Thematic ETF","BTCZ":"T-Rex 2X Inverse Bitcoin Daily Target ETF","ETTY":"Amplify Ethereum 3% Monthly Option Income Etf","XBTY":"GraniteShares YieldBOOST Bitcoin ETF","ETHT":"ProShares Ultra Ether ETF","ETU":"T-Rex 2X Long Ether Daily Target ETF","CETH":"以太坊ETF-21Shares","BEGS":"RAREVIEW 2X BULL CRYPTOCURRENCY & PRECIOUS METALS ETF","BTC":"Grayscale Bitcoin Mini Trust","QETH":"以太坊ETF-Invesco Galaxy","ETHU":"2倍以太币期货ETF-Volatility Shares","CBOO":"Calamos Bitcoin Structured Alt Protection ETF - October","ETQ":"T-Rex 2X Inverse Ether Daily Target ETF","BPI":"Grayscale Bitcoin Premium Income ETF","BITQ":"Bitwise Crypto Industry Innovators ETF","ETHV":"以太坊ETF-VanEck","ETH":"低成本以太坊ETF-Grayscale","SETH":"1倍做空以太币期货ETF-Proshares","ETHW":"以太坊ETF-Bitwise","BTF":"比特币&以太币期货ETF-CoinShares","09179":"嘉实以太币-U","GDLC":"Grayscale CoinDesk Crypto 5 ETF","03179":"嘉实以太币","ETHA":"以太坊ETF-iShares","FETH":"以太币ETF-Fidelity","BKCH":"AdvisorShares Sabretooth ETF","AETH":"以太坊策略ETF-Bitwise","IBIT":"比特币ETF-iShares","BITW":"Bitwise 10 Crypto Index ETF","ARKY":"ARK Active Autocallable Income ETF","YETH":"Roundhill Ether Covered Call Strategy ETF","ETHD":"ProShares UltraShort Ether ETF","09046":"华夏以太币-U","EZET":"以太坊ETF-Franklin","ETHE":"最大以太坊ETF-Grayscale","03046":"华夏以太币","LFGY":"YieldMax Crypto Industry and Tech Portfolio Option Income ETF","03009":"博时以太币","ETHI":"Defiance Leveraged Long Income Ethereum ETF","EETH":"以太币期货ETF-ProShares","CRPT":"First Trust SkyBridge Crypto Industry and Digital Economy ETF","CBTO":"Calamos Bitcoin 80 Series Structured Alt Protection ETF - October","BETE":"等权重比特币&以太币期货ETF-ProShares","BFJL":"FT Vest Bitcoin Strategy Floor15 ETF - July","ETCO":"Grayscale Ethereum HIGH Income ETF"},"translate_title":"Vitalik Buterin提出了一种处理以太币密码学的新方法","themeId":null,"isJumpTheme":false,"ttsUrl":null,"symbols_score_info":{"IBIT":0.6,"BEGS":1.5,"BTC":0.6,"BKCH":1.5,"ETHA":1.5,"ETHE":1.5,"ETHW":1.5,"ETU":1.5,"ETHI":0.6,"09009":1.5,"BTF":1.5,"CETH":1.5,"ETQ":0.6,"STCE":1.5,"BTCZ":0.6,"XBTY":0.6,"BFJL":0.6,"EZET":1.5,"BETE":1.5,"BPI":0.6,"ARKY":1.5,"09179":1.5,"BITW":1.5,"AETH":1.5,"03046":0.9,"CBOO":0.6,"GDLC":1.5,"BITQ":1.5,"QETH":1.5,"YETH":1.5,"03009":0.9,"EETH":1.5,"ETTY":1.5,"ETH":1.5,"SETH":0.6,"CRPT":1.5,"ETHU":1.5,"ETHT":1.5,"LFGY":1.5,"BETH":1.5,"CBTO":0.6,"ETHD":1.5,"09046":1.5,"ETCO":0.6,"METHmain":1.5,"03179":0.9,"ETHV":1.5,"FETH":1.5},"content_text":"Ethereum co-founder Vitalik Buterin has backed EIP-8288 as a proposed way to support complex cryptography without repeatedly adding new verification functions to Ethereum, arguing that most heavy cryptographic work should happen outside the network’s main execution process.\n\n\nSummary\n\n\n\nVitalik Buterin wants Ethereum to verify complex cryptography through aggregated proofs instead of repeated protocol upgrades.\nEIP-8288 proposes combining cryptographic signatures and STARK proofs before Ethereum validators verify their collective validity efficiently.\nThe proposal could support quantum-resistant wallet signatures without requiring separate Ethereum precompiles for every signature type.\nEthereum developers have not approved EIP-8288, which remains a draft requiring further implementation and network consensus.\nThe proposed system would keep large proofs outside block data while retaining transaction commitments for verification.\n\n\n\nIn a series of October 19 posts on X, Buterin argued that Ethereum’s existing virtual machine and specialized cryptographic functions are unsuitable for supporting every new signature or proof system. He instead favored a design that would let users generate proofs locally and submit them through an aggregation mechanism.\nThe proposal, EIP-8288, would allow Ethereum to verify that cryptographic operations were performed correctly without including every original signature or proof in a block.\nVitalik Buterin described this approach as part of his vision for Ethereum as a cryptographic world computer, where substantial computation can happen outside the blockchain while its results remain verifiable.\nThe specification remains a draft and has not received approval for deployment on Ethereum mainnet.\nVitalik Buterin wants less cryptographic work inside Ethereum\nVitalik Buterin’s latest comments focus on how Ethereum handles cryptographic operations that require large amounts of computation or data.\nCurrently, developers can use the Ethereum Virtual Machine, or EVM, to run smart contracts that verify certain cryptographic statements.\nEthereum provides precompiles, which are built-in functions that perform specific calculations more efficiently than ordinary smart contract code.\nThese functions can help developers verify signatures, hashes and zero-knowledge proofs.\nHowever, supporting additional cryptographic methods directly through precompiles can require changes to Ethereum’s protocol.\nVitalik Buterin argued that neither approach should become the default solution for every new cryptographic system.\nHis concern centers on the amount of data that must be included in Ethereum blocks when applications submit large signatures or cryptographic proofs for verification.\nIn the October 19 discussion, he estimated that even with improvements such as PeerDAS and blocks-in-blobs, the network would face practical limits around 8 megabytes per second before additional data became difficult to handle.\n\nUltimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata.… https://t.co/kb3JfEQKpj— vitalik.eth (@VitalikButerin) October 19, 2026\n\nThe estimate represents Buterin’s assessment of future engineering constraints, not Ethereum’s currently measured transaction throughput.\nHe described Ethereum as a cryptographic world computer in which the blockchain should handle only information requiring shared execution and verification.\nThe idea is consistent with his earlier work on reducing the amount of computation that every Ethereum validator must independently perform.\nIn September, crypto.news covered his cryptographic computer vision, which described Ethereum’s proposed transition toward proof-based verification, privacy and more efficient handling of data.\nHis October comments focused on a specific proposal for making that approach work across different cryptographic systems.\nEIP-8288 would combine proofs before they reach Ethereum\nThe proposed mechanism is described in EIP-8288, titled In-mempool signature and proof aggregation.\nButerin and Ethereum researcher Thomas Coratger created the proposal on June 3, 2026.\nAccording to the official specification, the system would let transactions declare which cryptographic statements must be verified without including all of the original proof material in the final block.\nThose declarations would identify the verification scheme, a hash representing the relevant data and a hash associated with the verification key.\nThe network would use these references to connect transactions with evidence that the required operations were performed correctly.\nUsers would generate signatures or cryptographic proofs outside Ethereum’s main execution environment.\nThe proposal allows these proofs to be combined recursively, meaning one proof can establish the validity of several smaller proofs.\nInstead of individually verifying every original signature and STARK, Ethereum would verify an aggregated proof covering the relevant transaction dependencies.\nA STARK is a cryptographic proof that allows someone to demonstrate that a computation was performed correctly without requiring every verifier to repeat the entire calculation.\nThe proposed aggregation system would use Lean Ethereum tooling to generate and verify these proofs.\nEIP-8288 describes a new transaction frame mode that would declare cryptographic dependencies. The proposal builds on EIP-8141, which introduces a framework for transactions with multiple execution and verification steps.\nAt the block level, a recursive STARK would demonstrate that the declared dependencies had been satisfied.\nThe system would continue recording necessary transaction information and cryptographic commitments on Ethereum.\nHowever, its intended design would avoid publishing the original large signatures and proofs as ordinary transaction calldata.\nThe proposal is not a plan to remove all transaction data from the blockchain or allow applications to operate without verifiable records.\nQuantum-resistant signatures are a major part of the proposal\nEIP-8288 includes support for cryptographic signatures designed to resist attacks from future quantum computers.\nEthereum currently relies on established digital signature systems for account authentication and blockchain consensus.\nDevelopers are researching alternatives that would remain secure if sufficiently powerful quantum computers become available.\nSome proposed quantum-resistant signatures are much larger than the signatures used in conventional Ethereum transactions.\nAccording to EIP-8288, hash-based signatures under consideration can require roughly 2–3 kilobytes and an estimated 150,000–200,000 gas to verify directly.\nLattice-based signatures present comparable challenges in the proposal’s cost discussion.\nSTARK proofs can require more than 128 kilobytes, with some configurations reaching approximately 512 kilobytes when optimized for fast proof generation.\nIncluding large amounts of this material directly in transactions could create substantial data and execution costs.\nVitalik Buterin argued that users should be able to produce their preferred signatures locally and prove their validity through STARK aggregation.\nHe discussed the possibility of using lattice-based cryptography for Ethereum accounts and wallets if the relevant security assumptions were established.\nHis October 19 statement referred specifically to cryptography that might be proven secure against AI-related attacks. That condition is separate from the standard definition of resistance to quantum-computer attacks.\nEarlier reporting on Ethereum’s roadmap described how quantum resistance and privacy had become priorities for the network’s future development.\nThe roadmap includes changes to signature verification and the cryptographic systems supporting Ethereum’s consensus and data availability.\nEIP-8288 addresses part of that work by proposing a common method for verifying multiple cryptographic schemes.\nRecursive aggregation would start before block production\nThe proposed process does not depend solely on a block producer collecting every signature and generating one final proof.\nEIP-8288 describes recursive aggregation beginning in Ethereum’s mempool, where transactions wait before being included in blocks.\nUnder the design, users would submit transactions along with the cryptographic evidence required to authorize them.\nMempool participants could validate the submitted evidence, combine several proofs into one and pass the resulting package to other participants.\nThe specification describes an aggregation interval of 1,000 milliseconds for this process.\nBlock builders would then collect the relevant transactions and aggregated proofs before constructing an Ethereum block.\nA final recursive STARK would cover the dependencies associated with the transactions selected for inclusion.\nThe draft proposes technical limits intended to prevent malicious users from overwhelming the aggregation system with excessive proof requirements.\nFor example, its current parameters allow up to 16 specified signature dependencies and one STARK dependency per transaction.\nThe specification also addresses compatibility with FOCIL, a proposed transaction-inclusion mechanism designed to make censorship more difficult.\nAn Ethereum analysis of proof-based verification published in September examined the distinction between verifying a computation’s result and ensuring the underlying data remains accessible.\nEIP-8288 addresses cryptographic verification while retaining the transaction information needed to identify and validate dependencies.\nIts design introduces additional work for mempool participants and block builders, which would need to generate, update and combine proofs. The proposal’s security section identifies the correctness of the proof circuits, hashing functions and recursive verification as assumptions that require careful evaluation.\nEIP-8288 remains a draft requiring network approval\nThe official Ethereum Improvement Proposal repository classifies EIP-8288 as a draft standards-track proposal in the core category.\nIts implementation would alter Ethereum’s consensus rules because blocks containing the proposed recursive proof format would not be understood by nodes running software without the update.\nThe specification identifies EIP-2718 and EIP-8141 as dependencies. Several implementation details remain incomplete, including parameters associated with the aggregated verification key and dependency hashing.\nThe proposal’s reference implementation is listed as forthcoming. Ethereum developers would need to complete technical work, review the security assumptions and agree on network activation before the design could be deployed. The repository does not currently list an approved mainnet activation date for EIP-8288.\nThe proposal’s existing test cases cover individual signature verification, multiple proof dependencies, invalid recursive proofs, mempool aggregation and compatibility with transaction inclusion lists.\nIts backward-compatibility section states that ordinary transactions without the new cryptographic verification frames would retain their existing behavior.\nNodes that do not implement the new rules would reject transactions using the proposed frame mode and blocks carrying the recursive proof header.\nThe proposal therefore requires a coordinated network upgrade before its cryptographic aggregation system can become part of Ethereum’s mainnet rules.\n\n\n\n\n\n                Read more:\n            \n\n                Ripple’s David Schwdartz sees retail DeFi opportunities on XRP Ledger","kind":"highlight","is_publish_news":true,"is_publish_highlight":false,"is_publish_live":false,"is_publish_wemedia":false,"editions":null,"column":"","sentiment":"0","news_tag":"","news_rank":0,"isVideo":false,"video":null,"symbols":[],"gpt_button":0,"need_auth":false,"need_login_tip":false,"code":"91000000","status":"200"},"commentList":[],"isCommentEnd":true,"newsSizeData":{"likeSize":0,"commentSize":0,"repostSize":0,"favoriteSize":0,"likeStatus":false,"favoriteStatus":false},"APP":{"userAgent":"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)","isDev":false,"isTTM":true,"isLaohu8Offline":false,"tenantId":"TBGLOBAL","deviceId":"web-server-community-laohu8-v3","version":"4.50.1","shortVersion":"4.50.1","platform":"web","vendor":"web","appName":"ttm","isIOS":false,"isAndroid":false,"isTiger":false,"isTHS":false,"isWeiXin":false,"isWeiXinMini":false,"isWeiBo":false,"isQQ":false,"isBaiduSwan":false,"isBaiduBox":false,"isDingTalk":false,"isToutiao":false,"isOnePlus":false,"isHuaWei":false,"isXiaomi":false,"isXiaomiWebView":false,"isOppo":false,"isVivo":false,"isSamsung":false,"isMobile":false},"href":"/m/news/2676501938","isCrawlerRequest":true}