Bitcoin Forum
December 08, 2016, 10:07:20 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: "Invisible Wallet" Addresses / Client Behavior  (Read 1128 times)
nhodges
Sr. Member
****
Offline Offline

Activity: 308


View Profile
September 29, 2011, 05:31:57 PM
 #1

Does bitcoind behave the same way as the client and generate change addresses? I am trying to send a transaction in a way that the recipient can verify it is coming from my wallet address without having "changed hands" in the interim. (I want to be able to see the recipient proper from just looking at the transaction details on Block Explorer, without having to go "one level deeper" so to speak.)

1481191640
Hero Member
*
Offline Offline

Posts: 1481191640

View Profile Personal Message (Offline)

Ignore
1481191640
Reply with quote  #2

1481191640
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481191640
Hero Member
*
Offline Offline

Posts: 1481191640

View Profile Personal Message (Offline)

Ignore
1481191640
Reply with quote  #2

1481191640
Report to moderator
1481191640
Hero Member
*
Offline Offline

Posts: 1481191640

View Profile Personal Message (Offline)

Ignore
1481191640
Reply with quote  #2

1481191640
Report to moderator
tlhonmey
Jr. Member
*
Offline Offline

Activity: 37


View Profile
January 19, 2012, 09:35:55 PM
 #2

Yes.  Bitcoind operates the same way.  It's the same program, but with only a CLI interface instead of both the CLI and the GUI.  Your best bet for doing what you're trying to do is probably to create a new wallet and transfer the required amount to a single address in it.  Then, when you send it on to the recipient, that single address will be the only possible source and all of the coins will come from it.


The simpler solution for the problem would be for the recipient to generate a new address and pass it to you and only you through a secure channel.  Then any coins showing up at that address almost certainly came from you, with a probability of exception so low as to not be worth calculating.

If neither of those solutions will work, then I'll need more details about just what you're trying to do.

Non plaudite, iam pecuniam iacite.
1N3nbedLt7PLKLapLbR1Jq7k5rTRGvjEV5
grue
Global Moderator
Legendary
*
Offline Offline

Activity: 1932



View Profile
January 20, 2012, 02:36:18 AM
 #3

1. use blockexplorer and find where the coins were sent from
2. use signmesage rpc/cli command to sign a string like "I'm nhodges!!!"
3. receiver can verify the message using verifymesage

It is pitch black. You are likely to be eaten by a grue.

Tired of annoying signature ads? Ad block for signatures
Garr255
Legendary
*
Offline Offline

Activity: 952


What's a GPU?


View Profile
January 24, 2012, 06:24:31 AM
 #4

1. use blockexplorer and find where the coins were sent from
2. use signmesage rpc/cli command to sign a string like "I'm nhodges!!!"
3. receiver can verify the message using verifymesage

Thanks for that bit of info Cheesy

“First they ignore you, then they laugh at you, then they fight you, then you win.”  -- Mahatma Gandhi

Average time between signing on to bitcointalk: Two weeks. Please don't expect responses any faster than that!
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!