I think everything is fixed now. Sorry about that.

IPs will now automatically be banned (temporarily) if they connect much faster than once per second.

Looks like it's caused by a lot of traffic. Maybe a DoS attack. I'm fixing it now.

You were labeled a scammer because you scammed someone. It was removed because you paid them back.

Terrytibbs scammed someone and has not paid them back. He has a scammer tag so that other traders are warned about this incident. Initially I was opposed to reacting to scammers at all, but I decided that if scammer accounts were not somehow marked, almost everyone would feel that the forum had neglected its responsibility to traders. (Most forums would ban scammers outright.)

The amount of time elapsed since terrytibbs' conflict and the quality of his posts are not relevant: he still scammed someone in the past and has not paid them back.

The paper is mostly about potentially worrying trends in RSA, which Bitcoin doesn't use.

Summary of the paper: We gathered several million TLS/PGP certificates in the wild. A surprisingly large percentage of RSA keys and maybe a few DSA keys were generated in such a way that they share certain properties with other keys which are never supposed to be shared, making encryption using the affected keys weak or totally useless. We're not sure why this happened.

The security vulnerability I used still exists. Read the email I sent to info@bitscalper.com.

It's UTC, so nodes with the correct time will all make the change at the same instant.

5 days until the protocol change.

Looks like an alert will be issued before the change in case anything goes wrong.

The Russian section has its own newbies section. You were informed of this in Russian when you registered.

Note that the board does not verify email addresses.

kujoking7
matthewkaraway@gmail.com
31.172.30.3, 31.172.30.1, 31.172.30.3, 68.4.91.26, 72.194.97.149

gurg2.o
acedpace@yahoo.com
31.172.30.1, 213.89.246.184, 68.4.91.26

westcoastconnect
pharohofpower@yahoo.com
31.172.30.3, 68.4.91.26

Users vincentio, millermint, and mgmtlol have also used the 68.4.91.26 IP address and have been marked as scammers, though I won't release the personal info associated with those accounts based on IP evidence alone.

I'll distribute the 6.22 BTC shortly. At least you got something...

I have the logins. I'll release technical details once it's fixed.

Here's me logged into the admin account (you can see I tried to withdraw his 851 BTC -- still pending):
https://i.imgur.com/l92H3.png

If you send me the email addresses you may have used to sign up, I'll check whether you're on the list.

In order to collect more money for the creation of good forum software, the forum is selling ad space in the area beneath the first post of every topic page.

Ads this week will be allowed to contain any non-annoying HTML/CSS style. No images, JavaScript, or animation (no marquee or blinking). Ads must appear 3 or fewer lines tall in my browser. Ads will be prefixed with "Advertisement:". Ad text may not contain lies, misrepresentation, or inappropriate language. Ads may be rejected for other reasons.

There are 10 total ad slots which are randomly rotated. So one ad slot has a one in ten chance of appearing. Eight of the slots are for sale here.

The ad lasts 7 days starting from when I put it up.

Stats: On the 20^th of November, 2011, there were about 120,000 views of topics. So one slot would have appeared around 12,000 times per day. The ad doesn't appear on topic pages with only one post, though, and it only appears for people using the default theme. Total views per day on more recent days (in February):
- 4^th: 112955
- 5^th: 128255
- 6^th: 133252
- 7^th: 137713
- 8^th: 131680
- 9^th: 129219
- 10^th: 128044
- 11^th: 191867


Efficacy stats:
https://bitcointalk.org/index.php?topic=54182.0

Info about the current ad slots:
https://bitcointalk.org/adrotate.php?adinfo

Auction rules

Post your bids in this thread. Prices must be stated in BTC per slot. You must state the max number of slots you want. When the auction ends, the highest bidders will have their slots filled until all eight slots are filled.

So if someone bids for 8 slots @ 5 BTC and this is the highest bid, then he'll get all 8 slots. If the two highest bids are 8 slots @ 4 BTC and 1 slot @ 5 BTC, then the first person will get 7 slots and the second person will get 1 slot.

- When you bid, all of your previous bids are automatically canceled.
- All bid prices must be divisible by 0.5.
- The bidding starts at 0.5.
- The auction end time is 02:00:00 on February 20, UTC. Countdown. (The end time may be extended -- see below.)
- If two people bid at the same price, the person who bid first will have his slots filled first.
- Bids are considered invalid and will be ignored if they do not specify both a price and a max quantity, or if they could not possibly win any slots

If any valid bids occur less than 30 minutes before the auction end time, then the auction will be extended by 30 minutes. If any valid bids occur less than 30 minutes before the new end time, then the auction will be extended again, etc. The time will not extend beyond 6 hours total.

You must pay for your slots within 24 hours of receiving the payment address. Otherwise your slot may be sold to someone else.

I have received and confirmed a report from chsx3 that a security flaw exists in the bitscalper.com website allowing all username/password combinations to be retrieved in plaintext. Passwords are not hashed. While it is not known for sure that an attacker has discovered the flaw, you should assume that the list is public.

Anyone with a bitscalper account should immediately:
- Withdraw all funds. No one should trust bitscalper.com after a security flaw of this sort, and I wouldn't be surprised if they run away with everyone's money once this gets out.
- Change your password on any site where you've used the same password as bitscalper.com.

Because I do not consider Bitscalper to be reputable, I've decided to announce the existence of this flaw publicly before sending the technical details to bitscalper. Otherwise I fear that he may run away with everyone's money instead of alerting his users and losing trust.

Hats off to chsx3 for not abusing this. He could have easily stolen thousands of bitcoins from Bitscalper users.

After it's decoded it's just a normal PHP variable. In this case it looks like you'd get the balance using $dec["Wallets"]["BTC"]["Balance"]["value"]. (This is a multi-layer array. Each [] goes down a layer.)

Current state:
Slots BTC Person
3 3.5 Goat
2 3 Nejc Kodric
3 3 wm-center.com

Bitcoin indents its JSON output to make it more readable, but this isn't required. PHP's json_encode doesn't indent. Extra whitespace in JSON is ignored.


This is var_dump output, not JSON.

That had nothing to do with it. Fees depend on the result of SelectCoins, and SelectCoins uses randomization, so whether you'll have to pay a fee is somewhat random.

No. It always uses its own rules to decide whether a fee will be necessary.

Report them.