-
Notifications
You must be signed in to change notification settings - Fork 71
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
add Execution #67
add Execution #67
Conversation
This PR is finally ready! |
contracts/starknet/space/space.cairo
Outdated
# TODO: L1 needs to know about L2 address, but L2 needs to know about the L2 address... need to fix that. | ||
# TODO: this should either be on the l1 contract or the l2 contract. Since l1 contract has an `owner` I think it should be on l1. |
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.
This needs to be addressed (we can merge like this, but will definitely need to be addressed soon)
test/starknet/shared/helpers.ts
Outdated
// This should be declared along with the other const but doing so will make the compiler unhappy as `SplitUin256` | ||
// will be undefined for some reason? |
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 need some TS gods to help me here... initially had it along with the other consts but it simply didn't work ^^
Currently working on adding:
|
…into add_execution
Im wondering whether the entire proposal should be cancelled if overflow on the voting power count happens rather than just making that vote fail. The proposal is broken if it happens so seems like it should be cancelled |
This PR adds the
execution
feature.Basically, this PR adds a
finalize_proposal
method to thespace
contract, and adds azodiac_relayer.cairo
contract that will relay the execution to L1. L1 smart-contract is also modified to have a mapping of whitelisted Spaces that can trigger the execution.This
finalize_proposal
can be called by anyone, but only after theproposal_period
has ended.It sends a message to the execution contract stored in
executor
, and notes the proposal asexecuted
. It is up to the execution contract to decide what to do with the information provided.