-
Notifications
You must be signed in to change notification settings - Fork 18
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
Extend IApplication to generalize tBTC, RandomBeacon and TACo apps #156
Comments
When bonding an operator, Keep do:
a) it's called registerOperator For Nucypher:
we have the idea of an Owner as well as stakingProvider so it's a bit more complicated. It would be ideal if we could bring this inline with Keep, certain areas of the dashboard are built very tightly around their Application Interface https://github.com/threshold-network/token-dashboard/blob/8652343fd254666e04bc90c601e4452c06c3fc38/src/threshold-ts/applications/index.ts#L82 Is that interface I've linked what everything else is based on? I don't want us to end up with multiple versions |
Looks like the
This way the actual contracts structure is reflected and you can easily add:
|
In addition to the discussion on #88, while developing the TACo app contract, and particularly when integrating it with the dashboard, we've detected several methods that should be generalized in
IApplication
due to common workflows. This is specially relevant in contexts that consume the 3 contracts (i.e. the dashboard).Also, consider if it's necessary the creation of an additional interface for Threshold apps that assume the existence of an operator role, something like
IApplicationWithOperator
, so we can abstract here methods likeregisterOperator()
.The text was updated successfully, but these errors were encountered: