If you are not getting a confirmation, it is fake, invalid, or an attempt to "seem valid". That money will be returned to the sender in time, if it does not confirm.

If you see it, it has been processed. (Confirms are just others saying it is in the block also. It is not still being added to blocks, it is already in a block.)

Few pools actually reject non-free transactions. They just take what is available, the paid ones first. Sadly, there are a lot of fake micro-transactions that are "zero", and "free". Someone is using older or poorly coded programs to add 0.000000000000BTC transactions to the blocks, by the millions. These "invalid dust transactions" are from some goof posting a wallets password online, and everyone is trying to withdrawal funds from it, and some goof is purposely adding 0.0000000001btc to it, keeping everyone trying to get it.

BTW, pool operators and miners DO come here. But there is nothing specifically we can do. The system is 100% automated, it isn't like a bank where we can pick and choose individual transactions to assist.

Just be sure you are using the latest wallet.

Don't accept any "incoming" transaction as an "actual transaction"... not until it has been validated with more than 30 confirms, 120 if you are a business. (6 confirms is hardly enough to validate a transaction, and I don't know why they display that as being available, when a branch can hold steady for over 30+ transactions from a tainted pool.)

That works in reverse too...

If, for some reason, your transaction was "sent" to another location, via a fake block... then when that invalid block is removed, your "real balance" will indicate the "restored missing coins". (Once that orphaned fake block is defeated by a real block, on that HAS the actual 6+ ->  120 confirmations.)

Stop trying to micromanage your blocks and wallets. You are watching it too closely.

Get an offline wallet, and use it only once, (encrypted first), and deposit all your transactions to that wallet, from your online wallet.

Also, change your password for your email/account, from a computer that is NOT the one you are using now. Just incase, for some odd reason, you are infected with a key-logger or monitoring virtual-machine, or someone is reading your COPY-PASTE from your mouse when you visit some website. (EG, when you copy/paste your passwords, that is a big No-No!)

It can not be moved with only 1 confirmation. Either the transaction was invalid, and from an orphaned block, due to it being fake... and returned back to the sender, or deleted if a double-spend... or you are not seeing that it actually had 6 actual confirms.

I can hack a block and it would show in your wallet... for at-least one-confirm... but as soon as the system sees it is fake, it removes it. Thus, it never made it past 6 confirms.

Where is this money coming from? The money you are seeing entering your wallet? If you are placing it there, then you should be worried. If this is from some automated payment system, you need to contact them to let them know the payments are not going through.

How does anyone see when you have money in there... simple... they just look at the block-info that you see. It is on everyones computer, and on that site, for the world to see.

Again... BTC can NOT be withdrawn by ANYONE if it was not validated (6+ confirms), unless a whole branch of fake transactions occurred on a block that was recently thrown-out, due to being invalid. (Thus, it was never your BTC to begin with. Thus, not a loss.)

If this was payment for something, you should wait for over 30 confirms... (120 to be realistic), before "accepting it as valid". People use double-spends and hacked blocks to fool automated systems. Those transactions do not survive 120+ confirms, unless a 51% attack is successful. No-one has 51% of the mining market.

Wow, that analogy was sooo useless, it wasn't even funny.

I found the answer I was looking for...

"There is only one pool-type that has preventions for this non-work-worker. (puddinpop)" (Though, it does not say if that is checking "worked failures metahashes", or just "metahashes of groups of shares-hashes", which would be back to being useless again.)

That is the only pool that actually checks if you are truly working, not just submitting "shares". (Which DO NOT require you to actually have worked for a block-solution.)

Finding difficulty 1-64 requires a micro-second or two. Finding difficulty 11,121,323 takes about 30 min. If you STOP processing after finding that share, and now process the next-servers share... then the next then the next then spend the rest of the time processing YOUR-SOLO... and return every time you are expected to submit the next 1-64 share for the others... you do that. (You can do a few in advance, to just release them at the right times, if needed.)

In any event, it is good to know that someone actually did something to attempt to prevent this situation. Though, in my eyes, I don't see that as a win, as it does not seem to be used. Or effective.

Again, (hashing a share) is like stopping after finding a 1-64 difficulty, is not = to work-solution. That is like stopping rolling after you hit a 1 or a 2 or a 3 or a 4 or a 5 on any ONE of the FIVE 6-sided dice... instead of keep rolling afterwards, trying to get Yahtsee, which takes hours (solving a valid block).

I know it is unique for each server. That is why you return each "share" where it belongs. Without actually processing the block.

We are working on the same block, until it says "new block". If you do not work on the block, for THAT server, but you do for your own (solo-mining)... then you are returning just the shares, which are usually 1-64 difficulty, which takes less than 1% to process from the servers "block", without actually trying to "find a difficulty 11,132,232 block for that server. It has no clue if you are actually hashing the block, and trying, or if you are just returning shares that are "valid" for "that servers block".

I know exactly how it works.

I want to know what measures are in place to prevent this.

The server only checks to see if the hash is valid for the share. Again, if "shares" actually consumed that much processing, then that would result in less processing for finding a block, thus, less actual hashing power. That is why the difficulty is so low for a share, so it does NOT interfere with processing the block itself (for a block-result).

"A share is awarded by the mining pool to the clients who present a valid proof of work of the same type as the proof of work that is used for creating blocks, but of lesser difficulty, so that it requires less time on average to generate."

EG... you do not have to actually process the block (looking for a valid-block, just keep processing the "share-difficulty", which takes nearly no time at all.)

EG... Running 4 clients, allows you to "present a valid proof of work of the same type as the proof of work that is used for creating blocks, but of lesser difficulty, so that it requires less time on average to generate", one for each of the servers.

Thus, you get paid 4x for doing absolutely nothing, except processing "valid shares". While on the fifth client, you are solo-mining on your server/wallet. (If you "happen" to stumble-upon, a valid share for another client, you could still submit it, but you wouldn't be "looking" for solutions, just accepting one if it came around.. for THAT server.)

There is NOTHING in place to stop me from solo-mining MY block (which is the same as the POOL BLOCK.), then simply submit useless invalid block data to the pool, for that block... if I find it, and submit it to MY WALLET. Or just "not submitting any block" to the pool. As far as the pool knows, I am still processing it, and just "have not found a solution yet".

EG, "Not actually doing the pools work, other than the share-work." Instead, using your actual processing to mine your own wallet/server.

I can mine both solo and a pool at the same time... anyone can.

A share has nothing to do with the block. It is just some useless value sent to you, to see "how fast you work". You are credited for the share, not for the actual block-work. (Block work is just thrown out once a new block is detected, if you have not submitted the solution to the pools wallet-ID.)

Like I said, what stops me from "Processing" useless shares from pool-a, pool-b, pool-c... but not actually doing the "block work" for pools a-c... Only submitting the "shares" to all three pools. (I am saying that you actually DO process the shares. Thus, they will all be valid.)

"You do not process shares when solo-mining, because you do not have to submit proof of your processing power."

"Shares are irrelevant blocks of data, distributed by the pool, to test your speed to give you credit for your power in a round, and have little impact on the processing power of hashing the actual block." (However, that is untrue. If you are stopping hashing the block, to hash a useless packet, then that takes-away hashing power that would normally be used to hash the actual block. No matter how easy it is. You just end-up hashing more easy useless shares then hard shares.)

Then, since that is not actually slowing the computer down... I am just solo-mining with my ID. Mining the block that I SHOULD be mining for the pool. Thus, since I am not actually mining that block with the pool, just pretending to mine it... the "pool" never gets the blocks I find. Yet, I get paid from all the pools, as if I am honestly mining away for them.

Yes, I realize the "stock program" is not programmed to do that. They would not be using a stock program.

They actually do the "share work". A share is just a fast and useless calculation, used to measure your speed, while you "solve the block". It has nothing to do with the block solution itself.

You had it right the first time... The open air... (Use a filing cabinet-rack, or milk-crate.)

As for bugs... A case will offer absolutely zero protection against bugs. Windows is full of them, Linux has a few, and the ones in the basement will easily crawl into your PSU vents, and any other open hole. It is warm in there, and they like the humming.

Yes, a super-tower "full ATX" case will hold most of what you need. (Provided that you have a MoBo that has 4x double-spaced 16xPCIe slots.

If you do not have 4x double-spaced slots, you will need risers, and no case is designed for that setup. (Which brings me back to the first line of my post, and the second line of your original post.)

Alternate "cases", would be a "filing cabinet", gutted "Microwave", or two towers combined. (You rip-out the mobo-plate, and remove the panel on that side. Raising your cards up to the slots, with the long extender-cables. Those should all be powered-cables, as that longer length thin wire will not handle those amps.)

Or, gut a mini-fridge, and vent it... A large oven-toaster... A medium metal trash-can with a lid... An old wall cabinet... The list goes on and on...

Windows XP can not use a 7970... (The 1.5GB version from walmart MIGHT work, with PCIe 2.1 slot.)

XP is limited to 4GB of ram.

1.2GB minimum is windows allocated. +3GB from the card = ERROR, OUT OF MEMORY ALLOCATION. (Only 64-bit server-edition of XP can allocate up to 128GB???) Windows assigns "Video ram first", then "system ram" with what is left-over. Which is less than the minimum the OS requires to start, of 1.2GB. (32-bits = only enough memory allocation for 4GB of ram-addresses.)

Not to mention the card is 3.0 PCIe, which windows can also NOT address. (Not the 32-bit version, not sure if server edition would have working drivers.)

Not sure if that mobo has PCIe 3.0 or 2.1... but 2.0 will not POST with a 3.0 or 2.1 card in the slot.

Just some things to think about down the line... You will need "Vista" minimum... 64-bit, for the >4GB ram limit.

Just for curiosity...

What measures are in place to stop a "miner" within a "pool" from doing this...
- Mine away all the useless shares (Which takes no effort)
- Don't actually mine for any coins... (Thus saving a lot of power, and being able to mine multiple pools at once.)
- Collect a percentage from the useless processed shares in the pools.

or...
- Mine away in a pool...
- Use your own wallets server-id, instead of the pools id... Thus, when you find a block, you keep it... and still get rewards for shares from the pool. (Only using your ID on the blocks, not the shares, which are returned.)
- Mine multiple pools, processing useless shares, while collecting the found blocks for yourself... Thus, ensuring invalid blocks are always returned to the pool, too late, after they have deposited into your wallet.

Not to mention it would punish those who just had a "network hiccup"...

Not all double-spends are done on purpose. Some are a result of the "system they run on".

Data can hop around, be delayed, be duplicated, or just be "present due to processing".

Not to mention that there are physical "delays" across a network, even in perfect order. As well as no true standard "time".

If the "system" allows double-spends, then that is something that the "system" should be charged for, not the user. If my bank charged me because they failed to track my money correctly, that should be them who pays for the loss, not me.

Is this version still seeing "merged transactions" as separate transactions for calculating the "minimum fee"...

The prior version was seeing things like this...

Example only... (min fee 0.0005)

{Attempting to send 0.000018506, pulled from many "partial amounts"}
ldfjslkfj 0.000000123 ->
sfoisud 0.000018273 ->
osidufo 0.000000010 ->
doifusid 0.000000100 -> = dkfjsldk [0.000018506] @ fee (0.0005 x 4):[0.00200000] = -0.002018506 total deduction.

Fees get real large, with up to 100 partial "change" mergers into one singular transaction. (Eg, it is treating every change-packet as a separate transaction, though it is simply merging them into ONE singular transaction... thus, expected payment would be 0.0005 not 0.0005x4 = 0.0020...

NOTE: After the "Last estimate" $month/day... add a box for "coin->USD"

That will let YOU and US, know how "off" the estimation is, based on actual prices. (If it says TRC = $100 per coin, and the actual value now is $0.30 per coin... you should suspect something is wrong with the conversions/numbers, thus, not to "trust" the "estimated results".)

Also, TRC has fluxuating difficulty... it fluxuates from 12K to 32K at the moment... I think that is messing with your values, when you see a pool has been "lucky" with a bunch of 12K finds, but the difficulty is being read as 32K at that specific moment. (Assume the high difficulty as the difficulty, but calculate with the AVG of (high+low)/2... Your numbers will be less "tainted".)

MSIE shows "day" always, for title-description... (But I "know" I selected month, so it's all good.)

Having a "refresh" button helps, even if it is "auto-refreshed"... helps when auto-refresh fails to update.

Your "terracoin" estimation is off...

It is estimating about 10x more than realistic values...

Says 1.9MHs will earn about 1700 coins... that should be about 330 coins, at best...

Thus it appears to earn $580 a month from a 1.9MHs machine, but that machine will only get you about $50.00 a month.

Compared to BTC which says you earn $290 a month... TRC is NOT that profitable, (barely even traded).

Perhaps your estimation is simply off by one decimal. Earnings are reporting as 60.0 when they should be 6.0 (value).

Great chart though... I didn't know PPcoin was nearly as high in value as BTC. That will make a nice fallback coin in the future. The rest are nice to "invest" for the future also.

You should also consider showing the values in USD (since that is what you use), instead of value to BTC, which is kind-of pointless and inaccurate. (Not BTC value of, to USD... that actual coins value in USD. Unless there is no conversion, then you * it, to note value is in x->BTC->USD. As opposed to x->USD.)

Get an account on every coin, and use real-world data, not just API from BTCe, which is a low-end trade service. Use MtGox values, where possible. (You can even "harvest" user data. Ask them to input "the results they get", which you "judgmentally" accept as a "weighted real-world value". Time-based... older has less relevance, other than to show if it is "climbing or falling".)

Or just seize them in legal issues... "taking ownership" of the machines... You know, "for national security reasons"... (Not because they are actually a threat, that would be an "excuse", to seize them.)

Show them that CPU's, GPU's, Iphones, Tablets, and itouche's can also MINE, and are, thus, "mining equipment"... and they will change the statement.

BFL's are not "dedicated" only to bitcoins, nor are any other devices, thus, can not be called "bitcoin miners", just because they are capable of that task. They would have to be dedicated to that task only. (ASIC's can mine any other alt-coin, that is based off SHA256, and perform other duties. Proof of that is on the website, in the software section. Shhh, that is for the FPGA's not the ASIC's... but they don't know that!)

Legally, you can sue them if you use CC or BANK-NOTES through PAYPAL... as... "This currency can be used for ALL DEBITS PUBLIC AND PRIVATE." It is a federal violation to "Refuse acceptance of currency of a federal note, for services." It is also a violation of the CC company, who is backed federally, and says roughly the same thing. (They had to agree to that, to accept a CC for transactions.)

They can only block actual "paypal - currency" that is originated from "paypal - currency". (EG, I pay THROUGH paypal, but the money I pay with is USD from a bank, or CC funds.)

Live and let learn...

Be happy it wasn't a loss of 100BTC.

In the end, the blame IS on YOU. You accepted a transaction with a stranger, you trusted the untrustable (took a personal risk), and lost-out on that risk.

I am sorry, but your own failure to take simple precautions is what got you scammed. You gave a stranger your car, expecting him to give you back a truck in return, and he just drove-off, because you failed to get his ID, a copy of his license, and have a witness present. (Or use an escrow service, or other "protective service".)

There is NOTHING anyone can do to HELP you, or anyone else who this has happened to. The best you can hope for is to locate this mystery person and ask them for your promised property, or a refund. Also, warn others about "how this scam was done", making it believable enough to become an event that led to YOU being scammed.

Day trading with anything is a lot of risk... but at the end of the day, you only loose what you put in. (As opposed to real day-trades, where you are "forced" to cash-out at the end of the day, thus all losses are "realized", not "figurative".)

I hope it goes down to 50 or 60 again... (That is the half-way drop from average.) That is both expected, and welcome, from me. It will rise, because losses are now real, as more coins sit in "buyers hands", rather than sellers hands. (Well, coins that are not lost or stolen/destroyed.) Thus, those losses are, "realized", and limiting the majority from "selling short", because they just can't, or they loose!

I gotta find that place that does hedges... Then I win more, when it falls!

The solution is to use bitcoins themselves, as the currency. However, even getting goods and services, you are entitled (in the USA) to pay taxes on the "value in dollars", for any "barter". Which is what the use of a bitcoin is. (Or paypal or imvu-credits or lindens.)

However, there is nothing that says, "This fund was for a service". As far as they know, you just moved credits from one account to another, of money you already paid taxes for. (That is why paypal now asks, "is this for PAYMENT of..." as opposed to being a "donation" or a "transfer of your other accounts". EG, transferring $1,000,000 USD from your account A to account B can be confirmed as a transfer, and not a $1,000,000 taxable income, at a bank. However, without that "proof", they actually just assume all transactions are income.)

This is what "governments" want from a bank. This is the "regulations" they are asking money-distributers to record and hand-over. Those who can not, are shut-down. Those who can, continue to operate and are fined if they are not "registered" and "insured".

Yes, mowing lawns and babysitting is illegal for a kid under 18 to do, without paying taxes. (The parents have to claim that income as their own.) So is selling/trading/giving-away beanie-babies-titles. They have to be valued, and you have to pay taxes on the value THEY think they are at, not what the value was, that you actually got/paid. (They do that with cars too. You pay taxes on $600,000 for a race-car, even if it was "given" to you or sold for $1.00)

The only LEGAL model, is the existing LEGAL model...

Now they can actually charge you for value, because of the "value" stated in the "charts"...