public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Aymeric Vitte <vitteaymeric@gmail.com>
To: Marcel Jamin <marcel@jamin.net>,
	bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin-transactions
Date: Wed, 1 Aug 2018 11:58:43 +0200	[thread overview]
Message-ID: <c6e469e7-30aa-08f5-7ce6-bfa42081bf39@gmail.com> (raw)
In-Reply-To: <CAAUq485wUxGyM0m5geQ2JvBz=yMw7tXu11vdkkYuAxDfaWJkRg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3834 bytes --]

You are right, that's what I have been saying for online services that
ask for private keys, and even the seeds

The problem is that people can't refrain to put their keys for example
to get "free" coins, typically they try to use bitcoin-transactions,
don't succeed and go put their seeds in an online service

At least it gives an alternative, private keys are optional and the tool
will output the command to use with bitcoin-transactions, and if they
want to put directly their keys, then...

"Move your coins by yourself" refers more to "don't get trapped by your
wallet(s) or things that you don't master like multisig, segwit, bech32,
etc"

As I said the idea would be to end up with an offline tool should some
people support/finance the effort


Le 01/08/2018 à 07:45, Marcel Jamin a écrit :
> IMHO you should almost never publish a service that asks users for
> private keys.
>
> A warning isn't enough. Your server might get compromised.
>
> "Move your coins by yourself" isn't even correct if your server is
> involved.
>
> On Tue, 31 Jul 2018 at 13:26, Aymeric Vitte via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org
> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>
>     I know this list is not to advertise personal projects but
>     https://peersm.com/wallet might be of some interest, this is the web
>     interface for https://github.com/Ayms/bitcoin-transactions since
>     apparently quasi nobody succeeds to use it
>
>     As far as I know (and surprisingly) this is the only online tool that
>     converts bech32 addresses (Sipa's one does not output something
>     understandable by everybody, the tool is using his code), the only one
>     that converts from any address to any address, maybe the only one that
>     decodes simply redeem scripts and probably the only one that allows to
>     create transactions by its own (the advanced mode is not
>     implemented for
>     now but will be soon)
>
>     Ideally it should be an offline tool if there is some incentive to do
>     so, so of course it is not advised to use his private keys for now
>
>     Maybe they are mistaken but some users are reporting invalid bech32
>     addresses from their Electrum wallet, after segwit, bech32 confusion
>     seems to be the topic of the moment
>
>     Regards
>
>     Aymeric
>
>     -- 
>     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
>
>     _______________________________________________
>     bitcoin-dev mailing list
>     bitcoin-dev@lists.linuxfoundation.org
>     <mailto:bitcoin-dev@lists.linuxfoundation.org>
>     https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

-- 
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: 8345 bytes --]

  reply	other threads:[~2018-08-01  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 11:25 [bitcoin-dev] bitcoin-transactions Aymeric Vitte
2018-08-01  5:45 ` Marcel Jamin
2018-08-01  9:58   ` Aymeric Vitte [this message]
2018-08-09  8:38     ` hth lipsch

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=c6e469e7-30aa-08f5-7ce6-bfa42081bf39@gmail.com \
    --to=vitteaymeric@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=marcel@jamin.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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