Succesfully built and released to Debian experimental.
I noticed that « silkaj authfile » spews a file in current directory - I find that a bad practice to do without confirmation, especially since this is confidential data, and ESPECIALLY since the file is stored group and world readable. I would expect to be asked to confirm where highly sensitive information should be littered, and I would expect it to be stored only readable by user.
I then (and before as well where it failed, that’s how I went looking for the authfile subcommand) tried « silkaj balance HdN1r7UPxRKeCScMorngBydr6shSxki32kKxgEMEx7a3 » which failed with a long backtrace seemingly caused by a network timeout. I would expect that command to not try read an authfile in current directory - few years ago all scripting languages was changed to not include current directory from default file lookup routines because it is very common to stand in an alien directory that might abuse processing of data in their control.