Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee

2015-06-19 Thread Chun Wang
On Fri, Jun 19, 2015 at 10:00 PM, Adrian Macneil wrote: > However, we do rely pretty heavily on zeroconf transactions for merchant > processing, so if any significant portion of the mining pools started > running your unsafe RBF patch, then we would probably need to look into this > as a way to pr

Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee

2015-06-19 Thread Chun Wang
Before F2Pool's launch, I performed probably the only successful bitcoin double spend in the March 2013 fork without any mining power. [ https://bitcointalk.org/index.php?topic=152348.0 ] I know how bad the full RBF is. We are going to switch to FSS RBF in a few hours. Sorry. On Fri, Jun 19, 2015

Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee

2015-06-19 Thread Chun Wang
Hello. We recognize the problem. We will switch to FSS RBF soon. Thanks. On Fri, Jun 19, 2015 at 9:33 PM, Stephen Morse wrote: > It is disappointing that F2Pool would enable full RBF when the safe > alternative, first-seen-safe RBF, is also available, especially since the > fees they would gain b

Re: [Bitcoin-development] User vote in blocksize through fees

2015-06-13 Thread Chun Wang
To tell you the truth. It is only because most miners are not located in the West. If Slush, Eligius and BTC Guild still on top 3, the core developers, including brain-dead Mike Hearn, would be very happy to do BIP100 just like they did BIP34 and BIP66. Shame on you! On Sun, Jun 14, 2015 at 6:20 A

Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

2015-06-01 Thread Chun Wang
The current max block size of 100 bytes is not power of two anyway. On Mon, Jun 1, 2015 at 10:46 PM, Oliver Egginger wrote: > On Mon, Jun 1, 2015 at 3:59 PM, Gavin Andresen wrote: >> What do other people think? Would starting at a max of 8 or 4 get >> consensus? Scaling up a little less tha

Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

2015-06-01 Thread Chun Wang
That is good. I oppose 20MB because I estimate it may increase the overall orphan rate to an unacceptable level. 5MB, 8MB or probably 10MB should be ok. On Mon, Jun 1, 2015 at 9:59 PM, Gavin Andresen wrote: > On Mon, Jun 1, 2015 at 7:20 AM, Chun Wang <1240...@gmail.com> wrote: >&

Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

2015-06-01 Thread Chun Wang
adopted. We should increase the limit and increase it now. 20MB is simply too big and too risky, sometimes we need compromise and push things forward. I agree with any solution lower than 10MB in its first two years. On Mon, Jun 1, 2015 at 7:02 PM, Chun Wang <1240...@gmail.com> wrote: > On

Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

2015-06-01 Thread Chun Wang
On Mon, Jun 1, 2015 at 6:13 PM, Mike Hearn wrote: > Whilst it would be nice if miners in China can carry on forever regardless > of their internet situation, nobody has any inherent "right" to mine if they > can't do the job - if miners in China can't get the trivial amounts of > bandwidth require

[Bitcoin-development] Fwd: Block Size Increase Requirements

2015-05-30 Thread Chun Wang
On Sat, May 30, 2015 at 9:57 PM, Gavin Andresen wrote: >> Bad miners could attack us and the network with artificial >> big blocks. > > > How? > > I ran some simulations, and I could not find a network topology where a big > miner producing big blocks could cause a loss of profit to another miner

Re: [Bitcoin-development] Block Size Increase Requirements

2015-05-29 Thread Chun Wang
Hello. I am from F2Pool. We are currently mining the biggest blocks on the network. So far top 100 biggest bitcoin blocks are all from us. We do support bigger blocks and sooner rather than later. But we cannot handle 20 MB blocks right now. I know most blocks would not be 20 MB over night. But onl