Remove Sequencer transaction in favor of Transaction with an optional hash #127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Helper PR to simplify the process of adding v3 transactions in #124
StarknetSequencerTransaction
; Move its optionalhash
field toStarknetTransaction
StarknetInvokeTransactionV1
andStarknetDeployAccountTransactionV1
constructors to estimate version based on whether they're intended for fee estimationStarknetInvokeTransactionV1
andStarknetDeployAccountTransactionV1
StarknetSequencerInvokeTransaction
,StarknetSequencerDeployAccountTransaction
testSequencerInvokeTransactionDecoding
Linked issues
Closes #41
Breaking changes
StarknetSequencerTransaction
StarknetSequencerInvokeTransaction
; Uses ofStarknetSequencerInvokeTransaction
are now of typeStarknetInvokeTransactionV1
StarknetSequencerDeployAccountTransaction
; Uses ofStarknetSequencerDeployAccountTransaction
are now of typeStarknetDeployAccountTransactionV1
StarknetInvokeTransactionV1
; Updated default oneStarknetDeployAccountTransactionV1
; Updated default one