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

Paying for Lit Pages #319

Merged
merged 25 commits into from
Aug 15, 2024
Merged

Paying for Lit Pages #319

merged 25 commits into from
Aug 15, 2024

Conversation

spacesailor24
Copy link
Contributor

@spacesailor24 spacesailor24 commented Aug 1, 2024

This PR inits several pages:

  • Capacity Credit intro
  • Delegating Credits
  • Minting Credits via Contracts SDK
  • Minting Credits via Lit Explorer
  • Paying for Lit Overview
  • Using Delegated Credits

@spacesailor24 spacesailor24 changed the title Paying for Lit Paying for Lit - Section headers and Overview page Aug 1, 2024

For a deep dive into the Payment Delegation Database, including how to register a Payer Wallet and add users as Payees, checkout the in-depth [documentation](./payment-delegation-db.md).

### Choosing the Right Payment Method
Copy link
Contributor

@alexvotofuture alexvotofuture Aug 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spacesailor24 wondering how we might word this given our discussion today about the relayer and payment delegation DB not necessarily being maintained long-term. So maybe we can suggest the relayer + payment delegation DB for rapid prototyping for now, and moving to self-hosted versions of those and/or direct capacity credit integration for production? Defer to your judgement on the best flow, since you've been helping people with this directly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably helpful to also tell people how they ought to go about self-hosting these services to get production-ready (where the code lives, things to consider, etc.) somewhere. Maybe in the repos for those tools themselves, with a link to them here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After the discussion on the strategy call, it seems like we'll be supporting these services for users, however I think it's still unclear to what capacity i.e. will this support user's production apps, or is this still for prototyping


Like other decentralized networks, Lit has a certain amount of computation available for users that's metered to allow for a responsive network with nodes that are able to stay in-sync with one another.

In order to use the paid pre-production ([Datil-test](../connecting-to-a-lit-network/testnets#datil-test)) and production ([Datil](../connecting-to-a-lit-network/mainnets#datil)) Lit networks, you must reserve capacity on the network. This is done using by minting Capacity Credits, and by making use of the Lit Relayer and/or the Payment Delegation Database.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In order to use the paid pre-production (Datil-test) and production (Datil) Lit networks, you must reserve capacity on the network. This is done using by minting Capacity Credits, and by making use of the Lit Relayer and/or the Payment Delegation Database.

Maybe we can simplify and say "In order to use the decentralized testnet (datil-test) and production-ready mainnet beta (datil) you will need to reserve capacity on the network using capacity credits. You can mint credits using the relayer and / or the payment DB"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed it to:

In order to use the decentralized testnet (Datil-test) and production-ready mainnet beta (Datil) Lit networks, you will need to pay for usage of the network. This is done using Lit test tokens, Capacity Credits, the Lit Relayer, and the Payment Delegation Database.

@spacesailor24 spacesailor24 changed the base branch from wyatt/temp-branch/paying-for-lit to main August 10, 2024 03:38
Copy link

netlify bot commented Aug 10, 2024

Deploy Preview for lit-dev-docs ready!

Name Link
🔨 Latest commit 5efc82b
🔍 Latest deploy log https://app.netlify.com/sites/lit-dev-docs/deploys/66be6afde69fcd00084b1421
😎 Deploy Preview https://deploy-preview-319--lit-dev-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@spacesailor24 spacesailor24 changed the title Paying for Lit - Section headers and Overview page Paying for Lit Pages Aug 13, 2024
@@ -0,0 +1,129 @@
# Paying for Usage of Lit

The Lit networks, like other decentralized networks, manage their computational resources to ensure optimal performance and synchronization across their nodes. To maintain a responsive and balanced network, Lit implements a metering system for resource utilization.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Lit networks, like other decentralized networks, manage their computational resources to ensure optimal performance and synchronization across their nodes. To maintain a responsive and balanced network, Lit implements a metering system for resource utilization.

IMO this wording is a little confusing. Maybe we can just say that the Lit network meters usage to ensure that optimal performance is maintained for all users, which is accomplished by allowing all users to reserve capacity on the network based on how much usage they require

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reverted it back to:

Like other decentralized networks, Lit has a certain amount of computation available for users that's metered to allow for a responsive network with nodes that are able to stay in-sync with one another.


The Lit networks, like other decentralized networks, manage their computational resources to ensure optimal performance and synchronization across their nodes. To maintain a responsive and balanced network, Lit implements a metering system for resource utilization.

When using the Lit networks, whether it's the decentralized testnet ([Datil-test](../connecting-to-a-lit-network/testnets#datil-test)) or the production-ready mainnet beta ([Datil](../connecting-to-a-lit-network/mainnets#datil)) - you'll need to pay for and reserve your usage. This is accomplished using *Lit test tokens* and *Capacity Credits*.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we leave out the mention of test tokens here? As the credits themselves are how the capacity is reserved and the tokens are just a means of paying for the credits (which could be abstracted for the sake of simplicity imo)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to:

When using the Lit networks - whether it's the decentralized testnet (Datil-test) or the production-ready mainnet beta (Datil) - you need to pay for and reserve your usage. This is accomplished using Capacity Credits.

Copy link
Contributor

@awisniew207 awisniew207 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tables in the overview look amazing!

I think these docs look great, approved

@spacesailor24 spacesailor24 merged commit 369badf into main Aug 15, 2024
@spacesailor24 spacesailor24 deleted the wyatt/paying-for-lit branch August 15, 2024 20:54
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

Successfully merging this pull request may close these issues.

4 participants