Vote - Remove getwork support

[bonesoul]

We do an initial implementation of getwork support (https://github.com/CoiniumServ/CoiniumServ/blob/2d4c8624dbfe156a0400683a4afed55a1a7154a1/src/CoiniumServ/Server/Mining/Getwork/GetworkService.cs) that's barely functional (actually mining &finding blocks is working but it can not communicate with rest of the systems).

I'm not aware of anyone that uses getwork support which is a quite old protocol. Today defacto standart is stratum. I'd like to also remove the support for getwork if the community agrees.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5402353-vote-remove-getwork-support?utm_campaign=plugin&utm_content=tracker%2F401667&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F401667&utm_medium=issues&utm_source=github).

[bonesoul]

my own vote: +1

[Caberhagen]

+1 remove Am 20.10.2014 15:25 schrieb "Hüseyin Uslu" notifications@github.com:

my own vote: +1

— Reply to this email directly or view it on GitHub https://github.com/CoiniumServ/CoiniumServ/issues/608#issuecomment-59752957 .

[djkyno]

+1

[Marty19]

+1

[artbatista]

Vote +1

Remove

[frndxyz]

+1

[ahmedbodi]

-1 we need it if we're having merged mining

[bonesoul]

Anyone using the merged-mining yet? is merged mining only available via getblock?

[ahmedbodi]

depends on how you implement it. if you implement the merged mining directly into the pool backend then you dont need getwork if youre going to do it seperately such as how most others do it then you need getwork