Dr.-Ing. Fabian Schuh

I prefer the second option :D

Interstingly, when loading from the sources, i can import the module just fine. Seems the release did not include some files. How did you install python-bitshares?

This explains [my issue here](https://discuss.hashicorp.com/t/port-labels-not-working-intuitively/21842). Thanks for making it clear

+1 got the same error. came out of the blue

> Do you want an off-chain synchronous solution (which is what I understand from the flow description) without using proposals? Yes. A flow that ends up in a transaction with...

> Hmmm...this would possibly require exposing the Beet websocket port to the internet The process would be like this: 1. Server provides unsigned tx via javascript to a webpage 2....

> Ah...simpler...albeit convoluted...thought you wanted to automate the first part The application here is `workers.bitshares.exchange`. I want to setup multisig there so that hacks into the server cannot compromise funds...

> When looking into the Wiki, it would be nice to have references to Bitshares client version numbers or so in order to know which guidance applies to which version....

doesn't telegram require to provide a mobile phone number?

Ran into the same issue. Somewhat unpleasant issue