{"type":"rich","version":"1.0","author_name":"npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6m","author_url":"https://nostr.ae/npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6m","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-03-13\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nOn 03/13/2015 04:48 PM, Mike Hearn wrote:\n\u003e That would be rather new and tricky legal territory.\n\u003e \n\u003e But even putting the legal issues to one side, there are\n\u003e definitional issues.\n\u003e \n\u003e For instance if the Chainalysis nodes started following the\n\u003e protocol specs better and became just regular nodes that happen to\n\u003e keep logs, would that still be a violation? If so, what about\n\u003e blockchain.info? It'd be shooting ourselves in the foot to try and\n\u003e forbid block explorers given how useful they are.\n\nI'm not talking about keeping logs, I mean purporting to be a network\npeer in order to gain a connection slot and then not behaving as one\n(not relaying transactions), thereby depriving the peers to which\noperator actually intends to offer service of the ability to connect.\n\nThat someone wants to run a large number of nodes in order to make\ntheir own logs more saleable, does not mean they are entitled to break\nthe protocol to make other node operators subsidize their log collection.\n\nEspecially if a data collection company is deploying nodes that do not\nrelay and aggressively reconnect after a ban, it seems like they'd\nhave a hard time arguing that they were not knowingly exceeding\nauthorized access.\n-----BEGIN PGP SIGNATURE-----\n\niQIcBAEBAgAGBQJVA16sAAoJECpf2nDq2eYjxsUP/3ASGcsdGR8IEO7Fk8VghuVp\njwIIM8Bu/WsoWKG76GhuPKs/qC0VC6GXKpGUBVy7bF8uwdhfdSXcyld9MIzIENJF\nI0wMX6B3SjqQG/g0rNZ91Dh3xKIF39/TQdDERM3yiQi1oavAc5TPLReN9ZbyRcVw\nvCfPWorTvrad5INCn/krcEopbI013aW2ryWnkN6sFGinF5Yf4xhrNQbQeGbhlH15\n/XUIBva6/PbUs4HaC+wqJPSUfB4OmcP1ZfXMuPDEmKEWdI+3WqUYF4sNAVOke560\n+RL5qMJIxSUMYMAb3p+025Fn6WOc2wupQzpH/ISkuaI+5+ne54Mx/ZHJg7Z7inov\nWMKfiUS6R8EHrY8IoNpO9uNqsgC+y0vlU3ELqu+gOhFTpMK7pVX2aAek8Qe7hSHy\nGwtG5U6AFubLqyzP9/pBJHnmDG71brsKffAXOePDjXWfLfhy78aeQ3HOnzVhv9QK\nsnmE2C6Ex/tQDUwT9MKTdw59Hy7E7GdQlSPH+MYQKUBlkpWLDGpi7oriBRwvEy4/\nNJCJU9+x7jijD7vrjBE+LSYdIQoZqE240N6teWqVc2wRPM8g+e+kSQqfjdKQdiQY\nwaeKHBKerqRq2EGffeJWV1RIEFtFND1l8zw/5ZQF4w959zLvhk/QPHzxKyTbCM2f\n3DOgEWCJFLsNzpPQ8es2\n=MV9D\n-----END PGP SIGNATURE-----\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: 0xEAD9E623.asc\nType: application/pgp-keys\nSize: 18381 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150313/dafc843f/attachment.bin\u003e"}