Achim Schneider

I added the following import in `App.tsx`: `// @ts-ignore import workerURL from "threads-plugin/dist/loader?name=gitWorker!./workers/add.ts";` And I spawn the worker now with: `const add = await spawn(new Worker(workerURL));` This seems to work!...

This is an incomplete Analysis of how common Solidity attack vectors relate to ink!: https://github.com/achimcc/ink-security

I also discussed the occurence of one very specific Solidity bug and why ink! would have prevented it by design here: https://codingconnects.com/cryptopunk-bug/

> (Maybe) dumb questions: > > 1. why the upstream version doesn't satisfy our use case? What patches were applied to the upstream? If I understood correctly some computational intesive...

@davxy We also want to use the arkworks.rs stuff in other context. @burdges said, a complete native code implementation of a verify function is not what we want, but I've...

This all builds and all tests pass! If no one complains, I will just wait for the official arkworks-rs 0.4.0 release and will turn it into Ready for review then!

> We could've a thinner substrate change @bkchr but then have an external repo that implements the runtime code for the curve models and curves themselves. I didn't ask for...

We have a funny testing duality: the curves repo is running the tests against the host functions in Substrate and Substrate is running the tests against the curve repo. In...

AFAIK Sassafrass consensus will use RingVRF's and with this also arkworks and the host functions. I was assuming that the consensus layer needs to be part of the Substrate core...

> > > > Good point! If this is the case, we can add it here :) > > A general node, the artworks stuff should go into some special...