Bxpana pfp

Bxpana

@bxpana

16 Following
100 Followers
Bxpana pfp
Bxpana
@bxpana
https://github.com/bxpana/TWIL
0 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
That’s it for this week! These transaction types highlight how ZKsync can still provide a similar experience to that on Ethereum, while providing more functionality with new txn types Next time, I’ll cover Account Abstraction 😎
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
+ max_blob_fee_per_gas: Separate gas market for blob data. + blob_versioned_hashes: Tracks blobs associated with the transaction. 🔥 Blob fees are burned upfront, so failed transactions are not refundable.
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
https://github.com/bxpana/TWIL
0 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
That’s it for this week! These transaction types highlight how ZKsync can still provide a similar experience to that on Ethereum, while providing more functionality with new txn types Next time, I’ll cover Account Abstraction 😎
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
♦️🧬 Type 3 (0x03 - Blob Transactions): - EIP-4844, introduced in the Dencun Fork. - Scaling solution for rollups via blobs. - Adds:
2 replies
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
+ max_blob_fee_per_gas: Separate gas market for blob data. + blob_versioned_hashes: Tracks blobs associated with the transaction. 🔥 Blob fees are burned upfront, so failed transactions are not refundable.
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
♦️🧬 Type 2 (0x02): - EIP-1559, introduced in the London Fork. - Handles congestion with: * maxPriorityFeePerGas: User-defined priority fee. * maxFeePerGas: Total fee limit. (Notes: ZKsync supports Type 2 but currently ignores maxFee parameters.)
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
♦️🧬 Type 1 (0x01): - Introduced with EIP-2929. - Adds an accessList for predeclaring addresses and storage keys. - Saves gas on cross-contract calls by reducing state access costs.
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
Ethereum and ZKsync Transaction Types ♦️🧬 Type 0 (Legacy): - Used before EIP-1559. - Still supported via Foundry’s --legacy flag.
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
ZKsync Transaction Types 🧬 Type 113 (0x71): - Enables advanced features like account abstraction. - Required for deploying smart contracts on ZKsync. - Adds fields like:
1 reply
0 recast
1 reaction
Bxpana pfp
Bxpana
@bxpana
🧬 Type 5 (0xff): - Priority transactions for moving data from L1 → L2.
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
+ gasPerPubData: Cost of L2 pubdata submitted to L1. + customSignature: For non-EOA accounts. + factoryDeps: Deployed smart contract bytecode.
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
Forgot to post earlier, but here's last week's TWIL. Last week I learned about transaction types in Ethereum and @ZKsync. Ethereum ♦️ and ZKsync 🧬 use different transaction types to optimize for scalability, gas efficiency, and account abstraction. Let’s break it down! 👇
1 reply
1 recast
3 reactions
Bxpana pfp
Bxpana
@bxpana
Why Diamonds? 💡 Modular: Break contracts into smaller, manageable parts. 🔄 Upgradeable: Update facets without changing the contract address. 🔗 Shared: Centralized storage for all facets. Smart contract engineering at its best! 🤖
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
That’s a wrap for this week! 🛠️ Thanks as always to @cyfrin
0 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
Diamond Proxy Architecture Another gem from this week: Diamonds! 💎 They enable modular, upgradeable contracts via EIP-2535. Think of it as: 🏨 A hotel where: • Front desk = Diamond proxy • Services = Facets • Shared resources = Shared storage
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
Finally, combine everything: The signature includes: 0x19 0x01 <domainSeparator> <hashStruct(message)> This ensures: 🔒 Security 🔍 Transparency for users EIP-712 = Better UX + Stronger Security 🚀
1 reply
0 recast
0 reaction
Bxpana pfp
Bxpana
@bxpana
Key Components of EIP-712 1️⃣ Domain Separator: It encodes metadata like app name, version, chain ID, and contract address. It ensures the signature is valid only within its intended domain.
1 reply
0 recast
2 reactions
Bxpana pfp
Bxpana
@bxpana
2️⃣ Hashing the Message: EIP-712 hashes the structured message to ensure integrity and prevent tampering.
1 reply
0 recast
0 reaction