Erik Zhang

Then I think there is no reason to join the config.json and protocol.json.

> We can add ExtensionAttribute with VarBytes payload and multiple allowed. Users can deserialize the payload to the structure they want. Do you agree on this solution? @roman-khimov

According to [NEP-6](https://github.com/neo-project/proposals/blob/master/nep-6.mediawiki#account), it should indeed be `isDefault`. This issue has been fixed in #2451.

Object creation benchmark: ```c# class TestClassForConstructor { private delegate TestClassForConstructor ConstructorDelegate(object arg); public TestClassForConstructor(object arg) { } public static void RunTest() { Type t = typeof(TestClassForConstructor); Type paramType = typeof(object);...

Property assignment benchmark: ```c# class TestClassForProperty { public string MyProperty { get; set; } public static void RunTest() { TestClassForProperty obj = new TestClassForProperty(); PropertyInfo property = obj.GetType().GetProperty(nameof(MyProperty)); Action setMethod...

Example: ```c# public class Transaction : ISerializable { [Serialized(0, Serializer = typeof(UnmanagedSerializer))] public byte Version { get; set; } [Serialized(1, Serializer = typeof(UnmanagedSerializer))] public uint Nonce { get; set; }...

> In my experience, reflection always it's slower It use reflection only once.

Even if you specify the format of the key, the value may be a serialized struct.

Values can be difficult to be mandated because they are business related. Even some of the contract balances are calculated, not directly stored.

Maybe it can be another NEP? Example: `NEP: Verifiable Token Standard`.