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

Learn how Berkeley signed commands are serialized #1620

Closed
Isaac-DeFrain opened this issue Oct 11, 2024 · 1 comment
Closed

Learn how Berkeley signed commands are serialized #1620

Isaac-DeFrain opened this issue Oct 11, 2024 · 1 comment
Assignees
Labels
Berkeley Spike Short (time-boxed), focused investigation to gather info, answer questions, or mitigate risk

Comments

@Isaac-DeFrain
Copy link
Member

Isaac-DeFrain commented Oct 11, 2024

Specially, we need to figure out what version bytes are being used.

@Isaac-DeFrain Isaac-DeFrain self-assigned this Oct 11, 2024
@Isaac-DeFrain Isaac-DeFrain converted this from a draft issue Oct 11, 2024
@Isaac-DeFrain Isaac-DeFrain added Spike Short (time-boxed), focused investigation to gather info, answer questions, or mitigate risk Berkeley labels Oct 11, 2024
@Isaac-DeFrain Isaac-DeFrain added this to the Berkeley Support milestone Oct 11, 2024
@Isaac-DeFrain
Copy link
Member Author

Related to #1647

@jhult jhult closed this as completed by moving to Done in MinaSearch.com Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Berkeley Spike Short (time-boxed), focused investigation to gather info, answer questions, or mitigate risk
Projects
Archived in project
Development

No branches or pull requests

2 participants