For what it is worth, I appreciate this info in a clear and timely manner. Stuff happens, but not knowing makes things Much worse. Good job.
Indeed, thank you for the quick and transparent info. Well, why was bitcointalk offline, then? (I was afraid they finally blocked it in the company's proxy! lol) Ente |
|
|
|
|
I still see "Warning! this bitcoin address contains transactions which maybe double spends. You should be extremely careful when trusting any transactions to/from this address." on my p2pool payout address. I only received payments from p2pool there, from nowhere else, and didnt transfer funds away yet.
Ente
|
|
|
|
why are bitcointalk and mtgox hosted on the same server anyway? ..which suggests even more trouble: Gain root on "bitcointalk" = gain root on "MtGox" too. megawallet.dat, achievement unlocked! All this doesnt sound too professionally thought out. Ente |
|
|
|
Pretty cool  If a game is not made, someone could simply make a quick website that sells stamps (like for ink pads). The stamp will say something like "Bitcoin is Happening" and it'd be small so it'd fit in the margin border of the bill. Anyone interested in promoting this viral phenomenon can order a stamp and join the legion. BitcoinIsHappening.com is available... QR Code would be awesome! This is like an IRL bitcoin faucet. All one would have to do is be directed to go to a special site (i like wheres satoshi!) and be presented with simple instructions on downloading a light client or mobile app like bitspinner. How about.. -Make a stamp to stamp QR codes and/or urls on bills. -Create priv keys from the bill's serial number (by sha256 etc) -Transfer smallish amounts do dozens, hundreds of such stamped bills -Website where the QR/url points to lets you directly enter the bill's serial number and the state you live in, lets you redeem the bitcoins and explains what this is all about -Extra points for making this big and viral! Ente |
|
|
|
Everyone already has a copy of the blockchain. All we need is a GUI or CGI to read it.
I would donate to that cause. For me (as a programming novice) it sounds like not-too-complicated to program a blockexplorer/blockchaininfo clone which works with the local blockchain copy? Someone make a bounty thread? Tried Abe? https://bitcointalk.org/index.php?topic=22785.0I love it! :-) Ente |
|
|
|
|
Just found it (from that other thread).
The page says the "seconds" hand does 144 blocks per revolution. why is that? Why 144, and why isnt it 60 blocks, like 1 block = 1 second?
I am unsure what I would use that clock for. mostly I watch the blockcount to wait for the 6 block verification count, and that I do right in bitcoin gui. but then, with an easily understandable and readable bitcoinclock, I would use it whenever I dont send/receive with my local bitcoin instance.
Maybe have a "stopwatch" function? I press "Start!", and can easily see when 6, or 100 blocks were added. Maybe with an alarm (popup, sound, flashing tab, changing tab icon)? Now that would make me use the bitcoinclock exclusively!
Nevertheless, thank you for that, sometimes its the small, easy things that help a lot!
Ente
|
|
|
|
Time to come up some ideas for a decentralized block data tool?
Everyone already has a copy of the blockchain. All we need is a GUI or CGI to read it. I would donate to that cause. For me (as a programming novice) it sounds like not-too-complicated to program a blockexplorer/blockchaininfo clone which works with the local blockchain copy? Someone make a bounty thread? Ente |
|
|
|
Is there any reason you're not using the latest websocket-client version(0.5.1)? Running your script with the latest version I get 'Message: 4:::{"op":"remark","message":"Now online (no channels)"}' lines. Huh?!? I tried it several times, did some more changes to the code, have debug messages print out at several points, and suddenly messages came in? I would say I didnt change any substantial parts, but now it works. Maybe it really was the websocket-client version. Maybe I was unlucky enough to connect when the websocket daemon wasnt sending stuff. Maybe I didnt let the script run long enough. Whatever, I'll get me a a beer now, cheers! :-) Ente Hmpf. I did not change the code since last time. Now I wont get any data any more. Its back ti heartbeats only again. I will now connect new every minute and see if I eventually get data again. So it seems that either the problem still exists, or the socket is totally unstable and only works randomly at best. Do you guys receive data? Ente |
|
|
|
Is there any reason you're not using the latest websocket-client version(0.5.1)? Running your script with the latest version I get 'Message: 4:::{"op":"remark","message":"Now online (no channels)"}' lines. Huh?!? I tried it several times, did some more changes to the code, have debug messages print out at several points, and suddenly messages came in? I would say I didnt change any substantial parts, but now it works. Maybe it really was the websocket-client version. Maybe I was unlucky enough to connect when the websocket daemon wasnt sending stuff. Maybe I didnt let the script run long enough. Whatever, I'll get me a a beer now, cheers! :-) Ente |
|
|
|
Is there any reason you're not using the latest websocket-client version(0.5.1)? Running your script with the latest version I get 'Message: 4:::{"op":"remark","message":"Now online (no channels)"}' lines. Lol now thats unexpected! I found out I use python 2.6.6 which shipped with my Debian, thats why I still have the old websocket-client version. Will see if it helps, thank you for the pointer! Ente Edit: Switched to python 2.7.2, have websocket-client installed for 2.7 only. Still no joy, only heartbeats come in. |
|
|
|
|
Thank you for checking, zelyony!
You are right, thats a typo in the snippet. I sent '1::' and '2::' accordingly in my full script, typo corrected.
I sent '4:::{"op":"mtgox.subscribe","type":"trades"}' over the websocket, no change. No response whatsoever, no trade-messages coming in.
Ente
|
|
|
|
My first problem is from https://bitcointalk.org/index.php?topic=5855.msg749200#msg749200: I try to connect to MtGox via socket.io. I get the connection-id fine, and am able to connect to the websocket too. I then receive heartbeats, which I answer, and continue to receive. I receive no other data. Things I send have no effect. Just heartbeats, nothing else. This code is heavily stripped. The full script worked some weeks ago, using these lines. #!/usr/bin/env python
# -*- coding: utf-8 -*-
from websocket import create_connection
import urllib
import re
import time
try:
import json
except ImportError:
import simplejson as json
wsurl = "wss://socketio.mtgox.com/socket.io/"
iourl = "https://socketio.mtgox.com/socket.io/"
############
print "Connecting to socket.io.."
url = iourl + "1"
f = urllib.urlopen(url)
output = f.read()
f.close()
ausgabe = re.search('[0-9]+', output, 0)
sessionid = ausgabe.group()
print "New websocket url:"
wssurl = wsurl + "1" + "/websocket/" + sessionid
print wssurl
############
print "Connecting to websocket..\n"
socket = create_connection(wssurl)
while 1:
echo = socket.recv()
if "1::" in echo:
print "Heartbeat 1"
socket.send("1::")
elif "2::" in echo:
print "Heartbeat 2"
socket.send("2::")
else:
print "Message: ",echo
time.sleep(2)
The websocket client I use here is from http://pypi.python.org/pypi/websocket-client/0.4. The whole script dies eventually, from having stripped all error-handling. If you like to see the whole script, let me know. I pledge 1 Bitcoin to the first answer to solve this problem. You are welcome to use PMs or post right here. Ente edit: typo which sent '1::' in both types of heartbeats. |
|
|
|
|
Hello fellow coders,
I try to write my own MtGox bot. I am no programmer, I am basically learning-by-doing python with this project. Beginning at almost zero, going step-by-step with help google. So you will need a bit of patience with me ;-)
I will probably have new issues from time to time and will post in this thread when I need more help.
This is the first time I try this approach. So for starters, I bid one Bitcoin to the (first) person which solves my problem.
Do you suggest a different approach? Sharing the pledge between several helpers, for example? Or a higher, or lower pledge? The more expensive this gets, the less I will use it and the more I will try to solve obstacles by myself.
Lets see how this turns out?
Ente
|
|
|
|
The error I keep getting says.. Error binding to P2P port. [Errno 10048]. Only one usage of each socket address (protocol/network address/port) is normally permitted. Retrying in 3 seconds... You may have two instances of p2pool running. Accidental doubleclick, or one instance was in the autostart or something like that? A reboot should solve it for sure. Or, the port is blocked by some firewall, which strangely reserves all ports for itself. Never heard of one like that.. Or you simply have not enough rights to open that port? Which operation system, are you working with admin rights (if windows)? Ente |
|
|
|
*bangs head on desk* I cant get it to work. 1 BTC bounty for the first person who helps me receive regular data again over the websocket! Here is my (totally stripped) python code: #!/usr/bin/env python
# -*- coding: utf-8 -*-
from websocket import create_connection
import urllib
import re
import time
try:
import json
except ImportError:
import simplejson as json
wsurl = "wss://socketio.mtgox.com/socket.io/"
iourl = "https://socketio.mtgox.com/socket.io/"
############
print "Connecting to socket.io.."
url = iourl + "1"
f = urllib.urlopen(url)
output = f.read()
f.close()
ausgabe = re.search('[0-9]+', output, 0)
sessionid = ausgabe.group()
print "New websocket url:"
wssurl = wsurl + "1" + "/websocket/" + sessionid
print wssurl
############
print "Connecting to websocket..\n"
socket = create_connection(wssurl)
while 1:
echo = socket.recv()
if "1::" in echo:
print "Heartbeat 1"
socket.send("1::")
elif "2::" in echo:
print "Heartbeat 2"
socket.send("2::")
else:
print "Message: ",echo
time.sleep(2)
The websocket client I use here is from http://pypi.python.org/pypi/websocket-client/0.4. I have a rudimentary heartbeat added here. The whole script dies eventually, from having stripped all error-handling. It worked some weeks ago. If you like to see the whole script, let me know. Bedtime here, will check back in, like, 9 hours.. *frustrated and tired* Ente |
|
|
|
|
OH! Thank you a lot for your help, zelyony!
I was already wondering about the heartbeat. I now answer 1:: and 2:: accordingly, now they keep flowing in constantly.
Well, the socket *must* be working, since the websites using it still work. There would be more outcry in the forum if it was dead altogether..
I am glad I'm not the only one here!
Ente
|
|
|
|
|
I am all for sub-p2pools.
Preferably, miners dont have to (and cant) choose where exactly they mine at, but are automatically transferred to the right sub-pool according to their own hashingpower and the general sub-pools-situation.
I just had another thought:
To stay as a single p2pool: How about every payout address has its own, adjusting difficulty?
You would just have to broadcast a lot of data/chains. But since you can compare/convert each miners difficulty to the total p2pool hashing power, payout should be easy to calculate?
Just a thought..
Ente
|
|
|
|
|
Being paranoid: Please trust (your local) keepass (keepassx in linux) instead of a website.. We just saw what you may get in trusting an external entity ;-)
Ente
|
|
|
|
TL;DR:
Will ws://websocket.mtgox.com/mtgox continue to work?
Some days ago I connected to the old, deprecated websocket. Connecting works, but no data comes in any more. Now thats an incentive to figure out socket.io :-) edit: As far as I know there is no possibility to do orders over the websocket...
Seems like now you can indeed do orders over socket.io: Authenticated commands
These commands require an API key and secret pair to sign requests. Any of the "version 1" requests from the HTTP API can be called.
So I got the handshake coded, getting me my connection-ID. I then can connect to the websocket just fine. However, I dont receive any data, only two messages: '1::' and '2::'. Both come once in the first few seconds of being connected, then total silence. I am not being disconnected neither, I think. Do I have to join a channel? Or am I connected to the default channels just like before? I dont have "sending messages" finished yet to test.. Any hints? Ente |
|
|
|
|
Show Posts
