nami-wallet-examples VS stakepool_python_tools

This is great stuff! We were also using multi-sig for selling our project (https://partyanimals.dance/) and it just works perfectly> The approach only uses blockchain capacity for successful purchases and does not litter up the chain like common drops. If you are interested in a code example using multi-sig for your new project have a look at https://github.com/dendorferpatrick/nami-wallet-examples/blob/master/Multi-Signature.md

you can check out the code here: https://github.com/dendorferpatrick/nami-wallet-examples/tree/node-js

Here is some code to get started with Nami wallet and js https://github.com/dendorferpatrick/nami-wallet-examples

As of today, a replacement for cncli sending tip to pooltool.io is available. I'm already using it and it works perfect. It's called sendtip.py and is available from https://github.com/Josef3110/stakepool_python_tools.

I have just recently release some scripts in python handling simple transactions wrapping cardano-cli - see link: pyhton transactions

In being always curious what the future will bring - especially for Xmas - I did some analysis. Usually, new node release happen soon after release candidates appear in github. This time with 1.32.0 it was a bit different. We all heard, that p2p network is being tested on public testnet and also on mainnet. Still the changelog for 1.32.1 says that p2p is still experimental and should not be activated. So, I guess we'll have to stay with topologyUpdater for some more time (did I mention that there's a python implementation (https://github.com/Josef3110/stakepool_python_tools). Speaking of python tools - today the new scripts for getting the balance and prepare simple transactions have been released.

As you know we have our own updater script written in python (https://github.com/Josef3110/stakepool_python_tools). There's a small update to it, accepting now the initial responses for relays that start requesting.

However, there's https://github.com/Josef3110/stakepool_python_tools with a topologyUpdater implementation in python. It not only provides a more convenient JSON configuration file and reasonable error handling, but also monitoring by sending emails if something goes wrong.

As a starter an alternative to topologyUpdater.sh has been released last night. At https://github.com/Josef3110/stakepool_python_tools you can find a python variant called topologyUpdater.py. It's still in its early stages, but does what it should do. An update to use a configuration file instead of changing the constants in the source code is already in the making.