JSON-RPC support for mobile devices (“ultra-lightweight” clients) #1

1. 
   gavinandresen commented at 4:17 pm on December 19, 2010: contributor

   The idea is to enable mobile or other not-always-connected-to-the-network clients, where the wallet is kept (encrypted, probably) on the mobile device, and the device periodically communicates with a bitcoin-network-connected node to:

   • Update balance for keys in its wallet
   • Submit signed transactions to the network
2. 
   rasos commented at 1:43 pm on February 7, 2011: none

   Yes, very important. If we enable mobile devices, pocket wallets will be soon obsolete ;-) GUI for smart-phones should include some QR reader, such as portapayment.com
3. 
   thiloplanz commented at 11:43 am on April 7, 2011: none

   “Submit signed transactions to the network”

   I want that as well, for Google App Engine, where you cannot participate in the regular peer-to-peer protocol, because you cannot open sockets. Having something like an XMPP proxy that pushes signed transactions into the peer network would be cool. Maybe the existing IRC channel can also be used for that.

4. mhanne referenced this in commit ca40e581eb on Jul 20, 2011
5. 
   Stemby commented at 12:35 pm on September 15, 2011: none

   I offer 1 BTC bounty.

   Regards, Carlo

6. gavinandresen closed this on Jan 21, 2013

   ---

7. theuni referenced this in commit 41d67c78bf on Sep 30, 2014
8. theuni referenced this in commit 2573771141 on Sep 30, 2014
9. theuni referenced this in commit 3d3a59be62 on Oct 1, 2014
10. rdponticelli referenced this in commit 78cb860733 on Nov 26, 2014
11. dexX7 referenced this in commit d6a48bf907 on Mar 25, 2015
12. ewgalvare referenced this in commit 02a95be977 on Feb 18, 2016
13. destenson referenced this in commit 47802b4d89 on Jun 26, 2016
14. destenson referenced this in commit 11cb1481a9 on Jun 26, 2016
15. destenson referenced this in commit c544f6ca61 on Jun 26, 2016
16. destenson referenced this in commit fddd577a32 on Jun 26, 2016
17. destenson referenced this in commit 43dc7e958a on Jun 26, 2016
18. practicalswift referenced this in commit 9c184a7b41 on Feb 28, 2017
19. dooglus referenced this in commit fccba75458 on Mar 26, 2017
20. dagurval referenced this in commit 24cf193c3c on Apr 1, 2017
21. nomnombtc referenced this in commit 31c4eeeecb on May 14, 2017
22. Christewart referenced this in commit 73607b5608 on Jun 17, 2017
23. rynomster referenced this in commit b3a81cb027 on Jul 17, 2017
24. laanwj referenced this in commit b13a68e129 on Aug 2, 2017
25. laanwj referenced this in commit 16fff80257 on Nov 30, 2017
26. nining referenced this in commit a3a0d2a31f on Jan 3, 2018
27. nining referenced this in commit ec335b980d on Jan 3, 2018
28. nining referenced this in commit 56c9f02522 on Jan 3, 2018
29. DaElf referenced this in commit 35f0a4e2e9 on Jan 10, 2018
30. HashUnlimited referenced this in commit fb8585691c on Mar 9, 2018
31. fruit37 referenced this in commit 680d702231 on Jul 1, 2018
32. MarcoFalke referenced this in commit 4d550ffab6 on Jul 30, 2018
33. hashtobewild referenced this in commit 4ba45136b7 on Aug 26, 2018
34. laanwj referenced this in commit 2d4749b366 on Sep 17, 2018
35. dooglus referenced this in commit cb2ad9334c on Oct 19, 2018
36. fanquake locked this on Jan 27, 2019
37. stplaydog referenced this in commit e48b45683e on Jun 25, 2019
38. MarcoFalke referenced this in commit 54532f46c4 on Nov 18, 2020
39. DrahtBot added the label CI failed on Apr 2, 2023
40. DrahtBot removed the label CI failed on Apr 2, 2023
41. DrahtBot added the label CI failed on Apr 2, 2023
42. DrahtBot removed the label CI failed on Apr 3, 2023
43. DrahtBot added the label CI failed on Apr 5, 2023
44. MarcoFalke removed the label CI failed on Apr 5, 2023
45. DrahtBot added the label CI failed on Apr 11, 2023
46. MarcoFalke removed the label CI failed on Apr 11, 2023

Contributors
gavinandresen rasos thiloplanz Stemby

Labels
Feature