From: Aymeric Vitte <vitteaymeric@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Browser version - Discover and move your coins by yourself
Date: Mon, 2 Sep 2019 09:38:50 +0200 [thread overview]
Message-ID: <afecae80-99a8-1dd3-727f-87344e0f99ad@gmail.com> (raw)
In-Reply-To: <93bdd23a-9a41-e531-76ad-e92ed571d587@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3204 bytes --]
The browser version is now released, please see https://peersm.com/wallet
Comments/suggestions still welcome
Le 07/08/2019 à 12:54, Aymeric Vitte a écrit :
>
> FYI Phase 3 is released https://github.com/Ayms/bitcoin-transactions,
> features:
>
> - create transactions
>
> - decode transactions
>
> - verify transactions
>
> - convert/map addresses (including bech32)
>
> - create/map wallets (bip32,39,44, etc), wallets recovery
> (missing/wrong words) and check
>
> - decode/create multisig redeem scripts
>
> - pubkey/privkey mapping , conversion and formats
>
> - sign/verify messages
>
> Browserifying everything now for the end of the month
>
>
>
> -------- Message transféré --------
> Sujet : Discover and move your coins by yourself
> Date : Fri, 12 Jul 2019 20:35:00 +0200
> De : Aymeric Vitte <vitteaymeric@gmail•com>
> Pour : Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
>
>
>
>
> Please see https://github.com/Ayms/bitcoin-transactions this is a merge
> of former bitcoin-transactions and bitcoin-wallets nodejs modules with
> additional features to be implemented as described in the README
>
> It is financed by NLnet via EU Horizon 2020 Next Generation Internet
> Search and Discovery call
>
> So the initial dev fees have been removed and the code is now open
> source and provided in clear under a MIT license
>
> The intent is to provide all the necessary tools for anybody to discover
> and manage their coins, as well as making transactions by themselves,
> without having to sync a full node or as an alternative to wallets when
> people don't understand where their coins are (we saw quite a lot of
> confusion for people not understanding at all how to find their coins
> and to what keys their addresses did relate in case of multisig, segwit
> and now bech32)
>
> It's somewhere bitcoin-cli outside of bitcoin core more easy to use and
> not restricted to its own wallet, available for any bitcoin based coins
>
> At the end it will be a secure standalone offline js webapp inside
> browsers (like https://peersm.com/wallet but the app does not reflect
> the current state of the nodejs repo)
>
> It's not a remake of iancoleman's tool but of course some features
> overlap, as well as for other existing tools, we will also extend all of
> this inside one tool with no limitations (for example some tools do not
> accept "invalid" bip39 seeds, or bip32 seeds, etc)
>
> Comments/suggestions welcome
>
> PS: initially sent to bitcoin-discuss but the list seems to be dead
>
> --
> Move your coins by yourself (browser version): https://peersm.com/wallet
> Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
> Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
> Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
> Get the torrent dynamic blocklist: http://peersm.com/getblocklist
> Check the 10 M passwords list: http://peersm.com/findmyass
> Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
> Peersm : http://www.peersm.com
> torrent-live: https://github.com/Ayms/torrent-live
> node-Tor : https://www.github.com/Ayms/node-Tor
> GitHub : https://www.github.com/Ayms
>
[-- Attachment #2: Type: text/html, Size: 6961 bytes --]
prev parent reply other threads:[~2019-09-02 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <758884fb-4332-71b8-093b-a21dcf596103@gmail.com>
2019-07-12 18:35 ` [bitcoin-dev] " Aymeric Vitte
2019-08-07 10:54 ` [bitcoin-dev] Fwd: " Aymeric Vitte
2019-09-02 7:38 ` Aymeric Vitte [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=afecae80-99a8-1dd3-727f-87344e0f99ad@gmail.com \
--to=vitteaymeric@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox