-
Notifications
You must be signed in to change notification settings - Fork 46
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
Web interface #67
Comments
I have a small pull request on bitcoinx/bitcoin-abe. I've also got a killerstorm/bitcoin-tx-spent-db version to work with bitcoin-abe called arichnad/bitcoin-tx-spent-db-abe. If you'd like to put that into bitcoinx, that's fine with me. I will continue to develop both bitcoin-abe and arichnad/bitcoin-tx-spent-db-abe to make them better. Once they're better, I'll probably put them up on a server. Is there a server you'd like to see it up on? Or should I put it up on my server? |
Thanks. Yep, we have a server which runs Abe, I'll update it and add explorer code in a couple of days. |
I've added user-defined colors to the javascript side. You can see arichnad/color-explorer-vagrant (which uses arichnad/bitcoin-tx-spent-db-abe and bitcoinx/bitcoin-abe) loaded up here: http://coloredcoinexplorer.org/ I'll continue adding features. Feel free to pull in whatever repos you want to bitcoinx. Any suggestions on new features? Let me know if you have any color definitions you're using for testing. |
Added the ability to parse URLs. So now we can pass around URLs with actual data in them: removed old URL Describes a few colors and goes to a specific transaction. |
Hmm, it didn't work, but anyway: using this kind of format for colors is a bad idea because it can be confusing, as NGCCC uses somewhat similar color_desc format. I think the right way to do it is to remember color set on server. Then user gets color_set_hash for colors he entered, server remembers association of color_set_hash with a set of colors. Page can get color_set_hash in parameter, does lookup on server, gets color set, and proceeds from it The algorithm to get color_set_hash is in ngcccbase: wallet_model.ColorSet.get_hash_string() Basically, it is sha256 of a deterministic JSON serialization of a list of color_desc's. color_desc is of form "obc:::" |
Oops, you can try again. "sha256 of a deterministic JSON serialization of a list of color_desc's" I understand the concept, I'll give it a try. I've been hoping to get the server to help out on color lookups. I might actually abandon bitcoin-tx-spent-db-abe and move most of the code over to the python/sqlite side. |
Is it possible to make it configurable? E.g. there is same front-end, but More code to maintain, but worth it. BTW NGCCC supports both forward scan and backward scan now. It looks like |
…iptor to ngcccbase I'm not sure how to get the height (or why I even need it yet) Also I'm not sure whether to allow the user to input the coloring scheme or not.
…iptor to ngcccbase I'm not sure how to get the height (or why I even need it yet) Also I'm not sure whether to allow the user to input the coloring scheme or not.
Should I use color_set.get_hash_string or color_set.get_color_string? (The latter seems much shorter, but I'm worried it could be too short [re birthday attack]) |
get_hash_string get_color_string is, indeed, too short. (We use it just for a sanity check now.) |
user gets color_set_hash for colors he entered server remembers association of color_set_hash with a set of colors Page can get color_set_hash in parameter, does lookup on server, gets color set, and proceeds from it --upgrade (Abe36)
user gets color_set_hash for colors he entered server remembers association of color_set_hash with a set of colors Page can get color_set_hash in parameter, does lookup on server, gets color set, and proceeds from it
Things Fixed:
Try new URL here: |
I've yet to test between color_set_hash values on ngccc vs coloredcoinexplorer. I've noticed the heights didn't seem right on ngccc when I used it on Tuesday. (also I'm not sure why we need heights, but I'm using them anyways) |
user gets color_set_hash for colors he entered server remembers association of color_set_hash with a set of colors Page can get color_set_hash in parameter, does lookup on server, gets color set, and proceeds from it --upgrade (Abe36)
… and their links to the transaction tables
…vagrant easier.
…vagrant easier.
…e much more push-button now.
…e much more push-button now.
also much better startup scripts.
…. split up the color table into the color and the color_link table.
About a month ago, I noticed people discussing color kernels on the mailing list ad nauseam. Is there a color kernel that we've settled on? I need to make sure bitcoin-abe-color-explorer stays consistent and probably need to get the python parts to use the same color kernel classes if we think this will change. |
It looks like we've settled on epobc. Yes, it's important to use same code, i.e. coloredcoinlib. Please let me know if there is any problem with it. |
I started a conversation with @killerstorm about some ways I can contribute. I think it'll be a web interface.
NOTE: this will likely go into a separate git repo (which might start out as a fork of abe) so as to keep from polluting ngcccbase.
I'd like to discuss what the requirements should be, and then some possible solutions.
To start us off:
Requirements: Should work with user-supplied colors. System should be able to be performant even on colors with lots of transactions.
Possible solution: Fork bitcoinx/bitcoin-abe ?
The text was updated successfully, but these errors were encountered: