Here is what I think
https://bitcointalk.org/index.php?topic=766190.msg11769397#msg11769397
In general no mater how big block tx becomes if Tx fee is low there will be always a chance with little money invested to "spam" the network. A reasonable solution for me is to increase tx fee in a first place then increase max block size if needed
That will be a good step forward to be ready when block reward will be arround zero - a good long term solution which will solve most or all of the current issues 

Matt,
My intentions are not to argue with you. But for me each valid TX which contains fee is not a spam.
No matter if it was useless and generated in artificial way or not
For instance
https://bitcointalk.org/index.php?topic=1098263.0
Let us imagine that current BTC transaction rules are 0.1 BTC min fee in order for TX to be accepted at all. So i do not mind the folks from the above thread to "SPAM" network and experiment

In order to overcome this in my opinion the Min required fee must be increased and TX with 0 fee shall be forbidden. There is no free lunch and that is all. Let us not forget that after some years when block reward decreases near ZERO all mining shall pay for its cost from TX only   Asuming BTC price does not reach 10K and net diff stays high.... No mining no TX at all. So an equilibrium must be found
Sooner or later it must be done. Sooner the better..

Just my two cents

Thanks

Does it mean that if someone mines 0.2 BTC he will get ( 7 NMC + 7 IXC + 7 I0C + 5 HUC) / 5?
Or 1 BTC is the minimum barrier in order to receive the bonus?

Thanks

Good so it might not be spam in that case

BLk size depends on POOL bitcoind config only
Max size=Max fee so it is done on purpose

Hats down to Eleuthria. He is the man of honor!!!!!!

I wish you "bugless" future Doc
For another 4x10 years at least....
Best

No hard feelings Philipma. My intentions were not to offend you or anyone else. I have just explained what is all about. I am not sure if you got details because I am not native English speaker.....
Peace....
Every one is free to chose where to lose his money..all of us are having tough times in current situation. For me the dilemma is not how much I am making and how to make more..but when I loose who to sport with my loss if that can be called suport at all.I am addicted to mining and all related  stuff including software part.
So...I have my choice and it will never be a Chinese pool..
I am dealing in my workwith Chinese software "miracles" unrelated to Bitcoin all day long. So I am enough.  Btc world is no exception except  one CHINESE company which does not have a pool and is truly opened sourced.
I am not naming it because I do not wanna start discussion about it. All I wanted to say that almost everything related with software in general comming from China is a total shit including BTC world  
When you are making a fortune or you count on next fool in the chain all is perfect and no one cares but it is time for all of us to think and start to care about that tiny details here and there otherwise BTC will be dead soon..
There is no fool chain any more and that community is that last fool in Chinese chain. So let us support each other and stop acting like total fools

The point is that merged mining pools shall not reject shares on aux chain changes....those shares are still valid for BTC chain   even frequent job restarts shal have zero impact on rejects in that case it turns out that they can even reject BTC block solver in that case   nice...
The real problem is not "shit coin" mining itself but shitty pool implementation...
At the end of the story they can even skip stratum jobs restarts (and hive higher stall aux block rate as side effect) on aux chain changes just to guard against shitty ASIC MCU (PIC) firmware written by same idiots
But who cares ...when I see topics like who speaks Chinese I need to mine in China pool I just feel petty for these guys .............
And assuming all participants have higher pool reject rate (Let us say 10%) in mm pool you lose nothing at the end except possible 25 btc rejected due to above reasons...In other words at 10% rejects one of 10 VALID BTC BLOCKS is rejected by the pool...Will MM coins value compensate for it ...NO!!!!!
Once again avoid using Chinese  pools at any cost not only because of the above but if you wanna help the BTC to stay alive in general!

Whatever you chose avoid Chinese pools
You can read the forum carefully and decide - the most important is to whom you trust and that is completely up to you

I know:)
once again i was speaking in general

for the record

             total       used       free     shared    buffers     cached
Mem:      16431628    6109668   10321960          0     393708    3062792
-/+ buffers/cache:    2653168   13778460
Swap:      9959420          0    9959420

Now Ontopic new relay client with log filtered out



Thu Jun 18 08:28:53 EEST 2015: Starting relaynetworkclient
Connected to bitcoind with version 70002
Finished connect handshake with bitcoind
Closing relay socket, failed to read message header (104: Connection reset by peer)

Connected to relay node with protocol version the blocksize
[2015-06-18 05:56:02+00] 000000000000000004fd86600f6a12e5186ec18f11d7502afba3b7f7e00cae1a Block recv'd, size 932103 with 5222 bytes on the wire
[2015-06-18 05:58:00+00] 00000000000000000bb1ed574ab76212bc3fd86fad043e48a804b5baab873114 Block recv'd, size 924435 with 1573 bytes on the wire
[2015-06-18 06:03:14+00] 000000000000000010e5b0cdfc902b4b7f700177dd400f411f85bb861837fe42 Block recv'd, size 213069 with 827 bytes on the wire
[2015-06-18 06:08:58+00] 00000000000000000d7ba82013c1bd3354330dfab5406e3b5b31d779bae7306d Block recv'd, size 298966 with 1170 bytes on the wire
[2015-06-18 06:22:16+00] 000000000000000008a705191b01905215e1c37de8c4fd5f3c8aec8f4a98fa3f Block recv'd, size 438564 with 1899 bytes on the wire
[2015-06-18 06:24:21+00] 00000000000000001023e903ecbc7d4308c2c0659c92c5bb8d67e95341b81990 Block recv'd, size 118202 with 561 bytes on the wire
[2015-06-18 06:24:47+00] 0000000000000000121fe92d40e84a77c5e1a3e2aa0ef202f2c150e82c7fd1ce Block sent, size 43943 with 35187 bytes on the wire
[2015-06-18 06:24:52+00] 0000000000000000121fe92d40e84a77c5e1a3e2aa0ef202f2c150e82c7fd1ce Block recv'd, size 43919 with 4917 bytes on the wire
[2015-06-18 06:54:13+00] 000000000000000014e4aca7174b5f4468836a7569147b1b6ed787b842869e05 Block recv'd, size 749195 with 3347 bytes on the wire
[2015-06-18 07:05:45+00] 00000000000000000dc26e1e68c1c04e34db2faeaa2771b0156738d463e074bf Block sent, size 707268 with 603451 bytes on the wire
[2015-06-18 07:05:46+00] 00000000000000000dc26e1e68c1c04e34db2faeaa2771b0156738d463e074bf Block recv'd, size 707244 with 1880 bytes on the wire
[2015-06-18 07:09:56+00] 0000000000000000148e854a12e5eb378e5adaf6f8f5e416963e6e78bd0b6e1a Block recv'd, size 201317 with 952 bytes on the wire
[2015-06-18 07:10:20+00] 00000000000000000d1e68b1aabb79565f8307b97655d2a21c6f99b0d209a989 Block sent, size 26317 with 24792 bytes on the wire
[2015-06-18 07:10:39+00] 00000000000000000d1e68b1aabb79565f8307b97655d2a21c6f99b0d209a989 Block recv'd, size 26293 with 229 bytes on the wire
[2015-06-18 07:30:18+00] 0000000000000000119247bbeea1fa3ae3697482e9d1ec294e7d151e5927c583 Block recv'd, size 741555 with 2971 bytes on the wire
[2015-06-18 07:32:34+00] 000000000000000007802e4a62af5b844a93271cb6ab6d14285a4fa34c3b23fe Block recv'd, size 115723 with 395 bytes on the wire

And i am faster with two blocks only  
There is no match between well connected bitcoin deamon and mat realy

Thanks once again Matt!

Honestly speaking I did not watch old client mem usage at all. My mem usage issues were not because of your client. What I wanted to say is that we do care about mem usage in general.

With gbt
Bitcoind does not support stratum and running full node well conected costs money ram cpu and bandwith...Chances to get orphan/stale block with home node are very very big. So unless you are NOT 100 sure what you are doing just spent 0.5% for fee and this will get back to you milion times if your are lucky to find a block
It worts trust me

Or just ant miner software sucks both controller and binary fork - closed source of cgminer...
If the software part is broken there is no ESSY fix - only fake stats and that is

and it works  
https://www.biteasy.com/testnet/transactions/fc845d0011e7075b81dde8dad784338e92a1fb5ca5da5047ba798968a00b062d

PS:

http://blockexplorer.com/testnet/tx/fc845d0011e7075b81dde8dad784338e92a1fb5ca5da5047ba798968a00b062d

Seems little buggy

I do not think so
I am a sawp hater
Thanks Matt great job!

http://testnet.tbdice.org/

Nice....They do test  M of N multisig address

Maya the bee
Another  remarkable comment
------
Main benefit is you will never lose your heart ashing power like solo mining (only 1 hashing power win , others gone)
-------
Says the OP of the ckpool

Pathetic  
Says the male nasty bug....

I think that he is just an young enthusiast and his intentions are not to run with 25 btc and to scam people ...
But meanwhile setting the pool NNNNth "private" instance he just can fickup pool config UNintentionally an send the 25 BTC in nowhere

Same thing at the end BTC are gone only good intentions are left
Such a waste for the pool op and his "partners"...