My goal is to suggest_brain_key using curl. Help was an example that I expected would function similar. Thus far I've been issuing curl requests to the witness node socket. I've not thought to query the CLI wallet socket. Does each app have a distinct set of functions to return queries for? I have made the assumption that Help, Info, About and suggest_brain_key were supplied by the witness node.

Done.
I also included the links and info to cryptofresh. Let's see what the big cheese says now, as usual I'll keep you guys filled in.

I can understand how demoralizing and time consuming this has been with Apple. Thanks for continuing to push it.

[...] I think it's safe to say if transactions weren't being processed the indication would be more obvious.

Please note: without any seed nodes accepting connections, the BitShares network is essentially invisible to new nodes attempting to connect, without manual and informed intervention. Obviously no transactions happening then.

Currently, it is conceivable to systematically DDOS individual witness nodes until none  (or is it only <11) remain to advance the chain state due to their inability to resync the blockchain following disconnect, given zero seed or known peer nodes which are actively synced and accepting connections.

@bytemaster, et al. devs: This is a series issue that needs to be resolved by analyzing the failed seed nodes (likely peer nodes are similarly impacted) identifying the root cause and issuing a patch or guidance on existing node re-configuration.   

Respectfully as always,
Fox

Peer Plays is having a crowdfunding on Friday (announced last week). It's based on Graphene.

http://peerplays.com/ (SSL not functioning)

• Built a new node from tag 2.0.160328 on Ubuntu 15.10
• It builds fine, but does not sync the network
• Used the two seed nodes provided by Xeroc above, but they fail to handshake:

2016-05-03T12:33:43 p2p:thread invoke for method load_configuration   load_configuration ] generating new private key for this node                     node.cpp:4404
2016-05-03T12:33:43 p2p:thread invoke for method load_configuration trigger_p2p_network_ ] Triggering connect loop now                  node.cpp:988
2016-05-03T12:33:43 p2p:thread invoke for method add_node trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43 p2p:thread invoke for method connect_to_endpoint  connect_to_endpoint ] node_impl::connect_to_endpoint(208.66.16.68:43192)                  node.cp$
2016-05-03T12:33:43 p2p:thread invoke for method add_node trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43 p2p:thread invoke for method connect_to_endpoint  connect_to_endpoint ] node_impl::connect_to_endpoint(208.66.16.68:45967)                  node.cp$
2016-05-03T12:33:43 p2p:thread invoke for method add_node trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 208.66.16.68:43192: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:60 error_handler                     peer_connection.cpp:260
2016-05-03T12:33:43   p2p:connect_to_task display_current_conn ] Currently have 1 of [20/200] connections                       node.cpp:1731
2016-05-03T12:33:43   p2p:connect_to_task display_current_conn ]    my id is e1101e7df032cd84410e8344c0114e7b588b064fe7068e6e553e70d0c3d7bd77b5                 node.cp$
2016-05-03T12:33:43   p2p:connect_to_task display_current_conn ]    handshaking: 208.66.16.68:45967 with 00000000000000000000000000000000000000000000000000000000000000$
2016-05-03T12:33:43   p2p:connect_to_task trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43   p2p:connect_to_task schedule_peer_for_de ] scheduling peer for deletion: 208.66.16.68:43192 (this will not block)                 node.cpp:1640
2016-05-03T12:33:43   p2p:connect_to_task schedule_peer_for_de ] asyncing delayed_peer_deletion_task to delete 1 peers                  node.cpp:1645
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task delayed_peer_deletio ] beginning an iteration of delayed_peer_deletion_task with 1 in queue                  node.cp$
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] calling close_connection()                    peer_connection.cpp:127
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] close_connection completed normally                   peer_connection.cpp:129
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] canceling _send_queued_messages task                  peer_connection.cpp:142
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] cancel_and_wait completed normally                    peer_connection.cpp:144
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] canceling accept_or_connect_task                      peer_connection.cpp:157
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"except$
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task   destroy_connection ] in destroy_connection() for                   message_oriented_connection.cpp:286
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task   destroy_connection ] in destroy_connection() for                   message_oriented_connection.cpp:286
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task delayed_peer_deletio ] leaving delayed_peer_deletion_task                    node.cpp:1607
2016-05-03T12:33:43   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 208.66.16.68:45967: 0 exception: unspecified

I'm unsure how to troubleshoot further.

Quote from: xeroc on May 03, 2016, 08:12:08 am

Please check your connectivity or change the API server in the settings to another one

o,sorry,20160328witness_node unable to sync up

Is this a new build of the witness_node or one that was previously synced to the network? 

If previously synced, you may add --replay-blockchain to the command line sting. Further, if the database became corrupt, you may add --resync-blockchain and this will download from peers starting at block 0.

Anybody signed an agreement? Do we gave to MS any BTS  rights to let us get on Azure? 

As the community member that submitted the initial pull request to Microsoft for the BitShares Template, I can resolve this question with a definitive "No, BitShares is not granted to Microsoft."  Further, it is not the intention of Microsoft to 'own' any of these blockchain submissions, rather sell compute time on their Azure platform.  Please note, as an individual I signed a contribution clause with Microsoft prior to submitting the template that basically said I would not knowingly upload anything malicious.  Cass would have signed the same statement when he corrected the spelling in the Readme file a few hours after my original submission.

Please review the Contribution Guide Microsoft provide for BaaS submissions for further details of the requirements:
https://github.com/Azure/azure-quickstart-templates/tree/master/1-CONTRIBUTION-GUIDE

BitShares running on Azure remains bound to the same MIT license contained within the source repository.

Respectfully,
Fox

I have purchased these twitter and fb handles for the community because it needed to be done.
[...]
I think a worker proposal is the best way to collect the funds for this but am not competent enough with CLI client to create one myself.

Brilliant work here JonnyBitcoin  very much appreciate the proactive efforts.  I'll reach out to @roadscape about authoring the worker proposal on your behalf.