Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration Test - Non standard transaction, but not invalid being anchored #5129

Closed
ASuciuX opened this issue Aug 30, 2024 · 2 comments
Closed
Assignees

Comments

@ASuciuX
Copy link
Contributor

ASuciuX commented Aug 30, 2024

A transaction that normally wouldn't be picked by miners is picked and anchored by a miner. The only type of transaction like this is a transaction without fees (which won't get to mempool, but can be anchored by the miner directly).

Steps:

  1. create transaction with 0 fees, signed
  2. as miner, anchor it
  3. check for any unexpected behaviour

Also, what are the limits in size of a transaction? Same as the block?

@janniks
Copy link
Contributor

janniks commented Sep 3, 2024

Optional: Check for possible reasons for dropped_problematic if those can be "mined" and chain will still continue?

Optional: RE Radone: get data from 0 (genesis) block in Clarity.

@ASuciuX
Copy link
Contributor Author

ASuciuX commented Sep 9, 2024

Limits for block and for transactions are tested.

Problematic transactions are tested here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Status: ✅ Done
Development

No branches or pull requests

2 participants