(WIP) chore: initial whitepaper structure #55
+215
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to do a temperature check on how we want to structure the Gno.land whitepaper.
The technical parts, especially Gno, GnoVM, Realm specifications, TM2, etc., should be filled in by the core engineers who have deep knowledge in each section, and they should be cited in the whitepaper for their contributions. cc @jaekwon @moul @thehowl @ltzmaxwell @zivkovicmilos @mvertes @piux2 @omarsy @notJoon, and more.
@jaekwon should be the chief author of this whitepaper, and I'm initializing the discussion by opening this PR.
I'd love to hear your opinions on how we should form the whitepaper.