README ¶
Fundamentally achieving ASIC resistant: A brief introduction to Truehash algorithm
As we all know, TrueChain adopted hybrid consensus technology, It uses PBFT as fast chain to process transactions and PoW as snailchain to supervise and elect the committee.
PoW algorithm was put forward by Cynthia Dwork and Moni Naor in 1993. The application scenario of it then was to resist the attack of ddos and email spam. In 1999, Jacobsson came up with partial hash inversion algorithm which is also the method that Satoshi Nakamoto utilized in bitcoin network.
Take a look at the coins that issued after the bitcion, it is not hard to see that blockchain developers are experimenting different kinds of mining algorithm to achieve ASIC resistant. And it turns out to be that all the attempts are failed. Their whole idea is to adding the computation against the shortcomings of ASIC to make the algorithms harder. However, algorithm like Ethash and Equihash or others may merely delay the appearance time of ASIC at best but cannot fundamentally resist ASIC. For further research, we must understand why CPU/GPU is way much slower than ASIC. And the main reason is that von Neumann architecture is adopted for Diversity calculation.
Von Neumann architecture is roughly divided into three parts, that is internal storage, control unit and calculating element. The operation program and data are written in DDR and will be transferred to the calculation element when performing calculations. The computational bottleneck caused by transmission bandwidth is called the von neumann bottleneck.
The idea of avoiding the von neumann bottleneck is simple for operations with high uniqueness, such as the calculation of hash values, the idea is to abandon the von neumann architecture and write the algorithm directly into the calculation element to make it become ASIC. That is why ASIC has such an astonishing advantages of computing powers in calculating Bitcoin Sha-256d. Even then Ethash adopted the method of reading the big table, but essentially a computer program can still be hard -coded to calculation elements. Although there's memory grain around the ASIC but that can only increases the cost.
In order to achieve ASIC resistant fundamentally we can borrow the experience from Monero, that is periodic algorithm changing design. The problems with Monero is the unprofessional voting for hard fork by the community. And the biggest problem with them is that no one knows if the project team (they can manipulate the voting results easily) prepared ASIC for new algorithm.
Therefore,we must assure this mechanism is under the control of mining algorithm. And to achieve ASIC resistant fundamentally, the following rules must be satisfied:
- Command S as a collection of algorithm, all algorithms in S must pass through the von neumann bottleneck.
- Algorithm will change every T blocks, and the changing methods must meet up with the condition of Verifiable and unpredictable.
- No human intervention in algorithm switching.
The specific design ideas are as follows
The implementation of Truehash is to set G as a group, for every group member g, make rho_V(G) be the showcase of G in vector space V. In ordinary mining algorithm, when calculate blockheade, nonce and other information with operations like padding and so on, there will form a Vector nonce. By the exhaustion of different nonce to find the results that are less than the difficulty coefficient.
The changing parts of Truehash
Change hash(v(nonce)) to hash(rho(g)*v(nonce)). As long as G (Truehash utilizes permutation group which contains 2048 elements) is complex enough, this algorithm collection will not be entirely hard-coded within the calculation elements. Because the algorithm will switch randomly, the bottleneck of von neumann will be inevitable.
The principle of Truehash's switching algorithm is that the group elements will be changed every 12 thousand PoW block. The production time of 12 thousand poW blocks is 83 days. The new group element information is composed of blocks 1-8192 in the previous cycle, and the composition method is generated by analyzing the hash values of blocks 11001-11256.
Because the hash value of the block is unpredictable in advance, it's impossible for anyone to know anything about the new algorithm until the 11256 block comes along. From the 11,257th block of the last cycle, to the algorithm being invalidated, there is only 88 days in total, so it makes no sense to produce ASIC in such a short period of time.
Documentation ¶
Overview ¶
Package minerva implements the truechain hybrid consensus engine.
Index ¶
- Variables
- func GetBlockReward(num uint64) *big.Int
- func LogPrint(info string, addr common.Address, amount *big.Int)
- type Config
- type ConstSqrt
- type Minerva
- func (m *Minerva) APIs(chain consensus.ChainReader) []rpc.API
- func (m *Minerva) Author(header *types.Header) (common.Address, error)
- func (m *Minerva) Finalize(chain consensus.ChainReader, header *types.Header, state *state.StateDB, ...) (*types.Block, *types.ChainReward, error)
- func (m *Minerva) FinalizeCommittee(block *types.Block) error
- func (m *Minerva) GetElection() consensus.CommitteeElection
- func (m *Minerva) Prepare(chain consensus.ChainReader, header *types.Header) error
- func (m *Minerva) SetElection(e consensus.CommitteeElection)
- func (m *Minerva) SetThreads(threads int)
- func (m *Minerva) Threads() int
- func (m *Minerva) VerifyHeader(chain consensus.ChainReader, header *types.Header) error
- func (m *Minerva) VerifyHeaders(chain consensus.ChainReader, headers []*types.Header, seals []bool) (chan<- struct{}, <-chan error)
- func (m *Minerva) VerifySigns(fastnumber *big.Int, fastHash common.Hash, signs []*types.PbftSign) error
- func (m *Minerva) VerifySwitchInfo(fastnumber *big.Int, info []*types.CommitteeMember) error
- type Mode
Constants ¶
This section is empty.
Variables ¶
var ( //ErrRewardedBlock is returned if a block to import is already rewarded. ErrRewardedBlock = errors.New("block already rewarded") ErrRewardEnd = errors.New("Reward end") )
Various error messages to mark blocks invalid. These should be private to prevent engine specific errors from being referenced in the remainder of the codebase, inherently breaking if the engine is swapped out. Please put common error types into the consensus package.
var ( Big1e16 = big.NewInt(1e16) // 0.01 unit //BaseBig ... BaseBig = big.NewInt(1e18) //NetworkFragmentsNuber The number of main network fragments is currently fixed at 1 NetworkFragmentsNuber = 1 NewRewardBegin = 53550 RewardEndSnailHeight = 1000000 )
var ErrInvalidDumpMagic = errors.New("invalid dump magic")
ErrInvalidDumpMagic errorinfo
Functions ¶
func GetBlockReward ¶
GetBlockReward Reward for block allocation
Types ¶
type Config ¶
type Config struct {
PowMode Mode
}
Config are the configuration parameters of the minerva.
type Minerva ¶
type Minerva struct {
// contains filtered or unexported fields
}
Minerva consensus
func NewFakeDelayer ¶
NewFakeDelayer creates a minerva consensus engine with a fake PoW scheme that accepts all blocks as valid, but delays verifications by some time, though they still have to conform to the Ethereum consensus rules.
func NewFakeFailer ¶
NewFakeFailer creates a minerva consensus engine with a fake PoW scheme that accepts all blocks as valid apart from the single one specified, though they still have to conform to the Ethereum consensus rules.
func NewFaker ¶
func NewFaker() *Minerva
NewFaker creates a minerva consensus engine with a fake PoW scheme that accepts all blocks' seal as valid, though they still have to conform to the Ethereum consensus rules.
func NewFullFaker ¶
func NewFullFaker() *Minerva
NewFullFaker creates an minerva consensus engine with a full fake scheme that accepts all blocks as valid, without checking any consensus rules whatsoever.
func NewShared ¶
func NewShared() *Minerva
NewShared creates a full sized minerva shared between all requesters running in the same process.
func NewTester ¶
func NewTester() *Minerva
NewTester creates a small sized minerva scheme useful only for testing purposes.
func (*Minerva) Author ¶
Author implements consensus.Engine, returning the header's coinbase as the proof-of-work verified author of the block.
func (*Minerva) Finalize ¶
func (m *Minerva) Finalize(chain consensus.ChainReader, header *types.Header, state *state.StateDB, txs []*types.Transaction, receipts []*types.Receipt, feeAmount *big.Int) (*types.Block, *types.ChainReward, error)
Finalize implements consensus.Engine, accumulating the block fruit and uncle rewards, setting the final state and assembling the block.
func (*Minerva) FinalizeCommittee ¶
FinalizeCommittee upddate current committee state
func (*Minerva) GetElection ¶
func (m *Minerva) GetElection() consensus.CommitteeElection
GetElection return election
func (*Minerva) Prepare ¶
Prepare implements consensus.Engine, initializing the difficulty field of a header to conform to the minerva protocol. The changes are done inline.
func (*Minerva) SetElection ¶
func (m *Minerva) SetElection(e consensus.CommitteeElection)
SetElection Append interface CommitteeElection after instantiation
func (*Minerva) SetThreads ¶
SetThreads updates the number of mining threads currently enabled. Calling this method does not start mining, only sets the thread count. If zero is specified, the miner will use all cores of the machine. Setting a thread count below zero is allowed and will cause the miner to idle, without any work being done.
func (*Minerva) Threads ¶
Threads returns the number of mining threads currently enabled. This doesn't necessarily mean that mining is running!
func (*Minerva) VerifyHeader ¶
VerifyHeader checks whether a header conforms to the consensus rules of the stock Truechain m engine.
func (*Minerva) VerifyHeaders ¶
func (m *Minerva) VerifyHeaders(chain consensus.ChainReader, headers []*types.Header, seals []bool) (chan<- struct{}, <-chan error)
VerifyHeaders is similar to VerifyHeader, but verifies a batch of headers concurrently. The method returns a quit channel to abort the operations and a results channel to retrieve the async verifications.
func (*Minerva) VerifySigns ¶
func (m *Minerva) VerifySigns(fastnumber *big.Int, fastHash common.Hash, signs []*types.PbftSign) error
VerifySigns check the sings included in fast block or fruit
func (*Minerva) VerifySwitchInfo ¶
VerifySwitchInfo verify the switch info of Committee