Chainweb: A Proof-Of-Work Parallel-Chain Architecture for Massive Throughput [pdf]
kadena.io2 pointsby buckie0 comments
;; Simulate message data specifying an administrator keyset.
;; In production use 'mockAdminKey' would be an ED25519 hex-encoded public key.
(env-data { "admin-keyset": ["mockAdminKey"] })
;; Simulate that we've signed this transaction with the keyset.
;; In pact, signatures are pre-validated and represented in the
;; environment as a list of public keys.
(env-keys ["mockAdminKey"])
;; Define the module.
(module helloWorld 'admin-keyset
"A smart contract to greet the world."
(defun hello (name)
"Do the hello-world dance"
(format "Hello {}!" [name]))
)
;; and say hello!
(hello "world")
I've always been of the opinion that their sharding effort would fail, but I want to stay well informed. Sharding POS is very hard because the "trilemma" is correct for POS (kadena.io / explorer.chainweb.com being the example that the trilemma is solvable if you stick to POW).
Layer 2/zk-rollups will only help successful dapp devs lower their gas costs (see: DyDx). It doesn't relieve the pressure on layer 1 as other apps/patterns move in until a new equilibrium is reached.