rusk vm is the part of the whitepaper that made me realize this isnt just a privacy chain with extra steps, its actualy building its own execution environment.
its webassembly based, so it inherits most of the native wasm opcodes, but then adds host functions on top. hashing, elliptic curve math, signature checks, zero knowledge proof verification, all callable natively instead of bolted
0n through some external library.
gas prices every function call, which keeps it quasi turing complete rather than fully turing complete, basicaly an workaround for.$BOME
the halting problem so execution cant run forever.
whats notable is the native zk verification. most vms treat proof verification as a expensive external computation, rusk treats.$BTW
it as a first class operation. curious how the gas costs for zk verification compare to a normal contract call on this thing??
#dusk @Dusk $DUSK
its webassembly based, so it inherits most of the native wasm opcodes, but then adds host functions on top. hashing, elliptic curve math, signature checks, zero knowledge proof verification, all callable natively instead of bolted
0n through some external library.
gas prices every function call, which keeps it quasi turing complete rather than fully turing complete, basicaly an workaround for.$BOME
the halting problem so execution cant run forever.
whats notable is the native zk verification. most vms treat proof verification as a expensive external computation, rusk treats.$BTW
it as a first class operation. curious how the gas costs for zk verification compare to a normal contract call on this thing??
#dusk @Dusk $DUSK
