because streaming was exceptional troublesome today i did slow down my node monitoring
but i think it wasn’t the monitoring - i think just found out today that doing a “safe wallet receive” does put some (for my internet) serious load onto the wires for about 40 seconds (red btw is the upload … not sure why that would interfere with my streaming that heavily … but the client for sure is not light on network resource usage)
Was looping that for the last day to try and receive a coin transfer that seems to be exceptional hard to receive… @qi_ma I did send you a message via discord… Not sure this is something you want to investigate or consider a non problem in the future anyway… (the failing receive… Not the network load on receiving)
I checked the two logs you shared, here here is my summary of what happened:
according to the sending log, there was 544400 nanos collected from 91 cash_notes to be transferred to one receiver.
This results in a complexed transfer to be composed, which has 91 inputs.
And for each of that input, a spend record needs to be published to the network to claim that amount of nano is spent. And each of that record has to hold that complexed transfer.
This result in the total traffic involved in send out & receive that tranfer will be aroud couple of hurnderds MB.
the send log does show all the 91 spends got sent out and stored by the network. which means your nanos are there in the network.
however, the receive log shows during the verification of those 91 spends, there is spend cann’t be fetched, which failed the trasnfer. the receive log does show less peers discovered compared with the send log (131 vs. 220), which might be not with a good connection or in bad time?
All these 91 spends have to be ALL fetched to make the trasnfter to be received successfully, which is really a challenge.
…but it’s the only way node runners will be able to “cash in” on their earnings in the future … and bundling 91 cash nodes doesn’t look like an insane amount to me tbh … just thinking loud … (ofc a workaround would be to do a send-to-oneselve on collecting the nanos every 20 nodes or so … which would result in no more than 20 inputs to ever occur in the process …)
Are we getting, at some stage in future, the ability to specify the wallet a node is to use to receive payments? This would seem to solve having to run a script to send from the individual node wallet to a central wallet.
Honestly this is needed if we want people to run nodes and not have a headache to use their earnings
but then i would specify my central wallet as receiver for all my nodes …would have incoming rewards from not only 91 locations but from a couple thousand nodes i’m currently running into my central wallet … and when i try to spend them i’d bundle the cash-notes there and see the same problem … just on a way way larger scale …
maybe a receiving wallet should do a reissue automatically after having received “too many” cash-notes to prevent this?
