[LEAKED] Private Bitcoin Foundation Discussions On Blacklisting, more (ZIP dump) - page 10.

corebob

full member

Activity: 238

Merit: 100

Quote from: piotr_n on November 16, 2013, 08:18:29 AM

Quote from: corebob on November 16, 2013, 08:07:31 AM

Quote from: piotr_n on November 16, 2013, 07:54:59 AM

Quote from: corebob on November 16, 2013, 07:50:13 AM

Good to see you around.

Keep up the good work on gocoin.

You take pull requests?

I haven't so far since I wanted to stay the only copyright holder, hoping to cash on it some day selling it for a commerce apps.
But unlike the fucking bunch of traitors I do care about the future of the bitcoin as we know it, more than personal profits, so I'm open for suggestions and ideas...

Is that why you are using openssl instead of https://github.com/titanous/bitcoin-crypto ?

OpenSSL is optional - its there just to speed up ECDSA verify operations, since the ones from standard go libs are damn slow.

But I ported sipa's ECDSA lib into native Go and it performs even better than openssl, so these days openssl is even disabled by default.
I left it there though, for paranoid people who trust more in the openssl mess than in the nice sipa's code

(I'm definitely not one of them).

I see.

By the way, what do you think about the memory usage, Are you considering/doing memory profiling and optimizations?

piotr_n

legendary

Activity: 2053

Merit: 1356

aka tonikt

Quote from: corebob on November 16, 2013, 08:07:31 AM

Quote from: piotr_n on November 16, 2013, 07:54:59 AM

Quote from: corebob on November 16, 2013, 07:50:13 AM

Good to see you around.

Keep up the good work on gocoin.

You take pull requests?

I haven't so far since I wanted to stay the only copyright holder, hoping to cash on it some day selling it for a commerce apps.
But unlike the fucking bunch of traitors I do care about the future of the bitcoin as we know it, more than personal profits, so I'm open for suggestions and ideas...

Is that why you are using openssl instead of https://github.com/titanous/bitcoin-crypto ?

OpenSSL is optional - its there just to speed up ECDSA verify operations, since the ones from standard go libs are damn slow.

But I ported sipa's ECDSA lib into native Go and it performs even better than openssl wrapper, so these days openssl is even disabled by default.
I left it there though, for the kind of paranoid people who trust more in the openssl mess than in the clean code from sipa and my re-implementation of it.

corebob

full member

Activity: 238

Merit: 100

Quote from: forzendiablo on November 16, 2013, 08:10:50 AM

if tghe thign listed here happends - then BTC is no different than USD or any other currency.

if there is reversile charges and easy tracking of wallets that means its no longer bitcoin. surely the market is big and there are people who want to enter it fro mthe backdoor, but we as a community should do everything o stop that. even if that will mean moving to some altcoin in the end.

Why would I want to use bitcoins instead of traditional currencies and payment systems if any of these suggestions is implemented?

forzendiablo

legendary

Activity: 1526

Merit: 1000

the grandpa of cryptos

if tghe thign listed here happends - then BTC is no different than USD or any other currency.

if there is reversile charges and easy tracking of wallets that means its no longer bitcoin. surely the market is big and there are people who want to enter it fro mthe backdoor, but we as a community should do everything o stop that. even if that will mean moving to some altcoin in the end.

corebob

full member

Activity: 238

Merit: 100

Quote from: piotr_n on November 16, 2013, 07:54:59 AM

Quote from: corebob on November 16, 2013, 07:50:13 AM

Good to see you around.

Keep up the good work on gocoin.

You take pull requests?

I haven't so far since I wanted to stay the only copyright holder, hoping to cash on it some day selling it for a commerce apps.
But unlike the fucking bunch of traitors I do care about the future of the bitcoin as we know it, more than personal profits, so I'm open for suggestions and ideas...

Is that why you are using openssl instead of https://github.com/titanous/bitcoin-crypto ?

justusranvier

legendary

Activity: 1400

Merit: 1013

Quote from: ffssixtynine on November 16, 2013, 07:46:17 AM

Quote from: piotr_n on November 16, 2013, 07:36:04 AM

Looks like the cartel is much farther with conspiring against the bitcoin principles, than I had ever expected.
That's exactly what we could predict after Google itself had put their dirty hands on the development - anyone with a working brain knew that nothing good could have come from

You haven't read the posts or the thread have you. Please go back and read what was actually said. I even posted a fair summary of quotes but you can read all the originals for yourself.

What's missing from that thread in the BF forum is the private conversations businesses and BF members have been having with regulators.

Of course the worst quotes aren't going to be made public - we've got to infer what's going on behind the scenes based on what is public. From the Forbes article:

Quote

“Essentially, we’ve been working with regulators for a structured approach for Bitcoin customers to be compliant,” says Waters. “We set up an API to work with their systems and we supply reporting tools they need for their databases. Which bitcoin addresses belong to a person? That’s the problem we’re solving.”

Who started telling the regulators this was even possible in the first place and also a good idea? Peter Vessenes. Where is Peter right now? Chairman of the Board for Bitcoin Foundation.

The leaked thread is not where the important discussions and decisions are being made.

A group of people including US government officials and business owners have decided this is going to happen, and the thread is one of many attempts to figure out a way to sell it to the community, before they give up and just ram it down everybody's throats (at least, everybody within the grasp of the US government).

piotr_n

legendary

Activity: 2053

Merit: 1356

aka tonikt

Quote from: corebob on November 16, 2013, 07:50:13 AM

Good to see you around.

Keep up the good work on gocoin.

You take pull requests?

Thanks.
I haven't been taking pull requests so far, because I wanted to stay the only copyright holder, hoping to cash on it some day selling it for a commerce apps.
But unlike the fucking bunch of traitors I do care about the future of the bitcoin as we know it, more than personal profits, so I'm open for suggestions and ideas...

If there will be a need for it, I will make gocoin free also for commercial use. I can also add bitcoind compatible mining API, if anyone is interested.

corebob

full member

Activity: 238

Merit: 100

Quote from: piotr_n on November 16, 2013, 07:47:40 AM

Quote from: ffssixtynine on November 16, 2013, 07:46:17 AM

Quote from: piotr_n on November 16, 2013, 07:36:04 AM

...

Good to see you around.

Keep up the good work on gocoin.

You take pull requests?

piotr_n

legendary

Activity: 2053

Merit: 1356

aka tonikt

Quote from: ffssixtynine on November 16, 2013, 07:46:17 AM

Quote from: piotr_n on November 16, 2013, 07:36:04 AM

Looks like the cartel is much farther with conspiring against the bitcoin principles, than I had ever expected.
That's exactly what we could predict after Google itself had put their dirty hands on the development - anyone with a working brain knew that nothing good could have come from

You haven't read the posts or the thread have you. Please go back and read what was actually said. I even posted a fair summary of quotes but you can read all the originals for yourself.

Spare me the bullshit, man.
I'm totally capable of drawing my own conclusions, not interested at all in your stupid excuses and I don't trust you a bit.

ffssixtynine

sr. member

Activity: 364

Merit: 250

Quote from: piotr_n on November 16, 2013, 07:36:04 AM

Looks like the cartel is much farther with conspiring against the bitcoin principles, than I had ever expected.
That's exactly what we could predict after Google itself had put their dirty hands on the development - anyone with a working brain knew that nothing good could have come from

You haven't read the posts or the thread have you. Please go back and read what was actually said. I even posted a fair summary of quotes but you can read all the originals for yourself.

piotr_n

legendary

Activity: 2053

Merit: 1356

aka tonikt

Looks like the cartel is much farther with conspiring against the bitcoin principles, than I had ever expected.
That's exactly what we could predict after Google itself had put their dirty hands on the development - anyone with a working brain knew that nothing good could have come from it.

Anyway, thanks for the leak!

wetroof

member

Activity: 75

Merit: 10

the future of bitcoin is with the miners. I'm excited to watch the battle unfold.

ffssixtynine

sr. member

Activity: 364

Merit: 250

Quote from: Severian on November 16, 2013, 12:00:42 AM

Quote from: ffssixtynine on November 15, 2013, 09:46:38 AM

Imagine Bin Laden is still around.

Anyone playing the bin Laden card as an argument for why Bitcoin should be debased and debilitated can be safely dismissed.

You're dismissed.

Except I didn't. It's funny that people see a terrorist name, immediately assume I'm playing the card that govs play, and then don't read the actual argument.

Which is exactly the same behaviour that allowed the US et al to start all this shit off in the first place, just from the opposite viewpoint.

So once again, follow the argument through and it's about the focus on bitcoin if/when that happens, not that they could use bitcoin as a bank but that everyone could see it and no one could stop it. A little bit of rhetoric from media and politicians and you'll immediately have the villagers besieging bitcoin and everyone who accepts it.

This entire thread is a great example of people only reading headlines and conflating topics. Imagine this on a US wide scale.

Think for yourselves. Read for yourselves. Use your brains.

I don't agree but at least those discussing forks or new currencies are perfectly valid in doing so and I'm sure we'll see a more anonymous coin take hold for black market and anon activities. It won't be used by legal businesses, but you'll just exchange it for btc. So what can they do?

That's my view on why any significant move on bitcoin is ludicrous.

corebob

full member

Activity: 238

Merit: 100

Quote from: wumpus on November 16, 2013, 06:48:21 AM

Quote from: jedunnigan on November 15, 2013, 11:21:53 PM

In the past most threats against the Foundation have been idle (imo), but even now I get a very bad feeling in my stomach about this. I wouldn't be surprised if we start seeing the BF forums get DDoS'd, defaced, among other things. Given the poor standing of other notable members (see: Peter Vessenes), the future of the Foundation is very fragile. Yes they pay Gavin, but that's only because we accept their changes and update our software. If we stop doing that and fork QT, the need for them diminishes quickly. It would be in their benefit to remember that.
the Foundation who has claimed to champion the fungibility of the protocol.

You know you can simply create a github account and start contributing? (right here: https://github.com/bitcoin/bitcoin, behold the Fork button) Like many others in this community you make it sound like forking the code is some grandiose act of rebellion. But it's simply how open source works.

No need to BF member, or go through a secret core dev initiation ritual.

Seriously, we can use more active contributors for Bitcoind/-qt. Get involved! Stop complaining, start coding (or as Erik Hughes wrote in his manifesto in 1993: Cypherpunks write code). Forking the code is not a threat to anyone. Don't confuse it with forking the blockchain.

Well said.

Developers should also be positive to alternative clients.
Gatekeeper mentality will only hurt open source projects

ffssixtynine

sr. member

Activity: 364

Merit: 250

Quote from: NewLiberty on November 15, 2013, 11:15:55 PM

Quote from: p2pbucks on November 15, 2013, 09:54:52 AM

you are out of the topic . The truth is Laden bought weapons using USD not bitcoin ,so why not ban USD worldwide ? Because it's not money's fault .

+2 bitcents:
If he'd been using bitcoin, he'd have been found sooner. Not to mention bitcoin transactions take technology, modern electronic communication and connectivity... all things he was forbidden to use and forbidding others around him to use. From a practical perspective, this terrorist funding angle is vulnerable to accusations of being a false premise, or worse yet, a theoretical fear floated to grab authority. It is fine to discuss it, but why be surprised when it invites severe criticism? It borders on the trollish.

The example was about the media, public and political reaction to it being done in public, not about bitcoin being usable by terrorists. It'd be very, very bad for bitcoin indeed and it is going to happen.

I apologise for not making that clear enough.

ffssixtynine

sr. member

Activity: 364

Merit: 250

Quote from: ?? on ??

I don't see anything wrong with the blacklisting issues being discussed. I think the suggestions are rather naïve but people are already worried that the development team is small and has significant say over what goes into the code. The perception, whether true or not, is that issues are being hidden and this whole discussion board things adds fuel that perception. When you want mass adoption perception matters more than facts.

In a sense I agree with you. Communication and trust is important. I posted earlier in this thread to explain why I wasn't a member. The Foundation know that the bitcoin crowd is a hard one to please as many have extreme views, however they don't help themselves by not being whiter than white with regard to some members. I think they have to bite the bullet in that respect.

There should be a separate business lead organisation IMHO. This would happen in other industries but in the bitcoin world it's all over connected still.

Re: forum - can't agree. This is pretty much the only place bitcoin people go, this and reddit. It is intentionally open to everything. Virtually all it's members will be on here. Bitcoin is (currently!) completely free, so scammers and businesses and everyone can use it. This forum has the same philosophy, and so do a very large number of bitcoiners.

Once we have a better place, then your argument will begin to hold more water.

justusranvier

legendary

Activity: 1400

Merit: 1013

Quote from: jedunnigan on November 16, 2013, 04:20:40 AM

Well, I am always reminded of this post by satoshi:

Quote

I don't believe a second, compatible implementation of Bitcoin will ever be a good idea. So much of the design depends on all nodes getting exactly identical results in lockstep that a second implementation would be a menace to the network. The MIT license is compatible with all other licenses and commercial uses, so there is no need to rewrite it from a licensing standpoint.

Although there are so many scenarios Satoshi could not have been expected to plan for. I've always been a fan of alternative implementations although they must be maintained and tested with utmost care and precision.

I think this is an artifact of Satoshi being stronger in crypto than in software engineering.

http://www.fastcompany.com/28121/they-write-right-stuff

wumpus

hero member

Activity: 812

Merit: 1022

No Maps for These Territories

Quote from: jedunnigan on November 15, 2013, 11:21:53 PM

In the past most threats against the Foundation have been idle (imo), but even now I get a very bad feeling in my stomach about this. I wouldn't be surprised if we start seeing the BF forums get DDoS'd, defaced, among other things. Given the poor standing of other notable members (see: Peter Vessenes), the future of the Foundation is very fragile. Yes they pay Gavin, but that's only because we accept their changes and update our software. If we stop doing that and fork QT, the need for them diminishes quickly. It would be in their benefit to remember that.
the Foundation who has claimed to champion the fungibility of the protocol.

You know you can simply create a github account and start contributing? (right here: https://github.com/bitcoin/bitcoin, behold the Fork button) Like many others in this community you make it sound like forking the code is some grandiose act of rebellion. But it's simply how open source works.

No need to BF member, or go through a secret core dev initiation ritual.

Seriously, we can use more active contributors for Bitcoind/-qt. Get involved! Stop complaining, start coding (or as Erik Hughes wrote in his manifesto in 1993: Cypherpunks write code). Forking the code is not a threat to anyone. Don't confuse it with forking the blockchain.

El Dude

hero member

Activity: 770

Merit: 500

and this is why you never put all your eggs in 1 blockchain , hurry and buy LTC before it skyrockets.

corebob

full member

Activity: 238

Merit: 100

Quote from: bluemeanie1 on November 15, 2013, 06:08:39 PM

Quote from: corebob on November 15, 2013, 05:58:27 PM

There is alternatives.

http://www.assets-otc.com/gocoin/

He's code looks sane, as go code usually does.

have you actually tried this?

apparently a web link is some sort of new form of argument proof in our modern times.

argumentum ad hrefium?

Yea I have tried it before and I tried it again. It works like a charm. Here is the output

Code:

Using NewEC wrapper for EC_Verify
Gocoin client version 0.8.3
You seem to be running Gocoin for the fist time on this PC
There is a database from Satoshi client on your disk...
Go you want to import this database into Gocoin? (y/n) : y
Go you want to verify scripts while importing (will be slow)? (y/n) : n
Be patient while importing Satoshi's database...
6.7MB of data processed. We are at height 31111. Processing speed 0.673MB/sec, recent: 689.5KB/s
15.3MB of data processed. We are at height 58725. Processing speed 0.763MB/sec, recent: 874.1KB/s
31.5MB of data processed. We are at height 82361. Processing speed 1.049MB/sec, recent: 1659.2KB/s
57.6MB of data processed. We are at height 100559. Processing speed 1.439MB/sec, recent: 2669.5KB/s
105.4MB of data processed. We are at height 115455. Processing speed 2.107MB/sec, recent: 4894.7KB/s
170.8MB of data processed. We are at height 125947. Processing speed 2.845MB/sec, recent: 6697.6KB/s
259.1MB of data processed. We are at height 131383. Processing speed 3.699MB/sec, recent: 9010.7KB/s
311.1MB of data processed. We are at height 133837. Processing speed 3.886MB/sec, recent: 5320.9KB/s
408.2MB of data processed. We are at height 137995. Processing speed 4.533MB/sec, recent: 9942.4KB/s
502.6MB of data processed. We are at height 142265. Processing speed 5.023MB/sec, recent: 9664.3KB/s
551.8MB of data processed. We are at height 144515. Processing speed 4.991MB/sec, recent: 4800.0KB/s
630.8MB of data processed. We are at height 148644. Processing speed 5.233MB/sec, recent: 8094.5KB/s
724.4MB of data processed. We are at height 154035. Processing speed 5.546MB/sec, recent: 9529.1KB/s
814.1MB of data processed. We are at height 159514. Processing speed 5.790MB/sec, recent: 9185.2KB/s
853.7MB of data processed. We are at height 161649. Processing speed 5.668MB/sec, recent: 4053.3KB/s
951.4MB of data processed. We are at height 166534. Processing speed 5.923MB/sec, recent: 9998.6KB/s
1044.0MB of data processed. We are at height 171066. Processing speed 6.119MB/sec, recent: 9483.3KB/s
1121.4MB of data processed. We are at height 174972. Processing speed 6.191MB/sec, recent: 7532.9KB/s
1183.4MB of data processed. We are at height 177427. Processing speed 6.191MB/sec, recent: 6347.2KB/s
1294.8MB of data processed. We are at height 180259. Processing speed 6.437MB/sec, recent: 11404.4KB/s
1419.6MB of data processed. We are at height 181721. Processing speed 6.718MB/sec, recent: 12578.9KB/s
1472.0MB of data processed. We are at height 182366. Processing speed 6.647MB/sec, recent: 5283.3KB/s
1579.3MB of data processed. We are at height 183675. Processing speed 6.823MB/sec, recent: 10985.7KB/s
1704.5MB of data processed. We are at height 184737. Processing speed 7.059MB/sec, recent: 12809.8KB/s
1828.7MB of data processed. We are at height 186098. Processing speed 7.272MB/sec, recent: 12716.0KB/s
1853.8MB of data processed. We are at height 186401. Processing speed 7.089MB/sec, recent: 2564.5KB/s
1973.0MB of data processed. We are at height 188237. Processing speed 7.267MB/sec, recent: 12200.3KB/s
2095.7MB of data processed. We are at height 189760. Processing speed 7.444MB/sec, recent: 12559.9KB/s
2203.9MB of data processed. We are at height 191032. Processing speed 7.559MB/sec, recent: 11029.8KB/s
2242.5MB of data processed. We are at height 191505. Processing speed 7.436MB/sec, recent: 3947.0KB/s
2364.3MB of data processed. We are at height 192878. Processing speed 7.588MB/sec, recent: 12477.8KB/s
2487.7MB of data processed. We are at height 194170. Processing speed 7.736MB/sec, recent: 12628.7KB/s
2583.2MB of data processed. We are at height 195135. Processing speed 7.789MB/sec, recent: 9703.2KB/s
2635.5MB of data processed. We are at height 195777. Processing speed 7.714MB/sec, recent: 5354.1KB/s
2756.5MB of data processed. We are at height 197116. Processing speed 7.839MB/sec, recent: 12389.2KB/s
2880.7MB of data processed. We are at height 198482. Processing speed 7.961MB/sec, recent: 12472.3KB/s
2921.0MB of data processed. We are at height 198943. Processing speed 7.855MB/sec, recent: 4131.7KB/s
3041.2MB of data processed. We are at height 200507. Processing speed 7.964MB/sec, recent: 12298.9KB/s
3158.3MB of data processed. We are at height 201856. Processing speed 8.060MB/sec, recent: 11994.5KB/s
3255.1MB of data processed. We are at height 202814. Processing speed 8.086MB/sec, recent: 9256.2KB/s
3310.6MB of data processed. We are at height 203434. Processing speed 8.020MB/sec, recent: 5553.3KB/s
3435.1MB of data processed. We are at height 204662. Processing speed 8.125MB/sec, recent: 12748.9KB/s
3553.4MB of data processed. We are at height 206256. Processing speed 8.210MB/sec, recent: 12102.8KB/s
3620.1MB of data processed. We are at height 207012. Processing speed 8.158MB/sec, recent: 6237.5KB/s
3701.9MB of data processed. We are at height 207994. Processing speed 8.158MB/sec, recent: 8374.0KB/s
3823.7MB of data processed. We are at height 209114. Processing speed 8.245MB/sec, recent: 12461.5KB/s
3944.6MB of data processed. We are at height 210353. Processing speed 8.326MB/sec, recent: 12368.5KB/s
3989.3MB of data processed. We are at height 210891. Processing speed 8.244MB/sec, recent: 4528.9KB/s
4091.0MB of data processed. We are at height 211776. Processing speed 8.283MB/sec, recent: 10411.0KB/s
4215.9MB of data processed. We are at height 212693. Processing speed 8.367MB/sec, recent: 12774.7KB/s
4303.5MB of data processed. We are at height 213332. Processing speed 8.358MB/sec, recent: 8158.2KB/s
4397.2MB of data processed. We are at height 214110. Processing speed 8.377MB/sec, recent: 9584.4KB/s
4517.3MB of data processed. We are at height 215259. Processing speed 8.445MB/sec, recent: 12298.3KB/s
4640.9MB of data processed. We are at height 216185. Processing speed 8.517MB/sec, recent: 12647.3KB/s
4680.8MB of data processed. We are at height 216443. Processing speed 8.433MB/sec, recent: 4030.6KB/s
4782.2MB of data processed. We are at height 217075. Processing speed 8.463MB/sec, recent: 10374.7KB/s
4909.5MB of data processed. We are at height 217953. Processing speed 8.531MB/sec, recent: 12509.2KB/s
4981.4MB of data processed. We are at height 218431. Processing speed 8.499MB/sec, recent: 6916.3KB/s
5089.6MB of data processed. We are at height 219194. Processing speed 8.538MB/sec, recent: 11071.1KB/s
5216.6MB of data processed. We are at height 220084. Processing speed 8.606MB/sec, recent: 12983.2KB/s
5343.4MB of data processed. We are at height 220847. Processing speed 8.672MB/sec, recent: 12974.3KB/s
5371.2MB of data processed. We are at height 221023. Processing speed 8.577MB/sec, recent: 2825.8KB/s
5497.4MB of data processed. We are at height 221971. Processing speed 8.641MB/sec, recent: 12919.3KB/s
5621.3MB of data processed. We are at height 222799. Processing speed 8.697MB/sec, recent: 12525.3KB/s
5682.1MB of data processed. We are at height 223196. Processing speed 8.657MB/sec, recent: 6220.8KB/s
5797.1MB of data processed. We are at height 223897. Processing speed 8.699MB/sec, recent: 11700.6KB/s
5926.8MB of data processed. We are at height 224669. Processing speed 8.762MB/sec, recent: 13270.4KB/s
6052.7MB of data processed. We are at height 225430. Processing speed 8.817MB/sec, recent: 12875.2KB/s
6081.6MB of data processed. We are at height 225600. Processing speed 8.730MB/sec, recent: 2905.8KB/s
6205.5MB of data processed. We are at height 226623. Processing speed 8.781MB/sec, recent: 12666.6KB/s
6323.9MB of data processed. We are at height 227618. Processing speed 8.824MB/sec, recent: 12123.3KB/s
6433.3MB of data processed. We are at height 228361. Processing speed 8.853MB/sec, recent: 11175.6KB/s
6474.1MB of data processed. We are at height 228592. Processing speed 8.788MB/sec, recent: 4183.1KB/s
6599.6MB of data processed. We are at height 229400. Processing speed 8.838MB/sec, recent: 12842.8KB/s
6719.2MB of data processed. We are at height 230055. Processing speed 8.880MB/sec, recent: 12230.4KB/s
6755.4MB of data processed. We are at height 230250. Processing speed 8.811MB/sec, recent: 3700.2KB/s
6875.4MB of data processed. We are at height 230923. Processing speed 8.849MB/sec, recent: 12007.3KB/s
6999.3MB of data processed. We are at height 231711. Processing speed 8.894MB/sec, recent: 12689.8KB/s
7105.3MB of data processed. We are at height 232391. Processing speed 8.915MB/sec, recent: 10834.8KB/s
7132.3MB of data processed. We are at height 232600. Processing speed 8.834MB/sec, recent: 2652.7KB/s
7252.0MB of data processed. We are at height 233307. Processing speed 8.872MB/sec, recent: 12250.7KB/s
7369.2MB of data processed. We are at height 234112. Processing speed 8.907MB/sec, recent: 11995.9KB/s
7413.2MB of data processed. We are at height 234359. Processing speed 8.851MB/sec, recent: 4430.0KB/s
7528.5MB of data processed. We are at height 235108. Processing speed 8.883MB/sec, recent: 11803.5KB/s
7645.3MB of data processed. We are at height 235764. Processing speed 8.915MB/sec, recent: 11941.6KB/s
7766.8MB of data processed. We are at height 236429. Processing speed 8.952MB/sec, recent: 12422.8KB/s
7793.4MB of data processed. We are at height 236575. Processing speed 8.880MB/sec, recent: 2724.4KB/s
7911.7MB of data processed. We are at height 237320. Processing speed 8.914MB/sec, recent: 12108.0KB/s
8029.4MB of data processed. We are at height 238143. Processing speed 8.945MB/sec, recent: 12031.6KB/s
8136.6MB of data processed. We are at height 238845. Processing speed 8.964MB/sec, recent: 10944.2KB/s
8177.7MB of data processed. We are at height 239176. Processing speed 8.912MB/sec, recent: 4209.1KB/s
8300.8MB of data processed. We are at height 240145. Processing speed 8.948MB/sec, recent: 12598.5KB/s
8416.6MB of data processed. We are at height 241095. Processing speed 8.976MB/sec, recent: 11836.0KB/s
8506.8MB of data processed. We are at height 241948. Processing speed 8.976MB/sec, recent: 9211.1KB/s
8547.2MB of data processed. We are at height 242236. Processing speed 8.920MB/sec, recent: 3932.9KB/s
8669.6MB of data processed. We are at height 243200. Processing speed 8.954MB/sec, recent: 12518.1KB/s
8784.3MB of data processed. We are at height 244227. Processing speed 8.980MB/sec, recent: 11731.2KB/s
8879.7MB of data processed. We are at height 245276. Processing speed 8.978MB/sec, recent: 9023.5KB/s
8936.7MB of data processed. We are at height 245900. Processing speed 8.945MB/sec, recent: 5841.5KB/s
9059.3MB of data processed. We are at height 247044. Processing speed 8.978MB/sec, recent: 12545.3KB/s
9165.3MB of data processed. We are at height 248145. Processing speed 8.994MB/sec, recent: 10846.7KB/s
9228.1MB of data processed. We are at height 248707. Processing speed 8.966MB/sec, recent: 6339.9KB/s
9319.6MB of data processed. We are at height 249580. Processing speed 8.968MB/sec, recent: 9353.4KB/s
9442.8MB of data processed. We are at height 250624. Processing speed 9.000MB/sec, recent: 12615.4KB/s
9557.5MB of data processed. We are at height 251724. Processing speed 9.023MB/sec, recent: 11746.2KB/s
9594.1MB of data processed. We are at height 251974. Processing speed 8.968MB/sec, recent: 3561.1KB/s
9719.2MB of data processed. We are at height 252854. Processing speed 9.001MB/sec, recent: 12798.6KB/s
9834.4MB of data processed. We are at height 253656. Processing speed 9.024MB/sec, recent: 11785.9KB/s
9946.2MB of data processed. We are at height 254484. Processing speed 9.044MB/sec, recent: 11433.0KB/s
9986.0MB of data processed. We are at height 254725. Processing speed 8.998MB/sec, recent: 4072.7KB/s
10094.3MB of data processed. We are at height 255740. Processing speed 9.014MB/sec, recent: 11083.9KB/s
10216.9MB of data processed. We are at height 256640. Processing speed 9.043MB/sec, recent: 12553.6KB/s
10307.7MB of data processed. We are at height 257410. Processing speed 9.043MB/sec, recent: 9232.4KB/s
10353.4MB of data processed. We are at height 257856. Processing speed 9.004MB/sec, recent: 4673.2KB/s
10477.4MB of data processed. We are at height 258777. Processing speed 9.033MB/sec, recent: 12698.5KB/s
10596.0MB of data processed. We are at height 259744. Processing speed 9.057MB/sec, recent: 12137.0KB/s
10669.1MB of data processed. We are at height 260308. Processing speed 9.039MB/sec, recent: 7177.6KB/s
10736.9MB of data processed. We are at height 260917. Processing speed 9.020MB/sec, recent: 6932.1KB/s
10858.3MB of data processed. We are at height 261824. Processing speed 9.046MB/sec, recent: 12428.2KB/s
10979.8MB of data processed. We are at height 262830. Processing speed 9.072MB/sec, recent: 12438.3KB/s
11040.7MB of data processed. We are at height 263380. Processing speed 9.043MB/sec, recent: 5920.7KB/s
11098.4MB of data processed. We are at height 263928. Processing speed 9.016MB/sec, recent: 5893.2KB/s
11223.3MB of data processed. We are at height 264952. Processing speed 9.044MB/sec, recent: 12791.6KB/s
11333.9MB of data processed. We are at height 265769. Processing speed 9.060MB/sec, recent: 11221.5KB/s
11345.7MB of data processed. We are at height 265855. Processing speed 8.997MB/sec, recent: 1216.1KB/s
11465.2MB of data processed. We are at height 266826. Processing speed 9.012MB/sec, recent: 10919.4KB/s
11588.7MB of data processed. We are at height 267952. Processing speed 9.038MB/sec, recent: 12651.2KB/s
11622.6MB of data processed. We are at height 268173. Processing speed 8.994MB/sec, recent: 3464.9KB/s
11749.8MB of data processed. We are at height 268826. Processing speed 9.023MB/sec, recent: 13024.5KB/s
END of DB file
11760.9MB of data processed. We are at height 268892. Processing speed 9.024MB/sec, recent: 10862.2KB/s
Satoshi's database import finished in 1303 seconds
Now saving the new database...
Database saved. No more imports should be needed.
Opening blockchain... (Ctrl-C to interrupt)
Blockchain open in 121.371 seconds
open /home/user/.bitcoin/gocoin/btcnet/wallet/DEFAULT: no such file or directory
open /home/user/.bitcoin/gocoin/btcnet/wallet.txt: no such file or directory
Starting WebUI at 127.0.0.1:8833 ...
>

And the web client

Topic: [LEAKED] Private Bitcoin Foundation Discussions On Blacklisting, more (ZIP dump) - page 10. (Read 61198 times)