As crappy as this is, Here you go.
Wow, you really felt you had to, eh? No wonder kids are put to bed early... |
|
|
|
I hope the difficulty triples. I haven't played video games in a month. And the new American McGee's Alice is out. I hear Duke Nukem sucks, but still. It's Duke Nukem.
I have a signed x-mas card from 3D Realms that has duke on it, and all the team. Wonder what that is worth in bitcoin land... maybe... |
|
|
|
It is quite encouraging to see how many people have voted for Mt.Gox. It means there are a great many retards trading that can be exploited for profit.
Hi mods, see this yet? Awesome. |
|
|
|
I think we are a bit too early on in the experiment that is bitcoin to start casting out in new directions. However, there is nothing stopping your plan. You could conceivably have your own blockchain and client.
Can you elaborate on this please? Thank you. I think you should take a look at the namecoin project. They've done just that, established another blockchain and a project that mirrors bitcoin in some ways, for their own purposes. |
|
|
|
|
The form factor would be very interesting. Having some kind of card implementation of wallet storage would be highly desireable. (At least, speaking for myself.) I would have to do more research on what would be required to get some kind of smartcard system going.
Heck, how about a bitcoin ATM that really is just a secure linux implementation that assigns coins to your card based on currency deposits?
|
|
|
|
|
I think we are a bit too early on in the experiment that is bitcoin to start casting out in new directions. However, there is nothing stopping your plan. You could conceivably have your own blockchain and client. I am not sure how you would handle the redemption part of the plan though.
I wouldn't be investing in bitcoin 2.0, because I think it has a few flaws based on possible government intervention, as you would be using their issued currency. Not to mention a central point of failure, being the physical delivery process, even if you didn't use coin shops or dealers.
Best of luck, but I am not as optimistic about your plan as I am about the original bitcoin.
|
|
|
|
|
They will be back in once they realize what we are going through are merely growing pains. It makes sense that bitcoin face these things early on, because surviving varied vectors of attack - even on the most vulnerable parts, will make the entire enterprise stronger.
You have to go through these 'tempering' events to make it in the real world. That applies to code, ideas, and people.
|
|
|
|
People were really fucking stupid to put every single penny they had in 1 website. It angers me beyond any reason, that the biggest destabilizer to the bitcoin, is human stupidity.
I agree. I would also extend that to include the mining pools. The irony there is rather thick. They are prime targets for disruptive behavior. I think our next crisis will involve something along those lines. We only learn when bashed over the head, it seems. |
|
|
|
|
Okay, I'll bite on the whole theory of "OMG HACKED" for a second. (And why it is wrong.)
Lets say for sake of theoretical argument it is true.
This is what I would do if I was some evil "Hax0r Do0d" that could produce blocks at will:
Strategy 1:
Stealth, produce blocks within a given distribution, probably driven by number generator that guarantees statistical analysis won't turn up an anomaly. Quietly wait while my blocks are verified, cue up 50btc orders on a few different exchanges and pull my funds into several different accounts. Rinse, repeat.
Strategy 2: (Which fits with the 'OMG HAX' part of this thread.)
Produce as many blocks as possible in a mad rush not only to authenticate what I'm already generating - but to stuff it down the throat of a few exchanges to cash out as soon as possible. Probability of detection - < HIGH >. Possibility of being caught and having my bitcoins 'stuck' at an exchange before I can flee - < HIGH >.
So, don't sweat the clusters.
Seriously.
|
|
|
|
Usual nslookup details and such: campbx.com 184.164.132.91 NetRange 184.164.128.0 - 184.164.159.255 CIDR 184.164.128.0/19 Name SS5 Handle NET-184-164-128-0-1 Parent NET184 (NET-184-0-0-0-0) Net Type Direct Allocation Origin AS AS20454 AS32164 Organization SECURED SERVERS LLC (SSL-65) Registration Date 2011-05-13 Last Updated 2011-05-13 Name SECURED SERVERS LLC Handle SSL-65 Street 2353 W University Bldg A City Tempe State/Province AZ Postal Code 85281 Country US Registration Date 2003-12-08 Last Updated 2009-11-25 Secured Servers website: http://www.securedservers.com/index.phpsecuredservers.com 209.188.23.6 NetRange 209.188.23.0 - 209.188.23.31 CIDR 209.188.23.0/27 Name CWIE Handle NET-209-188-23-0-1 Parent SECUREDSERVERS (NET-209-188-0-0-1) Net Type Reallocated Origin AS Organization CWIE, LLC (CWIE) Registration Date 2008-11-03 Last Updated 2008-11-03 Name CWIE, LLC Handle CWIE Street 2353 W University Bldg A City Tempe State/Province AZ Postal Code 85281 Country US Registration Date 1999-09-01 Last Updated 2009-02-20 CWEI website: http://www.cavecreek.com/ |
|
|
|
I've seen clusters like these before. I never started an alarmist thread claiming 'hacks' though, because I understand gaussian distributions and probability. Time for a statistics refresher course, imperi. |
|
|
|
nslookup tradehill.com 46.21.104.237 RIPE WHOIS: inetnum: 46.21.104.0 - 46.21.105.255 netname: GLESYS-CUSTOMER-SERVERS descr: Customer VPS services located in Falkenberg, Sweden remarks: INFRA-AW country: SE admin-c: GLE-RIPE tech-c: GLE-RIPE status: ASSIGNED PA mnt-by: GLESYS-MNT mnt-domains: GLESYS-MNT source: RIPE # Filtered Main website: http://glesys.com/VPS Details: http://glesys.com/vps.phpNot bad, they probably could migrate to dedicated later. |
|
|
|
Tradehill Last: 12.65
You guys are completely mental.
Tradehill Britcoin != The same My point was that different GBBO's (Global Best Bid/Offers) exist, focusing on bizarro non-crossed trades makes no sense. |
|
|
|
I've seen some repeating patterns on bitcoin monitor since my original post, and I find your snapshot interesting. I still have no idea what is really behind it, though. |
|
|
|
|
Tradehill Last: 12.65
You guys are completely mental.
|
|
|
|
I have a script for this too: IF(subject=="MtGox" || "25,000 BTC Stolen" || "allinvain"){
cout >> /dev/null;
return;
}
ELSE
{
ParseThreadComments();
}
|
|
|
|
|
The best compensation would be all these threads dying in a fire, never to pop up from the primordial ooze that spawned them.
|
|
|
|
|
Heh, like DNS?
Wallet Name Service, WNS
wnslookup bigvendor
Non-authoritative answer: 1sDjdf09dgjASFhg7832dsdsfh
|
|
|
|
|
Nothing against you personally, I just think all Mt. Gox threads should die in a fire, unless they are official reopening statements.
As for the database, restore from backup prior to the incident, solved.
|
|
|
|
|
My guess, the wild oscillations will be from 9.00 - 17.00, with 20+ seven days later.
|
|
|
|
|
Show Posts
