When working on one of my projects, it was asked “How do we ensure that transaction was indeed recorded on the blockchain” While we can (and did) store the transaction hash returned by the function call in the database, txn_hash alone does no good. e.g. “Official” method to get the details of the transaction (from the txn_hash) returns something like the following: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 web3.
Feel free to jump directly to the solution Background I recently started working on node based project. I’d been using nvm for quite some time now, since I liked the idea of having languages their own version managers, rather than having OS manage it ,which I doubt can do a good job. OS package managers were designed to have single version (and upgrade when needed) So I’ve been using pyenv and nvm for quite some time.
Initially, setting up Vyper (an experimental language, with python-like syntax, for writing smart contracts on ethereum) seemed as simple as following the instructions. it wasn’t. If you like to skip the details/troubleshooting, head over to TL;DR pyenv I’ve written about why I prefer pyenv earlier I’m not sure whether my “misfortune” was due to pyenv, but it could be. To top it off, I also used virtualenv as suggested in the official docs.
Recently, I had to create a technical document for a project, and I started with org-mode since that was easiest. Basic markup is easy in org, and was enough for me to get started. In order to share with external parties, I exported to HTML. In past I had tried docx but that did not work well, I wanted to export to PDF, but it requires pdflatex which seemed a lot of hassle.