CCF specification 1.0 release

[j1010001]

Objective

Make an advancement in CCF maturity.

Key results

• Move CCF spec from release candidate to 1.0 version after adding new Cadence types.

DACI

Role	Assigned
Driver	Technical: @fxamacker, EM: @j1010001
Approver	@dete
Consulted	@turbolent
Informed	Flow engineering team

Scope

This is mostly to replace some remaining placeholder text (e.g. in "Why CBOR") and to release tag CCF Specs 1.0.0 because the work to sync onflow/ccf (CCF specs) with onflow/cadence (CCF codec) was essentially done in CCF Specs PR 7.

• Check settings for onflow/ccf
• Replace placeholder text
• Merge Update to CCF Specification 1.0 ccf#7 to add new Cadence types and other updates.
• Release tag 1.0.0

[fxamacker]

Thanks for adding this to OKR! 🙏

More detailed issue (as non-OKR priority) was opened earlier this year at onflow/ccf:

• Update CCF specs to 1.0.0 by adding support for new types added to Cadence ccf#6

The PR for this work is at onflow/ccf:

• Update to CCF Specification 1.0 ccf#7 (add new data types introduced by Cadence 1.0 and tidy)

Note

CCF specs was written to handle changing priorities for trade-offs (e.g. security vs speed), so the specs explicitly specify how to do deterministic encoding and makes that an opt-in requirement for CCF-based protocols.

This allows trade-offs between speed and security, etc. without modifying CCF specs.