[
https://issues.apache.org/jira/browse/MILAGRO-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Matecki updated MILAGRO-15:
-------------------------------
Description:
Proposed Milagro Ecosystem Participants:
Milagro's proposed ecosystem participants can be divided into two camps: Those
that consume and derive
value from Milagro Tokens to perform a speci c action, and those that issue or
assist in the issuance of
Milagro Tokens.
For those who issue Milagro Tokens, being that they are identity based
cryptographic keys, ascertaining
identity is a critical function within the ecosystem, which further divides the
responsibility into those who
validate the unique identity of an entity petitioning to receive a Milagro
Token, and the entity that actually
issues a Milagro Token.
• People, Apps or Things (PATs) - entities that obtain Milagro Tokens to
perform various cryptographic actions within a Milagro partition.
• Identity Providers (IdPs) - an IdP is a term commonly used when describing
digital identity systems. IdP stands for Identity Provider, a party that o ers
user authentication as a service when used within the OpenID Connect ecosystem,
for example. Within Milagro, an IdP authenticates and veri es as true the
identity of the PAT that is petitioning a Distributed Trust Authority (D-TA),
the entity issuing a Milagro Token. The D-TA creates its own relationship with
an IdP on its own, and can rely on many IdPs to perform unique roles. The
OpenIDConnect protocol will serve as the basis for federation of the IdPs
capabilities to the Distributed Trust Authorities, who act as 'Relying Parties'
or RPs.
• Distributed Trust Authorities (D-TAs) - Distributed Trust Authorities are
services run by the stakeholders in a Milagro partition which issue Milagro
Tokens to People, Apps or Things who petition to obtain them. Distributed Trust
Authorities may run their own IdPs, or outsource entirely this function.
• Trusted Bitcoin (TB) Proxies - The TB proxy is con gured and administered by
the application developer or device manufacturer employed in the service of the
Milagro partition stakeholders. It is responsible for registering new devices
onto the Blockchain that are not able to download a full bitcoin client, but
also informing the new device or app which D-TA's and by extension IdP's it
will be interacting with.
was:
The whole MILAGRO project in future will be based on "blockchain-like"
architecture with few major actors and features.
Requirements:
- TBD
/Placeholder/
> MILAGRO ecosystem architecture
> -------------------------------
>
> Key: MILAGRO-15
> URL: https://issues.apache.org/jira/browse/MILAGRO-15
> Project: Milagro
> Issue Type: New Feature
> Reporter: Tom Matecki
>
> Proposed Milagro Ecosystem Participants:
> Milagro's proposed ecosystem participants can be divided into two camps:
> Those that consume and derive
> value from Milagro Tokens to perform a speci c action, and those that issue
> or assist in the issuance of
> Milagro Tokens.
> For those who issue Milagro Tokens, being that they are identity based
> cryptographic keys, ascertaining
> identity is a critical function within the ecosystem, which further divides
> the responsibility into those who
> validate the unique identity of an entity petitioning to receive a Milagro
> Token, and the entity that actually
> issues a Milagro Token.
> • People, Apps or Things (PATs) - entities that obtain Milagro Tokens to
> perform various cryptographic actions within a Milagro partition.
> • Identity Providers (IdPs) - an IdP is a term commonly used when describing
> digital identity systems. IdP stands for Identity Provider, a party that
> o ers user authentication as a service when used within the OpenID Connect
> ecosystem, for example. Within Milagro, an IdP authenticates and veri es as
> true the identity of the PAT that is petitioning a Distributed Trust
> Authority (D-TA), the entity issuing a Milagro Token. The D-TA creates its
> own relationship with an IdP on its own, and can rely on many IdPs to perform
> unique roles. The OpenIDConnect protocol will serve as the basis for
> federation of the IdPs capabilities to the Distributed Trust Authorities, who
> act as 'Relying Parties' or RPs.
> • Distributed Trust Authorities (D-TAs) - Distributed Trust Authorities are
> services run by the stakeholders in a Milagro partition which issue Milagro
> Tokens to People, Apps or Things who petition to obtain them. Distributed
> Trust Authorities may run their own IdPs, or outsource entirely this function.
> • Trusted Bitcoin (TB) Proxies - The TB proxy is con gured and administered
> by the application developer or device manufacturer employed in the service
> of the Milagro partition stakeholders. It is responsible for registering new
> devices onto the Blockchain that are not able to download a full bitcoin
> client, but also informing the new device or app which D-TA's and by
> extension IdP's it will be interacting with.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
