AirGap Vault, an air-gapped wallet focussed on security and usability #42
Replies: 2 comments 4 replies
-
|
@AndreasGassmann wrote:
Thanks! Welcome to the community! Your experience will be useful.
Great — you are here at the right time. These topics exactly what a number of us are focusing on right now. In particular, our wrappers for LibWally might be of interest to you.
We've got a first draft of our "release path" strategy at https://github.com/BlockchainCommons/Community/blob/master/release-path.md Particular relevant is that once we have at least two independent wallet vendors with some level of interoperability, we should move things from Research to WIP (aka Wallet Improvement Proposals or Work in Progress) — each WIP item should have a target destination, whether BIP, SLIP, IETF, W3C, etc. I consider this community more of an incubator of specifications, reference implementations, and best practices — not a standards body.
I've not seen javascript for any of these yet —Blockchain Commons tends to do C first, sometimes then Rust or Swift, the others have been contributing rust, java, pythons, go, etc. I'd ask in a separate question in this forum as I vaguely heard on the Signal Chat channel that someone was working on LifeHash in Javascript.
There has been some discussion here, but also more recently in Bitcoin-Dev list at https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-February/018388.html Blockchain Commons is releasing tomorrow a beta of Gordian Cosigner (keep an eye out!), which supports some of the current practices of the so-called BIP38 (which doesn't exist, isn't consistent, and is somewhat broken). But I feel we ultimately need an answer more like the above Bitcoin-Dev proposal. However, as approach requires state, and the community has to still work with the stateless 48' approaches currently of of Trezor, Ledger & Cold Card, we need to support that as well.
We periodically have interest from the Ethereum wallet community, but so far we seem to have attracted the more serious bitcoin wallet developers. There also has been some interested from the Decentralized Identity community. The #SmartCustody book we published last year is more chain agnostic — its best practices for responsible key management is good for most coins. However, the book and best practices have not been updated for multisig.
I look forward to collaborating with you! -- Christopher Allen |
Beta Was this translation helpful? Give feedback.
-
|
@AndreasGassmann My intention with LifeHash is that the C++/C implementation is now the "one implementation to rule them all," so rather than do a separate Javascript implementation, what I would like to see is a WASM target for that code, and in fact all the BC libraries. There is truly no need to "re-implement the wheel" here. 😄 ~ Wolf |
Beta Was this translation helpful? Give feedback.
-
|
That would be great. Do you have a timeline for that? I think we will use the available js implementation of |
Beta Was this translation helpful? Give feedback.
-
|
a bit too idealistic. for example, react-native has no way to run wasm, but can work with pure js. |
Beta Was this translation helpful? Give feedback.
-
|
Can't react native run wasm? I remember there was an issue in the polkadot-wasm library and there appear to be workarounds (Because we don't use react-native I didn't look into it in detail): polkadot-js/wasm#19 Having a native js/ts implementation would be nice (probably also smaller in size), but I would not be comfortable implementing this myself because of the possible security implications. I'm not a cryptographer and from past security audits that we did I learned that you should just stick with well established standards that handle all the corner cases for you. |
Beta Was this translation helpful? Give feedback.
-
|
@ChristopherA How do you want to prioritize getting LifeHash running under WASM? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I would like to introduce our wallet called "AirGap" (https://airgap.it/) to this group. The AirGap project was started about 4 years ago. Ever since then, we have focussed on developing a secure and air-gapped, but also user friendly, wallet.
Back when we started, there was not a lot going on in the air-gapped wallet space. There were only technical options available, and it was nearly impossible to onboard beginners to those solutions. So our goal was to change that and build a better solution.
Some of the key points:
And some other interesting things we worked on:
If you have any questions about our apps, I'm happy to answer them!
I found this "Airgapped-Wallet-Community" a couple of months ago when I was investigating the SLIP-39 standard so we could replace our own SSS implementation. Back then I didn't have much time, so when I saw that SLIP-39 is not BIP-39 roundtrip compatible, I stopped looking. Only now I finally had some time and was able to go through all the research that has been going on here. I have to say, great job! There are some very interesting proposals open, such as SSKR (BCR-0011), UR (BCR-2020-005) and UR Types (BCR-2020-006). I hope we can integrate those standards and combine our efforts going forward.
The main reason I am reaching out right now is because the Bitcoin implementation in our app is a bit outdated. We only support legacy addresses, no mutlisig and no other advanced features. So I'm currently working on bringing it up to speed. Besides implementing features like Segwit and PSBTs, we would also like to be compatible with industry standards. We currently use our own data-serialisation (built on RLP, which is used by Ethereum) and QR paging method, so hopefully this can all be replaced by standards defined in this group.
I have some questions:
Thanks for time and I'm looking forward to hearing from you!
Beta Was this translation helpful? Give feedback.
All reactions