@chris-mercer
I'll like to work on this

Hey @Myestery, are you working on this? What is the progress?
@chris-mercer, I would like to take it if @Myestery is not working on it. I have some experience working on Uniswap connector: hummingbot/gateway#136.

Hey @VPashkov
Yeah I already started working on it and hope to finish soon.
You'll see the updates as I drop them here

@VPashkov @Myestery hi, we will discuss about this bounty assignment based on developer experience

This not assigned yet.

@nikspz Ok. I hope that @Myestery will be able to finish it since they already started, but I'm ready to pick this up if needed.

Would also offer to take it if needed.

I can work on this and get it in asap

Assigned to @vic-en, please be informed:

• Since you’re assigned to this bounty exclusively, please keep us informed on your progress over the next few days
• Please review and follow contribution guidelines (https://hummingbot.org/developers/contributions/)
• Please review the checklist after PR submitted (https://hummingbot.org/developers/contributions/#checklist)
• Let us know if you don’t have time, and we will unassigned and keep it open for other devs
• Only one dev can be assigned to one bounty

Thanks for your contribution!

Hi @vic-en do you have an expectation of when this bounty will be submitted for code review? Thanks in advance - Chris

@chris-mercer This week. As soon as I'm done testing.

@chris-mercer Pr created

@chris-mercer Pr created

Great I dropped a brief review on naming convention stuff so its clear for the decentralized users on Ethereum Classic. Can you make the edits that make sense. Sorry if some don't, I'm not super familiar with the codebase yet- hence the bounty. :)

Also I made a note of the stable RPC endpoint to use.

NCP is submitted:
https://snapshot.org/#/hbot-ncp.eth/proposal/0x5face44f80c3c0d3d290da1a6973ec0c030a483023a4647ff91e4339af085770