Nick Johnson
Nick Johnson
Unfortunately that results in a very confusing UX - you have to tell all the other keyholders "approve the transaction with nonce x and hash y, not the otherwise identical...
Amazing job! It's over 4 times the speed compared to generating ECDSA keypairs. If you have any ideas for further performance optimizations, let me know!
One slight problem: "Init code must be shorter than 199 characters". A nonstarter for proper contracts! Maybe you could make it take the hash instead?
Alternately, you could hash it in C, before passing it to the GPU code?
I only just saw your earlier question about CUDA. I am running on NVIDIA hardware. It's a bit late now, but would it be significantly faster in CUDA?
@nventuro Sounds good! I'm happy to relicense my contributions under any license you see fit - MIT is absolutely fine. Please let me know if you need anything else from...
> There are several functions for which we haven't seen concrete use cases before. For example, do you know of situations where a smart contract needed to use `find`? I'm...
@jarednielsen You can use `abi.encodePacked`!
> Could you elaborate on what's the issue you're envisioning here? In most database systems, a query like `SELECT * FROM table LIMIT x OFFSET y` involves the database internally...
True, but I don't think it's possible (at least without low level DB support) to do a good implementation that uses offsets - so better to fix the API early....