Sort:  

Yes, Credo's contract code lacks of exception for such case. Probably the coder has not even knew about decentralized exchanges... no expierience in this area implies the team has to resolve this issue manually.

Hi Zack. Thank you for your response but for me it's little bit ridiculous. I know that you don't want to touch people money but after sending by Steward Credo tokens to you global address with transfer() function [instead of depositToken()] this is no longer our money as affected people or Steward money as the sender. These are your tokens because at least one person from EtherDelta should know the private key and will be able to transfer this. So theoretically you can wait a few weeks, months or years, maybe in this time everybody will forget about these Credo tokens and someone will sell them for Ethereum and in this way gain some nice money. Of course maybe you have the policy that people should not involve in the smart contracts or something so you can still make some cron job that will run at least once per day and send back every token that will be transferred to your global account instead of deposited. Then you still have people away from the core of the market and everything will be automated. I know that you probably don't want do to this because market is decentralized but be honest: currently is whole EtherDelta decentralized? Really? Orders are stored in the Ethereum network? Or rather decentralized are only results of the trades and orders are on one or few your servers?

Thank you, Zack! I think we have all the info now.

Coin Marketplace

STEEM 0.20
TRX 0.26
JST 0.039
BTC 99772.57
ETH 3596.28
USDT 1.00
SBD 3.10