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

Drop script sizes #1630

Open
kderme opened this issue Feb 16, 2024 · 1 comment
Open

Drop script sizes #1630

kderme opened this issue Feb 16, 2024 · 1 comment
Labels
enhancement New feature or request needs user input

Comments

@kderme
Copy link
Contributor

kderme commented Feb 16, 2024

Fields tx.script_size and script.serialised_size are redundant, since their values can be derived by the length of the script.bytes. If there is no significant reason to keep them, they should be dropped.

This requires users input

@kderme kderme added enhancement New feature or request needs user input labels Feb 16, 2024
@rdlrt
Copy link

rdlrt commented Apr 19, 2024

Only advantage I can think of is they can have is when analysing scripts by sizes on DB, but that can easily be achieved by point-in-time views. Agree they should be dropped

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs user input
Projects
None yet
Development

No branches or pull requests

2 participants