This is super useful !
A few more tools that I use regularly, if you are looking to expand:
- Base58 encoding to Hex conversion
- Hex to decimal and vice versa
- Strlen
- Compute SHA-256 of text or hex string
- Compute Keccak-256 of text or hex string
No that’s not how it works.
When a transaction is submitted on the blockchain to withdraw funds from an address it needs to be signed by the private key and it exposes the full public key. A bot that would monitor such transactions would therefore see the public key. With just the public key you can’t create a valid signature, you still need the private key, however for this particular case, knowing the public key reduces the entropy of the puzzle by a factor of 2 (from 66 bits to 33 bits), so this puzzle was easier to solve for the bot knowing the public key published by the person who found the private key. This is very specific to this specific puzzle which had 66 bits of entropy. In general, bitcoin transactions have 256 bits of entropy.
Near-zero dependency example of how to use AWS Nitro enclaves from Deno. Can serve as a code sample or a blueprint to understand the whole process, because I found the AWS documentation and process quite unclear and over-engineered. Parts of the code (the code to access the Nitro Secure Module and the HTTP Proxy that connects on a VSOCK) are written in Rust and accessed in Deno through FFI.
We run a medium sized trading system (20 microservices) in Deno for about a year now. There have been a few runtime quirks but they have currently all been ironed out. I love the approach that Deno takes with respect to permissions which allows you to strictly specify which urls your program can access, which files/directories can be read/written, etc.
Being able to allow custom behaviour via JS/TS in Rust is definitely something that I wanted to explore too.
If you haven’t already you should check out these two articles from the Deno blog website which go a bit further: