Alpha centauri client
ALPHA CENTAURI CLIENT UPDATE
The protocol update starts a new chain with the genesis block containing genesis data in the `GDP2Regenesis` format. The instruction does not need any auxiliary data. The protocol update instruction is identified by the SHA256 hash of this file. This is used when restarting a chain as a result of a protocol update. `GDP2Regenesis` specifies core genesis parameters, the hashes of the first genesis block, previous genesis block and terminal block of the preceding chain, and the state at regenesis. `GDP2Initial` specifies core genesis parameters and an initial state, which may be used as an initial genesis block. In particular, the `GDP2Initial` and `GDP2Regenesis` genesis data formats are the same as `GDP1Initial` and `GDP1Regenesis` respectively. The genesis data format at protocol version 2 is the same as at protocol version 1, except that the version tag is 4 instead of 3.
![alpha centauri client alpha centauri client](https://cdn.cloudflare.steamstatic.com/steam/apps/1362270/header.jpg)
Outcomes of all transactions in a block are hashed, and their combined hash is included in a block. These events are part of a transaction outcome. For example an event is “Transferred” a given amount of GTU from address A to address B. In protocol version 1 there are 21 possible events that can be generated. When a valid transaction is included in a block it generates a list of one or more events.
![alpha centauri client alpha centauri client](https://i.ytimg.com/vi/T01vhpYv3cg/maxresdefault.jpg)
Each supported transaction type has a protocol-defined tag. When transactions are parsed their type is determined by a single-byte tag value. If a transaction payload is not among the above listed recognized payloads then the transaction can still be included in a block, but its outcome will be `SerializationFailure`, and it will have no other effect on the state of the chain. Hash: 9b1f206bbe230fef248c9312805460b4f1b05c1ef3964946981a8d4abb58b923 BackgroundĪlpha Centauri 1.0 supports the following 16 account transaction types `DeployModule`, `InitContract`, `Update`, `Transfer`, `AddBaker`, `RemoveBaker`, `UpdateBakerStake`,`UpdateBakerRestakeEarnings`, `UpdateBakerKeys`,`UpdateCredentialKeys`, `EncryptedAmountTransfer`,`TransferToEncrypted`, `TransferToPublic`, `TransferWithSchedule`,`UpdateCredentials`, `RegisterData`.Įach transaction has a common signature and header, and a transaction-type specific payload.