-
Notifications
You must be signed in to change notification settings - Fork 1
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
proper delegator behavior #17
base: main
Are you sure you want to change the base?
Conversation
} | ||
|
||
#[derive(Debug, Clone, PartialEq, Eq, PartialOrd, Ord, Serialize, Deserialize)] | ||
pub struct JobData { | ||
pub reward: u64, | ||
pub reward: U256, |
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 had switched the type into U256 as it's compatible with deposit
function call amount input. Wondering if we could also use U256 in bootloader input type @Okm165
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.
@rkdud007 I agree.
I also confirmed that on other starknet smart-contracts values/amounts are u256
so it stays this way for sure.
Feel free to change it and other necessary things on a rust side.
I will handle the bootloader compatibility in this PR.
aim to resolve #13
n_step
that static from cairo progrm (PIE) and dynamic input from delegator.stake
&balance_of
function call to cover up delegator node behavior- compiler : input file path -> out put cairo PIE ( responsible of compile )
- registry handler : responsible of streaming subscribed event. As this reponsibility moves registry handler object in mutable state, regarding other contract actions we use node account
- node account : store identity that used in both p2p network and its corresponding starknet account / with this signer and provider, also perform read/write contract call