-
Notifications
You must be signed in to change notification settings - Fork 5
Documentation on "Encryption standards for V.systems" #59
Comments
UPDATE: NaCl has been implemented on https://wallet.crypto.red/, it works and the string result is somehow sometimes smaller than 160 characters. Since there is no property is_message_encrypted or such, the web app mentioned above offer a "tool" not a module which detect and decrypt the message, why not creating instruction like "E_NACL {{encrypted_text}}", it takes 7 chars... and "E_MCLE ..." too. |
I am not sure the keypair of Vsys is compatible with McEliece... EDIT: Note (As seen on https://www.npmjs.com/package/mceliece-js): McEliece generally shouldn't be used to directly encrypt your data; in most cases, you'll want to pair it with a symmetric cipher and use it to encrypt symmetric keys. |
@Primerz can you please let me know the goal? passing encrypted info between users or something else? |
@faddat Yes to encrypt the transaction's message, McEliece doesn't seem to fit (the VSYS key-pair can't achieve to work with it), more than that, it isn't recommended to use McEliece to encrypt messages, rather it should be used to encrypt a symmetrical key. So we probably should remove McEliece from the recommendation, meanwhile, NaCl works great, cool enough, the vsystems blockchain could provide a format such as "NACL:{encrypted_message}" in order for all application to recognize encrypted memo. |
I think an auto decrypt mechanism along with a way to encrypt message is recommendable, also can't deal with McEliece by the way nevertheless NaCl works fine. :) |
As explained by the Vsys team (here https://github.com/virtualeconomy/js-v-sdk/wiki/How-to-Encrypt-and-Decrypt-a-message) it is possible to encrypt a message in a transaction using js-nacl, the key-pair from the vsystems account are compatible with it, meanwhile, for the McEliece algorithm it is not specified how could we transfers the public key to someone, therefore, it is potentially, useless.
In some chain, it is possible to have a transaction object property called "is_encrypted" which can correlate to "nacl" for example, very good for a standardized way to use it.
Also, a question that I have is the size limit of the message embed in a transaction.
The text was updated successfully, but these errors were encountered: