There is no commentSelect some text and then click Comment, or simply add a comment to this page from below to start a discussion.ideas to discuss on a internal presentation about OS:
In order to provide forward security in Cardano, we are in the process ofimplements KES (Key Evolving Signatures).
Jul 5, 2023Implement a KES Agent service to provide complete forward security forblock-forging signatures.
Jul 5, 2023In this document we make some back-of-the-envelope computations to see how feasible it is to verify SNARKs on main-net. We have some preliminary benchmarks made by Kenneth that show how expensive each function is. The goal of this document is to use those values and estimate SNARK verification on-chain. Similarly, we will estimate how much data the script needs to process, to understand if we are within the script data budget.
Feb 10, 2023Goal: We will have one curve or cycle of curves chosen for Midnight Goal of being rollup friendly There are sidechain constraints and there are plutus constraints Came up from weekly executive meeting. We need to justify the decision. If we make changes soon enough (before handing the keys over), we are the ones taking the decision (rather than convincing the community). Nonetheless, we should justify/motivate this decision as if we had to convince the community (we should have ADRs for this decision). The discussion here concerns (cycle of) curves that will be used in midnight. However, the mid/long-term goal is to be able to verify midnight proofs on main-net. This is why Cardano also has weight on this decision (as Plutus will need built-in functions for efficient verification on main-net). Seems to be clear that there is not one perfect curve that solves all our problems. So we have to understand the trade-offs:
Jan 27, 2023
HackMDor
By clicking below, you agree to our terms of service.
Sign in with Wallet
New to HackMD? Sign up