All committers have signed the CLA.

Hi @cryptokek, could you please also add an object like this one to KnownOrganizations? Thanks!

@bpierre - Sorry, accidentally closed this. I have created the known org as you requested. See pull #1534 I believe everything is correct. Let me know if I need to do anything.

@cryptokek the Ethereum address seems to be pointing at a token contract, instead of an organization. What URL are you using to access it?

@bpierre
https://client.aragon.org/#/kek/
the contract itself is 0x3fa400483487A489EC9b1dB29C4129063EEC4654

Or are you asking for kek.aragonid.eth ? <-- that's what our sub ens domain is.

Thanks!

the contract itself is 0x3fa400483487A489EC9b1dB29C4129063EEC4654

This is the token contract (associated to the Tokens app), the organization address is 0xe00F7B744AB8333d64ed940dd36ed9398D8eDBD2.

Or are you asking for kek.aragonid.eth ? <-- that's what it's currently set as.

Exactly yes! Do you intend to point cryptokek.eth to 0xe00F7B744AB8333d64ed940dd36ed9398D8eDBD2 (the token) or 0xe00F7B744AB8333d64ed940dd36ed9398D8eDBD2 (the DAO)?

@bpierre Well that's the thing, I hadn't really decided yet. Most likely the DAO, but I'm not sure it would change "kek.aragonid.eth" on this webpage -> client.aragon.org/#/kek" to -> Cryptokek.eth (On the top left of the webpage). I also know Aragon connect might make all of this trivial in the medium term as I plan on hosting the DAO on my own server and potentially building it with Connect. (similar to 1hive's DAO)

@bpierre - Works for me! Merge please :)