{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-09\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nTwo talking points for said developers yo their user re: \"Why use a full node?\":\n\n1) It's more private. Bloom filters gives away quite accurate statistical information about what coins you own to whom ever you happen to be connected too. An attacker can easily use this to deanonymize you even if you don't reuse addresses; Tor does not help much against this attack.\n\n2) It's more secure. SPV means you are trusting miners to do validation for you. With the extremely high degree of mining centralisation we currently have it would only take one or two pools getting hacked for an attacker to be able to get enough hashing power to easily fool your SPV wallet into accepting a fake transaction.\n\n\nAs for what we can offer those developers, partial UTXO set mode would be a great long term goal.\n\nOn 9 April 2014 11:29:32 GMT-04:00, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\u003eHello,\n\u003e\n\u003eThis is primarily aimed at developers of SPV wallets.\n\u003e\n\u003eThe recently reported decrease in number of full nodes could have\n\u003eseveral\n\u003ereasons, one of them that less people are running Bitcoin Core for the\n\u003ewallet because the other wallets are getting ahead in both features and\n\u003euseability.\n\u003e\n\u003eIt's great to see innovation in wallets, but it's worrying that the\n\u003enumber\n\u003eof full nodes decreases.\n\u003e\n\u003eIt may be that lots of people would support the network by running a\n\u003efull\n\u003enode, but don't want to go through the trouble of installing bitcoin\n\u003ecore\n\u003eseparately (and get confused because it's a wallet, too).\n\u003e\n\u003eHence I'd like to explore the idea of adding an option to popular SPV\n\u003ewallets, to spin a bitcoind process in the background. This could be\n\u003epretty\n\u003emuch transparent to the user - it would sync in the background, the\n\u003ewallet\n\u003ecould show statistics about the node, but is not dependent on it.\n\u003e\n\u003eIn exchange the user would get increased (full node level) security, as\n\u003ethe\n\u003eSPV wallet would have a local trusted node.\n\u003e\n\u003eDoes this sound like a good idea?\n\u003e\n\u003eIs there any way that Bitcoin Core can help to accomedate this\n\u003e'embedded'\n\u003eusage? Specific Interfaces, special builds - maybe add a walletless\n\u003ebitcoind build to gitian - bindings, dlls, etc?\n\u003e\n\u003eWladimir\n\u003e\n\u003e\n\u003e------------------------------------------------------------------------\n\u003e\n\u003e------------------------------------------------------------------------------\n\u003ePut Bad Developers to Shame\n\u003eDominate Development with Jenkins Continuous Integration\n\u003eContinuously Automate Build, Test \u0026 Deployment\n\u003eStart a new project now. Try Jenkins in the cloud.\n\u003ehttp://p.sf.net/sfu/13600_Cloudbees\n\u003e\n\u003e------------------------------------------------------------------------\n\u003e\n\u003e_______________________________________________\n\u003eBitcoin-development mailing list\n\u003eBitcoin-development at lists.sourceforge.net\n\u003ehttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\n-----BEGIN PGP SIGNATURE-----\nVersion: APG v1.1.1\n\niQFQBAEBCgA6BQJTRW88MxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8\ncGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhUIBB/4tVMqj7NEHFekUgv7O\nhKgUNreD5RQbVLjiG9BIKWTdOrD79qNk66QVxuH7oOCypMLCdT2ctdvsvfH8ncdG\nGVpTcbXL39vEk9qkGN4wY2++pKn5unqKg1C99YbJAcC62XMFJjjES2XiwyKGsYmb\nIplOEN7BXh9KE01f7gPh4nZqtqsb6XnlLQGjjRWGlX/oIMphUOdfMtBdWql59bx3\nwnHUDc1pAv2bCcyiUI/nOoyNyZixZC16wXoM2pnAJ9PhPbd79lmiKVmjNmrqhu17\nHIHlKXk6YD8JVlHD8NoaC1GUwG39jmt5nk1vsfvvesXF+c0VqctVNIitVkvqLNj+\nmwXd\n=4b5H\n-----END PGP SIGNATURE-----"}
