The second was copied from google images and belongs to a Korean teen band:
https://www.google.com/search?q=exo+logo So I tried to do something, but it was not good.
The only thing that seems to be made by a designer is gvans.
If it is not choice, the devs should hire a professional designer.
As stated in the first post of the logo thread - we are not going to use the corean band logo. Well some of them might not be professionally created but in the end what counts is the design itself. If it fits the purpose (and is not a trademark of something else etc) I - personally - do not care how much effort have been needed to create it.
Nevertheless I highly appreciate the suggestions we got so far. I think we can pick a good logo from them.
And yes, our current graphic is a self generated vector graphic.
just an idea,
a skinnable wallet!!
just choose the look yourself!
someone can sell skins for exo too!
The community will have the ability to make other wallets or redesign ours once we release the full source for it. We will possibly distribute good ones through our website as well.
Well I programmed a lot and used sqlite many times. It's easy to use, no question. But in this context I do not see an advantage? Sure, you can overwrite blocks but why would you do that / you would not get any advantage of doing that. You can alter a sql database as well if you want. Please tell me why you think it would be an advantage to use.
I am short in time again, so I just wanted to say: We made a first investigation of the error logs and found something very interesting already.
Normally all blocks looked like (we filtered the log's output to get faster the important details):
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:19393]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:64428]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
2014-05-23 10:45:40
saved last block to file.
new block started with id=112
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
[censored_ip:60639]: got a block is done [ID=111] inchain-Hash: F8165176D3BD5BAB145716C985F9BF1836E96CD1E691BA3EC6E6CC3FF82A9557
=>everything is synced.
but then 10 minutes later we get:
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 7E4C1EE55F19E02CA8B52F699A82D954784F56E3CF47374DA1BA5567ED1451AA
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 8D34A4716350A9AF1EEAD7956431EF81DD683E71F67B60D9A8EE131566790FA5
[censored_ip:46727]: got a block is done [ID=112] inchain-Hash: DDF522B95899F0B27DC9712A6D31D61D35122AE33CBC558E48D09AA7F122639D
[censored_ip:19393]: got a block is done [ID=112] inchain-Hash: 4EC5B570FF11C959E0182C04DD781503FA60354AD79DD48B1E9E0E43104A5120
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 1F9AF8F595BAA938426613B9164DA894476569DE9826A6C9D6B7E89BFBBC3EBA
[censored_ip:64428]: got a block is done [ID=112] inchain-Hash: 2568679456023FB7BA3CDA589E4FAC75C0FA9E29700F7589325AFCCFD943B22E
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 5905BA7D8EC26FC326320537AB28F356EE599565D072746F19A816F660A4EB1C
[censored_ip:5312]: got a block is done [ID=112] inchain-Hash: 18B573F57F322615F1648C92AFAAC62774B860046C0CF96DB76DE0D9FC44910E
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: EDFAD98D8DCD0A1A7052113A3C6EEA78186D8873226648005DF29023FA168A4C
[censored_ip:27139]: got a block is done [ID=112] inchain-Hash: DBCE079FAB408756240BB1F91B7FD313BB7D5DBB434905A555030D5010EC5CCB
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 41213322E94C84306181D4D767F0268C79499DF02EC76498E657097450C2250E
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 5905BA7D8EC26FC326320537AB28F356EE599565D072746F19A816F660A4EB1C
2014-05-23 10:55:40
saved last block to file.
new block started with id=113
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 4EC5B570FF11C959E0182C04DD781503FA60354AD79DD48B1E9E0E43104A5120
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 9B6741A9594D392927290850E3BF768DE14A6E5B11025A08AC4FFFF2839ECFB8
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: 84995B9AEBC3B3AD05E621D7D8E6082D8164217620D20C0AA3095E12D0389358
[censored_ip:60639]: got a block is done [ID=112] inchain-Hash: F8655D24C7886B191CE8E37760F9BCD9431FAD97233E3C5F6E60E2F7417936F5
...
invalid hash@block@load
---
only two nodes got the same result. Everything else is totally different. Now, that is strange. We thought of a transaction might be processed by the one node and not by the other somehow. But then again we would only have 2 different results PLUS they should sync up again. After a binary comparision of 112.block on all nodes we could see that they are completly equal except in one detail - the block's hash value. And we found the "invalid hash@block@load" line as well.
So, this just as a background information for you if you are interested in some technical details
We will nail the problem further down this evening and probably tomorrow. We now know where the problem is roughly. It seems to be a minor issue (might be caused by a caching step) but we have to locate it exactly first. I'll give a further status notification in about 24 hours. If it is indeed only a smaller problem then we can still have the launch early June.
best regards
#edit: As stated, we want to have a stable client and don't try to rush the launch. This just as an addition to the quora/exo discussion. Also, we are quite fast until now in comparision to what we have reached in my opinion. We don't have a professional company/ paied team plus we have fulltime reallife jobs;) By the way I was not able to follow the quora movement since I did not find time for something like that. So I cannot tell anything about their quality etc.