Well,  if PPT-PR's info is accurate the SEC investigation is probably the only recourse anyone has for prosecution and potential recovery.  The problem is, the longer it takes the longer Trendon Shavors has to hide whatever assets he has remaining so its highly unlikely there will be any recovery.

Welcome to bitcoinlandia.

I'd be curious to know what the Bitcoin Foundation is up to these days.

Charlie Shrem (who I like and is obviously one of bitcoin's biggest supporters) was on Bryan Micon's Donked Down podcast recently quoting  inaccurate dates in US monetary history and claiming that the US Dollar will collapse in 3-10 years.

http://www.donkdown.com/donkdown-radio-charlie-shrem-from-bitcoin-foundation-bitinstant/


Charlie, I love the enthusiasm, but if the Bitcoin Foundation want's legitimacy and support in the community, I strongly suggest you developer some talking points or a position paper and try to stick to the facts when your members are representing the Foundation in a public forum.

Received.

Thanks.

JoelKatz

MOE-PR is obviously not a smart guy.  What do you keep arguing with him. 

This thread is exhausting.

It's kind of like a train wreck or a traffic accident.  You really don't want to watch but you somehow can't turn away.

Trendon Shavors' Master Plan, his End Game is playing out perfectly.

He's untouchable.


There are a number of individual investors who would obviously like to see him brought to justice but most of the major players fear unexpected legal and tax liabilities in coming forward.

So unless the SEC is collecting enough information to file civil charges (and who knows how long that could take)

Trendon Shavors has already walked off into the sunset with everyone BTC - and probably  getting ready to scam again.

This guy is HUGE Scammer....

YES.

Thanks.

25.61 BTC

http://bitcoin-otc.com/viewratingdetail.php?nick=bcb

He doesn't have any coins. That's his scam.

Scammer

Why don't you pay the people back you stole from.

kentrolla
Hero Member

Re: shit, shit, shit
January 27, 2012, 04:23:40 AM
  #20
GRRRR i panicked and  sold all my coins at 5.19 lol   right before it jumped up to 5.48          GRRRRRRRRRRRRRRRR IM SO BAD AT TRADING!


https://bitcointalk.org/index.php?topic=61337.msg715996#msg715996

25.57

I need a clear in-focus photo of the entire receipt showing it was purchased with cash on today's date with BCB written on it.

Thanks.

ahhhh

no wonder the server didn't work. I was using joric's.  So there are two versions of pywallet.

https://github.com/joric/pywallet

https://github.com/jackjack-jj/pywallet (with server)

Thanks.

What is the location of the Torrent file.  I'm actually going to install bitcoind on a new clean install laptop.  I'll give it a try.

I'm not questioning your ability. I'm trying to have a discussion about bitcoin security which is not a bad conversation to be having.  I just don't see the security benefit of separating front end web service and back end bitcoind on two boxes and though you might have some insight.

I do think dedicated, physical servers, locked cages, hardware security device for private keys and cold storage, with multiple encrypted back up  for 90% of any coin over a certain level is the best practice for significant amounts of coin regardless of the number of boxes you are running. 

Thanks.

Good questions:

you have

DATE - Mt. Gox Hack - loss estimate:??  -- significant price drop and trade roll back.  (still in operation)

DATE - Bitcoinica linode hack - loss estimate: ??  (closed)

DATE - Bitcoinica/Bitcoin Consultency hack  - loss estimate: ??  (closed)

DATE - Bitcoinica/Bitcoin Consultency Closure  - loss estimate: ??  (closed)

DATE - BTC-E Hack   - loss estimate: ?? - quick recovery  (still in operation)

DATE - Bitfloor Hack - loss estimate: $250,000 USD  - (still in operation)

DATE - BCTS&T Default - loss estimate: $2M USD (closed)

DATE - GLBSE shut down - loss estimate:

DATE - Bitcoin-24(??) Compromise - loss estimate:

Maybe someone else can supply dates and amounts lost.

you mean "time limited" so that only some many send commands can be sent in a limited about of time?

Do you also limit the amounts that can be send via rpc.

Your logic about the bitcoind box only being accessible from the web app box is not really a security feature as the attacker who compromised the web box, can still access the bitcoind box.

Binford 6100

He was able to access the wallet and recover the funds.

After 3 days his client was still not synced with the block chain.

he was also not able to run commands from the console.

He was getting the following error:

Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade. (code -2)

I'm guessing Windows Permission error but I have not idea for sure.


**Also I have never been able to get pywalled working using http://localhost:8989/  on a windows machine.

That is why I described the method we used in my previous post which worked just fine.

Thanks.

gweedo,

Could you explain how web app on one box and bitcoind on another box increases security.

If the web app box is compromised, attacker still has full access to the bitcoind through  rpc?

I have no idea why his bitcoind was not functioning.  I believe it was a windows permission problem.

He as able to download and install pywallet,
https://github.com/joric/pywallet

Extracted the private keys

Then import the private key of the receive address into blockchain.info using the "sweep" method.

on Windows install
http://www.python.org/ftp/python/2.7.2/python-2.7.2.msi

then download and unzip
https://github.com/joric/pywallet/archive/master.zip

unzip master.zip in you your "My Documents" folder

type "cmd" in the "run" box (above Start in Windows7)

also on windows 7 you'll need to run as administrator
so type "cmd" in the command box then hit "Ctrl+Shift + Enter"

Then hit "YES"

then in the command prompt (the black screen) navigate to to location of pywallet.py (it is in pywallet-master folder)

then type:

pywallet.py --password=your_password --dumpwallet > c:\wallet.txt
(only use "--password=your_password" if you walled it encrypted.)

you should now have a new file "wallet.txt" which is a PLAINTEXT list of every Public and Private  Key in you wallet.

Find the Public Key or Keys you want to import (or you could import the whole wallet if you don't have more then a few hundred addressed in there)


Remember any funds you had in the wallet or in those individual address in that are now fully accessable to anyone who has access to that unencrypted plaintext wallet.txt file so be careful what you do with it.