[Solved] Sending transactions after London Fork considering EIP 1559

Darren Jensen Asks: Sending transactions after London Fork considering EIP 1559
I have an application that sends legacy transactions containing to, from, gasPrice, gasLimit, value and data properties.

I know that following the London Fork there is backward compatibility with legacy transactions, however, in order to prepare and to make use of the updates in EIP 1559 I want to test the new transaction types in Ropsten Testnet. My understanding is that the London Fork is already applied in Ropsten Testnet.

Can someone point me to an example transaction that uses the new fields in EIP 1559 and what to expect in the transaction receipt? I want to know the correct transaction payload to send and the expected receipt to receive.

Below is an example of how I think a transaction payload might look (some fields omitted for brevity):

Code:
{
   from: 0x111...
   to: 0x222...
   type: 0x2 <-- do I need to set this now?
   maxPriorityFeePerGas: 10000000000 <-- pay 10 GWei for priority gas fees
   maxFeePerGas .... <-- do I need to set this?
}

Ten-tools.com may not be responsible for the answers or solutions given to any question asked by the users. All Answers or responses are user generated answers and we do not have proof of its validity or correctness. Please vote for the answer that helped you in order to help others find out which is the most helpful answer. Questions labeled as solved may be solved or may not be solved depending on the type of question and the date posted for some posts may be scheduled to be deleted periodically. Do not hesitate to share your response here to help other visitors like you. Thank you, Ten-tools.