Michael Grønager [ARCHIVE] on Nostr: 📅 Original date posted:2011-08-25 🗒️ Summary of this message: A discussion on ...
📅 Original date posted:2011-08-25
🗒️ Summary of this message: A discussion on blockchain split has been postponed, and new standard transactions are considered a good enough short-term solution. Simplifying the problem is suggested.
📝 Original message:Hi Gavin (the list escaped the cc...),
I participated also in the hacakathon Sunday @ OnlyOneTV and I felt that this had a strong chance to diverge. So - yes - I agree - no "constitution" changes now. Further, I have thought later on on the analogy of a clerk and a safe.
WHen you enter the bank you hand over your money to the clerk (one key) - then after the clerks wallet has been filled over the day _he_ transfers the money to the safe (3 keys). My point is do we really need the customer to bypass the clerk and have 3 key addresses, or could we just leave it to the/a client to implement the multisign transaction after the money has been received - as a transfer to a safe? This would greatly simplify the problem and cover the vast majority of use cases. Not covered in this is huge single transfers where the intruder of a single key system finds it profitable to reveal their intrusion by grabbing the entire wallet.
Put in another way - do we *really* need to couple the securing of the wallet to creating a new address type ?
Cheers,
M
On 24/08/2011, at 19:57, Gavin Andresen wrote:
> This discussion is convincing me that scheduling a blockchain split is
> definitely the wrong idea at this time. We can revisit in N months,
> when we've got a roadmap and nice unit tests and a bunch of
> well-tested patches for fixing all of the things that aught to be
> fixed when we DO decide a blockchain split is necessary.
>
> There seems to be rough consensus that new, imperfect standard
> transactions are a good-enough short term solution.
>
> --
> --
> Gavin Andresen
>
> ------------------------------------------------------------------------------
> EMC VNX: the world's simplest storage, starting under $10K
> The only unified storage solution that offers unified management
> Up to 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Michael Gronager, PhD
Owner Ceptacle / NDGF Director, NORDUnet A/S
Jens Juels Gade 33
2100 Copenhagen E
Mobile: +45 31 62 14 01
E-mail: gronager at ceptacle.com
🗒️ Summary of this message: A discussion on blockchain split has been postponed, and new standard transactions are considered a good enough short-term solution. Simplifying the problem is suggested.
📝 Original message:Hi Gavin (the list escaped the cc...),
I participated also in the hacakathon Sunday @ OnlyOneTV and I felt that this had a strong chance to diverge. So - yes - I agree - no "constitution" changes now. Further, I have thought later on on the analogy of a clerk and a safe.
WHen you enter the bank you hand over your money to the clerk (one key) - then after the clerks wallet has been filled over the day _he_ transfers the money to the safe (3 keys). My point is do we really need the customer to bypass the clerk and have 3 key addresses, or could we just leave it to the/a client to implement the multisign transaction after the money has been received - as a transfer to a safe? This would greatly simplify the problem and cover the vast majority of use cases. Not covered in this is huge single transfers where the intruder of a single key system finds it profitable to reveal their intrusion by grabbing the entire wallet.
Put in another way - do we *really* need to couple the securing of the wallet to creating a new address type ?
Cheers,
M
On 24/08/2011, at 19:57, Gavin Andresen wrote:
> This discussion is convincing me that scheduling a blockchain split is
> definitely the wrong idea at this time. We can revisit in N months,
> when we've got a roadmap and nice unit tests and a bunch of
> well-tested patches for fixing all of the things that aught to be
> fixed when we DO decide a blockchain split is necessary.
>
> There seems to be rough consensus that new, imperfect standard
> transactions are a good-enough short term solution.
>
> --
> --
> Gavin Andresen
>
> ------------------------------------------------------------------------------
> EMC VNX: the world's simplest storage, starting under $10K
> The only unified storage solution that offers unified management
> Up to 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Michael Gronager, PhD
Owner Ceptacle / NDGF Director, NORDUnet A/S
Jens Juels Gade 33
2100 Copenhagen E
Mobile: +45 31 62 14 01
E-mail: gronager at ceptacle.com