Regarding release time estimation, we made a mistake by again stating expected dates for fluent case scenario and having to fall short when confronted by unseen issues, as usually happens in software development.

Obviously as has been demonstrated, I'm not adept in foreseeing the completion of what's primarily my partner's extensive coding plate, so we'll have another attempt at avoiding that kind of policy despite the pressure to estimate release dates.

We're getting very close. However with a piece of tech that's been sweated on for soon 3 years, very close doesn't unfortunately mean a few hours. That much I know, though I suspect it's not a surprise!

It's good to remind myself that we were able to release FIMK comparatively well within the schedule, and it was our first strike at the crypto. While FIMK was technically nothing to sneeze at, the complexity of HEAT is on another level, which reflects into the recurring and continual birth pains, surprises and requirement to maneuvre. This could be considered a merit by the insightful who understand that nothing valuable comes easy.

That's a healthy statement, greatly expanding views for many who may not be following the "trends". Thank you for coming out with that.

I just tried out a working draft UI of the test A2AE on p2p network of 3 inhouse servers. Having come this far and seeing concrete functioning was a fairly pleasant experience. We continue on Friday and try to get it in a form for the stakeholders to try out, and will keep going throughout the weekend if necessary to release the overdue HEAT tokens asap.