Bitcoin Forum
August 06, 2024, 09:33:36 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Sending messages with transactions  (Read 977 times)
Gareth Nelson (OP)
Hero Member
*****
Offline Offline

Activity: 721
Merit: 503


View Profile
May 21, 2011, 04:05:01 AM
 #1

There's a simple way to do this without taking up space in the blockchain.
Simply send the transaction ID and your message to an external server, encrypt if desired.

This could be integrated with the client rather easily, but i'm wondering how many would actually use it - thoughts?
FooDSt4mP
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile
May 21, 2011, 04:33:24 AM
 #2

There's a simple way to do this without taking up space in the blockchain.
Simply send the transaction ID and your message to an external server, encrypt if desired.

This could be integrated with the client rather easily, but i'm wondering how many would actually use it - thoughts?

I doubt you'd get support from the official client unless the "external server" was actually a distributed network.  Also, it should be encrypted with the public key the coins were sent to (the address).  The recipient has the matching private key to decrypt it.

As we slide down the banister of life, this is just another splinter in our ass.
Gareth Nelson (OP)
Hero Member
*****
Offline Offline

Activity: 721
Merit: 503


View Profile
May 21, 2011, 04:38:50 AM
 #3

I obviously wouldn't expect the official client to rely on an external server (although oddly enough it still relies on IRC) - but this does seem a sensible idea.
FooDSt4mP
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile
May 21, 2011, 04:47:20 AM
 #4

I obviously wouldn't expect the official client to rely on an external server (although oddly enough it still relies on IRC) - but this does seem a sensible idea.

It doesn't rely on IRC... IRC just helps it bootstrap faster when it is available.  There is a list of fallback nodes (in addition to those built into the client) and -addnode.

Regarding messages: you should probably also require the message be signed by at least one private key matching one of the public keys the transaction is sent from.  Otherwise, messages could be forged.

As we slide down the banister of life, this is just another splinter in our ass.
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!