Pages:
Author

Topic: MinerGate Pool [PPS 1.5%] [PPLNS 1%] ZEC-ETH-ETC-BTC-LTC-BCN-XMR-QCN-FCN-XDN - page 32. (Read 306083 times)

full member
Activity: 333
Merit: 100
Have not been able to withdrawal MCN all day.
full member
Activity: 199
Merit: 100
Dashboard has stopped updating. Shows all miners as offline.
legendary
Activity: 1364
Merit: 1000
Payouts are back to normal for me.
newbie
Activity: 3
Merit: 0
Have 3 web widgets. 10 to 60 active workers. No Dashboard update for more than a day!
legendary
Activity: 2450
Merit: 1002
Are BTC payouts fixed now or they still all done by manual request?
legendary
Activity: 1364
Merit: 1000
Still haven't received payout for XMR, XDN and MCN for the last 16hours ?

What's going on ?

Thx
hero member
Activity: 605
Merit: 500
Hi folks,

  Thanks for pointing out DSH issue – we've updated pool today.
  We are listening to your comments and try our best to implement your suggestions.

--
Best regards,
MinerGate.com

Thank you
legendary
Activity: 1078
Merit: 1059
FROSTING
Hi folks,

  Thanks for pointing out DSH issue – we've updated pool today.
  We are listening to your comments and try our best to implement your suggestions.

--
Best regards,
MinerGate.com
full member
Activity: 149
Merit: 100
minergates has manny issues.

          a lot of Orphaned   blocks from yesterday.

          BCN, XMR, FCN, QCN, XDN, MCN & INF8. issue
          AEON, DASH no issue

  you can check the Orphaned    in minergates "pool stats" menu and navigate thru different coin and blocks


   all issue are fixed now.

   May be on general attack to all cryptocoin's network because other pool are similar issues in this dates.
full member
Activity: 199
Merit: 100
My dashboard refuses to update since yesterday and it's not reporting the right number of workers.

should I be worried?  Huh
full member
Activity: 149
Merit: 100
minergates has manny issues.

          a lot of Orphaned   blocks from yesterday.

          BCN, XMR, FCN, QCN, XDN, MCN & INF8. issue
          AEON, DASH no issue

  you can check the Orphaned    in minergates "pool stats" menu and navigate thru different coin and blocks
full member
Activity: 333
Merit: 100
Its been 24 hours for my missing coins so I'm going to chalk it up as a loss and moving on.  Minergate is not to be trusted.
hero member
Activity: 605
Merit: 500
Note to Dashcoin miners!

Minergate is using an outdated daemon and refuses to reply to support messages from the dev team to fix the issue. For the health of the network, please consider moving your miners off Minergate and using one of the pools with latest code:

http://dsh.democats.org
https://www2.coinmine.pl/dsh/
http://dsh.extremepool.org/

Thanks guys
full member
Activity: 333
Merit: 100
Any reason why this hash is not yet confirmed even after 6 hours from minergate?

eeae9ffa9b76511f8111a7b116fb80dcbf716f5cc214cb9dda42461a98e51ea0

https://minergate.com/blockchain/dsh/transaction/eeae9ffa9b76511f8111a7b116fb80dcbf716f5cc214cb9dda42461a98e51ea0
sr. member
Activity: 384
Merit: 250
And on a side note I was told in an email that minergate would add BoolBerry to their list of minable coins... So, when is this gonna happen for fudges
sake?! I'm getting tired of all the empty promises (not just from minergate)

PS: enough with the P.O.S coins allready! P.O.S = Piece.of.Shit
hero member
Activity: 605
Merit: 500
Hello, can Minergate please fix their DSH Dashcoin issues and provide an explanation? https://bitcointalksearch.org/topic/m.9252417

Hi folks!

First of all, I use the latest version of dashcoind from 16 Sep on my pool. Here is the --version output:

Code:
> dashcoind --version
2014-Oct-20 10:18:48.631403 Starting...
2014-Oct-20 10:18:48.633060 dashcoin v1.0.2.358()
dashcoin v1.0.2.358()

Secondly the statement that MinerGate has moved to modified daemon code on 10/06/2014 is totally incorrect. CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE represents a base median value of block total transactions size and can be shifted forward. As you can see the current median of 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110 'malicious' block equals 23,142 bytes, which means it can contain up to 23 Kb of transactions. Real block size depends on the daemon's tx pool state - the mining pool have nothing to include into the block if it is empty. So, since this isn't correct, the remaining statements are incorrect also.

Lastly for whose benefit? Please answer what my pool will gain from this potential modification?

Instead of blaming the honest mining pool you should better ask the network maintainers to check the Dashcoin code.


Your pool is obviously not up to date. So tell us, what are your motivations?  Roll Eyes
hero member
Activity: 605
Merit: 500
nopedope89, please update your DASH pool.

Minergate is using an outdated daemon

here is how it should look:

  "majorVersion": 1,
  "minorVersion": 1,

here is how yours looks:

  "majorVersion": 1,
  "minorVersion": 0,

Please refer to the screenshots below:








full member
Activity: 333
Merit: 100
DSH withdrawals are failing currently.
slb
hero member
Activity: 598
Merit: 501
Hello, can Minergate please fix their DSH Dashcoin issues and provide an explanation? https://bitcointalksearch.org/topic/m.9252417

Hi folks!

First of all, I use the latest version of dashcoind from 16 Sep on my pool. Here is the --version output:

Code:
> dashcoind --version
2014-Oct-20 10:18:48.631403 Starting...
2014-Oct-20 10:18:48.633060 dashcoin v1.0.2.358()
dashcoin v1.0.2.358()

Secondly the statement that MinerGate has moved to modified daemon code on 10/06/2014 is totally incorrect. CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE represents a base median value of block total transactions size and can be shifted forward. As you can see the current median of 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110 'malicious' block equals 23,142 bytes, which means it can contain up to 23 Kb of transactions. Real block size depends on the daemon's tx pool state - the mining pool have nothing to include into the block if it is empty. So, since this isn't correct, the remaining statements are incorrect also.

Lastly for whose benefit? Please answer what my pool will gain from this potential modification?

Instead of blaming the honest mining pool you should better ask the network maintainers to check the Dashcoin code.


print_block 79399
block_id: <2019486df631cfc5e822c38069a57ffc27526820443933540635e4467d8fa5ac>
{
  "majorVersion": 1,
  "minorVersion": 0,

In which cases this version of a block is generated? All minergate's blocks have and majorVersion 1 and minorVersion 0.
legendary
Activity: 1078
Merit: 1059
FROSTING
Hello, can Minergate please fix their DSH Dashcoin issues and provide an explanation? https://bitcointalksearch.org/topic/m.9252417

Hi folks!

First of all, I use the latest version of dashcoind from 16 Sep on my pool. Here is the --version output:

Code:
> dashcoind --version
2014-Oct-20 10:18:48.631403 Starting...
2014-Oct-20 10:18:48.633060 dashcoin v1.0.2.358()
dashcoin v1.0.2.358()

Secondly the statement that MinerGate has moved to modified daemon code on 10/06/2014 is totally incorrect. CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE represents a base median value of block total transactions size and can be shifted forward. As you can see the current median of 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110 'malicious' block equals 23,142 bytes, which means it can contain up to 23 Kb of transactions. Real block size depends on the daemon's tx pool state - the mining pool have nothing to include into the block if it is empty. So, since this isn't correct, the remaining statements are incorrect also.

Lastly for whose benefit? Please answer what my pool will gain from this potential modification?

Instead of blaming the honest mining pool you should better ask the network maintainers to check the Dashcoin code.
Pages:
Jump to: