You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These functions are triggered by block timestamps, not extrinsics, so their complexity can't be abused for an attack. Still, substrate enforces block times and for parachains it seems that the computation time per block is even more restrictive. relaychain validators will probably just refuse to check block validity if it takes too long.
approach 1: split by cid
We could assign one cid per block only, but that doesn't guarantee much. Maybe one cid has a million participants.
👎
approach 2a: offchain workers (substrate)
We could use offchain workers to do the computation. In order to ensure integrity, we'd need some threshold consensus. In order to ensure liveness, we may have to just wait for the first few offchain workers to send their identical results.
Assignment has to be deterministic!
approach 2b: offchain TEE
We could use SubstraTEE to compute the assignment and issuance in a TEE and the result will be sent to the chain via one or several extrinsics.
The TEE guarantees integrity and random assignment. for availability, we'd need redundancy
No need for deterministic assignment
The text was updated successfully, but these errors were encountered:
The ceremony pallet has two expensive functions:
These functions are triggered by block timestamps, not extrinsics, so their complexity can't be abused for an attack. Still, substrate enforces block times and for parachains it seems that the computation time per block is even more restrictive. relaychain validators will probably just refuse to check block validity if it takes too long.
approach 1: split by cid
We could assign one cid per block only, but that doesn't guarantee much. Maybe one cid has a million participants.
👎
approach 2a: offchain workers (substrate)
We could use offchain workers to do the computation. In order to ensure integrity, we'd need some threshold consensus. In order to ensure liveness, we may have to just wait for the first few offchain workers to send their identical results.
Assignment has to be deterministic!
approach 2b: offchain TEE
We could use SubstraTEE to compute the assignment and issuance in a TEE and the result will be sent to the chain via one or several extrinsics.
The TEE guarantees integrity and random assignment. for availability, we'd need redundancy
No need for deterministic assignment
The text was updated successfully, but these errors were encountered: