aelfproject / aelf Goto Github PK

An exception (sometimes) threw when we run the test case TxMemPool.IntergrationTest.StartMultiThread:

Google.Protobuf.InvalidProtocolBufferException : Protocol message contained an invalid tag (zero).

Later we found the position causing this failure is a method of ChangesStore:

        public async Task<Change> GetChangeAsync(Hash pathHash)
        {
            var value = await _keyValueDatabase.GetAsync(pathHash.Value.ToBase64(), typeof(Change));
            return value == null ? null : Change.Parser.ParseFrom(value);
        }

It seems like something went wrong with the Parser of Change (deep research shows Protobuf failed to ReadTag of input data). But before long we found a interesting/weird/upset solution: by slightly modifying the implementation of AccountContextService.SetAccountContext:

From

await adp.GetDataProvider().SetAsync(GetKeyForIncrementId(), accountDataContext.IncrementId.ToBytes());

To

await adp.GetDataProvider().SetAsync(GetKeyForIncrementId(), new UInt64Value
            {
                Value = accountDataContext.IncrementId
            }.ToByteArray());

Basically we put a ulong type to a protobuf type UInt64Value, so at first we thought the reason cased aforementioned failure is the stuff we tried to set to database ain't a protobuf type. But during the attempt to confirm our conjecture, we found that the code actually does not reach the interaction of database, also the logic of Change is none of its business.

That's why I have to record this situation as an issue as well as seeking for help.

as documented here:

https://github.com/AElfProject/AElf/blob/master/docs/INTEROPERABILITY.md

Implement parallel execution of transactions using akka.net

child of #141

• Build genesis block with specific transaction defined
• Deploy AccountZero with transaction
• Chain storage

• Parallel metadata calculation, efficient method for calculating state occupied by each transaction
• State updating mechanism/algorithm

child of #158

Access/save of chains.

• Tx size calculating
• Fee rule
• Verify signature
• Account address

a reference implementation of the concept on scheduler is required:

https://github.com/AElfProject/AElf/blob/master/docs/SCHEDULER.md

Hello!

The "CreateChainTest" test in the Aelf.Kernel.Tests project is failing because it is expecting the CurrentBlockHeight to be 1. It appears that adding a new chain will add the genesis block, seen here. The second block is added in the test itself, seen here. I would expect the CurrentBlockHeight to be 2.

child of #141

child of #141

child of #141

Aelf Wallet plizzz

• Calculate transaction metadata
• Build dependencies among transactions
• Correctness guaranteed for dispatch
• Scheduling algorithm performance research

child of #141

• get/set
• functionalities

parent

child of #141

a reference DPoS implementation is required:

https://github.com/AElfProject/AElf/blob/master/docs/CONSENSUS.md

child of #141

Disconnect in a way that frees the socket(s)/network stream.

it should be sha-256 @dhe0627

I see that you use MD5 for merkle hashing, why not SHA?

See: https://github.com/AElfProject/AElf/blob/ff73574afaf9ecf64f98ff472da4247c6586a209/AElf.Kernel/ExtensionMethods.cs

child of #141

child of #158

child of #141

• Signature for transaction
• Signature for block
• update memory pool validation

child of #141

parent

• pool config
• validate tx
• add/remove tx

and more details..

Serialization plan for storage and network transmission

child of #158

parent

child of #141

• Structure to record change results from the transactions execution

Transaction structure for persistence and network transmission

child of #141

child of #141