-
Notifications
You must be signed in to change notification settings - Fork 23
Operating documentation #391
Comments
We don't have anything for ECDSA keeps yet. The best source of information here is tBTC spec for now. |
This is probably not the right thing to do. The beacon “docs” are a full spec, not documentation. The keep-ecdsa docs will most likely start as something less complete for folks to get oriented, and will be referring to the “beacon” docs for a lot of things, as what is currently the beacon spec also defines a lot of the root of the Keep system (e.g., authorizations and staking). It would be better if you wanted to compile a list of questions you need/would like the docs to answer, as well as some initial takes at answers if you have them. If you want to base that on what's in the beacon docs, that's fine. We can gather that in this issue and start turning it into either checkboxes or multiple issues as we start organizing the written work. |
This part is 100% in Some stuff that might be appropriate in this issue though
@creckhow do you have any other questions in your notes? |
keep-core has a great set of docs on the random beacon -- a glossary, details on misbehavior and slashing, how to run and operate the client.
Am I correct, these don't exist yet for ecdsa/tBTC? Of particularly urgency for our business partners is information about running and operating the client, and ETH slashing/liquidation parameters.
@Shadowfiend @sthompson22 @pdyraga let me know how I can help. I will just start forking Promethea's beacon docs and filling them with vague guesses over here in this repo at some point. :):):)
The text was updated successfully, but these errors were encountered: