-
Notifications
You must be signed in to change notification settings - Fork 85
Exchange FAQ
This document provides general information to exchanges that are considering listing Grin.
- General info
- Technical
- Economics
- Governance
- Community
- Exchange related integration
- Exchange info
- Legal
https://github.com/mimblewimble/grin/blob/master/doc/intro.md
Done.
https://github.com/mimblewimble/grin/milestones
Original MimbleWimble whitepaper: https://download.wpsoftware.net/bitcoin/wizardry/mimblewimble.txt
Andrew Poelstra's MimbleWimble whitepaper: https://download.wpsoftware.net/bitcoin/wizardry/mimblewimble.pdf
https://github.com/mimblewimble/grin
https://github.com/mimblewimble/grin-miner
https://github.com/mimblewimble/grin-pm
and many more in the mimblewimble github org.
Keybase: https://keybase.io/team/grincoin
Gitter: https://gitter.im/grin_community/
Forum: https://forum.grin.mw/
Security Process: https://github.com/mimblewimble/grin/blob/master/SECURITY.md
There is no foundation or any kind of legal entity running this project. Grin is run by volunteers and is sustained by donations.
The one and only Ignotus Peverell.
We rely solely on donations to keep working on the project. See https://grin.mw/funding
No ICO.
No airdrop.
No premine.
No founder's reward.
Grin is mostly backed by individuals volunteering their time to the project. While companies are more than welcome to provide resources and participate in Grin's development, no single company is meant to influence the decision making process which is based on meritocracy.
No CEO.
On the development side, key contributors to the core project can be found in the Github contribution graph.
UTXO-based model, similar to Bitcoin, with the caveat that there are no addresses supported at the protocol level.
1 minute
Similar to Bitcoin, we use PoW mining and Nakamoto consensus.
Yes, no different to Bitcoin, inherent of PoW mining.
Block time is 1 minute, the main grin wallet waits for 10 block confirmations before it enables reusing a transaction output.
No smart contracts but we can still support some logic on top of simple transaction.
Not at the moment, but we may support Confidential Assets in the future.
Only one.
No bonuses.
- Calculate tx_weight first:
MAX(-1 * (num_inputs + 4 * (num_change_outputs + 1), 1)
- (+1 covers a single output on the receiver's side)
- Calculate fee:
tx_weight * 0.001 GRIN
No accounts.
Block Header structure documented here
See Grin Transactions Explained, Step-by-Step and What’s inside a Grin Transaction File?.
Dual PoW based on Cuckoo Cycle. See How to mine Grin and Grin's Proof of Work.
https://github.com/mimblewimble/docs/wiki/Community-projects#explorers
Every six months for the first two years.
The crowdfunding campaign for the security audit is finalized. A company has been found to carry out the audit and they are meant to start on it soon. More details to be added soon. At the same time, Jean-Philippe Aumasson volunteered to do an independent security audit (read his report here).
Security Process: https://github.com/mimblewimble/grin/blob/master/SECURITY.md
- Detailed documentation https://github.com/mimblewimble/grin/tree/master/doc/api
- Invocations and responses
- Protocol: RPC? HTTP?
- Demo for interacting using Node APIs
9 decimals.
1 grin per second forever. Each block contains a 60 grins reward and the block confirmation time is targetted at 1 minute per block.
Ownership and distribution
The total supply is unlimited. See our Monetary Policy on why.
There is no token distribution plan beyond the coinbase reward to the miner that mines a valid block.
We have no projected token price.
We have no market cap projections.
We have no plans to increase the value of the token. We do however make continuous updates to the Grin protocol and the supporting tools and services, which in turn may affect demand.
- How to set up a node
- Hardware requirements
- Steps to set up a mainnet (docker preferred)
- How to build a transaction and signing it offline.
- Transaction structure
- Broadcasting a signed transaction
- Instructions for how to interact with wallet or node with the private keys stored separately.
- Address
- How to generate large amount of addresses
- Validating an address
- Demonstrations
- Mapping such that: 256bit private key -> public key -> address
GRIN |
---|
ツ |
---|
png | svg |
---|
Wallet Guide: https://github.com/mimblewimble/docs/wiki/wallet-user-guide#listening-via-tor
Tor gives users addresses, which allow support of payment proofs. It is more private and user-friendly to configure than HTTP listeners.
No. Tor is only used for the wallet-to-wallet interaction, not by the node.
No. Extra ports will not be publicly opened.
It sits idle in the background waiting to be used for depositing or withdrawing.
A diverse group of people are involved in Tor, and it is funded and used by governments, universities, and other reputable organizations.
See "Who uses Tor?": https://2019.www.torproject.org/about/torusers.html
See the Tor Project's sponsors: https://www.torproject.org/about/sponsors/
Some (not all) exchanges and their supported transaction method (not completed yet):
Exchanges | Tor | HTTP | File |
---|---|---|---|
Bittrex | ✓ | ||
Gate.io | ✓ | ||
Hotbit | ✓ | ||
Kucoin | ✓ | ||
MXC | ✓ | ||
Poloniex | ✓ | ✓1 | |
Tradeogre | ✓ |
Legend Table
✓ | supported |
✓1 | only deposit supported |
Some (not all) exchanges and their "Know Your Customer" details (not completed yet):
Exchanges | Non-KYC | Partial | KYC |
---|---|---|---|
Bittrex | ✓ | ||
Gate.io | |||
Hotbit | ✓ | ||
Kucoin | ✓ | ||
MXC | |||
Poloniex | ✓ | ||
Tradeogre | ✓ |
Note: "Partial" is defined as having no KYC under a certain withdrawal limit.
Some (not all) exchanges and their contact details:
Exchanges | Help Desk | Telegram | ||
---|---|---|---|---|
Bittrex | [Link] |
|
||
Gate.io | support@mail.gate.io | gate.io | ||
Hotbit | [Link] | @Hotbit_news | ||
Kucoin | [Link] | KuCoin Exchange | @kucoincom | |
MXC | service@mxc.com |
|
||
Poloniex | @Poloniex | |||
Tradeogre | @tradeogre |
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