Cosign - #586
Conversation
|
| Directory | Self-Assigned Number |
|---|---|
XLS-0103-onchain-cosigner |
103 |
What to do
Please rename your directory to use the draft convention instead (e.g., XLS-draft-my-feature). An XLS number will be automatically assigned after a maintainer approves the PR.
This warning was automatically generated.
|
|
||
| ### 4.3. Ownership | ||
|
|
||
| **Owner:** `Owner` (the proposer). |
There was a problem hiding this comment.
I have a question: As a Proposer, I can gobble up all the Ticket ledger-objects of any target account, at the cost of the TransactionProposal ledger-object-reserve.
While this is not causing any harm to any of the parties, I'd imagine this would be frustrating to the targeted accounts.
Does the design of the Cosigner prevent this aspect?
There was a problem hiding this comment.
The Proposer doesn't actually gobble up the Tickets from creating proposals - tickets are used only when the proposed transaction is actually submitted.
There was a problem hiding this comment.
Yes, I understand. However, the TargetAccount is not consulted at the time of TransactionProposalCreate operation, which is initiated by the Proposer.
Suppose TargetAccount (TA) has created 10 tickets, which they intend to use for future Proposals. However, a Malicious-Proposer observes these available 10 tickets and decides to create 10 spurious TransactionProposal ledger-objects with the combination of
{ltTRANSACTION_PROPOSAL, indexHash(TA, 1)},
{ltTRANSACTION_PROPOSAL, indexHash(TA, 2)},
...
{ltTRANSACTION_PROPOSAL, indexHash(TA, 10)},
This prevents the Target-Account (TA) from being able to create genuine Proposals with its tickets. The lack of consent from the TA can lead to spurious TxnProposal objects on the ledger.
2 participants
High Level Overview of Change
Context of Change
Type of Change