Author

Topic: Bitcoin and WebRTC (Read 1797 times)

legendary
Activity: 1386
Merit: 1000
October 25, 2013, 05:36:58 PM
#2
Might be it is better to implement darkexchange this way.
In darkexchange the orders can be limited in time (and purged),
thus the local database can be small

retroshare might also be a good candidate, because there is no need to keep full history.
Only state is kept.

http://bennolan.com/2013/08/28/dispersion,-a-webrtc-social-network.html
full member
Activity: 136
Merit: 100
June 02, 2011, 01:19:17 PM
#1
Has anybody considered implementing Bitcoin in the browser on top of WebRTC?

Quote
Google WebRTC, all open source, is part of the web revolution that allows one browser to talk directly to another without the need for a server getting involved.

Source: http://tech.slashdot.org/story/11/06/02/1541246

I think having something like that would be really cool and very convenient. One wouldn't need to worry about downloading a separate bitcoin client, but could simply load up the application in the browser and be good to go.

Here is another article discussing WebRTC:

Quote
Can my browser speak to your browser?
Written by Harry Fairhead  
Monday, 09 May 2011 00:00

New P2P and real time communications APIs currently under development by W3C could revolutionize the architecture of the web and the way users can interact with one another.
Currently the web is mostly a client-server architecture. That is the web browser connects to a server to download a page or any data for that matter. Servers are the single source of information on the web and browsers are their clients. This could be all about to change and so bring about the biggest revolution since the web was invented. If you think HTML5 or Ajax are important, then the new P2P and real time communications APIs that are under development by W3C should open your eyes to the fact that it is a much bigger world out there than you have so far dreamed of.

Source: http://www.i-programmer.info/news/81-web-general/2402-can-my-browser-speak-to-your-browser.html
Jump to: