Skip to content
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.

IS-1120: Prevalidate a TX more strictly #520

Closed
wants to merge 2 commits into from

Conversation

cow-hs
Copy link
Contributor

@cow-hs cow-hs commented Sep 11, 2020

It is a draft to review.
I'm going to full sync after confirm that PR.
include IS-1123 bug fix

Content

Append validate logic about

  • Malformed number string: "0x0001", "100"
  • Malformed address format: "hx1234", "0xqw1234"
  • Tx which has call data though its "to" address is EOA
  • Unused field (only V2)
  • Version 2 deprecated

TODO

There is the plan to append validate logic about SCORE Call after merge this.

@cow-hs cow-hs requested a review from a team September 11, 2020 07:34
@cow-hs cow-hs self-assigned this Sep 11, 2020
create_tx_hash().hex(),
]
)
def test_origin_request_execute(
Copy link
Member

@goldworm-icon goldworm-icon Oct 6, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This unit-test has a critical problem.
It seems to work well but in fact origin_request is always empty dictionary and any checking codes are not executed.

@cow-hs cow-hs closed this Oct 7, 2020
@cow-hs cow-hs deleted the IS-1120-prevalidate-a-tx-more-strictly branch October 13, 2020 00:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants