 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
This looks pretty nifty. I noticed on that BTCServ hack that the small part gets spent twice to merge into a 40 BTC address. It would be useful to know what addresses payments get combined with as that may give clues about wallet (like a "back-link" on an address). I have no idea how it could be fit in a diagram because it would get "hairy" fast.
My hypothesis is that the coins change hands at the 40 BTC merge as the ip addresses switch from Germany to U.S. Maybe you could hover over a node to show any new inputs. Also the "Purity" of the coins (i.e. how much they have been mixed with the other transactions) could be represented by the thickness of the line. So, that means the hacker either is close topologically by default or has added manually BTCServ IP as a peer? If the hacker is manually relaying thru BTCServ that's a bit like rubbing salt in a wound! Or another interpretation is that it's still controlled by BTCServ, though obviously not provably.
Or maybe the attacker sent some change back to BTCServe for some reason. I guess no matter how good future tools like this get it will still be almost impossible to prove anything. The 0.63 transaction was a legit withdrawal. I think its displayed because it was happend at the same block count. Also the 419 transaction has been relayed by an US ip, apparently Tor Network. The 0.63 transaction did go out from btcserv.net ip |
|
|
|
|
whoever says this was a scam should think about if he maybe have the least reason to do this. it's easy to blame the pool operators, but those who made such comments probably have never had to do with us, so just shut the fuck up.
i understand doubts but amateur sherlocks that make that stretch from an expiring domain name in 6 months to a scam just make me wanna puke.
|
|
|
|
|
kann ich noch nicht sagen. müssen uns was überlegen, damit möglichst wenig, oder bestenfalls keine funds auf dem server liegen damit sowas gar nicht erst passieren kann.
|
|
|
|
ein bischen mehr Information wäre sehr hilfreich.
Wurden auch die Passwörter und emailadressen gehackt ?
er hatte eingeschränkten zugriff auf den server, zugriff auf die datenbank dürfte er nicht gehabt haben. zudem sind die passwörter verschlüsselt. trotzdem sollte man sicherheitshalber das passwort ändern, wenn man das selbe bei anderen seiten nutzt. |
|
|
|
Hi!
I just join some of my miners (3.5GHash by now) into your pool...
Tks!
Velox
expert decision  thx |
|
|
|
|
pls send me a private message with your registered email address
|
|
|
|
|
Pool ist wieder online und dank p2k läuft er nun auch mit seiner ecoinpool pool software, die auch verbesserungen für den pool einfacher machen.
|
|
|
|
Pool is up and running again. Big Thanks to p2k who also made it possible that BTCServ probably runs with the best pool software on this planet now |
|
|
|
|
Sorry, hatten größere Probleme, aber es wird dran gearbeitet. Dauert allerdings noch ein paar Stunden.
|
|
|
|
Is something wrong with the pool right now? My miners can't connect and I noticed on the web interface the pool hashrate has dropped almost in half.
We experienced some unusual high CPU load which probably caused the hashrate to drop dramatically. When trying to restart the daemons we experienced some unexcepted errors. Now we are working on it, but unfortunately cant say when it will be up and running again. I am sorry for that inconvenience. |
|
|
|
Does this pool pay for invalid/stales as well? Hopefully because I have a high stale rate on this pool.
well, no, BTCServ doesnt pay for invalids. sorry that 0% pps is not enough for you. currently there are like 0.20% stales for all users. |
|
|
|
|
für nen toten ist der echt noch sehr aktiv
|
|
|
|
I'm really liking your pool so far.  Is there any way to put my bitcoin address in permanently or do I always have to put the address in manually when I wanna get paid? Also what is the current pool buffer? Is it located somewhere on your website? Thanks! Auto payout does not work. I was close to implementing it once but decided to not develop the site until I overcome some problems. Definitely put an too unhealthy amount of time into the site, so I decided to completely stop for a while except for maintaining the uptime. But it looks like I will start again in maybe a month. Probably not earlier. Current pool buffer is 100 Bitcoins. Not listed at the website. |
|
|
|
|
von welchem pool ist die rede
|
|
|
|
|
0% PPS here and pretty high uptime
|
|
|
|
Merged Mining implemented but not yet split in to Bitcoin and Namecoin payouts. Thus I have increased the Bitcoin PPS to 0.0000385 for now until this has been done.
What rates are you currently offering for NMC -> BTC and how often is it updated? I have never offered rates for NMC -> BTC and are not doing this currently aswell. The last of responses and participation from the pool operator in this thread... is worrying.
Ah cmon. I know that I am not really present currently but everyone is always being paid properly and the pool is running stable. |
|
|
|
|
Hey, happy holidays everyone.
Thought of dropping some info about the current state of the queue after the recent lucky streak. Still the queue is not evened out but we are currently only 3 blocks behind and not 10 anymore. Let us hope the streak continues so everyone receives their share more quickly.
|
|
|
|
Was ist denn mit dem letzten Block los der immer noch "pending" Status hat?
Hi, sorry, das war ein Namecoin Block, kein Bitcoin Block. Da war ein Fehler im Script, sodass der zuletzt gültige Bitcoin Block nicht mit Bitcoin Flag markiert wurde. Dadurch wurde der nächste Namecoin Block auch in die Solved Block Tabelle eingetragen und genau das sollte nicht passieren. Gerade wenig Zeit für den Pool, daher hab ich es bisher nicht repariert. Ich weiß, Service ist schwach. Momentan gehts leider nicht anders. Dieser unlucky Streak nimmt irgendwie auch kein Ende. |
|
|
|
Na dann hoffen wir mal, dass die nächsten Blöcke wieder schneller gelöst werden und der Puffer wieder ins Plus wechselt Ja, das hoffe ich auch. Pech haben macht keinen Spaß.  |
|
|
|
|
