📅 Original date posted:2014-04-09
📝 Original message:This could probably be done fairly easily by bundling Stratum (it's
not just for pools!) and allowing SPV wallets to ask Bitcoind to start
it (if you don't use it, there's no need to waste the resources), and
then connect to it. The point of using Stratum is that it already is
being used by Electrum, and that it might be an easier way to support
SPV clients than creating a new API in bitcoind for it since Stratum
itself already relies on bitcoind to provide it's services.
On Wed, Apr 9, 2014 at 5:29 PM, Wladimir <laanwj at gmail.com> wrote:
> Hello,
>
> This is primarily aimed at developers of SPV wallets.
>
> The recently reported decrease in number of full nodes could have several
> reasons, one of them that less people are running Bitcoin Core for the
> wallet because the other wallets are getting ahead in both features and
> useability.
>
> It's great to see innovation in wallets, but it's worrying that the number
> of full nodes decreases.
>
> It may be that lots of people would support the network by running a full
> node, but don't want to go through the trouble of installing bitcoin core
> separately (and get confused because it's a wallet, too).
>
> Hence I'd like to explore the idea of adding an option to popular SPV
> wallets, to spin a bitcoind process in the background. This could be pretty
> much transparent to the user - it would sync in the background, the wallet
> could show statistics about the node, but is not dependent on it.
>
> In exchange the user would get increased (full node level) security, as the
> SPV wallet would have a local trusted node.
>
> Does this sound like a good idea?
>
> Is there any way that Bitcoin Core can help to accomedate this 'embedded'
> usage? Specific Interfaces, special builds - maybe add a walletless bitcoind
> build to gitian - bindings, dlls, etc?
>
> Wladimir
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
Natanael [ARCHIVE] /
npub179…lpmjt
2023-06-07 15:18:10
in reply to nevent1q…sv3r
Author Public Key
npub1798ncudyucap9jzzujjsgufx8tdykm8auzfledjcs6f6wf4ekqvq8lpmjtPublished at
2023-06-07 15:18:10Event JSON
{
"id": "2060c33c2ac772dba14dfdc364a3838904b27dac5d5d4a86f0bd45c7b5048e38",
"pubkey": "f14f3c71a4e63a12c842e4a50471263ada4b6cfde093fcb6588693a726b9b018",
"created_at": 1686151090,
"kind": 1,
"tags": [
[
"e",
"ed99a8ad47eb2c18db74cd3bd79e8fcc6fa95e61654848c6ab9c5bb9f7a7e8bf",
"",
"root"
],
[
"e",
"5c8f3b430492afe7b14d1a8be50c88415c5fa6fe21c5b94f613ae5c98f32eeb7",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "📅 Original date posted:2014-04-09\n📝 Original message:This could probably be done fairly easily by bundling Stratum (it's\nnot just for pools!) and allowing SPV wallets to ask Bitcoind to start\nit (if you don't use it, there's no need to waste the resources), and\nthen connect to it. The point of using Stratum is that it already is\nbeing used by Electrum, and that it might be an easier way to support\nSPV clients than creating a new API in bitcoind for it since Stratum\nitself already relies on bitcoind to provide it's services.\n\nOn Wed, Apr 9, 2014 at 5:29 PM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\u003e Hello,\n\u003e\n\u003e This is primarily aimed at developers of SPV wallets.\n\u003e\n\u003e The recently reported decrease in number of full nodes could have several\n\u003e reasons, one of them that less people are running Bitcoin Core for the\n\u003e wallet because the other wallets are getting ahead in both features and\n\u003e useability.\n\u003e\n\u003e It's great to see innovation in wallets, but it's worrying that the number\n\u003e of full nodes decreases.\n\u003e\n\u003e It may be that lots of people would support the network by running a full\n\u003e node, but don't want to go through the trouble of installing bitcoin core\n\u003e separately (and get confused because it's a wallet, too).\n\u003e\n\u003e Hence I'd like to explore the idea of adding an option to popular SPV\n\u003e wallets, to spin a bitcoind process in the background. This could be pretty\n\u003e much transparent to the user - it would sync in the background, the wallet\n\u003e could show statistics about the node, but is not dependent on it.\n\u003e\n\u003e In exchange the user would get increased (full node level) security, as the\n\u003e SPV wallet would have a local trusted node.\n\u003e\n\u003e Does this sound like a good idea?\n\u003e\n\u003e Is there any way that Bitcoin Core can help to accomedate this 'embedded'\n\u003e usage? Specific Interfaces, special builds - maybe add a walletless bitcoind\n\u003e build to gitian - bindings, dlls, etc?\n\u003e\n\u003e Wladimir\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment\n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees\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",
"sig": "f69cbb9481bd5263a14467074f320a877186e75b359de955ae4dbf5778e607a307d3277f3ba4f78838df53e19fe8a12202fc08de95d0842594603f36b9a14420"
}