-
Notifications
You must be signed in to change notification settings - Fork 250
feat(pyth-lazer-publisher-sdk): Add Public key to Transactions #2700
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
optional bytes payload = 3; | ||
optional bytes payload = 2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for my information, what is the side effect of changing these numbers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It changes the wire format so once the protocol is in use we should never change it. While we're prototyping it doesn't really matter.
Summary
Adds public key to transacitons. Expanded signature format to support a much greater set of possible signatures.
Rationale
We are eliminating access tokens in pyth lazer so we need publishers to send public keys to establish identity.
How has this been tested?