-

Logging RPC to file: /home/ader/.decent/logs/rpc/rpc.log
Logging transfers to file: /home/ader/.decent/logs/transfer.log
Starting a new wallet with chain ID 0000000000000000000000000000000000000000000000000000000000000000 (empty one)
0 exception: unspecified
Timer Expired
   {"message":"Timer Expired"}
   asio websocket.cpp:656 operator()

   {"uri":"ws://localhost:8090"}
   th_a websocket.cpp:906 connect

From now on, you will be able to see the transaction history.
DECENT Blockchain Explorer is live: https://explorer.decent.ch/

in terminal i'm seeing block # 2360

explorer isn't updating ?

EDIT: nvm i refreshed the page

), however the GUI wallet still says it's syncing with the network...

Yes the Explorer works but the syncing issues is being worked on right at this moment. hold off just a few more minutes. Sorry for the hiccup.

Ok thought something wasn't happening right, thank you, keep us updated please !

Ok something definitely going on, i terminated the GUI and followed the daemon/cli instructions, the daemon starts and syncs blocks however upon starting the cli_wallet binary i get the following output:

Code:

Logging RPC to file: /home/ader/.decent/logs/rpc/rpc.log
Logging transfers to file: /home/ader/.decent/logs/transfer.log
Starting a new wallet with chain ID 0000000000000000000000000000000000000000000000000000000000000000 (empty one)
0 exception: unspecified
Timer Expired
    {"message":"Timer Expired"}
    asio  websocket.cpp:656 operator()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:906 connect

@DECENT please assist, thank you

Can you see line like this when starting decentd?:

3587555ms th_a application.cpp:215 reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090

yes that was shown when the daemon starts. you can also confirm it's listening on that port if you're on windows using the command netstat -a, or in linux type lsof -i:8090

Can you also see lines like this in decentd output when cli is started?

334744ms th_a database_api.cpp:246 database_api_impl ] creating database api 140201863400512
334744ms th_a database_api.cpp:246 database_api_impl ] creating database api 140201863408688

Yes, at this point if you are seeing lines such as:

Code:

960258ms th_a       application.cpp:497           handle_block         ] Got block: #3031 time: 2017-06-30T14:16:00 latency: 273 ms from: init3  irreversible: 3020 (-11)
965219ms th_a       application.cpp:497           handle_block         ] Got block: #3032 time: 2017-06-30T14:16:05 latency: 234 ms from: init8  irreversible: 3020 (-12)
970181ms th_a       application.cpp:497           handle_block         ] Got block: #3033 time: 2017-06-30T14:16:10 latency: 196 ms from: init9  irreversible: 3022 (-11)

then your daemon is running correctly