and this works, reliably? If so this is quite possibly the best thing I’ve seen for the IC, ever.
My understanding was that this was far away from being plausible.
If a single onchain compiler canister has a conventional reproducible build and becomes widely ‘known’, verified and therefore highly trusted, then it can sign canisters that itself compiles, coupling their build hash and source code with a verification certificate. This avoids the need for people to have to build canisters before they can confidently review the source code (that’s a lot of effort and in my opinion a huge blocker).
Are you able to share more details about this on-chain compiler? Did you run into any challenges with it? What’s the cycles burn rate like? What do you think about blackholing it at some point?
I’d love to help support a blackholed on-chain Motoko compiler with an immutable perpetual cycles endowment. I would heavily use such a canister.
Looking forward to hearing more about this ![]()