Someone I know is planning an ICO for his offline company. He is considering launching an erc20 token on etherium which seems to be a popular option lately. Should he consider Bitshares for his ICO? Is Bitshares suitable, ready?

$ ./programs/witness_node/witness_node
..
921223ms th_a       application.cpp:233           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
921223ms th_a       application.cpp:438           startup              ] 13 N11websocketpp9exceptionE: Underlying Transport Error
Underlying Transport Error:
    {"what":"Underlying Transport Error"}
    th_a  application.cpp:236 reset_websocket_server
921223ms th_a       application.cpp:984           startup              ] 13 N11websocketpp9exceptionE: Underlying Transport Error
Underlying Transport Error:
    {"what":"Underlying Transport Error"}
    th_a  application.cpp:236 reset_websocket_server
rethrow
    {}
    th_a  application.cpp:438 startup
921223ms th_a       main.cpp:192                  main                 ] Exiting with error:
13 N11websocketpp9exceptionE: Underlying Transport Error
Underlying Transport Error:
    {"what":"Underlying Transport Error"}
    th_a  application.cpp:236 reset_websocket_server
rethrow
    {}
    th_a  application.cpp:438 startup
921406ms th_a       thread.cpp:115                ~thread              ] calling quit() on p2p
921406ms th_a       thread.cpp:160                quit                 ] destroying boost thread 140527597115136
921406ms p2p        thread.cpp:246                exec                 ] thread canceled: 9 canceled_exception: Canceled

    {}
    p2p  thread_d.hpp:461 start_next_fiber


Hi,
I imported my keys using cli commands and balances for my accounts show up in cli, but when I open gui and reload the page, it is still showing a spinning icon and says loading balance claims, no accounts show up in the gui.

./programs/witness_node/witness_node
3408061ms th_a       witness.cpp:86                plugin_initialize    ] witness plugin:  plugin_initialize() begin
3408061ms th_a       witness.cpp:96                plugin_initialize    ] key_id_to_wif_pair: ["BTS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
3408061ms th_a       witness.cpp:114               plugin_initialize    ] witness plugin:  plugin_initialize() end
3408061ms th_a       object_database.cpp:91        open                 ] Opening object database from /home/user/local/bitshares-2/witness_node_data_dir/blockchain ...
3411465ms th_a       object_database.cpp:97        open                 ] Done opening object database.
3411465ms th_a       db_management.cpp:125         open                 ] last_block->id(): 0002a8b4791ef4b8979d60df2a42f6a4f0b576db last_block->block_num(): 174260
3411465ms th_a       db_management.cpp:133         open                 ] 10 assert_exception: Assert Exception
head_block_num() == 0: last block ID does not match current chain state
    {}
    th_a  db_management.cpp:128 open
3411465ms th_a       db_management.cpp:133         open                 ] data_dir: /home/user/local/bitshares-2/witness_node_data_dir/blockchain
3411465ms th_a       application.cpp:400           startup              ] 10 assert_exception: Assert Exception
head_block_num() == 0: last block ID does not match current chain state
    {}
    th_a  db_management.cpp:128 open
rethrow
    {"data_dir":"/home/user/local/bitshares-2/witness_node_data_dir/blockchain"}
    th_a  db_management.cpp:133 open
3411465ms th_a       application.cpp:946           startup              ] 10 assert_exception: Assert Exception
head_block_num() == 0: last block ID does not match current chain state
    {}
    th_a  db_management.cpp:128 open
rethrow
    {"data_dir":"/home/user/local/bitshares-2/witness_node_data_dir/blockchain"}
    th_a  db_management.cpp:133 open
rethrow
    {}
    th_a  application.cpp:400 startup
3411465ms th_a       main.cpp:192                  main                 ] Exiting with error:
10 assert_exception: Assert Exception
head_block_num() == 0: last block ID does not match current chain state
    {}
    th_a  db_management.cpp:128 open
rethrow
    {"data_dir":"/home/user/local/bitshares-2/witness_node_data_dir/blockchain"}
    th_a  db_management.cpp:133 open
rethrow
    {}
    th_a  application.cpp:400 startup
3411465ms th_a       db_block.cpp:401              pop_block            ] head_id: 0002a8b57cf1832d33ebc4b1317bfc29c1708ecc head_block_num(): 174261
3411592ms th_a       db_block.cpp:401              pop_block            ] head_id: 0002a8b57cf1832d33ebc4b1317bfc29c1708ecc head_block_num(): 174261


Are there instructions anywhere on how we are to calculate and claim expected sharedrops from all the mergers and new BitShares clones? It is very confusing and I am yet to claim anything post merger in November. Clear instructions are needed.

http://blogs.wsj.com/moneybeat/2014/12/08/bitbeat-sec-fines-another-seller-of-unregistered-bitcoin-securities/

"The Securities Exchange and Commission said Monday that it had sanctioned an Oregon man for running unregistered trading venues for securities that used the virtual currencies bitcoin and litecoin."

Delegate team - bitcoiners

Introduction
After a great deal of consideration, hours of discussion and several nights of ‘sleeping on it’, we have decided to relaunch KeyID as new BitShares DNS DAC. We recognize that our community has been through quite a whirlwind as of late, and we are mindful of not causing additional concerns. To that end we will make every effort to present a clear picture of what we hope to achieve and why.

The Vision
We feel that there’s a strong case to be made for a ‘stand alone’ BitShares DNS DAC, which in all reality, is not fully independent from the main DAC, but coexists with it in a symbiotic relationship.  We recognize the importance of the strategic decision to form the BitShares Super DAC at this time, and the benefits that will inevitably bring to BitShares community.  At the same time, we feel there is so much room for development within the DNS space itself and huge potential for symbiosis and co-evolution of independent blockchains.

BitShares DAC diversity can only strengthen BitShares community,providing another playground for experimentation in organizational structures, business plans,and governance models.  Multiple BitShares DACs sub-communities may take different approaches and learn from, and collaborate with one another. BitShares DNS DAC will aim to reach a complementary development path with BitShares, each working on features beneficial to the other, but focusing on different applications and user groups within this large field.

BitShares DNS DAC will position as a “web 2.0” DAC, and may have a different regulation and oversight profile from BitShares super DAC, potentially providing some extra insulation from external threats.

We foresee BitShares DNS DAC accepting some BitAssets from the main BitShares DAC, such as BitUSD as payment for offered services, adding liquidity to the main BitShares DAC.

Our primary allegiance being to the BitShares community and vision, we are compelled by the possibilities of keeping the BitShares DNS dream alive in it’s own right and seeking out areas of collaboration between the chains.

Immediate goals:

• Seek broad consensus from the community based on the merits of this proposal.
• Seek agreement on pushing out KeyID blockchain end-of-life a month or more into the future to allow adequate preparation for re-launch as BitShares DNS and to reduce disruption to existing participants.
  
• To continue listing KeyID’s DNS tokens on exchanges past November 5, as “proto-shares” in the upcoming BitShares DNS until the new DAC is launched.
  
• Give community members the opportunity to take a position and make a choice on whether they wish to participate in the project based on the new plan.
  
• Discuss blockchain symbiosis.
  

Midterm goals:

• Discuss organizational and funding considerations
  
• Assemble team with all the necessary skills and expertise to preparate smooth and secure launch of the new DNS DAC.
  
• Write new BitShares DNS White Paper
  

Come with us! Lets build the “Web 2.0” DAC!