On Wed, Aug 7, 2013 at 11:44 PM, Mike Hearn <m...@plan99.net> wrote: > >> My concerns here are: >> * Making sure wallet applications can function without supporting the >> P2P protocol (which drops a huge implementation overhead for simple - >> perhaps hardware-based - wallets) > > > How would such wallets get transactions into their wallet in the first > place?
By connecting to some other client, presumably. Have a small hardware client that is able to do payments via NFC/QR/... directly with a merchant, and can get 'recharged' by connecting with your desktop client, for example. Maybe too futuristic to be a concern, but it nicely illustrates how doing direct sender-to-receiver negotiation can help decoupling tasks. > I don't really have a strong opinion either way, but doing more work to > prevent transactions being announced to the network feels weird. Ok. -- Pieter ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development