Ok, so I found out that tronpy does allow to export transactions to JSON, before or after signing. And it also supports importing such JSONs to broadcast elsewhere.

As much as I hate JSON, I think this use case gets a pass from me.

Reply to this note

Please Login to reply.

Discussion

Well, it turned out that tronpy doesn't interact with JSON directly, onlly transforms transaction objects into/from a serializable form; you still need to call json.dumps/json.loads to actually serialize/deserialize them.