Skip to content

Conversation

@bplatak
Copy link
Contributor

@bplatak bplatak commented May 22, 2025

Summary

Add a new payload context for TransactionEnvelope to represent governance insutructions.

Rationale

The Lazer transactions are used to convey both publisher updates as well as governance actions

How has this been tested?

  • Current tests cover my changes
  • Added new tests
  • Manually tested the code

@vercel
Copy link

vercel bot commented May 22, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm
component-library ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm
developer-hub ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm
entropy-debugger ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm
entropy-explorer ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm
insights ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm
proposals ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm
staking ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 23, 2025 5:11pm

// Context contains status of each governance instruction found in transaction
message GovernanceInstructionContext {
// [required] ID of publisher based on the access token used to connect
optional uint32 publisher_id = 1;
Copy link
Contributor

Choose a reason for hiding this comment

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

publisher doesn't make sense in this context I think.
@darunrs ?

Copy link
Contributor

Choose a reason for hiding this comment

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

Not really no

// [required] the governance instruction
GovernanceInstruction governance_instruction = 2;
}

Copy link
Contributor

Choose a reason for hiding this comment

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

@bplatak bplatak closed this May 27, 2025
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.

5 participants