Mr. Seppia

This happened after a restart and during the sync process If you look at the log /var/log/dusk.log-20220522.gz it start with block 52.000 zgrep 'curr_h":52089' /var/log/dusk.log-20220522.gz -B310 ``` {"block_time":10,"cert_step":3,"curr_h":52000,"event":"accept_block","hash":"2ea891e456...6ed4aba33c","height":52001,"level":"info","msg":"run state transition","process":"chain","prov":30,"time":"2022-05-16T19:06:35Z","txs_count":0}...

In addition to what already said, I believe we should remove the `ipc_method` argument and start to derive it from the url itself ```rust let url = Url::parse("http://mydomain:8585").unwrap(); let url...

Could you attach the output of `cat ~/.dusk/config.toml` command? Curious to know if you're waiting the tx to be included in a block before you start to send another tx

I would like to reopen this, as it seems doable to implement `ESC` interceptor with requestty

I disagree about this being a bug. Furthermore the creation of the column families happens only when the cache database file is created, and not every time that it's instantiated...

> Edit: This is wrong, we can just add a warning on first init that this process is gonna take a while @Daksh14 Do you believe that this hint would...

You can add a new address using non-interactive cli too ```shell # List current addresses ~ > rusk-wallet addresses 5i9RZjT87TLa1BtWXRRoFy3FoMzFHiXT3GWasHdUaxuo3YapUKYeXXiY1yuAeKng2hmxxaYsGNhKhjyrE9KYTSE7 4TogtFZzWTre567DWfj1BoNdFLRjpGbgjFma9ZqE2RLCDDTJVcC4DobrUySiQk9vctNofxMH3aBD5NE84trkhDXF 5SVB7Q1knQBemRmvj6woeCkvrPxXbQD6RoP35BrEFnPBHEnVVczLNVpFFMHq6JV1XCkMeFTYXQNzwtdZvdDLJEb1 # Add two new addresses ~ > rusk-wallet...

See also #970

> @fed-franz @goshawk-3 @herr-seppia is this still relevant? Probably not, but we should close it only when superseded by a new tracking issue explaining our direction on the topic

See also #1094 and #970