Add ability to blind only value in the PSET output #301

Activity

1. apoelstra commented on Oct 14, 2026

   

   apoelstra

   on Oct 14, 2026

   Last edited by apoelstra

   Member

   More actions

   Yep, concept ACK, though I'm not exactly sure what the API should look like. But we did deliberately design the consensus protocol and PSET so that this should be possible.

   👍React with 👍1Reacted by Kyrylo Riabov
2. KyrylR commented on Oct 20, 2026

   

   KyrylR

   on Oct 20, 2026

   ContributorAuthor

   More actions

   Opened #302 for the discussion of API

   The implementation there is just to prove that the concept works, I would rewrite it after we align on API itslef
3. KyrylR commented on Oct 20, 2026

   

   KyrylR

   on Oct 20, 2026

   ContributorAuthor

   More actions

   4. Opened #302 for the discussion of API
   The implementation there is just to prove that the concept works, I would rewrite it after we align on API itslef

       pub fn blind_last_with_modes<C: secp256k1_zkp::Signing, R: RngCore + CryptoRng>(
           &mut self,
           rng: &mut R,
           secp: &secp256k1_zkp::Secp256k1<C>,
           inp_txout_sec: &HashMap<usize, TxOutSecrets>,
           modes: &BTreeMap<usize, BlindingMode>,
       ) -> Result<BTreeMap<CtLocation, (AssetBlindingFactor, ValueBlindingFactor, SecretKey)>, BlindingModeError> { ... }

   #[allow(missing_docs)]
   #[derive(Debug, Clone, Copy, PartialEq, Eq)]
   pub enum BlindingMode {
       ValueOnly,
       AssetAndValue,
   }

   Above are core API choices

   Overall user could provide an empty set and the blinding will happen for both value and asset

   If user wants to value only blind, the user would need to explicitly specify so

   I was not able to avoid re-implementing the blinding (reusing blind last, or something like that)

   Will wait for your feedback