add murmur32 to crypto lib

[Jim8y]

Add efficient hash function

[erikzhang]

We need to have a mechanism to update the native contract manifest first. Otherwise, we cannot add or delete methods in the native contract.

[vncoelho]

Maybe we may need to do an onchain transaction that activate this manifest update (following

neo/src/neo/SmartContract/Native/NativeContract.cs

Lines 145 to 160 in b3b2207

	this.Manifest = new ContractManifest
	{
	Name = Name,
	Groups = Array.Empty<ContractGroup>(),
	SupportedStandards = Array.Empty<string>(),
	Abi = new ContractAbi()
	{
	Events = Array.Empty<ContractEventDescriptor>(),
	Methods = descriptors.Select(p => p.Descriptor).ToArray()
	},
	Permissions = new[] { ContractPermission.DefaultPermission },
	Trusts = WildcardContainer<ContractPermissionDescriptor>.Create(),
	Extra = null
	};
	contractsList.Add(this);
	contractsDictionary.Add(Hash, this);

).
In this sense, method becomes available to be called as soon as we call this update function (maybe signed by Neo Council).

[shargon]

We need to have a mechanism to update the native contract manifest first. Otherwise, we cannot add or delete methods in the native contract.

But the manifet it will be updated with NativeUpdateHistory so the native smart contract should use the stored manifest

[ProDog]

According to my test results, the unit fee of Murmur32 is about 0.6 times the unit fee of SHA256:

Times	Mur GAS	Mur Time	Mur GAS/ms	SHA GAS	SHA Time	SHA GAS/ms	Mur / SHA
100	1.0069706	5.0233	0.200459977	1.9894806	5.601	0.355200964	0.56435651
1000	9.8689206	41.5222	0.237678172	19.6942006	43.9438	0.448167901	0.530332877
10000	98.4883206	347.5932	0.283343634	196.7413006	433.9716	0.453350635	0.624998869
100000	984.6823406	3748.8223	0.262664448	1967.212321	3981.9332	0.494034486	0.531672294
1000000	9846.622341	40126.1208	0.245391833	19671.92232	54009.3751	0.364231622	0.67372468
10000000	98466.02234	432472.6809	0.227681485	196719.0223	411076.3747	0.478546164	0.475777474

[ProDog]

After testing, change to CpuFee = 1 << 15, the GAS fee of Mur32 will be the same as SHA256.

[Jim8y]

After testing, change to CpuFee = 1 << 15, the GAS fee of Mur32 will be the same as SHA256.

It makes no sense, murmer shoud be way more efficient than SHA....... can we just hold this for a while? I need to dig into this.

[superboyiii]

After testing, change to CpuFee = 1 << 15, the GAS fee of Mur32 will be the same as SHA256.

It makes no sense, murmer shoud be way more efficient than SHA....... can we just hold this for a while? I need to dig into this.

In debug mode, time for Mur is closed to SHA. However, in release mode, Mur is about 4 times faster than SHA.
So the price of Mur shoud be 1 << 13.

[erikzhang]

@Liaojinghui Merge?

[Jim8y]

@Liaojinghui Merge?

Yes please.