search

RiskProtocol / core-protocol

2 stars 0 forks source link

Implementation of Orchestrator #137

Closed haidarally closed 11 months ago

haidarally commented 1 year ago

https://github.com/RiskProtocol/core-protocol/issues/134

Tunji17 commented 1 year ago

So if i understand this correctly what the orchestrator does is to save all rebase transactions in the correct order and execute them in that same order? @haidarally is there anything else

haidarally commented 1 year ago

So if i understand this correctly what the orchestrator does is to save all rebase transactions in the correct order and execute them in that same order? @haidarally is there anything else

Yes, that's the main purpose of the orchestrator @Tunji17

openzeppelin-code[bot] commented 11 months ago

Implementation of Orchestrator

Generated at commit: 6680cab2e82c23e5d13ceedfd349ad1920b4cbaf

🚨 Vulnerabilities Summary

Process Issues Results
Contract Inspector low
note
Total		 6
28
34
Dependency Checker Total 0

For more details view the full report in OpenZeppelin Code