Blog

The year 2024 represented a key milestone for the crypto industry. With the SEC’s approval of Bitcoin and Ethereum spot ETFs, cryptocurrencies took significant steps toward mainstream adoption. In parallel, the scope and value of tokens continued to evolve. To meet user needs, imToken focused on token-centric innovation, designing products, services, and systems to deliver a more seamless and user-friendly token experience.  

Cap3 of Babylon Bitcoin staking mainnet Phase-1 is launching soon! Stake with imToken to secure a guaranteed reward of 100 USDC and earn up to 800 USDC — first come, first served. The more you stake, the greater the rewards! ⏰ Time:  Starting on Dec 10 2024 at 7:20pm (UTC+8) and lasting for 1,000 BTC blocks (roughly a week)🏆 Total Prize Pool: 17,500 USDC (provided by Babylon) Rules 1️⃣ Participation Rewards  Stake 0.005 BTC to qualify for rewards! The first 100 users to successfully complete staking through imToken and comment with a screenshot of your staking under this tweet will each receive 100 USDC. Participants who stake successfully will also earn Babylon points. 2️⃣ The More You Stake, The More You Earn During Cap3, the top 10 users with the highest BTC stakes (with at least 0.1 BTC in accumulated staking amount) will each receive an additional 700 USDC. (Note: Rewards from 1️⃣ and 2️⃣ can be combined.) 3️⃣ X Rewards Like and retweet this tweet https://twitter.com/imTokenOfficial/status/1866320741039550621 25 lucky users will be randomly selected to win 10 USDC each! FAQs 1. How to participate in the event with imToken? Switch to a BTC account starting with bc1p or bc1q in imToken. Open the Babylon DApp from the browser tab, connect your wallet, select a finality provider (validator), enter the staking amount, and confirm to complete the staking process. Once staking is successful, you can check your record in Stake history. Tutorial 👉 https://support.token.im/hc/en-us/articles/36702982047257 2. How will rewards be distributed? After successfully staking, please fill out the form to provide your reward address 👉 https://forms.gle/PQvzVT1vv2Av1oGs8 Rewards will be distributed on the Arbitrum network within 7 business days after the event ends. 3. How to confirm eligibility for rewards? Staking rewards will be calculated and announced after staking is completed. Users can follow imToken X for updates. For further questions, join the imToken Discord to contact us. 4. Important Notes Rewards apply only to staking completed during the event period; pre-event staking is not eligible. Users must complete staking through the imToken wallet to qualify for rewards. In Phase-1, staked Bitcoin has a lock-up period of a maximum of approximately 15 months. Early unlocking requires a wait of about 7 days before withdrawal. For more details, visit the Babylon website.   imToken Team December 10, 2024

Since launching the new account management in imToken 2.15, we have enhanced efficiency and convenience by expanding account types and features. imToken 2.16.1 adds support for Dogecoin and Osmosis accounts, improves account activity, and introduces a new "Token" button for easy access to token features. This update is as follows👇👇👇 🎉Support for Dogecoin and Osmosis accounts 📝Enhanced account activity for quick access to on-chain activities 💰New "Token Function" button for one-click exploration of token features 🛡️Improved risk control system to ensure token security Other Updates- Optimized token management features- Added native staking information to token detail pages 🥳Gas-Free Transfers on BSC - Limited Time Offer Support for Dogecoin and Osmosis Accounts imToken 2.16.1 adds support for Dogecoin and Osmosis accounts. To add an account, simply go to the "Manage wallets" page, click "Add," and select Dogecoin or Osmosis from the list. For bulk account addition, click the three dots in the upper right corner of the account and select "Advanced." As a key part of the Cosmos ecosystem, Osmosis serves as an on-chain liquidity hub via the IBC protocol. With IBC support and Cosmos Kit integration, imToken enables seamless transfers between Cosmos and Osmosis, paving the way for future support of more Cosmos applications and DApps, including the upcoming Babylon Chain. imToken is dedicated to enhancing support for the Cosmos ecosystem by continuously expanding cross-chain interaction and token management capabilities to improve your overall experience. 🔺Steps to add a Dogecoin account Enhanced Account Activity for Quick Access to On-Chain Activities The latest version of imToken optimizes account activity. Simply click "Activity" to quickly access your account activity page and view transaction details. It allows users to easily see key information like transaction type, time, amount, and status, enhancing token management efficiency. Additionally, clicking on any transaction takes you to the transaction details page, where you can view information such as the network and gas fees, and you can also directly navigate to a blockchain explorer for more on-chain data. 🔺Steps to view Polygon account activity New "Token Function" Button for One-Click Exploration of Token Features imToken introduces the "Token Function" button for easy access to token features like buying and trading. Users can also access various DApps directly through this button. Simply click on any token in your account, find the "Token Function" button, and select your desired action for efficient management. Note: The "Token Function" button is not yet available for Ethereum, Arbitrum, and EOS accounts, but support will be added soon. 🔺Steps to use the “Token Function” button Improved Risk Control System to Ensure Token Security imToken 2.16.1 introduces risk address indicators on the activity and transaction details pages, making it easy to identify potentially risky transactions. This enhancement keeps users informed about transaction security and helps reduce token loss. Risk addresses entered during a transaction will be highlighted in red with a warning message, and even completed transactions will show the risk indicator in the records. Other Updates Optimized token management features imToken upgrades token management for Tron, Cosmos, Layer 2, and EVM accounts. Simply click “+” on the wallet page to quickly add tokens by name or contract address. You can view all tokens, adjust the display order, or remove unwanted tokens. EVM accounts also support custom token management for added flexibility. Added native staking information to token details pages The token details pages for ATOM, KSM, DOT, CKB, and others now feature native staking information. For example, ATOM holders can view their balance, staking status, and rewards by clicking "ATOM." Note: Native staking requires users to lock their tokens for a specific period, during which they cannot use these tokens. Gas-Free Transfers on BSC – Limited Time Offer imToken 2.16.1 supports gas-free transfers on the BNB Smart Chain network. From now until January 5, 2025, 11:00 PM (UTC+8), imToken users can enjoy free transfers of stablecoins (FDUSD, USDT, USDC) via their BSC accounts. Each user can make up to 2 free transfers per day for each stablecoin, with a minimum transfer amount of $0.1. Click here for more details. How to Update  Android users: You can download from the official website https://token.im or your favorite App Store (Google Play). iOS users: You can download from the App Store. If you encounter any problem during the process, you can email the subject "Download" to [email protected] to get the latest version of the imToken App. Always Backup Your Keys Before upgrading, please ensure you backup all your wallet identities properly. Write your mnemonic phrase on a piece of metal or paper, and store it in a safe place. Please refrain from sharing your private key, mnemonic phrase, or keystore with anyone! If you find potential hacking activities in imToken, kindly email us at [email protected] to prevent more people from being deceived. Finally, remember to visit our Help Center at https://support.token.im/hc/en-us for more detailed information about imToken. Download imToken: Google Play | Apple App Store Follow us: Twitter | Support | token.im

imToken unveils imToken Web, offering a seamless Web3 experience at the Web3 Coffee Carnival during Devcon 7. This initiative aims to integrate crypto into daily life, bridging the gap between blockchain technology and real-world use. Since the start of 2024, the Ethereum community has become increasingly aware that, while the underlying infrastructure is well-developed and a variety of rollup solutions are emerging to tackle the scalability issue, there remains a shortage of practical, consumer-facing applications. At EDCON 2024, Vitalik stated that while Ethereum focused on theory over the past decade, the focus for the next decade would shift toward building impactful, real-world applications. With the regulatory environment expected to improve, the ecosystem now needs to prioritize creating consumer applications that bridge the gap between Web3 and Web2, from liquidity integration to the development of new use cases. At Devcon 7, the community's growing sense of momentum and creativity around consumer applications is evident. So, what would a better user experience look like? Our answer is “Token-centric design” and here’s why: Tokens carry both information and value across the network. They embody the intrinsic value of blockchain utilities as well as digital assets. It’s intuitive to think—and true—that the most direct interactions, as well as the most direct value extraction, occur through tokens. Ethereum ushered in the era of smart contracts, transforming traditional tokens into dynamic, programmable assets. These tokens now go beyond simple value transfer and storage, becoming a novel type of data that evolves continuously, offering possibilities that extend well beyond the realm of text, images, and multimedia. Given their complex and dynamic nature, there is a need for precise, real-time information to detail their states and values—information that is best connected and displayed directly from the token's perspective. As tokens emerge as a new and effective means of storing, transferring, and growing value, it's essential to clearly articulate information about the token itself and the outcomes it can generate. imToken refers to this as "Token Function," which essentially defines what a token can do and the specific outcomes it delivers. This concept promotes an intent-based approach and makes token-centric design a logical evolution for navigating the complex, multi-chain, multi-state nature of tokens. Currently, accessing Web3 often means downloading and creating a wallet, which can be a barrier for newcomers. With imToken's token-centric approach, users start with tokens, seamlessly create accounts using AA (Account Abstraction) technology, and continue interacting with, managing, and operating tokens throughout the journey. A New Frontier: imToken Web Start your token journey! Explore tokens at imToken Web (https://web.token.im) and experience our new token-centric design. Note: imToken Web is currently in beta, offering users a preview of the token-centric experience. As the product is still undergoing rapid iteration, it may contain bugs or vulnerabilities. Please use with caution. imToken welcomes your feedback as we collectively explore the future of tokens.

imToken Web Beta is Now Live! Try it out here 👉https://web.token.im. In 2024, fifteen years after Bitcoin’s inception, the crypto landscape exploded, with tens of thousands of tokens now in circulation. While some may fade away, imToken believes the true era of tokenization is just beginning. Tokens are becoming as essential as money, electricity, and the internet, seamlessly integrating into daily life. imToken is building a streamlined, accessible platform to bring clarity to the world of tokens—empowering users with essential information and seamless access to the token economy anytime, anywhere. Our vision is a world where everyone, regardless of age or region, can easily participate in the token economy and enjoy its freedom and convenience. What is imToken Web? imToken Web is a non-custodial, web-based app designed for easy token exploration, featuring quick account creation and passkey sign-in. Enjoy full control without needing a private key or mnemonic backup, allowing seamless access to diverse token functions anytime, directly from your browser. Key Features: No Download Required: Unlike traditional token management apps, imToken Web operates directly in your browser—no downloads or complex sign-ups required—ensuring a streamlined user experience. AA Account Support: imToken Web allows the creation and recovery of AA (Account Abstraction) accounts, combining the benefits of EOA and smart contract accounts, and eliminating the need for seed phrase backups. Passkey-Based Account Creation: Set up accounts with locally stored passkeys, protected by biometrics, enhancing security against phishing and other common attacks. Paymaster Contract Support: With imToken Paymaster, pay gas fees using alternative tokens, like ERC-20 tokens, instead of the chain’s native token. Comprehensive Token Exploration: The token discovery page lets you explore token prices, security info, and more without needing to hold any tokens. Click on any token to view details, transfer, receive, and exchange with ease. imToken Web Beta version includes essential functions like explore, claim, send, receive, swap, plus Paymaster and account recovery, with more features coming soon. How to Use imToken Web Open browser and visit https://web.token.im Create or log in with a passkey (currently supporting Arbitrum and Optimism networks) Once your account is set up, click on any token to view details and perform actions like transfer, receive, and exchange If you’d like to explore more token features, go to the homepage through the menu bar to view various token categories, access detailed information, and click on "Token Function" for additional actions. Devcon7 & imToken Web Devcon7 is happening in Bangkok, Thailand from November 12 to 15, 2024! 🎉 imToken hosts a series of exciting events throughout the week. Join us at Web3 Coffee Carnival to experience imToken Web, claim free tokens, and enter our lucky draw! You can also click here to participate in the online event and win rewards. Discover more details here: 📢imToken Devcon7 Event Announcement Note: imToken Web is currently in beta, offering users an early experience of this token-centric platform. As the product is still evolving, it may contain bugs or vulnerabilities. Please use with caution, and we welcome any feedback. Thank you for your support!

Devcon 7 is coming to Bangkok from November 12-15, 2024! imToken is thrilled to be part of the Devcon 7 Supporter Program, contributing to the Ethereum ecosystem. Join us for a series of exciting events—see you in Bangkok! #1 Web3 Coffee Carnival ​​📅 Date: November 11-15, 2024​​📍 Location: QSNCC MRT Station (near Exit 3 on Metro Mall Floor)🔗 Get Your Ticket: https://lu.ma/ef7fdt5p Web3 Coffee is a special space created by imToken during Devcon7, running for five days. imToken will team up with 11 partners, including imKey, Umy, LI.FI, Tokenlon, HashKey, Fiat24, Taiko, Orbiter, Feee.io, Bifrost, and CKB, to deliver an unforgettable experience! At Web3 Coffee, we’ll unveil our new product, imToken Web, where you can claim free tokens and enjoy crypto-fueled coffee. From November 11-15, different projects will offer benefits each day. Experience imToken’s new product on-site to receive up to $100 in newcomer gifts and a chance to win exciting prizes in our gacha game, with a 100% win rate on items like hardware wallets and thermoses! #2 Preconfirm the Next Gen Ethereum UX ​​📅 Date & Time: 14th November, 4:00 - 9:00 PM​​📍 Location: So Asean, FYI, Khlong Toei, Bangkok🔗 Get Your Ticket: https://lu.ma/p1v3zyp7 🚀 Unlock the Future of Ethereum Transactions with Pre-Confirmation at Devcon 7! Join founders & devs from imToken, Luban, Taiko, Nethermind, Primev, Commit-Boost, Tokenlon, Rabby Wallet, Soul Wallet, CoW Swap, Blocknative as we dive into how preconfirmation is transforming resource allocation & user experience on Ethereum. Highlights🔹 Networking with thought leaders🔹 Transaction pre-confirmation & MEV strategies🔹 Insights into base-layer rollup platforms & their impact Don’t miss this unique opportunity to shape the future of Ethereum transactions and stay at the forefront of innovation! #3 Retweet to Win Free Coffee! 📅 Pre-Event: November 7, 2024, 3:00 PM - November 9, 2024, 11:00 PM (UTC+7) How to Participate: Retweet our event tweet for a chance to be one of 20 winners to receive Web3 coffee! Comment "I want free coffee" for a chance to get a cup of crypto-fueled coffee or try the gacha machine, with prizes worth up to $100!Location: Web3 Coffee, QSNCC Station (near Exit 3), Bangkok, Thailand 📅 Event Period: November 11, 2024, 8:00 AM - November 15, 2024, 8:00 PM (UTC+7) Rules: The first 500 users to create an AA account on imToken Web and submit their addresses in the form will each receive 1.99 USDT. Users who are the 501st to 901st to create an AA account will each receive a .bit domain name (sponsored by .bit). After submitting the form, users will receive a system serial number. Users with serial numbers 77, 177, 377, 577, 777, 977, 1277, and 1777 will receive an additional 100 USDT. Users who complete the tasks and retweet the event tweet will be entered into a draw, with 40 winners each receiving 10 USDT. If retweets reach 2,000, the prize pool and the number of winners will double. Note: Your address will be used solely for reward distribution. Rewards will be issued within 7 business days after the event, and winners will be drawn using X's (formerly Twitter) draw tool, with announcements posted on X. 🎉 Join Us at Devcon 7 Join us at Devcon 7 as we come together with friends, old and new, both online and offline, to celebrate the Ethereum’s annual event and witness its return to the global spotlight!

imToken is turning 8! 🎉🎉🎉 From 2016 to 2024, imToken has been witnessing the ups and downs of the crypto industry alongside all of you. We express our gratitude to every user for their support and companionship, enabling us to keep moving forward. Building a Token-Centric World In 2018, imToken embraced the ethos of open source, infusing fresh energy into the crypto industry with its TokenCore code. However, as the ecosystem continues to evolve, simply patching up old code is no longer the optimal choice. We're committed to embracing innovative solutions that propel us forward in this ever-changing landscape. As the crypto industry rapidly evolves, wallet products need to meet a wider range of needs. We believe the ultimate state of an ideal wallet should be: A shield for users and their families: protecting tokens from compromise, data leaks, and identity tracking. Helping users access the tokenized world with low cost and low threshold: permissionless accounts, affordable hardware, and user-friendly interfaces. Looking ahead, we are steadfast in our belief that "a Token-Centric World" is the best way to achieve this vision. Tokens are changing the way we innovate, share, and interact, whether it's in transfers, payments, NFTs, staking, governance, or in the realms of DeFi and DID. We keenly perceive the profound impact of this paradigm shift. A New Beginning: imToken 2.15 Driven by the concept of "a Token-Centric World," we've dedicated ourselves to crafting imToken 2.15, introducing a revolutionary architecture and design. The flat account system not only enhances flexibility in accommodating diverse account types but also establishes the groundwork for token-centric product design, heralding a fresh beginning. In line with this transformative journey, we've designed a new brand centered around tokens, unveiling it to commemorate our 8th anniversary, symbolizing a pivotal milestone in our evolution. imToken 8th Anniversary More importantly, we have prepared a wealth of surprises and airdrop events, and we sincerely invite you to join us in celebrating imToken's 8th birthday! Join the 8th Anniversary Event now: https://token.im/anniversary8 imToken Team2024.05.22

The Pectra hard fork is scheduled for deployment on the mainnet in March 2025. Pectra includes 11 EIPs: EIP-2537: Precompile for BLS12–381 curve operations EIP-2935: Save historical block hashes in state EIP-6110: Supply validator deposits on chain EIP-7002: Execution layer triggerable exits EIP-7251: Increase the MAX_EFFECTIVE_BALANCE EIP-7549: Move committee index outside Attestation EIP-7623: Increase calldata cost EIP-7685: General purpose execution layer requests EIP-7691: Blob throughput increase EIP-7702: Set EOA account code EIP-7840: Add blob schedule to EL config files The following sections group related EIPs for clarity, rather than numerical order. Prerequisites Ethereum is divided into two layers: ​Consensus Layer (CL): Manages network consensus and block validation. ​Execution Layer (EL): Handles transaction execution and smart contracts. Staking-related EIPs: EIP-6110: Supply validator deposits on chain Simplifies the staking process and reduces waiting time. Users participate in staking by depositing 32 ETH into a ​Deposit Contract on the Execution Layer (EL), which is recorded via event logs. Consensus Layer (CL) nodes then parse these event logs from the EL blocks to detect and register staking activities, allowing users to become validators. However, CL validators must first reach consensus on ​which specific EL block's deposit data to parse. Without this agreement, discrepancies may arise (e.g., some validators might see 5 new deposits, while others see only 3). To resolve this, CL validators vote on ​which EL block (referred to as eth1data) to reference, ensuring all validators observe the same EL block. Original Design Constraints: To prevent chain splits caused by critical EL errors, eth1data references EL blocks that are ​~10+ hours old. This ensures CL developers have sufficient time to react to major issues. However, this introduces a ​minimum 10+ hour delay for staking activations. CL block 10,900,000 references EL block 21,683,339 (10 hours older) Post-EIP-6110 Improvements Deposit data from the Deposit Contract is ​directly embedded into EL blocks. Since CL blocks inherently include EL blocks (distinct from eth1data), CL validators no longer need to coordinate on "which EL block to reference." Once a CL block is finalized (achieving >2/3 validator votes), all validators inherently trust the ​same EL block data. Result: Staking activations occur ​around ~13 minutes (time for EL blocks to finalize). CL clients can ​remove complex logic previously used to process deposit events. EIP-7002: Execution layer triggerable exits Enhances the process for validators exiting or withdrawing stakes and rewards. When a user participates in staking, they require two keys: ​Validator Key: Used for validator duties (e.g., block proposals, attestations). ​Withdrawal Credential: Specifies the address where staked funds and rewards are sent upon exit. Current Risks: ​Lost Validator Key: Cannot perform validator duties or initiate exits. Penalties accumulate until the validator is forcibly exited (due to low balance). ​Lost Withdrawal Credential: Permanent loss of all staked funds and rewards. ​Third-Party Staking Services (e.g., Lido): Users retain Withdrawal Credentials, but Validator Keys are controlled by the service provider. Providers can threaten users with ransom demands by withholding exit approvals. ​Post-EIP-7002 Improvements Users can now trigger exits or withdrawals directly via the ​Withdraw Contract (0x0c15F14308530b7CDB8460094BbB9cC28b9AaaAA) using their Withdrawal Credential, bypassing third-party control. Key Features: ​Parameters: validator_pubkey: The validator’s public key. amount: The withdrawal amount (partial or full exit). ​Authorization: The Withdrawal Credential must match the validator’s registered credential. ​Fee Mechanism: Transaction fees (in ETH) scale with ​the number of pending withdrawal requests currently queued in the network. ​For Contracts: Query the Withdraw Contract for real-time fee estimates before submitting requests. For EOAs: Overpay fees (no refunds) to ensure transaction success. Benefits: Eliminates reliance on third-party services for exits. Enables self-custody validators to recover funds even if the Validator Key is lost. Note: If your Withdrawal Credential is still in BLS public key format, remember to switch it to the EL address format. EIP-7251: Increase the MAX_EFFECTIVE_BALANCE Reduces validator count and enables auto-compounding by raising the staking cap. ​Current Limitations: Validators must stake ​exactly 32 ETH (the current MAX_EFFECTIVE_BALANCE). Large stakers (e.g., 1,024 ETH) must run ​32 separate validators, increasing network load. Over ​1 million validators exist today, straining the CL’s state data and P2P layer: Each slot (12 seconds) requires transmitting and aggregating ​tens of thousands of validator signatures. Post-EIP-7251 Improvements ​Lower Bound: MIN_ACTIVATION_BALANCE remains ​32 ETH. ​Upper Bound: MAX_EFFECTIVE_BALANCE increases to ​2,048 ETH. Validators can stake ​any amount between 32–2,048 ETH. Auto-Compounding: Rewards automatically compound without manual withdrawals. ​Validator Consolidation: Existing validators can merge stakes ​without exiting and re-entering. Use the ​Consolidation Contract (0x00431F263cE400f4455c2dCf564e53007Ca4bbBb): Triggered via the validator’s Withdrawal Credential. Request Parameters: source_pubkey: Validator key of the source validator (to be merged). target_pubkey: Validator key of the target validator (receiving the merged stake). Requirements: The Withdrawal Credential ​must belong to the source validator. Fee Mechanism: Transaction fees (in ETH) scale with ​the number of pending consolidation requests in the network. ​For Contracts: Query the Consolidation Contract for real-time fee estimates. ​For EOAs: Overpay fees (no refunds) to ensure transaction success. Note: BLS-formatted Withdrawal Credentials must be converted to ​Execution Layer (EL) address format. EIP-7685: General purpose execution layer requests Establishes a formal EL→CL communication channel for users and staking services. ​Purpose: Enables direct requests from the Execution Layer (EL) to the Consensus Layer (CL). Enhances decentralization for staking services (e.g., Lido): Users no longer need to trust third-party providers to execute actions like exits (EIP-7002) or consolidations (EIP-7251). Requests are initiated via ​EL smart contracts and embedded in EL blocks. ​Mechanism: Requests are written into EL blocks and parsed by CL nodes. Request Types eliminate the need for custom parsing logic on the CL. ​Integration with Other EIPs: EIP-7685 defines the framework for the following request types: Request Type EIP Contract Address Description 0 EIP-6110 0x00000000219ab540356cbb839cbe05303d7705fa Deposit Requests 1 EIP-7002 0x0c15F14308530b7CDB8460094BbB9cC28b9AaaAA Withdrawal/Exit Requests 2 EIP-7251 0x00431F263cE400f4455c2dCf564e53007Ca4bbBb Stake Consolidation Requests User experience improvement EIPs: EIP-7702: Set EOA account code Enables EOAs to morph into smart contract accounts, significantly improving user experience. ​EOA Limitations: ​Private Key Dependency: Requires secure storage of private keys/mnemonic phrases, raising onboarding barriers. ​Single-Operation Transactions: Complex interactions (e.g., Uniswap swaps) require multiple sequential transactions. ​No Granular Permissions: Users must manually sign every operation. No Recovery Mechanisms: Loss of private keys/mnemonics results in permanent asset loss. ​Smart Contract Account Advantages: ​Keyless Onboarding: Use secure hardware (e.g., TPM) or email-based authentication instead of private keys. ​Batch Operations: Execute multiple actions in a single transaction. ​Granular Permissions Control: Delegate partial account control with constraints (e.g., spending limits, allowed contracts). Recovery Options: Safeguard assets even if private keys/phones/emails are lost. ​EIP-7702  Users sign a ​morphing message with their EOA private key, containing: ​chain_id: Prevents cross-chain replay attacks. Use 0 to enable morphing across all chains. contract_address: Target contract address (e.g., Safe). Use address(0) to revert to EOA. nonce: Prevents signature replay (invalidates old signatures after nonce increments). ​Critical Considerations: ​1. EOA Private Key PersistenceEven if a user’s EOA morphs into a smart contract, they can still use their account in the original EOA manner. For example, if your EOA morphs into a Safe contract, you can: Use the Safe interface and follow Safe transaction workflows. Continue sending transactions by signing with your original EOA wallet. However, this also means the ​account’s security remains tied to the private key. The EOA’s private key is still the sole safeguard for the account, and its compromise would jeopardize the entire account, regardless of its morphed state. 2. Security Remains EOA-BasedEven if a user’s EOA morphs into a multi-signature (multi-sig) contract, ​the account’s security remains entirely dependent on the EOA’s private key. Retaining the private key or mnemonic phrase does not elevate the account’s security to that of a true multi-sig. Users must still securely manage their private keys or mnemonics, as the account’s safety fundamentally hinges on them. 3. EOA Storage PersistenceWhen an EOA morphs into a contract and writes data to its storage, ​the data persists unless explicitly deleted. This means that even if the EOA morphs into another contract or reverts to its original state, the storage data remains intact. Developers must ensure that their contracts do not inadvertently read outdated data from previous morphing cycles. For guidance, refer to ERC-7201 4. EIP-7702 Lacks Built-in Initialization Typically, smart contract accounts require an ​initialization step during deployment to register the owner’s information (e.g., public key or address). This prevents frontrunning attacks that could hijack account ownership. Initialization is usually handled by a ​Factory contract that performs both deployment and setup. However, EIP-7702 enables ​direct morphing without a Factory contract. This creates a ​frontrunning risk: attackers could intercept a user’s morphing signature, submit it first, and initialize the account under their control. To mitigate this, developers should implement safeguards, such as ​verifying the EOA’s signature during initialization. This ensures that even if the request is frontrun, the attacker cannot forge the EOA’s signature to complete the initialization. 5. Wallet Security Warnings Wallets must ​intercept and warn users about suspicious morphing requests. For example, if a malicious DApp prompts a user to sign a morphing transaction, the wallet should block the request and alert the user. If users unknowingly sign malicious morphing transactions, their assets could be ​instantly drained. ​Example Implementations ​Modified Safe ​Ithaca Account DApp related EIPs: EIP-2537: Precompiles for BLS12-381 curve operations Lowers costs for BLS-curve-based zero-knowledge proof applications. EIP-2537 introduces several precompiled contracts to provide cost-efficient BLS curve operations, making it more feasible to develop zero-knowledge proof applications based on the BLS curve. EIP-2935: Save historical block hashes in state Allows developers/nodes to read past block hashes directly from system contract storage. To prove the contents of a past block—for example, in an Optimistic Rollup fraud challenge requiring proof that a transaction existed in block 9000 (1,000 blocks prior)—a challenger cannot simply assert its existence. Instead, they must ​sequentially verify the chain backward, one block at a time, from the latest block (e.g., block 10,000) to the target block (block 9000). ​Example: Start with block 10,000’s hash. Prove block 10,000 links to its parent block 9,999. Repeat this process backward until reaching block 9,000. Finally, prove transaction X exists in block 9,000’s content. △ Every block points to a parent block, allowing proof of any block in history by following the chain backward. source Post-EIP-2935 Improvements The system contract (deployed at 0x0F792be4B0c0cb4DAE440Ef133E90C0eCD48CCCC) maintains a rolling window of the ​most recent 8,192 block hashes in its storage. Here’s how it works: ​Automatic Updates: When a new block is added (e.g., block N), the system contract overwrites the ​oldest stored hash (from block N-8192) with the hash of the ​newly added block (N). This creates a circular buffer where only the latest 8,192 block hashes are retained. ​Fraud Proof Optimization ​Case 1: Proving a Block Within 8,192 History To prove the hash of block 9,000 (1,000 blocks before block 10,000): ​Direct Reference: Since block 9,000 is within the 8,192-block window of block 10,000, its hash is stored in the system contract’s storage at the state of block 10,000. The challenger can directly reference the storage slot corresponding to block 9,000 to retrieve its hash. ​Case 2: Proving a Block Beyond 8,192 History To prove the hash of block 1,000 (9,000 blocks before block 10,000): Step 1: Find the Closest Stored Hash Calculate the oldest block hash stored at block 10,000: 10,000 - 8,192 = 1,808. The system contract at block 10,000 stores hashes from block 1,808 to block 10,000. ​Step 2: Prove Block 1,808’s Hash Verify the hash of block 1,808 using the system contract’s storage at block 10,000. Step 3: Prove Block 1,000’s Hash Since block 1,000’s hash is stored in the system contract’s storage at block 1,808. Retrieve block 1,000’s hash directly from this storage. ​Stateless Client Support This paves the way for ​stateless clients: Light nodes no longer need to store all historical block headers. When historical data is required, proofs can be requested on-demand using the fraud-proof mechanism described above. EIP-7623: Increasing calldata cost ​EIP-7623: Raising Calldata Costs to Enable Safer Increases in Block Gas Limits and Blob Capacity ​Background With the increasing demand for data publication by Rollups, ​EIP-4844 introduced blobs, enabling Rollups to publish data at significantly lower costs. Since then, the Ethereum community has advocated for ​increasing blob counts and ​raising block gas limits to accommodate higher throughput. However, these upgrades risk amplifying network strain and spam attack efficiency unless data publication costs are adjusted. △ An increasing number of validators are expressing support for raising the Block Gas Limit.  source EIP-7623 increases calldata costs by 2.5x to mitigate risks while enabling scalability improvements: ​Original Calldata Pricing: Zero byte: ​4 gas Non-zero byte: ​16 gas ​Post-EIP-7623 Pricing: Zero byte: ​10 gas Non-zero byte: ​40 gas ​Impact on Attack Efficiency: ​Pre-EIP-7623: A block filled entirely with non-zero calldata: At ​30M gas limit: 30,000,000 / 16 = 1,875,000 bytes ≈ 1.79 MB. At ​40M gas limit: 40,000,000 / 16 = 2,500,000 bytes ≈ 2.38 MB. Average block size: ~100 KB. ​Post-EIP-7623: Attackers’ maximum data capacity drops: At ​30M gas limit: 30,000,000 / 40 = 750,000 bytes ≈ 0.72 MB. At ​40M gas limit: 40,000,000 / 40 = 1,000,000 bytes ≈ 0.95 MB. This reduction in spam efficiency allows safer increases to block gas limits and blob counts. ​Dual Gas Calculation to Protect Regular Users To avoid unintended impacts on non-data-publishing users, transactions are priced using ​two parallel calculations, with the ​higher value applied: ​Legacy Calculation: Calldata priced at original rates (4 gas/zero byte, 16 gas/non-zero byte) + execution/deployment gas. ​New Calculation: Calldata priced at new rates (10 gas/zero byte, 40 gas/non-zero byte), ​excluding execution/deployment gas. ​Why Regular Users Are Unaffected: For typical transactions (e.g., token swaps), most gas is consumed by ​execution logic (e.g., contract interactions), not calldata. The new calldata costs (even at 2.5x) rarely exceed execution costs under the dual calculation, leaving regular users unaffected. The ​most affected will be ​small-scale Rollups. Since blobs have ​fixed sizes and costs, they are inefficient for small data batches, making calldata a more cost-effective option for these Rollups. However, after EIP-7623, calldata costs will increase by ​2.5x, significantly raising expenses for small Rollups. As a result, they may need to: ​Switch to blobs despite their inefficiency for small data. ​Collaborate with others to share a single blob and split the costs. EIP-7691: Blob throughput increase Increases the number of Blobs, providing more data publishing capacity for Rollups. EIP-7691 raises the Blob count from "Target: 3 Blobs, Maximum: 6 Blobs" to "Target: 6 Blobs, Maximum: 9 Blobs", expanding the available space for Rollup data publication. Note: There are still some design adjustments needed for the Blob fee market, such as improving the speed of fee adjustments and raising the minimum fee, but these issues are not within the scope of this EIP. Miscellaneous EIP EIP-7549: Move committee index outside Attestation Adjusts validator voting content for easier aggregation and reduced p2p network pressure. ​Current Mechanism: Validators are randomly assigned to ​committees each epoch and vote on blocks. Votes within the same committee can be ​aggregated, reducing the volume of data transmitted over the p2p network. However, each vote includes the ​committee index (i.e., which committee the validator belongs to), preventing aggregation of votes from ​different committees—even if they vote on the same block. ​Improvements: The ​committee index is moved outside the attestation content. Votes from different committees can now be ​aggregated if they share the same content (e.g., voting for the same block). This further reduces the volume of attestation data transmitted over the p2p network, alleviating network pressure. EIP-7840: Add blob schedule to EL config files Simplifies blob parameter access for EL nodes by creating a dedicated configuration file. ​Current Limitations: Blob-related parameters are stored in ​CL nodes. EL nodes occasionally need these parameters (e.g., for eth_feeHistory RPC calls), requiring them to query CL nodes. ​Improvements: A ​configuration file for blob-related parameters is added to the EL layer. EL nodes can now directly access these parameters from the config file, eliminating the need to query CL nodes. Related Readings: https://pectra.wtf https://x.com/binji_x/status/1874422557992263720 https://www.galaxy.com/insights/research/pectra-upgrade-and-other-eth-catalysts/ https://gaslimit.pics/ https://x.com/spire_labs/status/1881445292815597913

The Ethereum Pectra upgrade has been deployed on two testnets so far: Mekong testnet on November 7, 2024, and Holesky testnet on February 24, 2025. Additionally, the Pectra upgrade is scheduled to go live on the Sepolia testnet on March 5, 2025. These testnets provide a preview environment for optimizing transaction scalability and enhancing security ahead of the upcoming Ethereum Pectra upgrade. Notable improvements include: Rollup-centric roadmap: The Pectra upgrade aligns with Ethereum’s roadmap by further improving scalability with a rollup-centric approach. Enhanced user and developer experience: Upgrading testnets enable developers to test and explore user experience changes, familiarize themselves with the upcoming technical adjustments in the Pectra fork, and ensure a smooth transition when the Ethereum mainnet implements the Pectra upgrade. Mekong Testnet The Mekong testnet is the first testnet launched for the Pectra upgrade. It includes all the technical protocols that will be implemented in the upgrade, such as EIP-7702 (enhancing user experience), EIP-7251 (raising the staking limit from 32 ETH to 2048 ETH), and EIP-6110 / EIP-7002 (changes to deposit and withdrawal mechanisms). These features will gradually be rolled out on public testnets and the Ethereum mainnet. Pectra Upgrade FAQ: https://epf.wiki/#/wiki/pectra-faq Mekong Testnet Usage: https://mekong.ethpandaops.io Holesky Testnet On February 24, 2025, at Epoch 115,968, the Holesky testnet activated the Pectra upgrade, focusing on three key areas: EIP-7702: Enhancing functionality by enabling externally owned accounts (EOAs) to mimic smart contract accounts. EIP-7251, EIP-7002, and EIP-6110: Improving the validator user experience. EIP-7691: Increasing blob throughput, expanding the number of blobs supported per block from 3–6 to 6–9. For a detailed introduction to the Pectra upgrade, please refer to: Introduction to the Ethereum Pectra Hard Fork Technical Documentation EIP-7702: https://eips.ethereum.org/EIPS/eip-7702 EIP-7251: https://eips.ethereum.org/EIPS/eip-7251 EIP-6110: https://eips.ethereum.org/EIPS/eip-6110 EIP-7002: https://eips.ethereum.org/EIPS/eip-7002 EIP-7691:https://eips.ethereum.org/EIPS/eip-7691 For the Pectra upgrade execution layer specification, visit: https://github.com/ethereum/execution-specs/releases/tag/v1.17.0rc6.dev1 For the consensus layer specification, visit: https://github.com/ethereum/consensus-specs/releases/tag/v1.5.0-beta.2