-
Notifications
You must be signed in to change notification settings - Fork 5
Tee transaction filtering by viewing key #239
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
base: main
Are you sure you want to change the base?
Conversation
|
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.
I'm assuming you're going to figure out the encryption part at a later stage?
@@ -7,11 +7,14 @@ pub const VSOCK_PORT: u32 = 5000; | |||
#[derive(Serialize, Deserialize)] | |||
pub enum Request { | |||
Ping, | |||
CalculateReward { viewing_key_base64: String }, |
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.
Question: This will need to be encrypted later, right?
CalculateReward { reward: String }, | ||
Error { message: String }, |
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.
Comment: I was wondering what's better here... this generic Error
variant or CalculateReward(Result<CalculateRewardResult, CalculateRewardError>)
no strong opinions either way.
No description provided.