Pool Information
posted 11/11/2017 03:18:53 by vlad

To join the pool you can follow the Getting Started Guide. Feel free to click on the right-bottom Button if you have any question.

You may find more about the pool here.

For any issues and how we may better everything please use our Support Portal

Pool Features : 
  • Normal Fees : 3% (Special Event discount to be defined)
  • Protection by PoolProtect
  • Fully Redundant Infrastructure
  • 4 working on parallel stratum servers
  • 2 Active/Passive load balancers
  • Separate wallet server
  • Separate web-server
  • Separate database server
  • Separate redundant database server
  • Wallet protocol version used: 90040
  • DDoS protection
  • Daily backups - 4 slots per day
  • Servers in a professional datacenter in Europe (North America & Asia Servers coming soon !)

Frequently Asked Questions
posted 11/11/2017 03:17:09 by vlad
  • Q: When will I get paid?
  •  A: This pool uses the following payout system.

    Proportional (Prop) - The block reward is distributed among miners in proportion to the number of shares they submitted in a round. The expected reward per share depends on the number of shares already submitted in the round. 

  • Q: What is a orphan block?
  •  A: Coins generated by a block will not be available to you right away. They will take some time to be confirmed by the entire network before you are allowed to transfer them out of the pool. Usually coins have a confirmation set to 120. What that actually means: the network (not the pool) has to discover 120 additional blocks on top of the one found by the pool to confirm it. 

  • Q: What is estimated payout?
  •  A: Estimated payout is your estimated payout if a block is found at that time. This is an estimate according to your amount of shares submitted for the round(s). 

  • Q: What is a share?
  •  A: Finding blocks is not an easy task. Since it would take a really long time on some coins, finding a block is broken down into shares. Depending on the server side setting, each share can be a certain difficulty. The more difficult each share is to find by miners, the fewer total shares are required to eventually find a block. 

    On the server side, each share is checked against the coin daemon (a server side wallet with more features) if it is indeed a valid block solution. Every share computed has the potential to be a block solution. I will not go into details why this is, but rest assured that share estimates for blocks can sometimes be exceeded. In the long run though, shorter round with less shares than required will make up for those taking very long. 

    Keep in mind: shares are not blocks! Shares are part of a block and will count towards the block payout! 

    At times, you will see shares being rejected by the pool. This can happen if you try to send an outdated share right after a block was found. Stratum, a protocol used by a miner to request work from a server, is used for share submission and getting new work. It is very solid when it comes to avoiding rejects but they can still happen once in a while. 

    If you are seeing reject all the time, then something isn’t working right on your end. You may also notice that your hashrate on the pool website is not increasing while your invalid share count keeps climbing up. In that case turn off your miner and check your settings! 

  • Q: I am having problems connecting to the pool.
  •  A: Double check your settings against our getting started page.

  • Q: What are orphaned blocks?
    A: An orphaned block refers to a block that was originally accepted by the network (a part of the network, anyway) as a valid block with a valid hash and valid transactions.

    Due to the physical constraints of computers and the internet, a block that is solved by a miner and contributed to the network is not instantly propagated to the rest of the network. At minimum, it could take several seconds for data to transfer around the world. Due to this potential time lag, two miners may effectively simultaneously solve the same block. There will be nodes geographically closer to miner A than miner B, and vice versa, so the network will be temporarily split into two very similar but different chains, as the nodes broadcast to one another what they believe to be the most recently mined block.

    Eventually, one of the two chains will demonstrably have a greater proof-of-work than the other, and the nodes on the other chain will update/reorganize their blockchain records/database accordingly and begin to only accept transactions on the chain with the greater proof-of-work.

    Orphaned blocks are the legitimate blocks from the chain that lost out to the chain with a greater proof-of-work.

    If a transaction was reflected on the 'B' chain, in an orphaned block, but not the 'A' chain, then once the network subsequently is fully on the 'A' chain, that transaction from the B chain will revert to being unspent (or will have been subsequently mined on the 'A' chain). Spent outputs do not get lost on a 'B' chain, since the history of any 'B' chain spends is effectively erased once the network accepts the 'A' chain.

    (Note, I used 'A' and 'B' for example purposes only, with 'A' as the chain that ends up being the "true" chain, as demonstrated by its greater proof-of-work.)