Dunno if this just has not been implemented yet…
That’s it exactly
First chunks, then we’ll get payment there.
6 Likes
FYIs, I suspect I’ll be bringing this down in the near future. Feels like we’ve learned a good amount from this one already. Thanks everyone for participating, as ever!! 
Edit: FYIs, since the other day we’ve lost one more node only. But we can also corroborate the mem increase over time. Also: more nodes looking full there.
16 Likes
My crystal ball says that is code for holepunchnet is at the doorstep.
9 Likes
I suspect not until that rising memory bug is squashed, so they may hold back until then.
5 Likes
Crystal ball 
vs Crystal ball.
It is not a necessity though is it, all tests so far have had the memory issue.
Would possibly be as exciting to get mem_squashed_net as hole punching is not directly affecting selfish little me.
6 Likes
it has remained because it is elusive although I think there was a fix that wasn’t yet merged.
They may well want to add in hole punching if they are confident that it won’t make tracking down the memory leak more difficult. 
I want it all, and I want it NOW. 
9 Likes