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

Product questions #1

Open
talkol opened this issue Jun 13, 2022 · 0 comments
Open

Product questions #1

talkol opened this issue Jun 13, 2022 · 0 comments

Comments

@talkol
Copy link
Member

talkol commented Jun 13, 2022

The lambda code is on github, when does it sync to the nodes, how fast?

Separate process that does the code sync that runs every few hours. Customers cannot trigger an immediate deploy.

What are the triggers for running?

Scheduled time (cron expression). What about preventing too frequent running?

Event?

Block range?

Can the code assume that it's stateful?

No, the nodes may be reset at any time so they are stateless. They may implement memory based caching mechanisms for optimization purposes. If persistent state is required then Ethereum should be used for now.

Can the implementor require consensus for side effects?

For example, to send a transaction only if a majority of nodes agree - for example, on stop loss unlike auto compounding, deciding to exit a position needs to be a little more secure.

How does the customer pay for the gas costs?

Also, bidding on gas amount.

How to make sure we don't run more than once if needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant