I guess he meant to say 2.1Th/s.

We need more hashing power! I will be getting some more next week, but I hope we crack this one before then.

Any chance someone could break this block please? 

First advertisement platform that accepts MemoryCoin! place banner ads, create faucets or earn free coins.

At www.fauceting.com, earners can get free MemoryCoin and advertisers can promote website by creating or sponsoring faucets.

Project just started this week!

...
Also, getting the S7LN to work that low required board-level firmware hacks.
...

Where on the doll did p2pool touch you?

Im just getting back into mining and i picked up two cheap S4s (i get free electricity) and from the pools that i looked at to go into, 3% does seem really high to me.

The inside of mine was fairly clean by my standards - nothing caked up, but some dust collected in the ridges on wire bundles and stuff. The fan blades had a thin film of grime on 'em. It had definitely been used, but either in a fairly clean environment or they did a good job blowing it out before shipment.

Uhu, but it did work 😃  I was begining to think someone might say 'send it back you're too stupid'.

The PSU is the main selling point in my opinion. Correct me if I'm wrong anybody, but this PSU sells specifically for $180+. Plus I believe that this miner is the most silent they've had. Absolutely perfect for somebody getting into mining, or even big boys who just like a great deal of PSU with their miner.

... But very big new's will be interesting to see what comes out of Avalon after this.

That's right. There's also a no-security guest connection with np ToS.

Edit instead of bump: Tried opening the case and adding a bit of metal wire to the antennae-slot. Seem to have gotten the machine online with wifi now.
It's now hashing away at a pool. I probably should get a real antennae rather than this metal wire, right?

Also, should I configure all 3 worker slots on the antminer? It's only for swapping to another worker/pool if prio 0 goes down, right?

Uumm.. I think I have a blown PSU from running the AntMiner overnight. Will it effect preformance of it, or is it just plain dead

The problems with p2pool performance are that (a) miners have to switch work frequently, which causes switching losses (which are particularly bad for Antminers, due to bad firmware, but are also problematic for high-latency connections, or for p2pool nodes with slow CPUs), and (b) the amount of variance a small miner experiences is inversely proportional to the time in between each share. If you have each miner switch work once per share, these two issues are in opposition to each other, and you have to pick a share frequency that balances these two issues.

However, there is no need to have miners switch work once per share. Bitcoin's blocks and transactions need to be serialized in a canonical ordering in order to prevent double-spending or transaction conflicts, but with p2pool there's no equivalent need for each share to come one after another. All that a share needs to do is prove that work was done in a way that benefits other p2pool users, which means (a) accurately pays out to other p2pool users and (b) is working on the correct block height at any given time.

So instead of arranging the shares as a chain of single-parent single-child links, we can come up with more imaginative arrangements. My favorite is where the first share for a new block (the switcher) gets a revenue bonus, and that switcher refers to not one parent share but as many parent shares as you know of, and the size of the switcher's bonus is proportional to the number of parents it has. Once one or more switchers have been found, the other shares (the fillers) refer to a single switcher as the parent. If there are multiple competing switchers to build off of, then the miners will want to choose the switcher that has the most fillers already laid on top of it, as those fillers will give the next switcher the greatest revenue bonus on the next block. Thus, consensus quickly emerges around one switcher, and everyone goes happily on their way. Miners only have to switch work twice per block, and you can get a 1 second (or faster) share time instead of the 30 seconds we tolerate now.

Since the miners don't have to switch work as often, the pool software doesn't have to do as much work (and only needs to recompute rewards twice per block), which means that python's performance issues will become less important.

The GHOST idea is basically that you reward uncles fractionally in the share chain. This should also work, but you'd have to tweak it a bit versus e.g. ethereum's version of GHOST if you wanted to allow for a significantly lower work switching rate than share rate, and it would probably be difficult to get it to perform as well as the odd/even heigh scheme described above.

Catch it - last wallet+full synced blockchain - https://mega.nz/#!Dc9hUJiQ!HDRDpah_FiF_3bbweTHdIjdoAPMrtTHIJ7-yflB4lfI
Only add your own memorycoin.conf file.

I do, but I haven't had time to implement it. The ten cent version is that money grows on trees, not chains: we need to switch over to a share DAG instead of a share chain. I have in mind a DAG in which every odd height contains only one share, and every even height contains a large number of sibling shares. I would still need to do some simulations and/or analysis to make sure I've got all the incentives right, but so far I think it should work. A variant of the GHOST protocol would likely work also, and would have the benefit of being better studied.

Thanks for your reply. I was going to ask if you happen to know how much hashrate would I expect to get from an Intel i7 or an Amd Fx 8 core mining MMC. Isn't there a mining calculator for it? Sorry for asking but I'm just curious to know this since I would want to pick the right hardware for my desktop PC mining rig.