mimblewimble team mailing list archive
-
mimblewimble team
-
Mailing list archive
-
Message #00046
Re: Compact blocks
-
To:
mimblewimble@xxxxxxxxxxxxxxxxxxx
-
From:
Merope Riddle <merope07@xxxxxxxxxxxxxx>
-
Date:
Tue, 07 Mar 2017 10:36:56 -0500
-
Feedback-id:
XAPoGc9z-Sx8Gs_73KQmjWrMmkVk7J-jsZvPxClegrEG_drDnUhFE0ZE67nPBzmTmPF0Ee7x_FNt1UQdMBn8JQ==:Ext:ProtonMail
-
In-reply-to:
<Li0BDhGo-rjyGxwu2xEPP0jHmRl1EXsBF3b269iuM9K-Oe0v-8-DtChneQlMQE7USJ9cTOn9oVWOgq3NI-hRoV-qAQQ2ZT3t_YIuf8yY85E=@protonmail.com>
-
Reply-to:
Merope Riddle <merope07@xxxxxxxxxxxxxx>
Myrtle Warren said:
> As far as I can tell, the specific construction of the output hash's preimage has not been determined. If we move forward with this mechanism, it becomes critically important that the hash covers the range proof itself. A situation where the hash resolves ambiguously should be avoided at all costs.
It should be sufficient for the output and its rangeproof to be separately committed to the chain to prevent ambiguity. Committing to rangeproofs, which are witness data and can be ignored (at a trust tradeoff), will reduce flexibility.
Follow ups
References