Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow signing Omni transactions with the keys stored in secure hardware #67

Open
msgilligan opened this issue Apr 14, 2015 · 1 comment
Milestone

Comments

@msgilligan
Copy link
Member

The RivetzSDK allows signing of Bitcoin transactions with a private key stored…

… in the Trusted Execution Environment (TEE) available in many modern devices. The TEE is a hardware environment that runs small applets outside the main OS. This protects sensitive code and data from malware or snooping with purpose-built hardware governed by an ecosystem of endorsements, beginning with the device manufacturer.

Currently, the method OmniTxBuilder.createSignedOmniTransaction() requires local ECKey objects with private keys and the method OmniTxBuilder.createOmniTransaction() creates unsigned, incomplete transactions (no change output.) To support Rivetz we'll need some form of pluggable signing.

@msgilligan msgilligan added this to the 0.4 milestone Apr 14, 2015
@msgilligan msgilligan changed the title Allow signing Omni transactions with the RivetzSDK (Trusted Execution Environment) Allow signing Omni transactions with the keys stored in secure hardware Dec 22, 2015
@msgilligan msgilligan modified the milestones: 0.5, 0.4 Dec 22, 2015
@mawenpeng
Copy link

I also need this feature. I'm trying to find a workaround.

@msgilligan msgilligan modified the milestones: 0.6, 0.7 Oct 26, 2021
@msgilligan msgilligan modified the milestones: 0.7, 0.8 Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants