Re: [Bitcoin-development] BIP: Voluntary deposit bonds

On Mon, Dec 29, 2014 at 04:21:02PM -0300, Sergio Lerner wrote: > I propose to allow miners to voluntarily lock funds by letting miners > add additional inputs to the coinbase transaction. Currently the > coinbase transaction does not allow any real input to be added (only a > pseudo-input). > This

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

I agree with Gregory Maxwell, I don't think it would be as easy as just changing IsCoinBase(), since there are places where the code assumes that the coinbase's vin doesn't spend any prevouts and/or has size 1. For example, here

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

On Tue, Dec 30, 2014 at 4:25 PM, Sergio Lerner wrote: > Slight off-topic: > That looks like an abuse of the VM. Even P2SH is an abuse of the VM. > Gavin's OP_EVAL (hard-fork) should had been chosen. I'm taking about a > simple change that goes along the lines of Satoshi's original design. > Bitcoi

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

On 30/12/2014 01:51 a.m., Gregory Maxwell wrote: > On Mon, Dec 29, 2014 at 7:21 PM, Sergio Lerner > wrote: >> I propose to allow miners to voluntarily lock funds by letting miners >> add additional inputs to the coinbase transaction. Currently the >> coinbase transaction does not allow any real i

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/30/2014 10:47 AM, Jorge Timón wrote: > What services? I must be missing something obvious about the > motivation. I understand the difference between "paying to myself > only when I mine the next block" and "offering fees to whoever > mines thi

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

On Mon, Dec 29, 2014 at 10:34 PM, Justus Ranvier wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 12/29/2014 09:10 PM, Mike Hearn wrote: >> How does adding inputs to a coinbase differ from just having >> pay-to-fee transactions in the block? > > If a miner includes pay-to-fee tran

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

On Mon, Dec 29, 2014 at 7:21 PM, Sergio Lerner wrote: > I propose to allow miners to voluntarily lock funds by letting miners > add additional inputs to the coinbase transaction. Currently the > coinbase transaction does not allow any real input to be added (only a > pseudo-input). > This is a ha

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

On Monday, December 29, 2014 9:10:20 PM Mike Hearn wrote: > How does adding inputs to a coinbase differ from just having pay-to-fee > transactions in the block? Pay-to-fee transactions can be "stolen" by another block at the same or greater height. Additional inputs to the generation transaction

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/29/2014 09:10 PM, Mike Hearn wrote: > How does adding inputs to a coinbase differ from just having > pay-to-fee transactions in the block? If a miner includes pay-to-fee transactions in a block, those fees could be claimed by another miner in

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

On Monday, December 29, 2014 7:21:02 PM Sergio Lerner wrote: > I propose to allow miners to voluntarily lock funds by letting miners > add additional inputs to the coinbase transaction. Currently the > coinbase transaction does not allow any real input to be added (only a > pseudo-input). This is

Re: [Bitcoin-development] BIP: Voluntary deposit bonds

Could you explain a bit further Sergio? I'm not sure I fully understand the proposal. How does adding inputs to a coinbase differ from just having pay-to-fee transactions in the block? -- Dive into the World of Parallel Pr

[Bitcoin-development] BIP: Voluntary deposit bonds

I propose to allow miners to voluntarily lock funds by letting miners add additional inputs to the coinbase transaction. Currently the coinbase transaction does not allow any real input to be added (only a pseudo-input). This is a hard-fork, and we could include it the next time a hardfork is made