Great! I'll test when I'll have some free time and put up a public server online.
Ditto. I have so many projects tho, it might be a while. Keep up the great work. The readability of python is a great benefit. |
|
|
|
like I stated on the other thread, BTCWebHost.com would be happy to offer full scale free hosting on our server.
Thanks for the support. If this is done right, we won't need any web hosting for the chain. However, hosting an e-portfolio service could still be of benefit. Just because we don't need web wallets, doesn't mean they don't exist (see instawallet) |
|
|
|
Some people are not content with the centralization and coresponding lack of control surrounding GLBSE. If a new exchange is setup, would you be interested in moving to it? Migrating/liquidating shares is something that we are going to have to figure out. There's a thread discussing our GLBSE alternative here: https://bitcointalk.org/index.php?topic=52494.0 |
|
|
|
|
Theres so many projects that I want to help out! Bitcoiners are still coming up with great ideas.
I'll pledge 10 BTC. I'll pledge 5 more if I ckolivas pulls the code into his main branch (even if he codes it). I think this would help us by keeping bugs to a minimum. Multiple versions of cgminer are sure to only complicate things and slow features down.
|
|
|
|
A blockchain implementation sounds nice for keeping everything distributed over p2p, but I see some potential problems (that I hope we can work out). For the sake of simplicity, lets call our fork stockcoin. Would you mine stockcoins just like bitcoins or would merged mining be a good idea? (I think merged mining would be smart) Would stockcoins be destroyed when a stock is purchased? Would there be a limited number of stockcoins? If there are a limited number, and they are being destroyed, what do we do when they are all gone? How do we tie the chains together? Right now you buy stocks on GLBSE with BTC. I'm assuming we would want to keep this ability even though our transactions are outside of the bitcoin chain. If we can tie our stockcoin to any other chain (not just bitcoin), I think we will be better off. Could we somehow tie into namecoin (or at least take their ideas)? We could use the personal namespace (or a similar namespace) to register an asset and it's pgp keys. http://dot-bit.org/Personal_NamespaceI think actually using namecoin might not be a good idea as it doesn't really have anything for issuing/selling stocks, but using some of its ideas could give us a head start. |
|
|
|
+1 for thie entire thread. GLBSE is a great idea, but execution and support has sadly faltered in the last few weeks/months.
We need either a distributed GLBSE (possibly utilizing blockchain tech), or one with a serious organization behind it.
I'm a web developer, and interested in assisting with building an open-source web exchange similar to GLBSE. A block-chain based exchange would be cool, but I would be less able to assist with it. Could we somehow use the personal namespace of namecoin? Should we start another thread to discuss this? EDIT: Looks like someone beat me to it. https://bitcointalk.org/index.php?topic=52494.0 |
|
|
|
You still seem to be being browser-centric. I have servers which don't even have a browser on them - and if .bit ever gains wider traction, I'd like them to be able to resolve .bit names. (for email, serverside api requests etc)
If various applications that might need to talk to your .bit domain need to be specifically configured or even reprogrammed - it greatly reduces the utility of the whole idea.
This is easy to do on a server with a socks proxy or by setting up your own DNS server. Yeah like Joe Average will do that. No chance. Namecoin just slipped and is now under SLC and BTC. Sad. Joe Average doesn't run servers... |
|
|
|
You still seem to be being browser-centric. I have servers which don't even have a browser on them - and if .bit ever gains wider traction, I'd like them to be able to resolve .bit names. (for email, serverside api requests etc)
If various applications that might need to talk to your .bit domain need to be specifically configured or even reprogrammed - it greatly reduces the utility of the whole idea.
This is easy to do on a server with a socks proxy or by setting up your own DNS server. |
|
|
|
I see a few implementations now of web services offering a green address option for sending bitcoins. But are there currently any that have stated they will accept them?
Instawallet will directly accept transactions from green addresses at some point. I am currently reworking the backend to make this easier for me to achieve and also be able to manage the risk (e.g. put a limit on the amount of unconfirmed funds that can be pending at any moment). How will this list of green addresses be populated? |
|
|
|
|
Awesome diagrams! I am really getting interested in scripts. This cleared up some grey areas for me on the "basic" transactions. Thanks!
|
|
|
|
|
I think someone asking a simple question like this should be given the most accurate answer.
What is obvious to you is obvious to you. Plenty of people seem to think that mining in a PPS pool actually mines that share. They are wrong, but not being explicit in answers like this is what helps to spread confusion.
|
|
|
|
About:
1 every 12 seconds.
5 every minute
50 every 10 minutes
300 every hour
7200 every day
50400 every week
2629728 every year (averaging for leap years)
Or:
Exactly 7588400 so far, in 1028 days of Bitcoin existence, averaging 7383 per day.
There aren't 5 made a minute. Thats if you look at the averages. 50 are made about every 10 minutes. |
|
|
|
The message appears because Bitcoin is talking to IPs directly over SOCKS4. Even if you stop Bitcoin from using DNS with the -nodnsseed and -noirc switches, you'll still get the warning.
But those flags would be safer, correct? I'm fine with warnings if I am sure that the IPs were given as IPs and not as names. |
|
|
|
|
Very neat. How much work would it be to write arbitrary scripts offline and then broadcast them?
I really like the idea of contracts and getting a way to write them easily and securely would be awesome.
|
|
|
|
I setup a small xubuntu VM to act as a safe for my wallet. I installed tor, polipo, and vidalia more for fun than anything. I set bitcoind to use the tor proxy and set my browser to use polipo. My browser is able to connect to the tor network fine. I added the proxy to my bitcoin.conf Bitcoin seems to be using the proxy, but when I look at Vidalia's message log, I see lots of Potentially Dangerous Connection!
One of your applications established a connection through Tor to "x.x.x.x:8334" using a protocol that might leak information about your destination. Please ensure you configure your applications to use only SOCKS4a or SOCKS5 with remote hostname resolution. So then I did sudo apt-get install torsocks
and then I start the daemon with but I get console warnings and I still get the "Potentially Dangerous Connection!" messages [user@btc-ubuntu ~]$ torify bitcoind -daemon
16:57:35 libtorsocks(2539): The symbol res_init() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_query() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_search() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_send() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_querydomain() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_init() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_query() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_search() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_send() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_querydomain() was not found in any shared library. The error reported was: not found!
Has anyone done this successfully without warning messages? |
|
|
|
|
This sounds really cool. It would be neat to have a site that sells vanity addresses based on their difficulty that you would not need to trust.
|
|
|
|
|
Show Posts
