Limit reduced to 60 seconds.
|
|
|
There was also a lot of PM spam.
But you can now PM with just 1 post.
|
|
|
No, it really was necessary. The forum was being overrun by trolls.
|
|
|
You can now PM with only 1 post. I was trying to post in newbie forum but I got some "300 second" message. What was that all about? That totally blows.
Don't post so fast.
|
|
|
There is way too much traffic in this section for me to handle. I need several moderators for this section. Apply here. Users with high "days online" are likely to be considered.
Moderators of this section will: - Delete garbage. - Delete posts that are just for increasing post count. - Move good topics elsewhere. - Send me lists of users to whitelist.
|
|
|
There needs to be both a post and time limitation, so trolls can't "age" many accounts. I'd do that if SMF supported it.
|
|
|
You should all still be able to reply to your own topics outside of this section.
|
|
|
This is already enabled for new users, but I don't want to prevent all signature images.
|
|
|
I would prohibit animated and large signatures if SMF supported it. Maybe there's a mod.
|
|
|
Due to a mass of trolling, only established posters are able to post in non-newbie sections.
If you have really good posts, you can post a request for preemptive whitelisting here
Also, you must have made 1 post to send PMs.
|
|
|
The sender encumbers the coins with restrictions. The person who spends those coins meets the specified restrictions.
|
|
|
Is this the same method being used on you site? http://blockexplorer.com/q/totalbcI hope you can consider providing these service to function as an early warning system for the bitcoin network. It's not. The value returned with the SQL is now actually less than the "ideal" number, as some miners have thrown away block reward BTC. I might make a /q page for it eventually, as the difference is interesting.
|
|
|
100 blocks to mature eh? Everywhere I've read says it's 120. Has it always been that way? Do you have a reference I could refer to for more reading up on this?
It has always been that way. Everywhere says 120 because that's what the client says. The actual network limit is 100, though. Check the code: static const int COINBASE_MATURITY = 100; Use the -printblock switch to dump all blocks (including orphans) to debug.log, and then post the last few thousand blocks to pastebin or something so I can examine your block.
|
|
|
The network only enforces a maturation time of 100 blocks. The extra 20 blocks is a client limit only. How does a block go "orphaned" after it's been "confirmed" (meaning, it reached 120 blocks then went "orphaned" shortly after that)? A bug, probably. Or maybe you were segmented for a really long time.
|
|
|
A ton of people got these. I banned the sender after getting mewantsbitcoins's report. I didn't clear the PMs (since doing this is complicated), but I marked his account to warn people.
|
|
|
What the hell? I can't lock my own thread and I can't report it to a moderator? I'm going to Bitcoinforums.net.
Someone please report this for lock.
You can lock your own threads. The link is near the bottom of the page. The person sending those PMs has already been banned.
|
|
|
Shopping could not be completed faster. If blocks were found twice as fast, then it would take 12 blocks for a transaction to confirm, as each block would be worth half as much.
|
|
|
In not too long, mining will be unprofitable with all consumer hardware.
|
|
|
(Split because it was not responding to the OP you responded to.)
Right click your certificate in Kleopatra and choose "export certificates". The file output by this action can be opened in a text editor and copied and pasted, or I think you can also just upload the file to pgp.mit.edu.
|
|
|
I don't have old getdata output. Here's a block header you can try hashing, though this does not have the reversal on 8-bytes: 010000001d8f4ec0443e1f19f305e488c1085c95de7cc3fd25e0d2c5bb5d0000000000009762547903d36881a86751f3f5049e23050113f779735ef82734ebf0b4450081d8c8c84db3936a1a334b035b
|
|
|
|