When the tip selection algorithm searches for transactions, it uses a depth parameter. You can find out more about depth here: https://docs.iota.org/docs/getting-started/0.1/transactions/depth


When you call getNewAddress with returnAll: true, it will not only return the new address but all other addresses before that one too. And you have to know all addresses to be able to ask for their balances. getNewAddress will not attach the new address or anything, just compute addresses until it finds one that has never been used before i.e. ...


The python wheel files you are looking for are hard to perma link. Login to github.com Go here: https://github.com/iotaledger/iota.rs/actions/workflows/python_binding_publish.yml Click on the latest action in the list Scroll to the bottom to access the latest python wheel files. The python bindings you can also build yourself: source: https://github.com/...


I don't really have much experience in permanodes nowadays, but I would expect that you set up your own Hornet node first, and connect your permanode to its MQTT port instead of connecting it to some "random" IOTA node from mqtt.iota.org. Perhaps you want to try that route if nobody has a better idea.


Which operating system did you install it on? Did you configure anything so far? (for example changed any ports or added any neighbors so far?) By the way this reminds me of something similar I have opened an issue a while back https://github.com/iotaledger/iri/issues/1678 Maybe you've added a neighbor with an invalid port? Please check /etc/default/iri ...

Only top voted, non community-wiki answers of a minimum length are eligible