This is mentioned in the first post of the blog post series that is mentioned in the first sentence of the article!
The gist is, use `wasmer create-exe --target other-target-triple` to cross-compile with zig (if available) to the targets wasmer compiler backends (llvm, cranelift, and our custom "singlepass" backend) support.
Disclaimer: I am the author of those features/git commits.
It was completely a joke as mentioned in the article :) It's not actually a blockchain, just a very crude linear merkle tree. The point is that pets are appended into the blockchain, and if enough blocks get appended that don't mention your pet's birth hash, your pet is "dead" like tamagotchi. You can read it in the article in detail.
It was an absurd application of "blockchain" in order to have a demo app to try to run on AWS Lambda within some hours and it worked! :)
wasmer (as a rust library) + .wasm payload was a 5.5MB .zip file uploaded to Lambda (should have mentioned that in the article). This was without size/speed optimization as the goal.
or just use golang, yes it might need 10MB or even 30MB for each static binary, but it's mature and production ready long time ago.
or, how about fastcgi, that's essentially what lambda does. by using shared libraries each fastcgi endpoint executable could be much smaller than 5.5MB, it's boring and mature, just a bit out of fashion.
The gist is, use `wasmer create-exe --target other-target-triple` to cross-compile with zig (if available) to the targets wasmer compiler backends (llvm, cranelift, and our custom "singlepass" backend) support.
Disclaimer: I am the author of those features/git commits.