rich1.0npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6mhttps://nostr.ae/npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6mnjumphttps://nostr.ae📅 Original date posted:2015-03-13 📝 Original message:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/13/2015 04:48 PM, Mike Hearn wrote: > That would be rather new and tricky legal territory. > > But even putting the legal issues to one side, there are > definitional issues. > > For instance if the Chainalysis nodes started following the > protocol specs better and became just regular nodes that happen to > keep logs, would that still be a violation? If so, what about > blockchain.info? It'd be shooting ourselves in the foot to try and > forbid block explorers given how useful they are. I'm not talking about keeping logs, I mean purporting to be a network peer in order to gain a connection slot and then not behaving as one (not relaying transactions), thereby depriving the peers to which operator actually intends to offer service of the ability to connect. That someone wants to run a large number of nodes in order to make their own logs more saleable, does not mean they are entitled to break the protocol to make other node operators subsidize their log collection. Especially if a data collection company is deploying nodes that do not relay and aggressively reconnect after a ban, it seems like they'd have a hard time arguing that they were not knowingly exceeding authorized access. -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJVA16sAAoJECpf2nDq2eYjxsUP/3ASGcsdGR8IEO7Fk8VghuVp jwIIM8Bu/WsoWKG76GhuPKs/qC0VC6GXKpGUBVy7bF8uwdhfdSXcyld9MIzIENJF I0wMX6B3SjqQG/g0rNZ91Dh3xKIF39/TQdDERM3yiQi1oavAc5TPLReN9ZbyRcVw vCfPWorTvrad5INCn/krcEopbI013aW2ryWnkN6sFGinF5Yf4xhrNQbQeGbhlH15 /XUIBva6/PbUs4HaC+wqJPSUfB4OmcP1ZfXMuPDEmKEWdI+3WqUYF4sNAVOke560 +RL5qMJIxSUMYMAb3p+025Fn6WOc2wupQzpH/ISkuaI+5+ne54Mx/ZHJg7Z7inov WMKfiUS6R8EHrY8IoNpO9uNqsgC+y0vlU3ELqu+gOhFTpMK7pVX2aAek8Qe7hSHy GwtG5U6AFubLqyzP9/pBJHnmDG71brsKffAXOePDjXWfLfhy78aeQ3HOnzVhv9QK snmE2C6Ex/tQDUwT9MKTdw59Hy7E7GdQlSPH+MYQKUBlkpWLDGpi7oriBRwvEy4/ NJCJU9+x7jijD7vrjBE+LSYdIQoZqE240N6teWqVc2wRPM8g+e+kSQqfjdKQdiQY waeKHBKerqRq2EGffeJWV1RIEFtFND1l8zw/5ZQF4w959zLvhk/QPHzxKyTbCM2f 3DOgEWCJFLsNzpPQ8es2 =MV9D -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xEAD9E623.asc Type: application/pgp-keys Size: 18381 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150313/dafc843f/attachment.bin>