Skip to content
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 instructions to Reserve and Deposit cli commands #3110

Open
Titan-Node opened this issue Jul 29, 2024 · 1 comment
Open

Add instructions to Reserve and Deposit cli commands #3110

Titan-Node opened this issue Jul 29, 2024 · 1 comment
Labels
status: triage this issue has not been evaluated yet

Comments

@Titan-Node
Copy link

Currently new gateway operators get confused with Reserve and Deposit terminology when funding their gateway.

I suggest we add a description once they have selected the option in the Cli.

Something like:

Reserve: This holding account does not spend any funds. It ensures Orchestrators get paid if funds run out. To start, add 100x the ticket value (e.g. with a ticket value of 0.0012 ETH, add reserve of 0.12 ETH).

Deposit: This spending account pays Orchestrators for completed work. Regularly add funds to keep services running. Start with 2x your deposit amount and increase as needed based on demand.

Note: You can withdraw both reserve and deposit amounts via the CLI.


As for the Reserve calculation, I may need some help in finding the correct calculation, but I think there needs to be concrete guidance on how much to fund.

@github-actions github-actions bot added the status: triage this issue has not been evaluated yet label Jul 29, 2024
@rickstaa
Copy link
Member

@Titan-Node, thank you for the suggestions. If I can guide you through the calculation, you could open a pull request to make changes at the following link:

GitHub Link

My only reservation is that I prefer to keep the client description brief and instead add this information to the gateway documentation if it seems unclear. Here is the relevant section for your reference: Fund Gateway Guide. Let's also get input from @thomshutt and @leszko on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: triage this issue has not been evaluated yet
Projects
None yet
Development

No branches or pull requests

2 participants