Tracking issue: Transaction kernel specs #3
Description
Goal(s)
- Define the specification for the transaction kernel we'll need for the Miden rollup.
Details
There have been a lot of discussions, but we need to bring all this info into one place and hammer out the details so we can move forward with the rollup implementation.
Discussion references
### Must have
- [x] AccountId object
- [x] Asset object (fungible and non-fungible assets)
- [x] Note object
- [x] Account object
### Nice to have
- [ ] #4
- [ ] Transaction object (#27)
Working group:
@bobbinth, @grjte, @vlopes, @hackaugusto
Workflow
- Discussion should happen here or in the related sub-issues.
- PRs should only be merged by the coordinator, to ensure everyone is able to review.
- Aim to complete reviews within 24 hours.
- When a related sub-issue is opened:
- add it to the list of sub-issues in this tracking issue
- When opening a related PR:
- request review from everyone in this working group
- When a sub-issue is completed:
- close the related issue with a comment that links to the PR where the work was completed
Coordinator: @bobbinth
Workflow
The working group coordinator ensures scope & progress tracking are transparent and accurate. They will:
- Merge approved PRs after all working group members have completed their reviews.
- add the PR # to the relevant section of the current tracking PR.
- close any completed sub-issue(s) with a comment that links to the PR where the work was completed
- Monitor workflow items and complete anything that slips through the cracks.
- Monitor scope to see if anything is untracked or unclear. Create missing sub-issues or initiate discussion as required.
- Monitor progress to see if there's anything which isn't moving forward. Initiate discussion as required.
- Identify PRs with especially significant changes and add @grjte and @bobbinth for review.
Metadata
Metadata
Assignees
Labels
No labels