---------- - page 5. | Bitcointalksearch.org

wonko

full member

Activity: 155

Merit: 100

Hey guys, I bought some sha256 shares and have been running them for several weeks now. Would love to report on it and also get some feedback from mintsy themselves.

I purchased 90 day SH256 minings shares. After a few weeks of mining the ROI is 143 days. This is a guaranteed loss. i'm interested if Mintsy will do something extra for us? If we I can edit my review

It's been running a while now so even if luck does come into play I don't see how I'll earn my money back. Hopefully Mintsy will comment or change their service but in the meantime I highly recommend that people do not invest.

alani123

legendary

Activity: 2422

Merit: 1451

Leading Crypto Sports Betting & Casino Platform

Quote from: efire54 on May 29, 2015, 10:32:26 AM

What is it? Huh

Contract 100gh (OMG - 1200gh max Grin

)
Income 0 coin, pool - MZC Mining Pool.

Also have a 100 Gh/s contract. Mine spikes at 22 Th/s for a second today but overall it's the same. Unstable hashrate and payouts, same from day 1.

efire54

hero member

Activity: 574

Merit: 504

What is it? Huh

Contract 100gh (OMG - 1200gh max Grin

)
Income 0 coin, pool - MZC Mining Pool.

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

Quote from: bitsolutions on May 17, 2015, 08:09:01 PM

I would like to know how a proxy could give out a nonce2len larger than the upstream pools they connect to.
It would appear whoever made this proxy fucked that up big time.
You are basically going to be mining on garbage because of this and won't failover, this would be why the miners would be mining but the renter was getting no pool side credit and no hashrate was showing up.
Mintsy should probably comp mining rig operators that they took refunds from since the hashrate was being provided but mintsy was not giving the hashrate to the renter due to messed up internal settings.

In more than one support ticket I pointed out that Mintsy should be comping people in this scenario and the tickets were simply closed. I'm not sure if there just simply aren't enough resources to attend to maintaining this site but the banners are all over Cryptsy, amongst other places, and it just doesn't work right. Seems like its time to either hire some more devs or shut 'er down.

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

Well it appears the UNO pool is now offline. No word on whether it's merged with any of the other SHA coins, but I'd like to see Mintsy follow iSpace's lead and merge UNO with all the other SHA coins.

EDIT: We've moved our altcoin mining to MMPool and iSpace until Mintsy can get things sorted out with pools and proxy.

bitsolutions

sr. member

Activity: 261

Merit: 257

I would like to know how a proxy could give out a nonce2len larger than the upstream pools they connect to.
It would appear whoever made this proxy fucked that up big time.
You are basically going to be mining on garbage because of this and won't failover, this would be why the miners would be mining but the renter was getting no pool side credit and no hashrate was showing up.
Mintsy should probably comp mining rig operators that they took refunds from since the hashrate was being provided but mintsy was not giving the hashrate to the renter due to messed up internal settings.

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

Hm we have another problem here:

As of 5/15 UNO is merge mined with BTC. However the Mintsy UNO pool appears to be in operation. Not sure what this means but the UNO network did hit 1.2 Ph/s at one point. I know the Mintsy pool is no longer finding blocks...

I also have not seen a response on the PPC pool being stuck for close to 7 weeks now.

alani123

legendary

Activity: 2422

Merit: 1451

Leading Crypto Sports Betting & Casino Platform

Quote from: ThePhwner on May 16, 2015, 03:37:57 PM

I'm hoping you can clarify this a bit - you mentioned that payouts some days are less than what 100 Gh/s should earn... but you are also mining at PPLNS pools... I'm mining with my own hardware so the Mintsy contracts aren't an issue for me, so much as the proxy and it not working with certain pools. Not to mention if you're mining the Altcoin pools whether you'll make the PPS amt of BTC or equivalent is also a gamble, again factoring in that Mintsy pools use a PPLNS model.

I'm using the contract's hash power, not pointed to external pools. I figured that mining to external pools wasn't ideal since my workers there were going offline often. Support agent I got a reply from was trying to be helpful, but I'm not blaming him/her since I guess there's no way for support agents to fix such issues.

I'm still giving mitsy the benefit of the doubt though, hopefully they'll find a way to fix serious issues soon.

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

Quote from: alani123 on May 16, 2015, 03:07:23 PM

Quote from: bitsolutions on May 16, 2015, 12:58:45 PM

Quote from: ThePhwner on May 16, 2015, 11:00:40 AM

1. Antpool SHA-256 does not work.
2. WestHash SHA-256 did not work last time we tried ~ 2 weeks ago
3. F2Pool SHA-256 works properly but double reports hashrate.
--I have seen this with rentals too. I cannot see what pool renter picks but some rentals show well over the speed of the rig.

Out of all of these the only one that doesn't make sense is Antpool as that's overall a pretty standard pool, could be an IP block or something like that but I haven't had issues like this there before.
Westhash/Nicehash will depend a lot on the proxy implementation but it is by far the hardest pool to get a proxy working properly due to obvious reasons.
The F2Pool bug is just a flaw in how the proxy handles share validation, now that I think about it a renter might be able to exploit this type of bug and get free hashpower(depending on proxy implementation details).

It also didn't work for me. I didn't bother contacting support as slush's pool worked and it's no difference to me. Thing is, my hashrate has been REALLY unstable. When mining in an external pool my workers went offline very often even when I had 100% of my hashrate allocated there. So I ended up pointing all my hashrate at mintsy's pool, but it's still really unstable. I was hoping that the payouts would at least be consistent, 100 Gh/s (the rate I paid for) would have been making 0.001 BTC. I understand that the hashrate can be unstable, but if it keeps like that, I'm not even going to come close to what I paid for the plan. Every payout I get each day has been well below what 100 Gh/s could have mined. Some days I don't even get a payout at all.

I like the idea of buying mining contracts that can be pointed to external pools, but so far, I'm not really having a great experience with mintsy.

I'm hoping you can clarify this a bit - you mentioned that payouts some days are less than what 100 Gh/s should earn... but you are also mining at PPLNS pools... I'm mining with my own hardware so the Mintsy contracts aren't an issue for me, so much as the proxy and it not working with certain pools. Not to mention if you're mining the Altcoin pools whether you'll make the PPS amt of BTC or equivalent is also a gamble, again factoring in that Mintsy pools use a PPLNS model.

alani123

legendary

Activity: 2422

Merit: 1451

Leading Crypto Sports Betting & Casino Platform

Quote from: bitsolutions on May 16, 2015, 12:58:45 PM

Quote from: ThePhwner on May 16, 2015, 11:00:40 AM

1. Antpool SHA-256 does not work.
2. WestHash SHA-256 did not work last time we tried ~ 2 weeks ago
3. F2Pool SHA-256 works properly but double reports hashrate.
--I have seen this with rentals too. I cannot see what pool renter picks but some rentals show well over the speed of the rig.

Out of all of these the only one that doesn't make sense is Antpool as that's overall a pretty standard pool, could be an IP block or something like that but I haven't had issues like this there before.
Westhash/Nicehash will depend a lot on the proxy implementation but it is by far the hardest pool to get a proxy working properly due to obvious reasons.
The F2Pool bug is just a flaw in how the proxy handles share validation, now that I think about it a renter might be able to exploit this type of bug and get free hashpower(depending on proxy implementation details).

It also didn't work for me. I didn't bother contacting support as slush's pool worked and it's no difference to me. Thing is, my hashrate has been REALLY unstable. When mining in an external pool my workers went offline very often even when I had 100% of my hashrate allocated there. So I ended up pointing all my hashrate at mintsy's pool, but it's still really unstable. I was hoping that the payouts would at least be consistent, 100 Gh/s (the rate I paid for) would have been making 0.001 BTC. I understand that the hashrate can be unstable, but if it keeps like that, I'm not even going to come close to what I paid for the plan. Every payout I get each day has been well below what 100 Gh/s could have mined. Some days I don't even get a payout at all.

I like the idea of buying mining contracts that can be pointed to external pools, but so far, I'm not really having a great experience with mintsy.

bitsolutions

sr. member

Activity: 261

Merit: 257

Quote from: ThePhwner on May 16, 2015, 11:00:40 AM

1. Antpool SHA-256 does not work.
2. WestHash SHA-256 did not work last time we tried ~ 2 weeks ago
3. F2Pool SHA-256 works properly but double reports hashrate.
--I have seen this with rentals too. I cannot see what pool renter picks but some rentals show well over the speed of the rig.

Out of all of these the only one that doesn't make sense is Antpool as that's overall a pretty standard pool, could be an IP block or something like that but I haven't had issues like this there before.
Westhash/Nicehash will depend a lot on the proxy implementation but it is by far the hardest pool to get a proxy working properly due to obvious reasons.
The F2Pool bug is just a flaw in how the proxy handles share validation, now that I think about it a renter might be able to exploit this type of bug and get free hashpower(depending on proxy implementation details).

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

To summarize my personal observations with external and Mintsy pools:

1. Antpool SHA-256 does not work.

2. WestHash SHA-256 did not work last time we tried ~ 2 weeks ago

3. F2Pool SHA-256 works properly but double reports hashrate.
--I have seen this with rentals too. I cannot see what pool renter picks but some rentals show well over the speed of the rig.

4. The PPCoin pool looks stuck. Even when I pointed hash to it, it showed no accepted shares or change in the hash of the pool.

5. The other SHA-256 Mintsy pools appear to work well. We use ACoin, MazaCoin, Unbreakable, and Unobtainium regularly.

BitJohn

hero member

Activity: 826

Merit: 1001

@Bit_John

Quote from: ThePhwner on May 16, 2015, 07:54:19 AM

Quote from: malickie on May 15, 2015, 10:36:24 PM

I bought a scrypt cloud miner from mintsy and sadly a Lot of External sites I point at do not function at all. suprnova, nicehash/westhash etc. So I went and just pointed at their own servers and so far so good there. Just wish I could point the miner at different altcoins than mintsy has listed. Pretty much when I figured out that issue I have just had the miner pointed at Litecoin in hopes that I will come out ahead of what I spent.

Have you tried the iSpace pools? Just curious. There seems to be a pretty large list of external pools that don't work. It might make sense to restrict or disable this functionality until the proxy is functioning as it should.

I have put a group of testers on some of the pools mentioned. If you have a list of pools beyond what is posted already that you want me to figure out why its not mining list them here and we will see what the issue is. I am currently using multipool.us which is working with my contracts.

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

Quote from: malickie on May 15, 2015, 10:36:24 PM

I bought a scrypt cloud miner from mintsy and sadly a Lot of External sites I point at do not function at all. suprnova, nicehash/westhash etc. So I went and just pointed at their own servers and so far so good there. Just wish I could point the miner at different altcoins than mintsy has listed. Pretty much when I figured out that issue I have just had the miner pointed at Litecoin in hopes that I will come out ahead of what I spent.

Have you tried the iSpace pools? Just curious. There seems to be a pretty large list of external pools that don't work. It might make sense to restrict or disable this functionality until the proxy is functioning as it should.

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

Quote from: bitsolutions on May 15, 2015, 07:15:57 PM

Quote from: ThePhwner on May 15, 2015, 12:25:48 PM

They were not failing over. This was the subject of 2 tickets which were simply closed after several days. For a few weeks the proxy seemed to be working, but we had 2 rental where the proxy messed up, the renter got nothing, we still had to pay our end of the fee, and lost all the mining time.

That's pretty bad, if an upstream pool connection fails the proxy should either fail all the connections to a backup or cut all its downstream connections so the miners failover to backups. They also shouldn't rely on upstream hash-rate validation as it could be inaccurate due to extremely high diff or other weird pool issues it should be measured on the downstream miner connection side.

Agree completely. There's a lot of potential here for a great service but these are the exact weaknesses that caused us to pull all but 600 Gh/s. It's kind of fun to have a little hash there to mine some alts (MZC has been doing well past couple days) but it's not worth the effort to put our larger rentals up and risk this scenario. My guess is that digitalX doesn't have a big team behind Mintsy but its frustrating that these core issues remain unacknowledged and unaddressed.

We are used to the models/functions of the other sites, where true failover occurs if the renter picks a bad pool, etc.

I'd like to see these issues addressed, as again, there is potential here. Especially for anyone who likes a few alts on the side.

malickie

member

Activity: 92

Merit: 10

I bought a scrypt cloud miner from mintsy and sadly a Lot of External sites I point at do not function at all. suprnova, nicehash/westhash etc. So I went and just pointed at their own servers and so far so good there. Just wish I could point the miner at different altcoins than mintsy has listed. Pretty much when I figured out that issue I have just had the miner pointed at Litecoin in hopes that I will come out ahead of what I spent.

bitsolutions

sr. member

Activity: 261

Merit: 257

Quote from: ThePhwner on May 15, 2015, 12:25:48 PM

They were not failing over. This was the subject of 2 tickets which were simply closed after several days. For a few weeks the proxy seemed to be working, but we had 2 rental where the proxy messed up, the renter got nothing, we still had to pay our end of the fee, and lost all the mining time.

That's pretty bad, if an upstream pool connection fails the proxy should either fail all the connections to a backup or cut all its downstream connections so the miners failover to backups. They also shouldn't rely on upstream hash-rate validation as it could be inaccurate due to extremely high diff or other weird pool issues it should be measured on the downstream miner connection side.

lobogil

member

Activity: 62

Merit: 10

Hey ThePhwner - you could take some of your own crap support advice:

and then:

Quote from: ThePhwner

Maybe you can choke on your Twinkies.

So happy to see this ex-BAN admin scammer getting the same treatment he gave to many others on his scam pool Cheesy

ThePhwner

hero member

Activity: 616

Merit: 500

something something Bitcoin

Quote from: bitsolutions on May 14, 2015, 05:54:47 AM

Quote from: ThePhwner on May 11, 2015, 12:36:26 PM

A few things I'd like to note after using the beta and official product for several weeks:

1. The proxy remains inconsistent. Some pools do not work at all (Antpool) and some pools report double hash rate (F2Pool).

Odd that Antpool doesn't work. I've seen the f2pool issue myself and know why it happens on certain poorly designed stratum proxies, it basically indicates a pretty bad flaw in the share validation logic which might even relate to the Antpool issue.

Quote from: ThePhwner on May 11, 2015, 12:36:26 PM

2. The current system is unfair to rig owners. There's no way to communicate with the renter, and in multiple instances, we've had a renter pick a bad pool. Then we get dinged with the fee, and the lost mining time. Per Mintsy policy, the decision to refund is based 100% on hash rate. In a system where owner and renter can communicate, we can provide support to ensure the renter is mining.

Hopefully your rigs were failing over, if they are not then Mintsy's proxy must have some serious issues.

They were not failing over. This was the subject of 2 tickets which were simply closed after several days. For a few weeks the proxy seemed to be working, but we had 2 rental where the proxy messed up, the renter got nothing, we still had to pay our end of the fee, and lost all the mining time.

BitJohn

hero member

Activity: 826

Merit: 1001

@Bit_John

Quote from: jonnybravo0311 on May 14, 2015, 09:00:13 AM

Quote from: ThePhwner on May 11, 2015, 12:36:26 PM

2. The current system is unfair to rig owners. There's no way to communicate with the renter, and in multiple instances, we've had a renter pick a bad pool. Then we get dinged with the fee, and the lost mining time. Per Mintsy policy, the decision to refund is based 100% on hash rate. In a system where owner and renter can communicate, we can provide support to ensure the renter is mining.

I like the way MRR handles this scenario. If the renter's pool goes offline, or fails, and the renter doesn't have a backup, MRR effectively looks dead to your gear. Your gear then fails over to whatever pools you've setup as backups so you as the rig owner don't lose any time.

For example, I've got my rigs setup like this:

pool 1 - stratum+tcp://us-east01.miningrigrentals.com:3333#xnsub
pool 2 - stratum+tcp://us-central01.miningrigrentals.com:3333#xnsub
pool 3 - stratum+tcp://104.131.12.128:9332

So, if a renter screws up, my gear fails over to my p2pool node.

@BitJohn, setting up something similar on Mintsy would be extremely useful, and alleviate the problem reported by ThePhwner.

I will get with the developers and see what we can do.

Topic: ---------- - page 5. (Read 27390 times)