maybe never, but in the alpha routeros there's something called xfrm interface.
Not a single mention to VRF hardware offload on improvements of this RC4, considering VRF Hardware Offload is very important o 7.24.
Not on routing protocols, or on connection tracking, Firewall, routing Rules.
Frightened silence.
There is a bug in 7.24rc3 and 7.24rc4 with wireguard, where if a peer is edited (or disabled and then re-enabled), it stops responding entirely (Tx/RX counters and handshake timer freeze in place). I assumed it would be quickly noticed in 7.24rc3 and fixed by 7.24rc4. Looks like it may find its way into the official/stable 7.24 release? that wouldn't be good. please fix 
It looks like we have this entry here, but situation is even worse - if peer is disabled/enabled or edited, then it does not pass any traffic at all. Reboot fixes the problem
Its happening!!!!
Finally VTI is in the horizon, I'm excited hahah
Maybe I missing something but maybe someone can explain why use VTI over wireguard when wireguard can do same thing more efficiently?
Only thing I can think of is due to older hardware that doesn't support wireguard yet?
Please keep on dicussing VTI over here: IPSec VTI or Feature Request: IPSEC Improvements
Thank you! 
Not sure it is the same case, but I needed to redo few WG tunnels, turning the towards the new location. Something was wrong - entered new public IP in the Peer section, pressed OK, it connected to the old one. Reopened the dialog and old address was there. So changed it again, pressed Apply, OK, once again, the same. Disabling / enabling the tunnel, or restarting the router, helped, don't remember precisely. Reverted back to stable.
Wireguard is software feature and is available on all hardware supported by ROS 7...
Yes but we dont always create tunnels between mikrotik to mikrotik... it could be cisco to mikrotik or juniper, etc
Or PC. So ?
What is the point you want to make ?
To reach this, or the upgraded the kernel, or they backported a ton of things...
What would be?
New issue in 7.24rc4:
/system/leds/set 0 type=interface-status
... doesn't work anymore. The LED remains off despite the SFP interface being up. Up to 7.24rc3, this worked fine.
type=interface-activity still works.
RB760iGS
Fixing one, breaking another.
Wouldn't this entry need to be:
- system - improved stability (additional fixes);
since it was already included in the rc2 and rc3 changelogs?
Naah, there are no limits to the improvements, and it would give no added information, every improvement is in itself an additional fix to the previous sitauation.
Now, something like:
- system - improved stability (fixes this and that, besides some other things)
would change nothing, but at least show that the good Mikrotik guys have some sense of humour 
.
The only explanation I have for not using the "additional fixes" suffix is that these are different stability improvements in completely different parts of the system, so there is no direct connection between them. We'll never find out.
Hi,
MikroTik support: [IPsec] [IKEv2] - VTI - Virtual Tunnel Interfaces
Hello,
This is an automated message. Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out. To be sure this specific fix is included, read the changelog when the next version comes out. If your issue is not mentioned, it might mean it will be in the next release.
If you would like any more details - please reply to this message and one of our support engineers will contact you.
Best regards,
Regards, MikroTik Support.