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

AirGap LPT Delegation #22

Open
pascuin opened this issue Sep 26, 2019 · 2 comments
Open

AirGap LPT Delegation #22

pascuin opened this issue Sep 26, 2019 · 2 comments

Comments

@pascuin
Copy link

pascuin commented Sep 26, 2019

Give a 3 sentence description about this proposal.

With AirGap we focus on keeping assets safe and stored offline on a dedicated mobile device, this is especially beneficial for staking assets. Having your LPTs truly secured offline and delegated to a Transcoder is the most secure approach.

Describe the problem you are solving.

Delegation of LPTs with a straight forward approach with safe offline storage is not solved yet. With AirGap's solution, which has been already applied in other staking environment like Tezos and in the near future Cosmos, this will be a thing of the past.

Describe the solution you are proposing.

Vault - Wallet

AirGap has already established itself as a wallet with the focus on accessible security, enabling its users to safely store their assets on a device completely cut off from any networks. This brings a new kind of security to the user as he generates a private key that has never touched the internet and securely stores it in the secure enclave of a mobile device only accessible by biometrics.

In AirGap this is made possible with a two device approach, where one device is taken offline after the installation of the AirGap Vault application. A new private key is then generate and stored on that device. On the other hand on an ever-day smartphone the companion application AirGap Wallet is installed which is responsible for the communication with the internet and the blockchain protocols. For example, a new delegation transaction is being prepared in AirGap Wallet by selecting the transcoder's address, a QR code with the transaction details are generated which is scanned by AirGap Vault and signed by accessing the secure enclave with the biometrics. The signed transaction is displayed on AirGap Vault as a QR code, scanned and broadcasted by AirGap Wallet.

More information about AirGap can be found on our website.

Describe the scope of the project including a rough timeline and milestones**

For the integration of LPT and enabling of the delegation the following milestones are relevant:

M1

Integration of the LPT token in AirGap Wallet & AirGap Vault

Prerequisites
Existing Ethereum integration in the airgap-coin-lib, AirGap Vault and AirGap Wallet

Expected Deliverables
AirGap Wallet & AirGap Vault support for LPT

M2

Creating, signing and broadcasting LPT transactions to send LPT tokens

Prerequisites
LPT token is integrated in the airgap-coin-lib

Expected Deliverables
The user can send LPT tokens from to another account and sign the transactions with AirGap Vault.

M3

Delegation to transcoder flow

Prerequisites
LPT integration: transaction creation, signing and broadcasting support

Expected Deliverables
The user can select a transcoder from a list and select it as a delegator and sign the delegation transaction with AirGap Vault.

M4

Security audit and testing

Prerequisites
Complete LPT integration with delegation support.

Expected Deliverables
Fully tested and audited code of the LPT integration.

Please estimate hours spent on project based on the above

28 hours a week for 4 weeks

@RaffiSapire
Copy link
Contributor

Hi there, could we schedule time for a call to walk us through how it works with tezos today? Send me an email at raffi@livepeer.org

@pascuin
Copy link
Author

pascuin commented Oct 28, 2019

Of course, will reach out to you via email.

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