Add Gnoland FAQs #41
Add Gnoland FAQs #41
Conversation
Signed-off-by: Antonio Navarro <antnavper@gmail.com>
gno.land.faqs.md
Outdated
| - Because everything is public, import a package is easy and straightforward. | ||
| - Go tooling is really good. | ||
|
|
||
| ### How are we going to manage the blockchain size? |
There was a problem hiding this comment.
I think this question relates to state management, and how we cap / prune the state size from getting out of control because contracts are being deployed
Is the official answer we're going with that the state is going to be distributed across different gno chains?
There was a problem hiding this comment.
I don't know the official answer, that is something we have to discuss. Maybe @moul can give a better answer for this?
There was a problem hiding this comment.
The correct approach is to provide a link to an issue where the discussion can be tracked until it is sufficiently completed to be included in the FAQ.
The FAQ should offer concise answers and encourage further exploration by providing URLs to relevant resources such as documentation, blog posts, tweets, issues, and pull requests.
|
I advocate for placing the FAQ on this repository instead of the main one. This way, it becomes a community-oriented document that primarily offers support. We can even rely on the community to assist in completing, clarifying, and continuously adding reference links to the FAQ. I support merging your PR, Antonio. I renamed the file to FAQ.md. After merging, we can iterate. I suggest updating the docs.gno.land website to automatically fetch this FAQ.md file. Alternatively, we could consider moving misc/docusaurus from the main repo to here to keep the main repo cleaner and focused on content. cc @gnolang/devrels @ajnavarro @zivkovicmilos Edit: see #49 for the expected next steps. |
|
Pinging @leohhhn @waymobetta for input on this PR |
|
@waymobetta , I don't know why your q's were marked as resolved, but even if they're marked as outdated (because they referred to the old file) I still support them 👍 |
|
@thehowl I marked them as resolved for sake of removing blockers on this and getting it merged; we would then follow-up with subsequent PRs to address additional questions like these and others. |
|
|
||
| ### How is the company behind gno.land planning to make money? | ||
|
|
||
| 25% of Genesis tokens will be owned by the company. That will encourage us to keep evolving and improving the ecosystem making it more valuable for the users. Also, we will create some packages and Realms that will be monetized thanks to Proof of Contribution. |
There was a problem hiding this comment.
@moul should we mention that part of the 25% fund will be used to fund an initial faucet for the chain, and used to be reinvested into the chain
|
@waymobetta okay, I still made a few comments because I still think some answers were a bit "half-correct". Nevertheless, Antonio's OOO until next week, but I think when he gets back he can incorporate my and your requested changes & merge :) |
Co-authored-by: Morgan <git@howl.moe>
Co-authored-by: Morgan <git@howl.moe>
|
Closes Issue#2 |
List of questions made at Gophercon EU almost for everyone asking for info about gno.land.
This is not intended to be the final answers and they must be reviewed and expanded.
cc @zivkovicmilos @moul