(WIP) chore: initial whitepaper structure

[dongwon8247]

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.

[Kouteki]

What about writing a yellow paper instead that outlines the current state of the Gno.land blockchain at its beta launch state? This has a few benefits:

• We can write a new version whenever we have a major change (e.g. once we integrate IBC and figure out the interaction between PHOTON, GNOT and ATONE)
• We avoid the pitfalls of theorizing how some components will work, and losing a lot of time on it
• A yellow paper is shorter, but much more substantial (e.g. 80% of the beta yellow paper would focus on the GnoVM)

I believe Ethereum came up with the concept and it's been very useful.

[moul]

Opened #56 with a litepaper as a starting point. We can write a proper whitepaper (or yellow paper) post-launch.

Let's choose if we prefer to start with white or lite.

EDIT: let's maybe just rename the file in this PR. Closing #56.

[moul]

why partial?

Suggested change

| Determinism | Partial | Partial | Strong | Strong |

[moul]

Suggested change

	## 3.1 The Bytecode Problem
	Ethereum stores compiled bytecode:
	```
	Deployed: 0x608060405234801561001057600080fd5b50...
	```
	Interpreting this requires decompilation or external source verification.
	Gno stores source code directly:
	```go
	func Transfer(to std.Address, amount int64) {
	caller := std.PreviousRealm().Address()
	balances[caller] -= amount
	balances[to] += amount
	}
	```
	Auditing requires only the ability to read Go.
	## 3.1 Source Transparency
	Gno stores source code directly:
	```go
	package token
	var balances = map[address]int64
	func Transfer(cur realm, to address, amount int64) {
	caller := runtime.PreviousRealm().Address()
	balances[caller] -= amount
	balances[to] += amount
	}
	Auditing requires only the ability to read Go.