22c521eec8
* Util to zip and unzip directories
* First pass at sumtree request/response. Add message types, implement the exchange in the protocol, zip up the sumtree directory and stream the file over, with necessary adapter hooks.
* Implement the sumtree archive receive logicGets the sumtree archive data stream from the network and write it to a file. Unzip the file, place it at the right spot and reconstruct the sumtree data structure, rewinding where to the right spot.
* Sumtree hash structure validation
* Simplify sumtree backend buffering logic. The backend for a sumtree has to implement some in-memory buffering logic to provide a commit/rollback interface. The backend itself is an aggregate of 3 underlying storages (an append only file, a remove log and a skip list). The buffering was previously implemented both by the backend and some of the underlying storages. Now pushing back all buffering logic to the storages to keep the backend simpler.
* Add kernel append only store file to sumtrees. The chain sumtrees structure now also saves all kernels to a dedicated file. As that storage is implemented by the append only file wrapper, it's also rewind-aware.
* Full state validation. Checks that:
- MMRs are sane (hash and sum each node)
- Tree roots match the corresponding header
- Kernel signatures are valid
- Sum of all kernel excesses equals the sum of UTXO commitments
minus the supply
* Fast sync handoff to body sync. Once the fast-sync state is fully setup, get bacj in body sync
mode to get the full bodies of the last blocks we're missing.
* First fully working fast sync
* Facility in p2p conn to deal with attachments (raw binary after message).
* Re-introduced sumtree send and receive message handling using the above.
* Fixed test and finished updating all required db state after sumtree validation.
* Massaged a little bit the pipeline orphan check to still work after the new sumtrees have been setup.
* Various cleanup. Consolidated fast sync and full sync into a single function as they're very similar. Proper conditions to trigger a sumtree request and some checks on receiving it.
|
||
|---|---|---|
| .hooks | ||
| api | ||
| chain | ||
| config | ||
| core | ||
| doc | ||
| grin | ||
| keychain | ||
| p2p | ||
| pool | ||
| pow | ||
| src/bin | ||
| store | ||
| util | ||
| wallet | ||
| .gitignore | ||
| .travis.yml | ||
| Cargo.toml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| grin.toml | ||
| LICENSE | ||
| README.md | ||
| rustfmt.toml | ||
Grin
Grin is an in-progress implementation of the MimbleWimble protocol. Many characteristics are still undefined but the following constitutes a first set of choices:
- Clean and minimal implementation, aiming to stay as such.
- Follows the MimbleWimble protocol, which provides great anonymity and scaling characteristics.
- Cuckoo Cycle proof of work (at least to start with).
- Relatively fast block time (a minute or less, possibly decreasing as networks improve).
- Fixed block reward, both over time and in blocks (fees are not additive).
- Transaction fees are based on the number of UTXO created/destroyed and total transaction size.
- Smooth curve for difficulty adjustments.
To learn more, read our introduction to MimbleWimble and Grin.
Status
Grin is still an infant, much is left to be done and contributions are welcome (see below). Check our mailing list archives for the latest status.
Contributing
To get involved, read our contributing docs.
Find us:
- Chat: Gitter.
- Mailing list: join the ~MimbleWimble team and subscribe on Launchpad.
Getting Started
To learn more about the technology, read our introduction.
To build and try out Grin, see the build docs.
Philosophy
Grin likes itself small and easy on the eyes. It wants to be inclusive and welcoming for all walks of life, without judgement. Grin is terribly ambitious, but not at the detriment of others, rather to further us all. It may have strong opinions to stay in line with its objectives, which doesn't mean disrepect of others' ideas.
We believe in pull requests, data and scientific research. We do not believe in unfounded beliefs.
Credits
Tom Elvis Jedusor for the first formulation of MimbleWimble.
Andrew Poelstra for his related work and improvements.
John Tromp for the Cuckoo Cycle proof of work.
J.K. Rowling for making it despite extraordinary adversity.
License
Apache License v2.0.