Sharding Abaddon's Soul

Important

• Abaddon's soul is never committed to the database. It is sharded, and discarded. At no stage is it compromised.

Event Flow

1. Invitations

Abaddon the Despoiler selects a list of his best reavers from his Chaos Army.

Abaddon hits confirm and the invitations send.

What does this do?

• Writes a secret_root object to the database, references the author as Abaddon with his ID
• Links together all relevant information for any specific secret sharing process
• Each receives a secret_invite that references the rootId

Therefore

• Abaddon is not restricted to just sharding his SSB key, he can shard anything he likes.
• Abaddon can still send out more invitations if he likes.

All of Abaddon's different secret sharing root events can be summoned using:

api.secrets.all.get(callback)

Invites can be viewed through the API and a FlumeView... something along the lines of:

api.secrets.invites.get(rootId, callback)

2. Responses

Each ally recieves a secret_invite and, if they're a dependable evil ally, they can send back a secret_response to either accept or reject the trust that Abaddon has placed in them. If they're not a regular scuttler, its likely they might not respond in time before Abaddon makes his final decision to share his soul.

What does this do?

• A response writes a secret_response that indicates whether they accepted the invite or not
• References the rootId so can be easily filtered through the API / a FlumeView

api.secrets.responses.get(rootId, callback)

3. Participants

Abaddon decides its time to proceed with his super evil plan and shard his soul...

I now have enough super evil allies. I can split my soul into pieces and give them each a piece so I can become immortal. Muhahahahaaa...

What does this do?

• Displays a list of all invited folk
• Shows a tick and a checkbox next to those that responded and accepted Abaddon's invite.
• Shows a cross next to those that rejected his invite.
• Shows a circle (or something) next to those who have yet to respond.

Therefore

• Abaddon can now select the ones he really trusts, his inner circle.
• Abaddon can now set a quorum of cosigners required to combine his sharded soul and make him mortal again.
• Abaddon can now select whether he wants the final cosigners to know who eachother are. Does he trust them enough not to conspire against his evil plans for immortality?
• Abaddon then hits send, his soul is sharded as he screams into the abyss.

• Generates a secret_participants event which includes:

  • IDs of the final cosigners
  • The required number of cosigners to release his secret

• If Abaddon enabled it, those within that group of final cosigners can now see who eachother are.

• Immediately triggers the Secrets event

  api.secrets.participants.get(rootId, callback)
  

Questions

• Does having a secretive or non-secretive sharding require two different types of event? Or is it just a boolean flag? Needs clarification as it depends how the data is scuttled...

4. Secrets

Immediately after Abaddon has confirmed the sharding of his soul, and the participants log has been created, each member of the participants will be gossiped a private message detailing their own shard.

What does this do?

• Each trustee receives a shard of Abaddon's soul.

api.secrets.pieces.get(callback)

// Needs more thought... Should the participants know the rootId? Do they need to?

Note:

• secret_invite and secret_response looks a lot like Patchbay's ssb-chess: chess_invite and chess_accept.
• Can't this be abstracted?
• Would it not make sense to have a more simple invite model that can have a type. This could then be used in both modules.