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

Record-centric mirror nodes need synthetic NodeCreates at genesis #17015

Open
15 tasks
tinker-michaelj opened this issue Dec 10, 2024 · 0 comments · May be fixed by #17461
Open
15 tasks

Record-centric mirror nodes need synthetic NodeCreates at genesis #17015

tinker-michaelj opened this issue Dec 10, 2024 · 0 comments · May be fixed by #17461
Assignees
Labels
Estimated Issues that has been groomed
Milestone

Comments

@tinker-michaelj
Copy link
Collaborator

tinker-michaelj commented Dec 10, 2024

Background

Even though all state changes are in the block stream, many mirror nodes will still depend on the V6 record stream to capture network activity.

In current develop, a network started from genesis will only externalize its initial Node metadata via the blockstream, not synthetic NodeCreate transactions.

Acceptance Criteria

  • Network Genesis
    • Synthetic NodeCreate transactions MUST be created
    • Testing
      • Verify synthetic transactions appear in record stream
      • Unit tests

Dependencies

  • None

Definition of Ready (DoR) Checklist

Note that DoR does not need to be 100% met prior to starting work

  • Clear acceptance criteria
  • Clear and detailed description
  • Dependencies identified
  • Links to documentation
  • Should be completable in 2-3 Days
  • Initial draft of Low-level design document
  • At least high level test plan
  • Groomed/Estimated

Definition of Done (DoD) Checklist

  • Acceptance Criteria complete
  • No Codacy issues greater than minor (in new code)
  • JavaDocs updated/created
  • Code commented
  • Unit tests created/updated
  • 80% test code coverage (in new code)
  • Happy Path and major negative cases in HAPI tests as applicable
@tinker-michaelj tinker-michaelj added this to the v0.58 milestone Dec 10, 2024
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Services Team Dec 10, 2024
@Neeharika-Sompalli Neeharika-Sompalli moved this from 📋 Backlog to To Do in Services Team Dec 10, 2024
@derektriley derektriley modified the milestones: v0.58, v0.59 Jan 14, 2025
@derektriley derektriley added the Estimated Issues that has been groomed label Jan 14, 2025
@derektriley derektriley self-assigned this Jan 16, 2025
@derektriley derektriley moved this from To Do to 👷🏼‍♀️ In Progress in Services Team Jan 16, 2025
@derektriley derektriley removed their assignment Jan 16, 2025
@derektriley derektriley moved this from 👷🏼‍♀️ In Progress to To Do in Services Team Jan 16, 2025
@MiroslavGatsanoga MiroslavGatsanoga self-assigned this Jan 17, 2025
@MiroslavGatsanoga MiroslavGatsanoga moved this from To Do to 👷🏼‍♀️ In Progress in Services Team Jan 17, 2025
@MiroslavGatsanoga MiroslavGatsanoga moved this from 👷🏼‍♀️ In Progress to 👀 In Review in Services Team Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Estimated Issues that has been groomed
Projects
Status: 👀 In Review
Development

Successfully merging a pull request may close this issue.

3 participants