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.

Sign up for GitHub

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

Jump to bottom

Avoid state transition use under different contract/schema #99

Closed
dr-orlovsky opened this issue Jun 10, 2022 · 1 comment
Closed

Avoid state transition use under different contract/schema #99

dr-orlovsky opened this issue Jun 10, 2022 · 1 comment
Labels
*consensus* Issues affecting distributed concensus question Further information is requested *security* Issues affecting safety/security (include undefined behaviours)
Milestone
v0.9.0

Comments

@dr-orlovsky
Copy link
Member

Ensure that it is impossible to construct an attack where a state transition from one contract is re-interpreted under a different contract or scheme. Consider adding commitment to the contract id into the contract nodes (state transitions and state extensions)
@dr-orlovsky dr-orlovsky added question Further information is requested *consensus* Issues affecting distributed concensus *security* Issues affecting safety/security (include undefined behaviours) labels Jun 10, 2022
@dr-orlovsky dr-orlovsky added this to the v0.7.0 milestone Jun 10, 2022
@dr-orlovsky dr-orlovsky modified the milestones: v0.7.0, v0.8.0 Jun 17, 2022
@dr-orlovsky dr-orlovsky modified the milestones: v0.8.0, v0.9.0 Nov 16, 2022
@dr-orlovsky
Copy link
Member Author

Not relevant with the introduction of contract interfaces

@dr-orlovsky dr-orlovsky closed this as not planned Won't fix, can't repro, duplicate, stale Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
*consensus* Issues affecting distributed concensus question Further information is requested *security* Issues affecting safety/security (include undefined behaviours)
Projects
Specification & reference implementation
Status: Done
Milestone
v0.9.0
Development

No branches or pull requests
1 participant
@dr-orlovsky