What is known about a transaction, based on slate?

Development and Technical Discussion
1

Alice creates a slate, and sends it to Bob.

  • Can Alice predict the input commits based on the slate she creates?
  • Can Alice predict the output commits based on the slate she creates?
  • Can Alice predict the kernel excess at this time?

Then, Bob signs the slate and returns it to Alice.

  • Can Bob determine the input commits after processing the slate?
  • Can Bob determine the output commits after processing the slate?
  • Can Bob predict the kernel excess before the slate is finalized?

Alice finalizes the transaction and broadcasts it.

1 Like
2

If she’s the payer, then yes, they’re all hers.

If she’s the payer, then no, that is for Bob to pick.

No, that depends on the former.

Yes, assuming Alice is the payer, she would have added those to the slate.

Yes, Bob adds his output as payee and the slate would already contain Alice’s change output, if any.

Yes, at this point all input and output commitments are known.

2 Likes
3

What information is then missing from the transaction, which awaits the finalization from Alice?

4

Alice’s half of the kernel signature

1 Like
5

Is the kernel signature also known as the excess_sig? Here’s an example kernel:

         { 
            excess:08bfac59869ab046f282fde728f4ee326edba015d039484a634458122ef8df6b78,
            excess_sig:52c1dbcfb828d32cb8b6f244ef56e36e838bc5b81ee92d4e7f1be3833f1ed8b087eb55c409a27f6e8bd1424b792d8030a3ad1be477e2f781fae4f238480af0c9,
            features:{ 
               Plain:{ 
                  fee:8000000
               }
            }
         }

Do I understand correctly that the excess is known by Bob in the scenario above, but the excess_sig is not fully built until Alice finalizes?

1 Like
6

You understood correctly:-)

2 Likes
7

Very glad that people are discussing this. If/when I get a thumbs up that I’m not doing something completely stupid, I’ll post here links to some ideas that try to improve on who knows what.

1 Like