📅 Original date posted:2014-08-19 📝 Original message:Only messages between ...

Why Nostr? What is Njump?

Raúl Martínez [ARCHIVE] /

npub1w8…a0p0k

2023-06-07 15:25:18

in reply to nevent1q…v5h8

📅 Original date posted:2014-08-19
📝 Original message:Only messages between peers are encrypted, only during transit.

Before sending a transaction to Node B you use his public key, so Node B
has the key
El 19/08/2014 17:05, "Richard Moore" <me at ricmoo.com> escribió:

> If you encrypt all messages with an asymmetric cipher, how would each node
> make use of the blockchain in an encrypted form? Each node would be able to
> encrypt the data, but only the Bitcoin Core Dev could decrypt it?
>
>
> On Aug 19, 2014, at 5:49 AM, Raúl Martínez <rme at i-rme.es> wrote:
>
> Hi,
> I believe that all comunications should be encrypted by default, no matter
> that is public information (tx info), the only exception I would make would
> be block packets (to avoid increasing propagation time).
>
> I suggest that Bitcoin Core should generate a public/private key pair and
> share the public one with peers.
>
> This could provide privacy and integrity but not autentication.
>
> This way you can impersonate a bitcoin node (active mitm) but you cant
> just be passive and record all transactions send or recieved by an IP
> address.
>
> Today you can just watch for incoming/outgoing transactions to determine
> what tx are created in the Node, when you find one you can see the Bitcoin
> address inputs and outputs and track that person's bitcoins.
>
> As an example, SSH provides this kind of encryption, althogh Bitcoin Core
> should ignore fingerprint changes (caused due to reinstalls).
>
> Please feel free to disqus why this is not needed or why you like this
> idea.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> .·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸><(((º>
>
> Richard Moore ~ Founder
> Genetic Mistakes Software inc.
> phone: (778) 882-6125
> email: ricmoo at geneticmistakes.com
> www: http://GeneticMistakes.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140819/65d3df95/attachment.html>;

Author Public Key

npub1w8ktyq2eljfp607atjk67x29ye6d4l8ugd49twgmpuqnn7eruy2sza0p0k

Show more details

Published at

2023-06-07 15:25:18

Kind type

1 Short Text Note

Event JSON

{ "id": "3765f9a5b07783279a1689daa23162f1824bc846f3ca5c9a55f6b891c61c98fc", "pubkey": "71ecb20159fc921d3fdd5cadaf19452674dafcfc436a55b91b0f0139fb23e115", "created_at": 1686151518, "kind": 1, "tags": [ [ "e", "f7d80207f3f3e09247c97d3e8c17b8e8b9ffc855be5e4ac09f019815084b2528", "", "root" ], [ "e", "51ad2fb667aff930cc3987b8c5bde1ca51010d01c2eec9024414ae5a4c33941d", "", "reply" ], [ "p", "71ecb20159fc921d3fdd5cadaf19452674dafcfc436a55b91b0f0139fb23e115" ] ], "content": "📅 Original date posted:2014-08-19\n📝 Original message:Only messages between peers are encrypted, only during transit.\n\nBefore sending a transaction to Node B you use his public key, so Node B\nhas the key\nEl 19/08/2014 17:05, \"Richard Moore\" \u003cme at ricmoo.com\u003e escribió:\n\n\u003e If you encrypt all messages with an asymmetric cipher, how would each node\n\u003e make use of the blockchain in an encrypted form? Each node would be able to\n\u003e encrypt the data, but only the Bitcoin Core Dev could decrypt it?\n\u003e\n\u003e\n\u003e On Aug 19, 2014, at 5:49 AM, Raúl Martínez \u003crme at i-rme.es\u003e wrote:\n\u003e\n\u003e Hi,\n\u003e I believe that all comunications should be encrypted by default, no matter\n\u003e that is public information (tx info), the only exception I would make would\n\u003e be block packets (to avoid increasing propagation time).\n\u003e\n\u003e I suggest that Bitcoin Core should generate a public/private key pair and\n\u003e share the public one with peers.\n\u003e\n\u003e This could provide privacy and integrity but not autentication.\n\u003e\n\u003e This way you can impersonate a bitcoin node (active mitm) but you cant\n\u003e just be passive and record all transactions send or recieved by an IP\n\u003e address.\n\u003e\n\u003e Today you can just watch for incoming/outgoing transactions to determine\n\u003e what tx are created in the Node, when you find one you can see the Bitcoin\n\u003e address inputs and outputs and track that person's bitcoins.\n\u003e\n\u003e As an example, SSH provides this kind of encryption, althogh Bitcoin Core\n\u003e should ignore fingerprint changes (caused due to reinstalls).\n\u003e\n\u003e Please feel free to disqus why this is not needed or why you like this\n\u003e idea.\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n\u003e .·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸\u003e\u003c(((º\u003e\n\u003e\n\u003e Richard Moore ~ Founder\n\u003e Genetic Mistakes Software inc.\n\u003e phone: (778) 882-6125\n\u003e email: ricmoo at geneticmistakes.com\n\u003e www: http://GeneticMistakes.com\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140819/65d3df95/attachment.html\u003e", "sig": "fad0bf03ad0cd4c024bf0a56313aa00c0edf97156e031faf6601b3c5dee76dfe006c11efe5d46c5517fd18d6a96a12a836b795d775b77b71980da5bd52e0214b" }