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

Support for transaction read/write sets #1919

Open
1 of 7 tasks
peterjgilbert opened this issue Jul 15, 2019 · 2 comments
Open
1 of 7 tasks

Support for transaction read/write sets #1919

peterjgilbert opened this issue Jul 15, 2019 · 2 comments
Labels
epic Epic (costed tracking issue)

Comments

@peterjgilbert
Copy link
Contributor

peterjgilbert commented Jul 15, 2019

Needed in order to support confidential to non-confidential cross-contract/service calls Initially, read/write sets will be specified at per-contract granularity.

Details

Estimated cost: 13d+

@peterjgilbert peterjgilbert added the epic Epic (costed tracking issue) label Jul 15, 2019
@kostko
Copy link
Member

kostko commented Aug 16, 2019

Filed subissues.

@kostko
Copy link
Member

kostko commented Sep 17, 2019

Updated dependencies as some issues were not covered initially but need to be done first (#1963 and #1466) in order to do reverts safely.

@kostko kostko removed their assignment Oct 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Epic (costed tracking issue)
Projects
None yet
Development

No branches or pull requests

2 participants