This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-08
Channels
- # aws-lambda (2)
- # beginners (66)
- # calva (7)
- # cider (1)
- # clj-kondo (1)
- # cljs-dev (4)
- # cljsrn (2)
- # clojure (79)
- # clojure-android (1)
- # clojure-spec (8)
- # clojure-sweden (3)
- # clojure-uk (12)
- # clojurescript (6)
- # datomic (18)
- # duct (1)
- # emacs (31)
- # fulcro (8)
- # hoplon (5)
- # joker (4)
- # luminus (9)
- # off-topic (7)
- # reagent (6)
- # rewrite-clj (8)
- # shadow-cljs (9)
- # spacemacs (42)
- # tools-deps (9)
- # yada (4)
I guess maybe you could have it do some testing on primitive operations to establish a baseline, and then measure the difference of higher order compositions of those those primitives to ensure things complete within expected time scales
I wonder if a temporal contract system type thing could help mitigate against timing attacks
Looks like the latest EOS VM built on wasm has metering "At no point during parsing or evaluation does EOS-VM use unbounded recursion or loops, everything is tightly bound to limit or eliminate the ability for a bad or corrupt Wasm to cause a crash or infinitely hang the machine." https://github.com/EOSIO/eos-vm/blob/master/README.md