Skip to content

Commit fc9e2de

Browse files
authored
Litepaper structure (#57)
1 parent 21bdff6 commit fc9e2de

File tree

1 file changed

+48
-0
lines changed

1 file changed

+48
-0
lines changed

LITEPAPER.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Gno: A Deterministic Multi-Realm Computing Platform
2+
3+
## Abstract
4+
TODO: Concise summary of what Gno is, the problem it addresses, and its core differentiators.
5+
6+
## Introduction
7+
TODO: Motivation for Gno, limitations of existing blockchain platforms, and high-level goals.
8+
9+
## Gno
10+
11+
### The Gno Language
12+
TODO: Describe Gno as a Go-compatible language, supported features, determinism constraints, and why Go is the chosen abstraction.
13+
TODO: Document security implications of language-level constraints.
14+
15+
### The Gno Virtual Machine
16+
TODO: Explain how GnoVM executes Gno code, its interpreter model, and how it differs from bytecode-based VMs.
17+
TODO: Describe how determinism, isolation, and safety are enforced by the VM.
18+
19+
### Execution Environment
20+
TODO: Describe how transactions are executed, lifecycle of execution, and runtime guarantees.
21+
TODO: Clarify how failures, reverts, and safety boundaries are handled.
22+
23+
### State and Persistence
24+
TODO: Explain how state is represented, how persistent objects are tracked automatically, and how changes are committed.
25+
TODO: Describe persistence guarantees and security implications of automatic state tracking.
26+
27+
### Gas and Resource Accounting
28+
TODO: Define how computation and storage are metered, what resources are limited, and how costs are calculated.
29+
TODO: Describe protections against resource exhaustion and abuse.
30+
31+
### Governance and Economics
32+
TODO: Describe the governance model (including Proof of Contribution) and economic incentives.
33+
TODO: Explain how governance mitigates capture, abuse, and long-term risk.
34+
35+
### Consensus
36+
TODO: Explain how nodes reach agreement on execution results and state, including the role of Tendermint2.
37+
TODO: Document assumptions and safety guarantees of the consensus layer.
38+
39+
### Interoperability
40+
TODO: Describe how Gno interacts with external chains and systems, including IBC.
41+
TODO: Describe trust boundaries and security considerations for cross-chain interactions.
42+
43+
## Applications and Vision
44+
TODO: Describe the long-term vision for Gno, including the Logoverse and core applications.
45+
TODO: Explain how the design choices enable safe, composable, long-lived applications.
46+
47+
## Conclusion
48+
TODO: Summarize the system and restate its core principles and goals.

0 commit comments

Comments
 (0)