Skip to content
This repository was archived by the owner on Jun 13, 2024. It is now read-only.
This repository was archived by the owner on Jun 13, 2024. It is now read-only.

Figure out how to handle when a clearing firm's private key is stolen #9

@benthayer

Description

@benthayer

Ex: Clearing Firm 1 gets their private key stolen.
Clearing Firm 1 starts issuing new bonds and moving traders' bonds to new public keys.

We can have a special type of consensus algorithm that allows the network to agree that Clearing Firm 1 is now a bad actor and is not to be trusted.

This would need to happen relatively quickly so all the transactions can be undone and the network can continue to operate. We may need the transaction processor to go back and restore the history to a previous state. We could also look into setting time delays on any clearing actions so that the network has time to determine that Clearing Firm 1 is now hostile and is not to be trusted. This would be okay since any clearing actions would generally take time to perform on the business/legal side.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions