[2.1 MHS] Experimental virtual scrypt mining

[matt4054]

Hello,

I am looking for a first tester for my experimental virtual scrypt mining project.

Mining hashrate would be about 1200 KHS and the tester can keep the proceeds from the mining tests. Currently the alpha interface should already allow you to dynamically switch pools, so you can mine any coins and follow profitability.

There is currently only one slot available, but more to come.

Watch this topic for more info. Thanks for your interest!

[1715066854]

1715066854

[1715066854]

1715066854

[1715066854]

1715066854

[1715066854]

1715066854

[1715066854]

1715066854

[1715066854]

1715066854

[matt4054]

Reserved...

[Mitchell]

I don't get what you want from us. Do you want a miner? Do you want someone to use your miner? Do you want us to mine for you? What?

[matt4054]

I want to provide a virtual mining service, i.e. you buy hash power for a certain duration and you control the workers, you can configure them to use any pool you want with any worker name.

I have put together a proof-of-concept interface and I want some feedback from an experimented alt-coin miners who is still believing in the possible profitability of scrypt-mining, of course. For the firsts tests, testers will not have to pay anything and will be rewarded with their mining profits, so it's small pocket money - yay - of course their is no SLA or guarantee of any kind.

Does that explain the project more clearly?

[Epicblood]

I think this is a pretty good Idea,
Wouldn't mind testing it for you.

[Mitchell]

Yes, it does. Now we get what you want from us Well I bet you can find someone. Free money, who doesn't want that?

[matt4054]

I think this is a pretty good Idea,
Wouldn't mind testing it for you.

Nice :-)

First to answer, so you get the first slot, I guess it's fair enough.
I will give you 120 minutes for the 1st test, and then I will redefine the slots according to the demand.

(EDIT: test rounds will be 60 min until further notice)

Currently, the pool settings work like this:

• Pool 0: static, will be used until you dynamically set pool 1
• Pool 1: dynamic, will be used instead of pool 0 as soon as you set it from the web interface

Please PM me the static settings you want for pool 0, i.e. URL, worker and password.

It is cgminer based, so you can use stratum+tcp:// format URLs.

Does that work for you?

[Epicblood]

I think this is a pretty good Idea,
Wouldn't mind testing it for you.

Nice :-)

First to answer, so you get the first slot, I guess it's fair enough.
I will give you 120 minutes for the 1st test, and then I will redefine the slots according to the demand.

Currently, the pool settings work like this:

• Pool 0: static, will be used until you dynamically set pool 1
• Pool 1: dynamic, will be used instead of pool 0 as soon as you set it from the web interface

Please PM me the static settings you want for pool 0, i.e. URL, worker and password.

It is cgminer based, so you can use stratum+tcp:// format URLs.

Does that work for you?

yea, that works fine. Let me just grab my usual settings and I'll PM to you

[Mitchell]

Just a quick tip.
I advice everyone using/trying this server to create a worker with a password which they don't use.

[matt4054]

Just a quick tip.
I advice everyone using/trying this server to create a worker with a password which they don't use.

Obviously a reasonable and sound advice

Traffic is *not* over HTTPS yet. Use dummy values. Create a sandbox account. Etc.

[mrm0]

Just a quick tip.
I advice everyone using/trying this server to create a worker with a password which they don't use.

While it is a good generic advice, I do not really see the point here. What harm can come out of everyone knowing my miner worker user and pass? The only outcome I can see is others mining for me, which they are certainly welcome to do.. ;-) Am I missing something obvious?

To the OP. An interesting idea, but If you have hashrate at your disposal, why not use it yourself?

[Mitchell]

Just a quick tip.
I advice everyone using/trying this server to create a worker with a password which they don't use.

While it is a good generic advice, I do not really see the point here. What harm can come out of everyone knowing my miner worker user and pass? The only outcome I can see is others mining for me, which they are certainly welcome to do.. ;-) Am I missing something obvious?

To the OP. An interesting idea, but If you have hashrate at your disposal, why not use it yourself?

There are people who re-use their password constantly (yes even in the BitCoin World). If OP has their miner password, he COULD get access to other accounts. Also, miner names (aka. nicknames) are often re-used too. You see where I am going?

[matt4054]

Just a quick tip.
I advice everyone using/trying this server to create a worker with a password which they don't use.

While it is a good generic advice, I do not really see the point here. What harm can come out of everyone knowing my miner worker user and pass? The only outcome I can see is others mining for me, which they are certainly welcome to do.. ;-) Am I missing something obvious?

To the OP. An interesting idea, but If you have hashrate at your disposal, why not use it yourself?

There are people who re-use their password constantly (yes even in the BitCoin World). If OP has their miner password, he COULD get access to other accounts. Also, miner names (aka. nicknames) are often re-used too. You see where I am going?

Yes, and it will never be repeated / reposted enough times...

So the next slot is starting at 20:10 UTC for those interested.

[mrm0]

Just a quick tip.
I advice everyone using/trying this server to create a worker with a password which they don't use.

While it is a good generic advice, I do not really see the point here. What harm can come out of everyone knowing my miner worker user and pass? The only outcome I can see is others mining for me, which they are certainly welcome to do.. ;-) Am I missing something obvious?

To the OP. An interesting idea, but If you have hashrate at your disposal, why not use it yourself?

There are people who re-use their password constantly (yes even in the BitCoin World). If OP has their miner password, he COULD get access to other accounts. Also, miner names (aka. nicknames) are often re-used too. You see where I am going?

Yes, and it will never be repeated / reposted enough times...

So the next slot is starting at 20:10 UTC for those interested.

OK, I'll bite.

@bitcoininformation: I see.

[matt4054]

Next slot available at 21:30 UTC

[Epicblood]

Miner works and is hashing away at about 1258 KH/s

[matt4054]

Miner works and is hashing away BTCBTCBTCBTCBTCBTC

Thanks for the positive feedback.

I'm working hard to build a real interface, like nodejs.

If there is enough interest, I have many interesting plans to carry on and scale this project.

The idea is to "recycle" somewhat my GPUs, I have a potential 8500 KHS to deploy.

[jdebunt]

i wouldn't mind testing it for you either , if you still have slots available

[matt4054]

i wouldn't mind testing it for you either , if you still have slots available

Thanks for your interest in testing.

You get the 21:30 - 22:30 UTC timeslot.

Please PM me your static worker config for the test (you may want to use a sandbox account, see above). I will reply you with the details.

Next available timeslot starts at 22:30 UTC.

[jdebunt]

Thanks for your interest in testing.

You get the 21:30 - 22:30 UTC timeslot.

Please PM me your static worker config for the test (you may want to use a sandbox account, see above). I will reply you with the details.

Next available timeslot starts at 22:30 UTC.

PM sent