-
Notifications
You must be signed in to change notification settings - Fork 89
Update pricing details for Lit Actions #1030
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
base: naga
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -44,5 +44,5 @@ Lit Actions have multiple pricing components that are charged based on resource | |||||
| - **Decrypts**: Cost per decryption operation | ||||||
| - **Fetches**: Cost per HTTP fetch request | ||||||
|
|
||||||
| The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. | ||||||
| The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. Since every Lit Action can be unique, we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices, and helps the network account for incoming Lit Actions before they have been executed. Your **actual** price will be calculated in real time as your action is being executed and will be billed when the action is finished. | ||||||
|
||||||
| The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. Since every Lit Action can be unique, we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices, and helps the network account for incoming Lit Actions before they have been executed. Your **actual** price will be calculated in real time as your action is being executed and will be billed when the action is finished. | |
| The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. Since every Lit Action can be unique, we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices, and helps the network account for incoming Lit Actions before they have been executed. Your **actual** price will be calculated in real time as your action is being executed and will be billed when the action is finished. |
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.
So this is saying that they do pay two base prices? But one is charged even if the action doesn't get run?
I don't think we need to explain why we have a base price ("we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices")
I think we need to explain why there are two "base prices" for running an action, and that they'll be charged both, or what the difference is.
I don't know, it's just really confusing to have two "base prices" here. it seems like one is the "cost to start to run the action" (products.litAction cost) and the second is the "successful execution cost" (lit action component basePrice) and you do get charged for both. Is this framing incorrect? could we explain it more like this, so it's immediately clear what the difference is?
Like do we need some copy like this?
i.e. "All endpoints require paying the product price at the start of the request. Since Lit Actions can have variable costs, successful execution incurs the costs of all the runtime components including an additional lit action component basePrice"
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.
The term "real time" should be hyphenated as "real-time" to match the documentation convention used elsewhere in this file (line 10: "real-time prices") and throughout the codebase.