-
Notifications
You must be signed in to change notification settings - Fork 4
FAQ
A blockchain protocol that provides privacy and scalability gains by verifying that all tx are valid without needing to store the entire history of the chain.
A lightweight implementation of the MimbleWimble protocol.
Both are output-based and use a PoW consensus model with a fixed Supply Cap.
- ☑ 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 implemented)
HTTP GET /v1/chain on a public peer node or check the Explorer
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 on the storage layer thanks to transaction cut-through! Slightly better than Bitcoin on transaction throughput but still not an order of magnitude better.
https://github.com/mwcproject/mwc-qt-wallet/releases
Check out the Build Docs.
See the official Webpage's Download Section.
The Wallets listener is configured to listen on localhost (127.0.0.1) by default.
If you want to receive over HTTP using port forwarding you may need to reconfigure your listener to accept connections from the "Outside world" first which is outlined in the linked document.
https://www.mwc.mw/mimble-wimble-coin-articles/emission-rate-changes
No.
Yes.
There was one, currently no future Airdrops are announced. Current Information can be found On the Webpage's Airdrop Section
- You can attach receipts 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.
- A GPU with >8 GB of very fast DRAM is the best bet, like the 1080TI. A perfect C31 Solver would have access to 20 GB of Ram according to lolliedieb, through creative tricks GPU's with >8GB Ram can mine C31 with good Fidelity.
There are multiple ones, some of which Include:
Yes, most Mining Software supports this.
Yes there are multiple pools availlable, see availlable Pools on the Webpage.
GrinGoldMiner has been confirmed to work with 8GB currently.
GPU will beat CPU in general.
A single 42-cycle in a graph of at least 2^30 nodes, i.e. a cycle of length 42.
The network can operate at a fairly high difficulty in order for blocks to be found on average every minute. To allow miners to contribute intermediate work, mining pools accept solutions that hash at a much lower difficulty. This is called a share. On average, a certain number of shares will result in finding a block. So if the network difficulty is D
and the mining pool difficulty is d
with D > d
, on average D/d
shares will be required for the pool to find a block.
Yes, measured as the number of nodes of the graph you find that single 42-cycle in. The lowest number of nodes that is allowed is 2^30, which we call cuckoo30. Graphs with more nodes in them require more memory and effort to solve, which is why we scale the difficulty with the size. For cuckooN the scaling factor is given by (N-1)*2^(N-30). This means cuckoo30 solutions are scaled by 29, cuckoo31 by 60, cuckoo32 by 124 etc.
The minimum size is currently 2^30, or cuckoo30. Solutions in graphs with larger nodes than the minimum threshold are also accepted. In the future, this threshold might be increased via soft forks.
I don’t get it, why does my Miner Software submit shares to the MWC node that are below what's accepted?
Mining pools will use the number of shares to estimate your graph rate and thus your payout.
That’s 1 Graph Per Second, i.e. trying one random graph in one second to see if it’s a valid solution.
On average you need to search 42 graphs to find a 42-cycle.
Also on average, you need to find diff/scale 42-cycles to solve a block, where
diff = current network difficulty, and
scale = (N-1) * 2^(N-30) for cuckooN cycles.
(e.g. 29 for cuckoo30, 60 for Cuckoo31, and 124 for Cuckoo32)
Finally, graphs per second is graphs per block divided by the blocktime in seconds.
Total Network GPS is then
gps = 42 * (diff/scale) / 60
As an example, let's assume:
- Everyone is mining cuckoo30;
- Current network difficulty is 241;
Then, the network GPS is 42 * 241/29 / 60 ~5.82.
If total network GPS is 5.82 in the above example, and I am currently mining at 0.582 GPS on my own, does that mean I can expect to win 10% of all blocks roughly?
Yes. You're then essentially contributing 10% of all the network mining power.
- Set
api_listen_interface = "0.0.0.0"
in yourMWC-wallet.toml
configuration file. - Ensure port 3415 is open on the device that is to receive MWCs.
Visit http://canyouseeme.org from your device and follow instructions.
Check that any firewalls set up on your device are letting through connections and that you have set up port forwarding on your router. Google "port forward" and the model and make of your router for further instructions. Some have also had success setting up mapping using the portmapper tool behind a router they don't know the admin password to.
After you’ve successfully mined your block, another 1000 blocks need to be found in order for your coinbase to mature. Prior to this occurring, the outputs cannot be spent.
These are transaction fees. You get paid for including a transaction into a block that you have successfully mined. If you run mwc-wallet outputs
you will see for which block that was, and can also check it on one of the block explorers.
That's great!
- See The Contributing File
- 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 tagged with "help wanted" is probably a good place to start. Also check that there are not any open pull requests that conflict to avoid duplication of effort.
Introduction
Sending Guides
Receiving Guides
- Accept Swap Offer - QT Wallet
- Receive via Atomic Swap - QT Wallet
- Receive via HTTP (NGrok) - QT Wallet
- Receive via HTTP (Port Forwarding) - QT Wallet
- Receive via HTTP (NGrok) - CLI Wallet
- Receive via Files - QT Wallet
- Receive via Files - CLI Wallet
- Receive via Files - Cold Wallet
- Receive via TOR - QT Wallet
- Receive via TOR - CLI Wallet
- Receive via Slatepack- QT Wallet