-
Notifications
You must be signed in to change notification settings - Fork 85
burrrata edited this page Dec 6, 2018
·
33 revisions
- An implementation of MimbleWimble
- Both are outputs-based, PoW. See also Grin for Bitcoiners
- ☑ Contracts
- ☑ Pruning
- ☐ Identity, like bitauth
- ☑ Something something SNARK/STARK/NIZKPs
- ☑ Cross chain atomic swaps, ☑ multisig, ☑ time locks, ☑ lightning network,
- ☑ Payment channels
- ☑ hidden nodes / onion routing
- ☑ Scripting - clean & native w/ tiny limits
- ☑ Dandelion privacy mixed with tx cut through (already implimented)
- HTTP GET /v1/chain on a public peer node or see the grin explorers and scanners in the Community Projects section.
- Target mean block time is 1 block per 60 seconds. The size is limited by transaction "weight", though there is also a hard cap on the order of tens of MB.
- Very well thanks to transaction cut-through!
- Check out the Build Docs
- See this rolling list of community created wallets
- You can also [build] your own node(https://github.com/mimblewimble/grin/blob/master/doc/build.md) and run your wallet through the CLI.
- No. Grin aims to be a useful cryptocurrency that allows people to transact just like they do with cash, but online.
- No.
- You can attach recipts or order IDs through the slate that comes with every tx
- Every tx is only known to the sender and the recipient and the network merely verifies that tx are valid. If you're part of a tx you can log that info and use it to prove that a tx is valid and thus definitely happened.
- On Testnet2 fees were 0.8% on a transaction of 1.0 coins.
- A GPU with >3.7 GB of very fast DRAM is the best bet, like the 1080TI. But don't invest Grin-specific equipment yet! There's not even a final beta released, and much can still change.
- https://github.com/mimblewimble/grin-miner
- https://www.grin-forum.org/t/grin-mining-faq-all-of-the-answers-to-your-mining-questions/71/2
- See this conversation.
- See the privacy primer
That's great!
- The wiki documentation can always use improvement. Anyone is free to just jump in and edit that directly.
- We also have more technical documentation that is not on the wiki. Here you can’t edit directly, but submit a pull request that is then peer reviewed before merged. A good place to start is to review the technical documentation table of contents and improve where you can.
- If you want to get your hands dirty, you’re also free to just submit a PR to any area of the project, the list of open issues is probably a good place to start. Also check that there are not any open pull requests that conflict to avoid duplication of effort.
- Look at the open pull requests.
- There is a bi-weekly dev meeting every other Tuesday at 21:00 UTC (on odd-numbered weeks) on the
/dev
channel on Gitter. Feel free to listen in. - @yeastplume is publishing a weekly progress update of his work in the forum, usually on Fridays.
- Preparing for main net launch! Check out the issues and milestones
- Jan 15th
Basics
- Getting Started
- User Documentation
- MimbleWimble
- FAQ
- Planned releases (Roadmap)
- Code of Conduct
Contributing
- Contributing Guide
- Code Structure
- Code coverage and metrics
- Code Reviews and Audits
- Adding repos to /mimblewimble
Development
Mining
Infrastructure
Exchange integrations
R&D
Grin Community
Grin Governance
Risk Management
Grin Internals
- Block Header Data Structure
- Detailed validation logic
- P2P Protocol
Misc