Given Dan and company's inability take care of the little things when they matter most (like coordinating the upgrade of exchanges) their total lack of business acumen

That leaved me a bad taste also...
One week before snapshot he states he will focus the last week to coordinate the upgrade off the exchanges...
And after snapshot he just confirms that bittrex (I suppose the same is true for others,bter(?)) was not individually  informed and they should know about it because 1 month prior we made a buzz about this news...
If we had 50 exchanges that support us I could  understand it,  but we have only six (poloniex,btc38,bittrex,bter,yunbi,metaexhange)...
With this logic he shouldn't care informing any exchange prior snapshot...

PS I believe that exchanges in reality knew of course about the migration.  But  we gave them the opportunity to blame us for the luck of communication/migration... If bm had sent them only one fu#$% email before snapshot (2 minutes "work") they would not even have the chance to do it...

PS2 I agree with almost everything clout has said...

Quote from: hadrian on October 18, 2015, 12:05:04 pm

I'm curious to know what you've tried so far. In the most recent mumble session bytemaster suggested using the CLI software if you're having trouble as a result of having many keys to process.

edit:
https://github.com/bitshares/bitshares-2/releases/download/v2.15.286/BitShares-2.15.286-66c18c6-win64-cli-tools.exe

Above is the download link for the CLI from the release page.

First I tried to import in openledger, everything seemed to work fine, I could see my old 0.9.3c wallet-account imported in openledger with all its balances

after I closed the wallet and reopened it, the account was there but with no balances and no "history" at all, I tried to restore the 3mb backup but the account was empty too, Itried to reimport the keys in another browser but I gave up after one and half day  of "Loading balance claims..."

CLI gives me the same error message luckybit gets in this thread https://bitsharestalk.org/index.php/topic,19205.0.html but I just saw a new reply from cube, Im going give it a try...

 

I had the same issues until I created the brainkey and confirmed  it.... then all accounts showed up!

The guy that played fuzzy sounded just like him ... good job casting crew!

 

lol lol
I couldn't stop laughing man 

 

so that mean I have lost all collateral for my shorts from bts1!
great!

look what they are posting on poloniex trollbox!

londonwhale: mindphlux, is dumping: http://imgur.com/du63Pkl

Quote from: liondani on October 16, 2015, 11:16:31 am

Is it a problem if we are running our seed-nodes on our VPS on a local---rpc-endpoint like this?:

./witness_node --rpc-endpoint=127.0.0.1:1776

why are many suggesting: 0.0.0.0

for example:
./witness_node --rpc-endpoint=0.0.0.0:1776. 

?

rpc-endpoint will open up the rpc port eg for your cli-wallet. This is not the right port.  It should be p2p-endpoint

./witness_node --p2p-endpoint=0.0.0.0:1776

This means other peers can connect to your seed.

I started my seed node 185.25.22.21:1776 located in Greece
using this command:

./witness_node --rpc-endpoint 127.0.0.1:1777 -s 104.236.144.84:1776 --p2p-endpoint 0.0.0.0:1776

after -s (on our example 104.236.144.84:1776) you can put any seed-node you are confident it is on the main-chain  and properly started.
any suggestions/comments are welcome... 


PS If instead 0.0.0.0 after --p2p-endpoint we would put another address, would it not work?

waiting for your votes   

get_witness liondani
{
  "id": "1.6.48",
  "witness_account": "1.2.376",
  "last_aslot": 0,
  "signing_key": "BTS7WngKXi3p6Ui1Zn41tK6mfSkH6H3TYVWbr6nNHbEQ5xUrzL19j",
  "vote_id": "1:59",
  "total_votes": 0,
  "url": "https://bitsharestalk.org/index.php/topic,6406.msg245698.html#msg245698",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}