Bitcoin Forum
November 09, 2024, 02:38:28 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Why did this transaction send bitcoins back to itself?  (Read 1068 times)
bkc888 (OP)
Member
**
Offline Offline

Activity: 60
Merit: 10


View Profile
November 18, 2013, 01:46:47 PM
 #1

https://blockchain.info/zh-cn/tx/c4de7f7152b117a2946d1c5513019e5dc1e79fa0fb5f9b1752c1c9e1c4e6c944

Thanks.
rebuilder
Legendary
*
Offline Offline

Activity: 1615
Merit: 1000



View Profile
November 18, 2013, 01:49:02 PM
 #2

Can a client be configured to send change to the originating address of the transaction?

Selling out to advertisers shows you respect neither yourself nor the rest of us.
---------------------------------------------------------------
Too many low-quality posts? Mods not keeping things clean enough? Self-moderated threads let you keep signature spammers and trolls out!
CIYAM
Legendary
*
Offline Offline

Activity: 1890
Merit: 1086


Ian Knowles - CIYAM Lead Developer


View Profile WWW
November 18, 2013, 01:49:47 PM
 #3

It just looks like the "change" was sent back to the original address (easy to do using "Coin Control" or by rolling your own "raw transaction").

With CIYAM anyone can create 100% generated C++ web applications in literally minutes.

GPG Public Key | 1ciyam3htJit1feGa26p2wQ4aw6KFTejU
drrussellshane
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


View Profile
November 18, 2013, 01:50:48 PM
 #4

Can a client be configured to send change to the originating address of the transaction?

Yes, and that sounds like what happened here.

Buy a TREZOR! Premier BTC hardware wallet. If you're reading this, you should probably buy one if you don't already have one. You'll thank me later.
kokojie
Legendary
*
Offline Offline

Activity: 1806
Merit: 1003



View Profile
November 18, 2013, 03:34:54 PM
 #5

Can a client be configured to send change to the originating address of the transaction?

blockchain.info wallet can do that

btc: 15sFnThw58hiGHYXyUAasgfauifTEB1ZF6
Barek
Full Member
***
Offline Offline

Activity: 168
Merit: 100


View Profile
November 18, 2013, 03:54:06 PM
 #6

However, it is not ideal to do that.

It reduces privacy (associates an address) and weakens security (reveals the public key).
rbdrbd
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250



View Profile
November 18, 2013, 04:09:15 PM
 #7

Can a client be configured to send change to the originating address of the transaction?

blockchain.info wallet can do that

Armory client can as well (on Expert mode)
rbdrbd
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250



View Profile
November 18, 2013, 04:11:18 PM
 #8

However, it is not ideal to do that.

It reduces privacy (associates an address) and weakens security (reveals the public key).

revealing the public key as-in exposing the address to a potential future quantum attack, or something more than this?
DannyHamilton
Legendary
*
Offline Offline

Activity: 3486
Merit: 4832



View Profile
November 18, 2013, 04:19:38 PM
 #9

However, it is not ideal to do that.

It reduces privacy (associates an address) and weakens security (reveals the public key).

revealing the public key as-in exposing the address to a potential future quantum attack, or something more than this?

When you receive bitcoins at an address that has never been used before, there are three levels of cryptography between the private key and the bitcoin address:

  • First there is ECDSA with the Secp256k1 curve resulting in a public key.
  • Then the public key is hashed with SHA-256.
  • Finally the result of the SHA-256 hash is hashed with RIPEMD-160.

It is the result of this RIPEMD-160 hash that is stored in the blockchain and converted to a bitcoin address.

When you send a bitcoin transaction that spends any of the outputs that have been received at an address, the ECDSA public key is included in the transaction.
This means that you then only have 1 level of cryptography between the address and the private key.  Since the ECDSA public key becomes publicly available, the protection of SHA-256 and RIPEMD-160 are lost.

From then on, any unspent outputs that remain associated with that address (or any new outputs sent to that address) no longer have the protection of SHA-256 or RIPEMD-160
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!