Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SZNiZ-0006Ta-Ob for bitcoin-development@lists.sourceforge.net; Tue, 29 May 2012 14:48:15 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1SZNiO-0005zf-Ku for bitcoin-development@lists.sourceforge.net; Tue, 29 May 2012 14:48:15 +0000 Received: from ishibashi.localnet (unknown [97.96.85.141]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id BE20F56059A; Tue, 29 May 2012 14:47:56 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 29 May 2012 14:47:28 +0000 User-Agent: KMail/1.13.7 (Linux/3.2.12-gentoonestfix-intelwr; KDE/4.8.1; x86_64; ; ) References: <5C824F0D-6025-4630-965B-E6C685588250@mac.com> In-Reply-To: <5C824F0D-6025-4630-965B-E6C685588250@mac.com> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201205291447.29823.luke@dashjr.org> X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SZNiO-0005zf-Ku Subject: Re: [Bitcoin-development] Punishing empty blocks? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2012 14:48:15 -0000 On Tuesday, May 29, 2012 8:52:49 AM Michael Gr=F8nager wrote: > The format of the sla.php page should then be specified too - but it could > be a json-rpc call returning a json object like (as result): { > sla_version: "0.1", > accept_no_fee_tx: false, > min_fee: 50000, > big_tx_fee: 10000, // extra fee pr kb > } > I guess miners could work out a more suitable set of fees... Please not JSON, and not hard-coded logic. Bitcoin already has a secure=20 scripting system - perhaps we can decide on an initial stack format and run= a=20 script retrieved from the URI?