Robrigo - EOS Detroit introduces discussion about exchange integration:
“Bringing this up here for transparency - I was contacted by the Openledger DEX team regarding problems with their exchange integration. Looked into it and it appears that AO-008 blacklisted their exchange's hot wallet account. Account => ha4timrzguge:
ECAF Order of Emergency Protection
Putting Moti and their CEO Ronny Boesing in touch. This seems like a case where the exchange may have mistakenly been caught in the crossfire. Is this setting a precedent whereby exchanges can be disrupted by ECAF orders if funds are moved to an exchange? I don't think this would fly with any of the big exchanges. :)
My recommendation to them is to use an account that actually names their exchange... then it would probably be less likely for this to happen in a future ECAF investigation.”
Katie | @eosasia | myeoskit.com makes an announcement from Block.one Developer Relations team:
“Hi guys, we are planning to do a major update to the EOSJS library hosted here: EOSIO/eosjs on the 2nd of October that is not backwards compatible.
We will not be releasing details on the update until then because we are still ironing out some things, but we would like to remind you it is very important that if you’re using EOSJS for any of your projects, make sure that you have version locking in you package.json locked down to v. 16.0.8 like this:
"eosjs": “^16.0.8” to make sure that your application doesn’t break.
Please spread the word to your peers as well”
Bohdan CryptoLions writes that the blacklist was updated:
[a35b4aafe884cc039b8382873a67dfd0720d1ba7b3a98ff17ebfbe50ec89aa5e]
Transaction:
b23d2520055a7c8fcd83195d5b0e71e78dd8ae5778abe3f69c0bfedd797516ec