-
Notifications
You must be signed in to change notification settings - Fork 143
feat: update registration to support horizon flow, add provisioning flow at startup #1120
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
Conversation
Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
…low at startup Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
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.
Looks good!
@@ -272,6 +278,13 @@ export const start = { | |||
default: true, | |||
group: 'Protocol', | |||
}) | |||
.option('max-provision-initial-size', { | |||
description: | |||
'The maximum number of tokens for the initial Subgraph Service provision', |
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.
should we mention here the minimum provision size limit in the contracts?
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.
Yeah good idea. Ill add it to my current PR.
Signed-off-by: Tomás Migone tomas@edgeandnode.com