Hot answers tagged

3

Yes, but you would encrypt and decrypt off-chain while only storing the encrypted data and other necessary data in the blockchain state. With eosjs, you can use the following set of commands to encrypt and decrypt data: // The message that will be encrypted let message = "my message" // For example purposes, this is the keypar of the recipient. Note I ...


2

You should have a look at the pEOS token for private transactions: https://peos.one/


2

Currently, EOS does not support this kind of functionality directly. However, smart contracts may enable this kind of functionality in the future. Nothing prevents EOS to adopt Ethereum style privacy transaction smart contracts. For example, Ethereum has AZTEC, that allows ZCash like operations on any tokens.


1

No, transactions are always public. If you want to hide content this is usually done through encryption. The user would at the end decrypt their secrets. For a poker game the dealer would encrypt the distributed cards and push it to the chain.


1

Data stored in a contract is public. Natively, EOSIO cannot assure privacy and there are currently no official public plans to change this. However, to preserve privacy, one may just store data that was previously encrypted. This question offers a similar discussion, and this question discusses ways to encrypt data before storing it on the chain.


1

Is it possible to have permissioned data access? No, not natively. Is there any way to change this or any other way to achieve permissioned data access? As suggested by others, the only way to keep some form of permissioned data on the blockchain is by only storing encrypted data. If you're worried about encryption / decryption resource consumption, ...


1

I don't think that it is possible to have permissioned tables.Because as you are calling cleos get table but you are not giving any authorization to call this table query.So, i suggest to not to keep any private data in tables. For more see this Can we add the permission to access the table?


1

Not yet. Block.one is not working on implementing privacy at the protocol level as they're currently focused on scaling the blockchain vertically (i.e. through side chains) Confidential transactions (CT) could be implemented at the protocol level on eosio-based side-chains, but there has been no public announcement of anyone working on something like this ...


1

Some sexy dude made this library https://github.com/dtrades/dtrades-communication Let's you encrypt a string with a public key, decrypt with the corresponding private. import { encrypt, decrypt } from 'eos-communication-lib'; const public_key = "EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV"; const private_key = "...


Only top voted, non community-wiki answers of a minimum length are eligible