Does anyone else have withdrawals problems.
I made bitcoin withdrawal on Sunday and status says confirmed / cleared.
I HAVEN'T RECEIVED ANYTHING IN MINE BITCOIN ADDRESS !! ??
Topic: [Official] Mintsy.co Thread **150% more SHA hashing for the same price RETRO!** (Read 10297 times)
May 19, 2015, 02:23:06 AM
May 15, 2015, 09:11:29 AM
Okay...now three blocks found 
May 15, 2015, 06:27:36 AM
I am very disappointed I rented 4 rigs, only 1 worked. I had 0khs for the 3 others. I changed pool and try everything even recreated a worker to see if it's not coming from this but nothing to do I can't rent anything from now....
Tickets are slow to respond (last ticket took 4 day to have a reponse that was : every rent is manually checked and refund if not correct....) that's not really what I call a working service. If even rig rental does not work I really don't want to pay 59$ for a contract....
Tickets are slow to respond (last ticket took 4 day to have a reponse that was : every rent is manually checked and refund if not correct....) that's not really what I call a working service. If even rig rental does not work I really don't want to pay 59$ for a contract....
Let me look into this for you. Contracts are services provided by us rentals are obviously others renting you their equipment so there is a difference in service level. Let me find out exactly what happened in your case. PM me your ticket #
May 15, 2015, 02:47:10 AM
Last bitcoinblock ..... 13.05 ??!!
May 14, 2015, 07:31:54 AM
I am very disappointed I rented 4 rigs, only 1 worked. I had 0khs for the 3 others. I changed pool and try everything even recreated a worker to see if it's not coming from this but nothing to do I can't rent anything from now....
Tickets are slow to respond (last ticket took 4 day to have a reponse that was : every rent is manually checked and refund if not correct....) that's not really what I call a working service. If even rig rental does not work I really don't want to pay 59$ for a contract....
Tickets are slow to respond (last ticket took 4 day to have a reponse that was : every rent is manually checked and refund if not correct....) that's not really what I call a working service. If even rig rental does not work I really don't want to pay 59$ for a contract....
May 09, 2015, 02:56:08 PM
Got any coupon codes for bitcointalk members 
?
?Well since you asked I'll throw up this coupon code it will work for the next few days MINEMINTSY
Good for 10% off a mining contract.
Yay you rock! Just bought a bunch
I'll report on how it does. May 08, 2015, 06:13:36 AM
Got any coupon codes for bitcointalk members ?
?Well since you asked I'll throw up this coupon code it will work for the next few days MINEMINTSY
Good for 10% off a mining contract.
May 07, 2015, 11:12:24 PM
Got any coupon codes for bitcointalk members ?
? May 07, 2015, 07:14:16 PM
Sha-256 Contracts have been increased. No Price changes.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
Thank you very much
I am guessing that made a bunch of folks day!
Our pleasure. I have updated the top of this thread with more screenshots and tidied up some areas.
May 06, 2015, 08:27:21 AM
Sha-256 Contracts have been increased. No Price changes.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
Thank you very much
I am guessing that made a bunch of folks day!
May 05, 2015, 11:08:12 PM
Sha-256 Contracts have been increased. No Price changes.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
Thank you very much
I am guessing that made a bunch of folks day!
May 05, 2015, 02:25:30 PM
Sha-256 Contracts have been increased. No Price changes.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
Thank you very much
May 05, 2015, 12:38:31 PM
Here's what my stats look like on MRR now that I switched to Mintsy:
I think the most telling factor here is - and I don't have it in the screenshot - that the number of workers reported keeps changing. I have 6 S3s pointed here. Yet the number of workers changes from 6 to 3 to 2 to 5 to 1 to 3 etc. I also notice that the miners are falling back to my backup pool (which happens to be my p2pool node). So now when I look at stats, I see all kinds of weirdness. My p2pool node goes from having about 1.5TH/s down to having 600GH/s depending I guess on whether or not the workers are showing up in MRR... the mintsy.co status page shows somewhere around 545GH/s total. MRR shows anywhere between 0 and 100GH/s... weird, right?
When I switch my miners back to point at my p2pool node, MRR is all happy again... I get the 2.75TH/s.
I think the most telling factor here is - and I don't have it in the screenshot - that the number of workers reported keeps changing. I have 6 S3s pointed here. Yet the number of workers changes from 6 to 3 to 2 to 5 to 1 to 3 etc. I also notice that the miners are falling back to my backup pool (which happens to be my p2pool node). So now when I look at stats, I see all kinds of weirdness. My p2pool node goes from having about 1.5TH/s down to having 600GH/s depending I guess on whether or not the workers are showing up in MRR... the mintsy.co status page shows somewhere around 545GH/s total. MRR shows anywhere between 0 and 100GH/s... weird, right?
When I switch my miners back to point at my p2pool node, MRR is all happy again... I get the 2.75TH/s.
May 05, 2015, 12:00:03 PM
I've got a question regarding pointing my own gear here. I have 6 S3s that are updated with the latest firmware and xnsub patched cgminer binaries. My primary pool is MRR, secondary is mintsy.co. On MRR, I have configured my miners to point to mintsy.co when they are not rented.
They absolutely refuse to connect and hash here when they are not rented on MRR. However, if I just set them to mine here directly (by changing up the pool config in the S3 configuration), they work fine.
Has anyone else experienced this problem?
S3 -> MRR -> mintsy = fail
S3 -> mintsy = success
Do I need to I cannot put the #xnsub in the URL in my MRR pool config like this:
https://i.imgur.com/g8nc42k.png
I've got it directly in the S3 config...
https://i.imgur.com/Uzg5SLb.png
Maybe that's what I'm missing? Unfortunately I can't test yet because my gear is currently rented on MRR...
By the way, the 3 month SHA256 contract I purchased is doing just fine... makes me keep my eyes on the alt coins... maybe I'll spread some of it to the other coins and see if I can get some good trade prices on cryptsy...
EDIT: MRR does not allow you to put the #xnsub in the pool config... it throws an error when you try to save the pool configuration
They absolutely refuse to connect and hash here when they are not rented on MRR. However, if I just set them to mine here directly (by changing up the pool config in the S3 configuration), they work fine.
Has anyone else experienced this problem?
S3 -> MRR -> mintsy = fail
S3 -> mintsy = success
https://i.imgur.com/g8nc42k.png
I've got it directly in the S3 config...
https://i.imgur.com/Uzg5SLb.png
By the way, the 3 month SHA256 contract I purchased is doing just fine... makes me keep my eyes on the alt coins... maybe I'll spread some of it to the other coins and see if I can get some good trade prices on cryptsy...
EDIT: MRR does not allow you to put the #xnsub in the pool config... it throws an error when you try to save the pool configuration
Is MRR subscribing to extranonce? If not it will not work properly.
My miners are all connected to MRR with the #xnsub parameter (as shown in my previous post's screenshot). Here they are happily hashing away on my p2pool node:
I'll switch them to Mintsy... and I'll edit this post in about 30 minutes to show you what happens.
May 05, 2015, 10:56:30 AM
Sha-256 Contracts have been increased. No Price changes.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
If you had a 100 Gh/s contract before, it is now 250 Gh/s. If you had a 1 Th/s contract, it is now 2.5 Th/s.
We are also giving you credit for the time used on your old contract. 60% of the time you have already used in your existing contract will be appended to the expiration date of your contract.
This means if you have had your contract for 30 days already, then 18 more days will be added to the end of your contract to extend it's expiration date.
May 03, 2015, 11:03:18 AM
I've got a question regarding pointing my own gear here. I have 6 S3s that are updated with the latest firmware and xnsub patched cgminer binaries. My primary pool is MRR, secondary is mintsy.co. On MRR, I have configured my miners to point to mintsy.co when they are not rented.
They absolutely refuse to connect and hash here when they are not rented on MRR. However, if I just set them to mine here directly (by changing up the pool config in the S3 configuration), they work fine.
Has anyone else experienced this problem?
S3 -> MRR -> mintsy = fail
S3 -> mintsy = success
Do I need to I cannot put the #xnsub in the URL in my MRR pool config like this:
I've got it directly in the S3 config...
Maybe that's what I'm missing? Unfortunately I can't test yet because my gear is currently rented on MRR...
By the way, the 3 month SHA256 contract I purchased is doing just fine... makes me keep my eyes on the alt coins... maybe I'll spread some of it to the other coins and see if I can get some good trade prices on cryptsy...
EDIT: MRR does not allow you to put the #xnsub in the pool config... it throws an error when you try to save the pool configuration
They absolutely refuse to connect and hash here when they are not rented on MRR. However, if I just set them to mine here directly (by changing up the pool config in the S3 configuration), they work fine.
Has anyone else experienced this problem?
S3 -> MRR -> mintsy = fail
S3 -> mintsy = success
I've got it directly in the S3 config...
By the way, the 3 month SHA256 contract I purchased is doing just fine... makes me keep my eyes on the alt coins... maybe I'll spread some of it to the other coins and see if I can get some good trade prices on cryptsy...
EDIT: MRR does not allow you to put the #xnsub in the pool config... it throws an error when you try to save the pool configuration
Is MRR subscribing to extranonce? If not it will not work properly.
May 01, 2015, 02:08:08 PM
I've got a question regarding pointing my own gear here. I have 6 S3s that are updated with the latest firmware and xnsub patched cgminer binaries. My primary pool is MRR, secondary is mintsy.co. On MRR, I have configured my miners to point to mintsy.co when they are not rented.
They absolutely refuse to connect and hash here when they are not rented on MRR. However, if I just set them to mine here directly (by changing up the pool config in the S3 configuration), they work fine.
Has anyone else experienced this problem?
S3 -> MRR -> mintsy = fail
S3 -> mintsy = success
Do I need to I cannot put the #xnsub in the URL in my MRR pool config like this:
I've got it directly in the S3 config...
Maybe that's what I'm missing? Unfortunately I can't test yet because my gear is currently rented on MRR...
By the way, the 3 month SHA256 contract I purchased is doing just fine... makes me keep my eyes on the alt coins... maybe I'll spread some of it to the other coins and see if I can get some good trade prices on cryptsy...
EDIT: MRR does not allow you to put the #xnsub in the pool config... it throws an error when you try to save the pool configuration
They absolutely refuse to connect and hash here when they are not rented on MRR. However, if I just set them to mine here directly (by changing up the pool config in the S3 configuration), they work fine.
Has anyone else experienced this problem?
S3 -> MRR -> mintsy = fail
S3 -> mintsy = success
I've got it directly in the S3 config...
By the way, the 3 month SHA256 contract I purchased is doing just fine... makes me keep my eyes on the alt coins... maybe I'll spread some of it to the other coins and see if I can get some good trade prices on cryptsy...
EDIT: MRR does not allow you to put the #xnsub in the pool config... it throws an error when you try to save the pool configuration
April 18, 2015, 02:57:38 PM
Hello BitJohn!
My sha contract with digital mintsy is useless as will not recover much b4 expiry. Can u give me some options
of external pooly which r more profitable and how to change it on the platform.
Thank U
Setup is pretty easy just choose the external pool option. I would try something like Multipool.us which will jump onto a few SHA alt coins. Though your correct most SHA contracts are hard to make ROI at current prices. Though if your smart and the price rebounds the investment might work out.
April 18, 2015, 06:17:29 AM
Hello BitJohn!
My sha contract with digital mintsy is useless as will not recover much b4 expiry. Can u give me some options
of external pooly which r more profitable and how to change it on the platform.
Thank U
April 16, 2015, 08:38:36 PM
I've got a question around the approximate expected contracts' return on investment. I'm getting a little confused with how hashing power units are used interchangeably within some of these contracts (MH/s, kH/s, GH/s etc...)
For instance, if we all agree 1 MH/s = 1,000 kH/s, then a 28,000 MH/s Scrypt contract would equate to 28,000,000 kH/s. Now, using a number of different litecoin mining calculators, 28,000,000 kH/s would generate approximately 672LTC per day which as much as I'd like to think it's true, it sounds way too over inflated for the small 0.026BTC required investment for such contract.
Am I missing something out here within my calculations? Apologies in advance if the answer is very straight forward.
Thanks
For instance, if we all agree 1 MH/s = 1,000 kH/s, then a 28,000 MH/s Scrypt contract would equate to 28,000,000 kH/s. Now, using a number of different litecoin mining calculators, 28,000,000 kH/s would generate approximately 672LTC per day which as much as I'd like to think it's true, it sounds way too over inflated for the small 0.026BTC required investment for such contract.
Am I missing something out here within my calculations? Apologies in advance if the answer is very straight forward.
Thanks
Well 28,000 MH/s would generate something like that but that is a ton of hashing power.
Jump to: