​One article to learn about new transaction types on Ethereum

There are different types of transactions on Ethereum, for example, sending ETH to an address, deploying a contract, and so on. Before the Berlin network upgrade, there were four different transaction types on Ethereum:

Regular transactions with receiving addresses, data fields, etc.;

For contract deployment transactions without destination addresses, the data field is used for contract codes;

A transaction with a v-value signature, but not including the chain ID (pre-EIP-155);

A transaction with a v-value signature, but including the chain ID.

Different Ethereum clients, libraries and other tools analyze each transaction and understand each transaction type. While there are only four transaction types, there are many complexities and situations to deal with. Technicians should check all the fields in the transaction to figure out what type of transaction it is. This is key for new types of transactions, such as pre-EIP-2718 transaction types such as meta transactions and multisig transactions.

Ethereum now has a new transaction standard, defined and created by developer Micah Zoltu in EIP-2718. Typed transaction envelopes form the basis for some and other untapped features on Ethereum.

Veratheape, a new member of the special committee of ApeCoin: will promote the structure of DAO 2.0 to expand the APE ecology: Jinse Finance reported that in the just-concluded election of members of the special committee of ApeCoin DAO, Veratheape became one of the three new members with a support rate of 26.36%. Term begins on 1 January. In the latest interview, Veratheape stated that he will promote the DAO 2.0 structure and use hackathons and partnerships to expand the APE ecosystem. Veratheape said: "Building an ecosystem has been a long journey, it took Ethereum 4 years to really build an ecosystem, I want to help with issues like transparency, DAO participation and rebranding, another thing for me The important thing is the change of DAO structure, APE ecology should have a structure similar to DAO 2.0.” [2023/1/1 22:19:56]

In this article we will detail some of the standards included in the Berlin upgrade, as well as others that may be included in the future.

Ethereum has a transaction format. Each transaction includes a nonce, gas price, gas limit, destination address, value, data, v, r, and s. These fields are RLP encoded as follows:

Open Web Collective announced the establishment of a new department called OWC Ventures to invest in early-stage crypto startups: Golden Finance reports that blockchain and web3 accelerator Open Web Collective has established a new department called OWC Ventures to invest in early-stage crypto startups. Crypto startups.

Jeff Lavoie, head of investments at OWC Ventures, said the unit is backed by Barry Silbert’s digital currency group and blockchain protocol NEAR.

There will also be a fund behind OWC Ventures, which has yet to close, but the team says it expects to “raise $20 million in funding for a pre-Series A seed deal with co-investment opportunities.

OWC's two-year-old accelerator program is made up of 26 alumni founders who collectively have raised more than $360 million in funding, according to OWC's website. [2022/9/19 7:06:51]

RLP([nonce, gasPrice, gasLimit, to, value, data, v, r, s])

EIP-2718 defines a new broad envelope for typed transactions. In the new standard, transactions look like this:

Data: 11,453 people have donated 12,231 times for V God’s new book "Proof of Stake", totaling 73.15 ETH: Jinse Finance reported that according to Dune data, as of the time of publication, Ethereum co-founder Vitalik Buterin’s new book "Proof of Stake" has totaled 73.15 ETH. 11,453 people have made 12,231 donations and received a total of 73.15 ETH.

Earlier today, it was reported that Vitalik's new book "Proof of Stake" will be published on September 27, and the proceeds will be used to support Gitcoin public products. [2022/8/31 13:00:34]

TransactionType || TransactionPayload

where the fields are defined as:

Transaction Type: A number between 0 and 0x7f, there are 128 possible transaction types in total.

Transaction Payload: An arbitrary byte array as defined by the transaction type.

These fields are concatenated and combined to form a typed transaction. The standard does not describe the format of the transaction payload; it can be any arbitrary series of bytes, encoded by the encoders defined by the new transaction types (e.g., RLP, SSZ, etc.). Simple byte concatenation was chosen because reading the first byte of a byte array does not require any libraries or tools: you don't need an RLP or SSZ parser to check the transaction type.

The decentralized trading platform HashFlow launched public pools, which are now in the testing phase: On December 15, the decentralized trading platform Hash Flow launched public pools, aiming to allow ordinary users to use the pricing algorithms of institutional-level market makers. At present, the total TVL of public pools is set at 10 million US dollars, and the actual test is underway. After that, the project party will open access to some holders of HashFlow's official NFT. HashFlow said that it will soon support more addresses on the Ethereum chain to use public pools. [2021/12/15 7:41:33]

This new approach enables new EIPs to introduce transaction types without introducing unnecessary complexity into existing transaction formats, and it becomes easier to differentiate between different transactions using different Ethereum tools (clients, libraries).

A good example of added complexity is EIP-155, which introduces reply protection by using chain IDs in transactions. Adding a new field to the transaction parameters would break backwards compatibility, so the chain ID is encoded into the recovery parameter (v) of the transaction signature (v). With EIP-2718, we can simply create a new transaction type to maintain backwards compatibility.

All three major U.S. stock indexes turned down: U.S. stocks opened higher and moved lower, and all three major stock indexes turned down. Earlier, the US Centers for Disease Control and Prevention confirmed that the first case of Omicron infection in the United States was found in California. [2021/12/2 12:44:51]

A big theme of EIP-2718 is backwards compatibility. EIP-2718 is in full backward compatibility mode, which means that any existing tools, libraries, (hardware) wallets and transactions can use it, but they will not be able to use the new "features" provided by EIP-2718 and the standard. The old transaction format (now called raw transactions) is still valid for new transactions on the Ethereum network.

The maximum number of new transaction types, 0x7f, was chosen to maintain backward compatibility with these old transactions. RLP-encoded transactions always start with a byte that is l, and the parameter is greater than or equal to 0xc0, so typed transactions will never collide with old transactions, and typed transactions can be distinguished just by checking the first byte and old transactions.

EIP-2718 itself does not define any transaction types, but there are some proposals for the new standard:

EIP-1559: ETH1.0 chain market fee changes;

EIP-2711: Sponsorship, expiration, and batch transactions, also created by developer Micah Zoltu, which is why EIP-2718 was created;

EIP-2930: Optional access lists.

Some of these criteria are further detailed below.

New transaction types can support the integration of functionality that would otherwise be handled through Solidity contracts or third-party solutions. Take, for example, a deal that is about to expire. In existing solutions, you can send funds to a Solidity contract, sign a transaction, and send that transaction to a dedicated node so that the transaction has additional parameters such as an expiration date. Nodes then process sending the transaction and make sure it is executed before the set expiration date, otherwise the transaction will not be broadcast. Some dApps and contracts (e.g. Uniswap) have this built in, but for most transactions, it's not easily achievable.

EIP-2711 adds this functionality natively to the Ethereum network, while maintaining backwards compatibility with primitive type transactions (as described in the previous section). It does not require smart contracts or dedicated nodes to run. However, currently EIP-2711 is still a draft and it is unclear whether this EIP will join the Ethereum network anytime soon. It may also be split into multiple smaller EIPs (such as EIP-3074).

In EIP-1559, the way gas works has changed significantly. Instead of paying full gas to miners, a portion of gas is burned. We don't detail all the changes in EIP-1559, but it does specify a new transaction format:

0x02 || RLP([chainId, nonce, maxPriorityFeePerGas, maxFeePerGas, gasLimit, to, value, data, accessList, signatureYParity, signatureR, signatureS])

The most notable changes are:

Gas price has been replaced by "highest priority fee per gas" and "maximum fee per gas".

The chain ID is encoded separately rather than included in the signature v-value. This essentially replaces EIP-155 with a simpler implementation.

The signature v value is now a simple parity bit ("signature Y parity") which is either 0 or 1, depending on which point on the elliptic curve should be used.

EIP-1559 also provides a way to specify access lists based on EIP-2930. This can reduce the gas cost of transactions.

Since EIP-1559 makes significant changes to how gas fees work, it is not directly compatible with raw transactions. To maintain backwards compatibility, EIP-1559 describes a method for upgrading raw transactions to EIP-1559-compatible transactions. It does this by using the raw gas price as the highest priority fee and highest gas fee per gas.

Metatransactions have been around for a few years, but until now have still required smart contracts. As with expiring transactions, this requires sending ETH to a smart contract, which must specifically support meta transactions.

EIP-2711 enables native meta transactions (called sponsored transactions) and batch transactions without the need for smart contracts. A new transaction format is defined with transaction type 0x02 (although this is subject to change as EIP-1559 uses the same transaction type). The transaction is as follows:

0x02 || RLP([...SenderPayload, ...SenderSignature, ...GasPayerPayload, ...GasPayerSignature])

Basically, EIP-2711 includes an (optional) payload and signature of the gas payer. This account will be used to pay the gas fee in the transaction. For example, ERC-20 tokens can be sent from an address without the address holding any ETH. The sender payload, signature, etc. are defined based on the transaction subtype. For example, for a transaction with transaction type 1, the sender payload is defined as:

[1, ChildTransaction[], nonce, ChainId, ValidUntil, gasLimit, gasPrice]

Child Transaction is defined as: send address, value, data. This makes it possible to specify multiple addresses, values, and data in a single transaction. For example, this can be used to invoke ERC-20 approvals and transfers in a single transaction.

For a detailed description of all transaction subtypes available in EIP-2711, readers are advised to read the official documentation.

Typed transactions bring many possibilities to the Ethereum network. They can be created without adding a lot of complexity to Ethereum clients, libraries, and other tools available.

Currently, new transaction types are not widely used as EIPs were only recently included in the network, but there are some exciting EIPs in development such as EIP-2711 which adds expired transactions, batched transactions and sponsored transactions (also known as meta-transactions) and other features. New transaction types can now be defined on Ethereum, so other EIPs can be easily created.

This article is from Mycrypto, the original author: Maarten Zuidhoorn.

Tags：

Best Ethereum Exchange