|
Ubuntu. Even if there's a patch for this problem, it's good to have a backup for if Bitcoin does crash.
|
|
|
|
|
This idea needs reviving.
|
|
|
|
|
Today bitcoind locked up on my server and wasn't responding to errors.
Apart from saying 'bitcoin shouldn't crash', what kind of backup systems could exist to gracefully recover when Bitcoin locks up?
Not sure what can be done except calling an safety check hook which kills/restarts bitcoind. Ideally it'd be nice to run multiple nodes and switch between them freely (sharing the same wallets or having 'backup' nodes with a BTC store).
|
|
|
|
|
Yep, I meant along the lines of: increment class counter, store it as private ID.
|
|
|
|
The class on the wiki already supports automatic introspection and uses python's Decimal class: https://en.bitcoin.it/wiki/API_reference_%28JSON-RPC%29#Pythonimport urllib
import decimal
import json
class JSONRPCException(Exception):
def __init__(self, rpcError):
Exception.__init__(self)
self.error = rpcError
class ServiceProxy(object):
def __init__(self, serviceURL, serviceName=None):
self.__serviceURL = serviceURL
self.__serviceName = serviceName
def __getattr__(self, name):
if self.__serviceName != None:
name = "%s.%s" % (self.__serviceName, name)
return ServiceProxy(self.__serviceURL, name)
def __call__(self, *args):
postdata = json.dumps({"method": self.__serviceName, 'params': args, 'id':'jsonrpc'})
respdata = urllib.urlopen(self.__serviceURL, postdata).read()
resp = json.loads(respdata, parse_float=decimal.Decimal)
if resp['error'] != None:
raise JSONRPCException(resp['error'])
else:
return resp['result'] How does this improve on that? I saw that you're using httplib instead of urllib. Any reasons for that? Also you may wish to read, http://www.python.org/dev/peps/pep-0008/Python libraries generally follow that style as to provide a consistent API. It doesn't always happen but everybody tries to use that same standard  Using the ID count is clever. Would it maybe be a good idea to either make that a class variable? For when people instantiate multiple Proxies across threads or something. |
|
|
|
Hi Everyone,
what would cause the BTC exchange rates to rise?
FUND INFLOWS INTO THE EXCHANGES from existing and / or new users. To make the BTC/USD exchange rate rise, the economy needs around 8000 BTCs worth of inflows every day (160 blocks per day * 50 = 8000 BTC). This of course assumes that all miners convert all back to USD regularly and dont save bitcoins at all, which is not 100% correct.
Still, there needs to be significant money inflows into BTCs regularly as we know that miners need to offset their costs and pay off hardware, pay electricity etc.
What could make BTC rates fall: no further money inflows make the BTC/USD rate fall on its own weight (because of the BTC inflation due to mining)
This means that ideally every current bitcoin users should convince another new user to start getting into bitcoins.
Perhaps we can start a tell-a-friend mechanism where there are incentives for existing users?
We need more FUND INFLOWS. We know what supply is. Over 5 million in circulation and a small fraction of that floating. More currency exchange is what we need. More points of entry. The Bottleneck is the conversion of fiat into BTC and vice versa. it's too difficult for most people. Mt Gox is important but we need larger and more numerous points of conversion. That is the key. Goods and services available for bitcoin directly will help but the explosive growth comes from BTC/fiat convertibility and the ease with which that is provided. for Britcoin is free. You can either try to set it up yourself, or I will do it for 600 BTC. Or 2 people at the same time for 800 BTC. |
|
|
|
|
Fool. I PM'ed you to ask if you want to help out. You replied then did nothing.
Your loss.
Don't know about Kiba but I suspect the same.
Are you both 12? I guess you're only good for making crappy forum posts attacking people rather than taking the initiative to write useful code. Not here to be your parent. In the future if you want to work on the net, you have to be pro-active and self-directed.
|
|
|
|
|
Excited to see where this goes! Where did you get this machine to mod?
|
|
|
|
Hey guys, Just thought you'd want to keep up on my daily adventures about me me me. So, I might shave my head completely... Honestly, do I pull it off well it enough to keep it like this in the long-term? Look at me... please.  |
|
|
|
 Anyone got the highres verrsion of this? thanks |
|
|
|
Sure.  Might take a few hours to paint the pictures. EDIT: Give me Saturday. Since this isn't a full site, I don't want donations either. EDIT2: Just so you know I'm working on this and haven't forgotten... Still early stages. But you can see the futuristic abstract direction we're going with:  |
|
|
|
It looks like at some point your remote machine had a commit that the local or gitorious didn't have. Now every pull from your remote machine is a merge.
Bleh. Will it be fixed then if I do a re-clone and use that one? |
|
|
|
|
I guess so.
If you can place a test.html in / and it works then that's probably your problem.
|
|
|
|
What files did you get in the install? I have: NameVirtualHost *:80
NameVirtualHost *:443
Listen 80
Listen 443
<VirtualHost *:443>
SSLEngine On
SSLCertificateFile /etc/apache2/ssl/britcoin.co.uk.crt
SSLCertificateKeyFile /etc/apache2/ssl/britcoin.co.uk.key
SSLCertificateChainFile /etc/apache2/ssl/gd_bundle.crt
ServerAdmin webmaster@britcoin.co.uk
ServerName britcoin.co.uk
DocumentRoot /www
ErrorLog /apache2/error.log
CustomLog /apache2/access.log combined
</VirtualHost>
Maybe that helps. |
|
|
|
FWIW, this is the python recipe, straight from Python documentation: >>> import decimal
>>> json.loads('1.1', parse_float=decimal.Decimal)
Decimal('1.1')
Except Python's JSON-RPC has no support for that. You have to use my (non-standard) modified version: https://en.bitcoin.it/wiki/API_reference_%28JSON-RPC%29#PythonI prefer wherever possible that people stick with official libraries. Bitcoin now is effectively saying that all other languages are broken therefore we won't fix our API. Oh but there's a hack you can use to workaround... It's mostly accurate to the 8th decimal place. Not the point! By exposing an API which nearly all languages interpret as floats, you are expressing a statement of intent that it's fine to use floats for clients (API users). It should be passed as strings (without the decimal point preferably) that users have to explicitly cast to mutable objects. Then they realise that since these values are in INT51 strings (since we can't use large ints in JSON), they'll hopefully understand to deal with the values using ints. You're encouraging users to deal with floats ATM. Bad practice, and shouldn't be encouraged. I am really paranoid about leakage, and for me to even touch a float when dealing with people's money is unacceptable. On Britcoin, there's a whole system of balances and checks at every stage of the various transactions to ensure consistency to all decimal places, and I would not want to throw a spanner in the works because of a tiny rounding error (which would throw up flags and warnings everywhere). Even hearing the words round(...) is like heresy. |
|
|
|
|
Why not make the wiki the front page?
I could even put that weusecoins as a huge banner on there.
|
|
|
|
On my local machine I push some commits: * 26810c9 (HEAD, origin/master, master) force fixed precision in exchange rates SQL.
* 2cc7743 fixed conversion function to stop float rounding errors.
* f61ca2e changed exchange rate wording to reflect new alg.
* 08ec5ac fixed decimal places for exchanger. I login to the remote machine and pull: * d095816 (HEAD, master) Merge branch 'master' of git://gitorious.org/intersango/m
|\
| * 26810c9 (origin/master, origin/HEAD) force fixed precision in exchange rates SQL
* | 85590e6 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * 2cc7743 fixed conversion function to stop float rounding errors.
* | f354456 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * f61ca2e changed exchange rate wording to reflect new alg.
* | 37af61e Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * 08ec5ac fixed decimal places for exchanger.
| * ebc9a87 per nanotube's suggestion: switch buy to show sell rates & vice versa.
* | 607d762 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \ Ugly! I have no local changes on the remote machine. How can I fix the merge graph so it's just a straight line like on my local machine. I don't see why it's needed to do merges when I have no changes locally. |
|
|
|
|
Show Posts
