{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-10\n📝 Original message:\u003e\n\u003e I find it is odd that we who hold the key to instant machine to machine\n\u003e micro payments do not use it to incentivise committing resources to the\n\u003e network.\n\u003e\n\nIt's not a new idea, obviously, but there are some practical consequences:\n\n1) To pay a node for serving, you have to have bitcoins. To get bitcoins,\nyou need to sync with the network via a node. Catch 22.\n\n2) If some nodes choose to charge and others choose to not charge, a smart\nwallet will always use the free nodes. In the absence of any global load\nbalancing algorithms, this would lead to the free nodes getting overloaded\nand collapsing whilst the for-pay nodes remain silent.\n\n3) The only payment channel implementations today are bitcoinj's (Java) and\none written by Jeff in Javascript. There are no C++ implementations. And as\nMatt and I can attest to, doing a real, solid, fully debugged\nimplementation that's integrated into a real app is .... a lot of work.\n\nI still think the lowest hanging fruit is basic, boring optimisations\nrather than architectural rethinks.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140410/47c486d0/attachment.html\u003e"}