Skip to content

Commit b6658cc

Browse files
committed
CAD002 additions
1 parent 458c31f commit b6658cc

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

cad/002_values/README.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -342,7 +342,7 @@ From a logical perspective, every Value is either present or excluded from the s
342342

343343
Records are specialised data structures that implement a defined sequence of fields.
344344

345-
Records behave like Maps when accessed using their field names as keys mapped to the corresponding field values. If updated, errors may occur if the update is inconsistent with the requirements on field values (e.g. attempting to put a value of the wrong Type into a field.
345+
Records behave like Maps when accessed using their field names as keys mapped to the corresponding field values. If updated, errors may occur if the update is inconsistent with the requirements on field values (e.g. attempting to put a value of the wrong type into a field).
346346

347347
#### Block
348348

@@ -363,17 +363,17 @@ A Peer Record represents the current state of a Peer.
363363

364364
#### Ordering
365365

366-
An Ordering a special record type used by Peers to represent their Belief regarding:
366+
An Ordering is a special record type used by Peers to represent their Belief regarding:
367367

368368
- The sequence of all Blocks
369369
- The current Consensus Point
370370
- The proposed Consensus Point
371371

372-
Orderings are not normally used or accessible in CVM code.
372+
Orderings are not normally used or accessible in CVM code, but are important for the CPoS algorithm and may be used to access the complete transaction history.
373373

374374
#### State
375375

376-
The State represents a total global State of the CVM. This includes
376+
The State reocrd represents an immutable snapshot of the global State of the CVM. This includes
377377

378378
- All Accounts
379379
- All Peers
@@ -382,10 +382,18 @@ The State represents a total global State of the CVM. This includes
382382

383383
#### Transaction Types
384384

385-
Transaction types represent instructions to Convex that can be submitted by external Clients. Transactions are specialised record types.
385+
Transaction types represent instructions to Convex that can be submitted by external clients. Transactions are specialised record types.
386386

387387
For more details see CAD010.
388388

389+
#### SignedData
390+
391+
A `SignedData` record combines any other CVM value with an Ed25519 digital signature.
392+
393+
SignedData records are used extensively for security, since the represent proof that someone constructing such data was in posession of the correct cryptographic key. In particular:
394+
- Peers sign Blocks and Orderings as part of CPoS
395+
- Clients sign Transaction records that they wish to execute
396+
389397

390398

391399
## Implementation notes

0 commit comments

Comments
 (0)