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.

Sign up for GitHub

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

Jump to bottom

Architecture document of TOGA++ #295

Open

hellwolf opened this issue Aug 2, 2022 · 0 comments

Labels

Contributor

hellwolf commented Aug 2, 2022 •

edited

Loading

As a protocol participant, I'd like to see that the protocol is backed by a robust off-chain network that addresses the protocol solvency conundrum.

Currently we are using TOGA system, but in general, we need more participation in the TOGA system, so that the protocol can be seen as more robust.

An architecture of TOGA++ is born from such need to include these key ideas:

User should be able to signal “intents” to the sentinel network.
Sentinel should have permission to perform the “civilian service” (as opposed to "military services", namely TOGA critical/insolvent account liquidations).
We should like to also converge to the overall MEV ecosystem.

Additional Requirements

Make the design process of this involving 3rd party who is also tackling similar problems. Using protocol forum as the avenue.

hellwolf assigned ngmachado and unassigned ngmachado

hellwolf assigned ngmachado

hellwolf unassigned ngmachado

hellwolf added the Type: Spike label

hellwolf transferred this issue from another repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment