Skip to content

Conversation

@dthaler
Copy link
Collaborator

@dthaler dthaler commented Jul 7, 2025

And why it's good enough for many purposes.

And why it's good enough for many purposes.

Signed-off-by: Dave Thaler <[email protected]>
@dthaler dthaler requested a review from LPardue as a code owner July 7, 2025 18:30
@tfpauly
Copy link
Member

tfpauly commented Jul 21, 2025

A very good point!

grease values are correctly treated as ignored or errors. As such, it is still possible
that ossification can still occur where other reserved values are not allocatable
without causing problems in practice. The goal is simply to increase the chances
of correct implementation.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I like the point.

I might change the language a little bit though. An alternative phrasing could be something g like

Greasing is limited to exercising grease values. It cannot exercise other values that are reserved for future use or later allocation by protocol extensions. As such, ossification remains a possibility, with the risk of non-grease values causing an issue in practice. The goal of greasing is to reduce this possibilty but it cannot eliminate it.

Copy link
Member

@tfpauly tfpauly left a comment

Choose a reason for hiding this comment

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

Proposed text to merge Dave/Lucas's suggestions

@tfpauly tfpauly merged commit d98a8a2 into intarchboard:main Oct 20, 2025
2 checks passed
@dthaler
Copy link
Collaborator Author

dthaler commented Oct 20, 2025

@tfpauly s/there by/thereby/

@tfpauly
Copy link
Member

tfpauly commented Oct 20, 2025

@dthaler fixed on ed3c99b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants