From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: John Smith <witchspace81@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.4 Release Candidate 2
Date: Thu, 22 Sep 2011 19:55:05 -0300 [thread overview]
Message-ID: <CAJSM8J1=FWAJVqgQ0HG=0TQU25hrsym=edthsB+sMqfzqgR2GQ@mail.gmail.com> (raw)
In-Reply-To: <CAJNQ0su4LjanK_miyL3_BqUxxvgr90A_aUcw8E4UPVUtAykG-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
Hi John!
Thank you for your answer...
I have "two kinds" of address, the "static address", which I created myself
for any personal reason, and the "dinamic address", which is the automatic
generated address when I receive some Bitcoin amount, I label each one (the
automatic created by the software) with something like "DINAMIC-1",
"DINAMIC-2" and so on...
I use my "dinamic address" in a "random" way, following the moon phase...
lol
My point is: I like to keep track of all my Bitcoin Address, they are all
my...
Please, leave this feature alive, as a option, disabled by default.
I don't know why people fear about their own address... It is all under
"Receiving" tab! There is nothing to fear about it.
---
BTW, I think this option should have some explanations at the "Options
screen", for example:
For increasing your anonymity, enable the "Dinamic Bitcoin Address" option
and make sure to always use one new and different address for each
transaction. And do not link each address with your person!
(X) Dynamic Bitcoin Address (a new Bitcoin Address will be created
automatically for you, after each new received Bitcoin amount)
---
Thank you so much!
Best,
Thiago
2011/9/22 John Smith <witchspace81@gmail.com>
>
>
> 2011/9/22 Martinx - ジェームズ <thiagocmartinsc@gmail.com>
>
>> Hi everybody!!
>>
>> This is my first message here... I'm ThiagoCMC at bitcointalk...
>>
>> Well, one of the features that I like most is that, every time I receive
>> some Bitcoin amount, a new address appear at my "AddressBook"automatically,
>> AND, I like to track it.
>>
>
> Can I ask your rationale for this?
>
> From what I've noticed, most people's workflow is to create a new receiving
> address for each new contact that sends them bitcoins (either for every
> transaction, or they reuse the address for this person). To make sure that
> the address is labeled, they create it themselves and then give out the
> generated address.
>
> They are utterly spooked by suddenly appearing unlabeled addresses, of
> which they are unsure whether they are used, and which can never be removed.
>
> I'm fine with adding it back as an option but please leave it disabled by
> default...
>
> JS
>
>
[-- Attachment #2: Type: text/html, Size: 3354 bytes --]
next prev parent reply other threads:[~2011-09-22 22:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 14:02 [Bitcoin-development] 0.4 Release Candidate 2 Gavin Andresen
2011-09-09 23:49 ` Matt Corallo
2011-09-10 5:18 ` Jeff Garzik
2011-09-16 16:38 ` Jeff Garzik
2011-09-22 7:46 ` Martinx - ジェームズ
2011-09-22 22:25 ` John Smith
2011-09-22 22:55 ` Martinx - ジェームズ [this message]
2011-09-23 1:20 ` Martinx - ジェームズ
2011-09-23 2:05 ` Martinx - ジェームズ
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='CAJSM8J1=FWAJVqgQ0HG=0TQU25hrsym=edthsB+sMqfzqgR2GQ@mail.gmail.com' \
--to=thiagocmartinsc@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=witchspace81@gmail.com \
/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