-
Notifications
You must be signed in to change notification settings - Fork 16
Examine MAM request size under the encryption mechanism #672
Comments
With this golang testing program, we got a string plaintext in 8 bytes Signature: 2e90dcea329871b646ebc5de3c0eddaa8de3b575189e38f80860ee4c840c827f07c5775ac29a5167ac51792404164774a6eeee03830170a3439dedc227e252f036f05d1790ae31a4f319ac69a21c67a5c2f7a7199bd160c364c9907ad4ba00d6c9ab90153baef3b7aec321efe38fee8ddd485cd53c30ef9d5705bc011972c7d2956e985e2e9bca11d8246cbfc0cc67953b9bc7c281a0d582f0cd01950ea927e5e2ba1b98659c726b3701e9ac65e6eed5f617599ae777f22f862633165ff828ee89db76cbcd64b70a83246a2530f298c9e6f68a4465390b3b0752879c173ed50570244c23f9b9c3bb7b8c2656196729f99a3fc91059f2b4c64eed9990702fd7be Signature length: 256 bytes |
It is about 15ms with the implementation of Noise framework |
Testing environmentprocessor : 1 |
Time DistributionStep Elapsing Time (generate AES key): 12.465µs |
We have planned to build another safe channel above MAM communication. We should examine the size of the request and even the efficiency
The workflow is here
The text was updated successfully, but these errors were encountered: