<oembed><type>rich</type><version>1.0</version><author_name>npub1ts9hljj3l4yrpdxelpqdup3l46lw40fmkhw3rr0feh6s5ml247vqerfl5y</author_name><author_url>https://nostr.ae/npub1ts9hljj3l4yrpdxelpqdup3l46lw40fmkhw3rr0feh6s5ml247vqerfl5y</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-18&#xA;📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----&#xA;Hash: SHA512&#xA;&#xA;On Thu, Jun 18, 2015 at 03:49:06PM +0200, Mike Hearn wrote:&#xA;&gt; One reason I keep banging on about *process* and how Wladimir needs to be&#xA;&gt; The Decider is that the current attempt at &#34;process&#34; is so vague, not only&#xA;&gt; is it unexplainable, but it&#39;s wide open to manipulation.&#xA;&#xA;It looks as if you entirely missed my point. I&#39;m The Decider for *code issues* regarding Bitcoin Core. Consensus issues should not be considered part of that, they span multiple implementations.&#xA;&#xA;So I&#39;m *not* the decider for anything that concerns the behavior of the global consensus, and I cannot be, as I have explained in the previous post, and as Sipa explained in his.&#xA;&#xA;Speaking of process, let me remind you that there is a BIP processs: https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki &#xA;&#xA;If you think it&#39;s not clear enough, which may explain why you did not even attempt to follow it for your block size increase, feel free to make improvements.&#xA;&#xA;Wladimir&#xA;-----BEGIN PGP SIGNATURE-----&#xA;Version: GnuPG v1&#xA;&#xA;iQEcBAEBCgAGBQJVgtAOAAoJEHSBCwEjRsmmLPUH/1ug5pvLz6ptIhvuROclV7Jh&#xA;z0Szk5FOqfg4ejT3nYV5LRV5WNHUGDdFnHZJRFsKYH9B0LFgOlnkc488Qg6hBb+1&#xA;rf5zEF/D2X4MhPIx6GqI++gvhDzdBH2t9yxbU7LVZALo7+wtW+ms5eHHFs8WrU0z&#xA;m7NgiZRen4cpQUiBWHlt0PojmXBVZQNU0CD6ErcOpQXhN8J0sb0l0DuFswQgUqxk&#xA;rrNe3LvKp89xT0kDxyzQts/CeIG/8kQYLwIJ1QQDXvYayj2aHHYMkSEWfDlew3IC&#xA;zQkFgHCTGihGHPFeow+dnuW1DI1l92yPYNDLbxivSam3X+qCAGzUTOWTFE+iprk=&#xA;=tE4K&#xA;-----END PGP SIGNATURE-----</html></oembed>