Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add participant ID as part of key to stored private transaction context data #117
Mostly as a fix for self-sending invoices (but also for future needs where there are multiple parties in a transaction,) this adds a participant ID as a part of the key for stored private transaction context data. The slate id on its own isn't enough, as a party can act in multiple participant roles during a transaction.
Note there's currently an assumption throughout the code that participant 0 means 'party putting in funds' and 1 means 'party receiving funds'. This will need to be factored out in future and made more flexible.