Wouldn't your Experts be able to answer that question - they are experts after all?
Yes, but their knowledge cannot compare to consulting "the crowd." I trust the people on here to poke holes in the plan or to know about methods or technologies that we may not have heard of or looked into yet. To assume that My and my team know all would be arrogant. 
Topic: Best Method to Store IDs on the blockchain (Read 132 times)
I have a client who needs to have KYC for users on the platform. We will have a KYC service provider validate the ID, but we do not want to store any PII (Personally identifiable information) ourselves.
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
You should be able to handle this process and store the information on the ETH Blockchain.
I would suggest speaking with a Solidity developer. They will give you the specifics about programming the system.
A database can be in various forms, there should be no restriction with the Ethereum Platform.
https://solidity.readthedocs.io/en/develop/
Wouldn't your Experts be able to answer that question - they are experts after all?
I have a client who needs to have KYC for users on the platform. We will have a KYC service provider validate the ID, but we do not want to store any PII (Personally identifiable information) ourselves.
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
You should be able to handle this process and store the information on the ETH Blockchain.
I would suggest speaking with a Solidity developer. They will give you the specifics about programming the system.
A database can be in various forms, there should be no restriction with the Ethereum Platform.
https://solidity.readthedocs.io/en/develop/
I have a client who needs to have KYC for users on the platform. We will have a KYC service provider validate the ID, but we do not want to store any PII (Personally identifiable information) ourselves.
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
You should be able to handle this process and store the information on the ETH Blockchain.
I would suggest speaking with a Solidity developer. They will give you the specifics about programming the system.
A database can be in various forms, there should be no restriction with the Ethereum Platform.
https://solidity.readthedocs.io/en/develop/
why do it on ethereum, not on bitcoin?
The project is already built out on ETH. As I said for identity we can use any blockchain, but I would need a technical reason to use something other than ETH. 
why do it on ethereum, not on bitcoin?
I have a client who needs to have KYC for users on the platform. We will have a KYC service provider validate the ID, but we do not want to store any PII (Personally identifiable information) ourselves.
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
It seems like we could take their ID, encrypt it (SHA256 or similar), then associate it with a auto-generated user ID number, and store it on the ETH blockchain. The platform will simply reference them with the auto-generated ID number.
Is there anything wrong with this idea or approach? Are there any recommendations to do it any other way? While the client is using ETH for their platform, I see no reason why we'd have to use ETH solely for the user ID/KYC functionality.
Obviously our concern is security, as the client would be screwed if someone figured out how to decrypt the IDs. Is this a realistic threat?
Does anyone see any problems with this plan?
Jump to: