Package convex.core

package convex.core

Fundamental Convex classes used for the decentralised network

Related Packages

Package	Description
convex.core.crypto	Crypto algorithms used within Convex, particularly for digital signatures and cryptographic hashes
convex.core.data	Data structures and algorithms, including a complete set of classes required to implement immutable, decentralised data objects.
convex.core.exceptions	Specialised exception classes used in the Convex implementation and libraries
convex.core.init	Package used to create genesis states for new Convex networks
convex.core.lang	Core CVM implementation
convex.core.store	Etch database for convergent immutable storage
convex.core.text
convex.core.transactions	Convex network transaction types.
convex.core.util	Convex utility classes and miscellaneous functionality

Classes

Class	Description
Belief	Class representing a Peer's view of the overall network consensus state.
BeliefMerge	Class representing the context to be used for a Belief merge/update function.
Block	A Block contains an ordered collection of signed transactions that may be applied collectively as part of a state update.
BlockResult	Class representing the result of applying a Block to a State.
Coin	Static Constants for Coin sizes and total supply These denominations are intended to provide more sensible human-scale units for better understanding.
Constants	Static class for global configuration constants that affect protocol behaviour
ErrorCodes	Standard codes used for CVM Exceptional Conditions.
Order	Class representing an Ordering of transactions, along with the consensus position.
Peer	Immutable class representing the encapsulated state of a Peer
Receipt	Transaction Receipt record.
Result	Class representing the result of a Query or Transaction.
ResultContext	Class for preparation of transaction results Mutable so that results can be accumulated efficiently as processing proceeds
State	Class representing the immutable state of the CVM State transitions are represented by blocks of transactions, according to the logic: s[n+1] = s[n].applyBlock(b[n]) State contains the following elements - Map of AccountStatus for every Address - Map of PeerStatus for every Peer Address - Global values - Schedule data structure "State.