Frequently Asked Questions - Zcoin XZC
Payouts are processed every hour on the hour.
The default minimum payout is 1 XZC. You can change the minimum payout to as low as 0.002 XZC using the "Settings" link located at the bottom of the pool dashboard or in top right menu.
The transaction (payout) fee is 0 XZC
The password is whatever you put as the stratum password argument in your mining software. Any stratum options added after the password are not part of the password.
- Ensure you are using the password you used in your mining software.
- Use the same password in all of your workers. Only one will be chosen as the correct password.
- Do not use commas in your password since they will be parsed as option delimiters.
- Some mining software such as ccminer require the arguments to be in a certain order to work properly.
The confirmations required are determined by the coin and serve to prevent funds from being used before being reasonably sure that they are valid and won't be orphaned. MintPond has no control over the number of confirmations required. In order to give funds earlier, MintPond would need to loan coins either from its own reserve or from the balance of other miners who have been encouraged to keep their coins in the pool via high payout fees. Since MintPond is not a bank or a lender, we do not award coins before they're available.
Rewards come from blocks mined. When a block is found your share of its reward is added to the "Unconfirmed" value in the Miner panel. When the block is confirmed the pool transfers your share of the reward to your "Balance". If the block is orphaned the pool loses the reward and the value is removed from "Unconfirmed". If your balance is 0 it's because a block has not been found yet and/or the block has not yet been confirmed and the reward amount is still immature.
The way your miner and the pool calculate hashrate are different. The miner has direct access to your actual hashing and so will be most accurate. The hashrate shown by the pool is an estimate based on the number of shares submitted at a particular difficulty over a period of time.
When you setup your mining software you can specify the worker name by appending it to the end of the username (wallet address) using a period to separate them. The miner name must be alphanumeric characters with no spaces and can contain dashes or underscores. (i.e. walletAddress.workerName)
Authentication failure can happen if you are not using a valid wallet address or your worker name or password uses invalid characters or are too long. Worker name and password may not be more than 20 characters. The worker name can contain alphanumeric characters, underscores and dashes. It may not contain any other special characters. If these constraints are not followed your authentication will fail.
In order to preserve bandwidth miners that are submitting too fast will be temporarily disconnected. If this is happening to you then your miner may be too fast for the initial difficulty. In this case try a higher port. If you are setting the difficulty manually via password options then the difficulty you have set is too low.
Each share submitted to the server by the mining software is approximately 200KB. The stratum will try to keep your software submitting at an average of 1 share per 20 seconds. This works out to about 1GB per day per connection.
With a typical hashing algorithm the server merely needs to assemble the same block header and hash it to verify that the share submitted by a worker is valid. This is a very fast and simple process for the server to handle. MTP on the other hand was designed to be ASIC resistant by using large amounts of memory and it would not be feasable to expect the server to reserve so much memory per worker to verify shares.
MTP gets around this by generating "proofs" that can be used to verify a share without having to use the large amounts of memory that were required to generate those proofs. The trade-off to this system is that the proofs are about 200KB in size. That may not sound like a lot but it can add up much quicker than the mere 0.1KB or so needed in typical algorithms.