Skip to content

Commit f01a3e9

Browse files
docs: describe briefly "Credits" in FAQ (#518)
* docs: describe briefly "Credits" in FAQ Signed-off-by: David Dal Busco <david.dalbusco@outlook.com> * 📄 Update LLMs.txt snapshot for PR review --------- Signed-off-by: David Dal Busco <david.dalbusco@outlook.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
1 parent 8c87dc7 commit f01a3e9

2 files changed

Lines changed: 18 additions & 0 deletions

File tree

.llms-snapshots/llms-full.txt

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10005,6 +10005,15 @@ For help and questions about best practices, join our [Discord](https://discord.
1000510005

1000610006
Getting started is free. Developers are responsible for operating costs. Transaction costs may apply for some features. [Detailed information and estimations](/docs/pricing.md) are available.
1000710007

10008+
### What are credits?
10009+
10010+
Credits are not money or tokens, they're simply Juno's way of helping you get started, like saying "drinks on us".
10011+
10012+
* 1 credit lets you spin up one module without requiring payment (see [Pricing](/docs/pricing.md)).
10013+
* Every new developer starts with 2 credits, enough to create a Mission Control and a Satellite to get going.
10014+
10015+
Sometimes, additional credits can be granted - for example, during onboarding or when launching exciting projects. Reach out if you need more.
10016+
1000810017
### How do I verify an upgrade?
1000910018

1001010019
Before approving an upgrade, developers can verify the proposed changes by checking the release details on [GitHub](https://github.com/junobuild/juno/releases). Each release includes a list of modules proposed for update, along with a checksums.txt file that contains the SHA-256 hashes of the module binaries. For example:

docs/faq.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,15 @@ For help and questions about best practices, join our [Discord](https://discord.
88

99
Getting started is free. Developers are responsible for operating costs. Transaction costs may apply for some features. [Detailed information and estimations](./pricing.md) are available.
1010

11+
### What are credits?
12+
13+
Credits are not money or tokens, they're simply Juno's way of helping you get started, like saying "drinks on us".
14+
15+
- 1 credit lets you spin up one module without requiring payment (see [Pricing](./pricing.md)).
16+
- Every new developer starts with 2 credits, enough to create a Mission Control and a Satellite to get going.
17+
18+
Sometimes, additional credits can be granted - for example, during onboarding or when launching exciting projects. Reach out if you need more.
19+
1120
### How do I verify an upgrade?
1221

1322
Before approving an upgrade, developers can verify the proposed changes by checking the release details on [GitHub](https://github.com/junobuild/juno/releases). Each release includes a list of modules proposed for update, along with a checksums.txt file that contains the SHA-256 hashes of the module binaries. For example:

0 commit comments

Comments
 (0)