Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser-based demo ideas? #15

Open
paulkernfeld opened this issue Feb 12, 2016 · 8 comments
Open

Browser-based demo ideas? #15

paulkernfeld opened this issue Feb 12, 2016 · 8 comments

Comments

@paulkernfeld
Copy link

I'm interested in implemented a browser-based demo that shows off the power of webcoin. Any ideas about this?

One pretty simple idea is to show activity from a hard-coded list of richest bitcoin addresses.

It would also be cool to show a visualization of all transactions that are occurring, but that would require a lot of bandwidth from web seeds.

I think an issue that would need to be tackled is web seed reliability, which I mentioned in #5.

@mappum
Copy link
Owner

mappum commented Feb 13, 2016

I think that's a good idea, maybe we should just start with a simple block explorer since the block header sync happens very quickly, and we can download full blocks when necessary on an ad-hoc basis. This wouldn't be able to look up addresses without a blockchain scan, but it could show newly announced transactions.

that would require a lot of bandwidth from web seeds

Do you mean the web bridges? Because the seeds only handle addresses and signaling of peers, they don't deal with the actual data. Web bridges would use bandwidth relaying the transactions, but not any more than a normal TCP peer connection.

@paulkernfeld
Copy link
Author

Yes, sorry, I meant web bridges, not web seeds. You're right that this will work fine once enough people are running bridge nodes, but if there are only a couple bridges, there might be a lot of load on them.

1 similar comment
@paulkernfeld
Copy link
Author

Yes, sorry, I meant web bridges, not web seeds. You're right that this will work fine once enough people are running bridge nodes, but if there are only a couple bridges, there might be a lot of load on them.

@mappum
Copy link
Owner

mappum commented Feb 15, 2016

Right, we'll have to do our best to get people to run bridges. It may make
sense to run then by default for webcoin clients running on Node.js.
On Feb 15, 2016 6:19 AM, "Paul Kernfeld" [email protected] wrote:

Yes, sorry, I meant web bridges, not web seeds. You're right that this
will work fine once enough people are running bridge nodes, but if there
are only a couple bridges, there might be a lot of load on them.


Reply to this email directly or view it on GitHub
#15 (comment).

@latimesmike
Copy link

Hello, I'm new here and I'm not sure this is possible with WebCoin, but I was wondering if it was possible to create a simple checkout demo?

Something like monitoring an address for an incoming payment, and show a success message once the full price has been paid? I was having trouble getting an easy/low cost way to do this for another project, and services like Blockcypher charge thousands of dollars for full access to their API that monitors addresses. Might be a useful demo to show developers how easy it could be to process a payment with a the WebCoin library.

@Head
Copy link

Head commented Nov 9, 2016

Hi @latimesmike wouldn't be that hard, you can look at my code at Gotoshi what you need would be the constructor stuff and maybe reading the raw transactions, look at the function decodeTransaction (maybe not the best implementation, but it worked for my purpose)

@paulkernfeld
Copy link
Author

I put up a simple demo, "Bitcoin Eater Live Feed," here. It just shows a live feed of bitcoins sent to the address 1BitcoinEaterAddressDontSendf59kuE. Hopefully this will be one of many demos!

@mappum
Copy link
Owner

mappum commented Nov 21, 2016

@Head @paulkernfeld Nice webcoin applications! We should build a list of applications that people can demo and put it in the wiki or README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants