Cryptographically Signed HTTP Lambda invocations

I have written about this before. However, since I've done some major changes to Magic, I figure it would probably be valuable to describe the thing again - This time in more details. Anyways, onwards to the future.

This is one of those oddball things you have probably never seen before, arguably turning your Magic server into a crypto wallet and a financial transaction server, by allowing you to securely execute Hyperlambda code created by a 3rd party client - And have receipts giving you a guarantee of that the executed code was in fact created by one specific client. In many ways, it could be argued that this creates a "blockchain" type of technology for generic HTTP lambda invocations, providing code to your server, that you can securely execute, while getting a cryptographic receipt of that the code that was executed was indeed created by a specific client. Watch the video below for a walkthrough of how this actually works.