forked from ShieldedLabs/zebra-crosslink-staging
-
Notifications
You must be signed in to change notification settings - Fork 3
Create/adopt a quint model of the Crosslink rules #278
Copy link
Copy link
Open
Labels
sl-bft-consensusShieldedLabs: Related to BFT consensus Crosslink sub-protocolShieldedLabs: Related to BFT consensus Crosslink sub-protocolsl-code-architectureShieldedLabs: code architecture issues separate from protocol designShieldedLabs: code architecture issues separate from protocol designsl-crosslink-consensusShieldedLabs: Related to Crosslink consensus protocolShieldedLabs: Related to Crosslink consensus protocolsl-pow-consensusShieldedLabs: Related to PoW consensus Crosslink sub-protocolShieldedLabs: Related to PoW consensus Crosslink sub-protocol
Description
Metadata
Metadata
Assignees
Labels
sl-bft-consensusShieldedLabs: Related to BFT consensus Crosslink sub-protocolShieldedLabs: Related to BFT consensus Crosslink sub-protocolsl-code-architectureShieldedLabs: code architecture issues separate from protocol designShieldedLabs: code architecture issues separate from protocol designsl-crosslink-consensusShieldedLabs: Related to Crosslink consensus protocolShieldedLabs: Related to Crosslink consensus protocolsl-pow-consensusShieldedLabs: Related to PoW consensus Crosslink sub-protocolShieldedLabs: Related to PoW consensus Crosslink sub-protocol
Type
Fields
Give feedbackNo fields configured for issues without a type.
It's a good time to start using modeling / spec writing tools like quint to connect the code and design as we're starting to do manually in #277.