Which Problem Does Reddcoin Solve?

(as requested to cross-post from reddit)

Hey Reddheads

This is more aimed at the Dev team:

We have seen some of the features and benefits of the proposed Redd-ID.

What we’d really like is a simple explanation of ‘what problem does Redd-ID’ solve?

The Identity and Access Management (IAM) Market is estimated to be worth $10Billion By 2018!


As time goes on, our writers encounter more and more companies facing Digital Identity & Access Management issues - and the solutions are not as easy in crypto as they are in what we refer to as the ‘old world’. This is due to a lack of solutions but there are companies working with blockchain tech ie: https://trustatom.com/

We would like to be able to converse better about the Redd-ID solution but we cannot find reference material.

Have we slept through the release of the Redd-ID whitepaper or is this yet to be released? Is Redd-ID designed to have a use-case for real-life problems? Is Redd-ID a small component of Social-X, designed to solve a problem for Social-X only - or is it a big reason to use reddcoin? I guess to rephrase: Can Redd-ID be used as a Identity Management & Access Solution for outside of Social-X? Real world example: We intend on launching our Portfolio Manager by March. Could we use Redd-ID as an option for Identity Management & Access?

Thanks for your time in reading this.

Techemy said:

Have we slept through the release of the Redd-ID whitepaper or is this yet to be released? Is Redd-ID designed to have a use-case for real-life problems?

This is an important discussion one should read and have.

If we could attach a Redd-ID to real usage situations like other services outside or countries that would be an splendid goal. In my opinion. Allowing individuals to make trustworthy transactions on the internet and down the line the so called smart contracts. Providing even more authenticity to each end user. Bringing social and real life trust into the online realm.

Instead of signing with facebook or google accounts you would sign with This cryptographic ID. Has these Id’s are associated with timestamps and verified by a network of peers it is very difficult to pose an artificial way to defeat the all project. (I say difficult because it is possible to fake social number Id’s by making a trail of fake transactions and interactions on it of more than 30 years. )

For what I know the Redd-ID is part of SocialX and is more of a link between of your online social media foot print. It is not dificult to link but less more authentic the more engaging accounts will be a good analogy of that. Privacy is still accounted for, since your accounts could be not accessed publicly trough each system settings. That is Important for each individual.

It will work like an aggregation of your online accounts and signed to a encription key. It is not news but What I didn’t know is that this was a nice market of 10Bn$ by 2018 :smiley:

Edit: Please read this post to understand and bring other points to conversation


Oliver Thank you for this reply and link in the bottom.

You have offered some interesting insights about further mechanics of the Redd-ID.
However I’d like to hear from the Dev’s if this system will have an API so that infact it can become another log-in option. Just like this forum offered to sign in via several social platforms.

I can see the use case now "Sign into your (any service here) using facebook, twitter, Disqus or ‘Redd-ID (preferred).
with a note stating ** Redd-ID is preferred on this website because it is the world’s first Decentralized Identity system based on Mathematics and requires less trust then centralized option’ etc etc

There would be a the hurdle of on-boarding. Redd-ID will require reddcoins to power. Which is great but some teen who just wants to play some new flavor of bejeweled will have to Procure Reddcoin (probably first bitcoin), then register.
With a good ‘user-story’ built into the user-experience, this can be aided but just stating what hurdles this would realistically see.

1 Like

Techemy on Second thought, for critical services, like say my tax-website in NZ, I have to register a ‘Real-ID’ which is a pain in the arse. All citizens must have one to do their taxes online and there is a fee to set it up.

Realistically, if organizations wanted this superior identity system, they could literally just charge $5 via credit-card during the ID set-up process. Like a value-added reseller.
The Organization would then effectively buy the reddcoins, offer their own user-interface for sign-up, pay the network reddcoin fees, and the user would end up in the Redd-ID/Reddcoin portal but the organization will have what they wanted too - which is their users registered on their preferred system - the Redd-ID
If they really wanted to remove the hurdles and funnel their users through as seamlessly as possible to use their preferred ID system.

Just thinking out-loud.

I’d like to see a 1 page of how Identity Management sucks today and the Problem that Redd-ID is solving. I’ve been viewing this as a ‘unexpected’ or ‘chance’ invention (derived from the Reddcoin specific Social-X) which turns out to have a stand-alone use-case, But I might be wrong if this system does not have an ‘Unfair Advantage’

Techemy Why don’t we start with a list of problems first?

1 Like

Good point

I will do some research and come back

1 Like

Techemy I will as well. IAM is a huge industry and covers a lot of areas. The one area which is the most relevant to Social X is SSO so let’s all do some research on it and compile its limitations.

I’ll provide more technical information on Social X in due course.

1 Like

laudney Sounds great - glad you understand this is an area Redd-ID can touch on.

Here’s an excellent paper for reference material: http://arxiv.org/ftp/arxiv/papers/1101/1101.0427.pdf

Laudney you may know some of the below but I’m putting it here for anybody else interested in this train of thought.

The 4 basics of IDM:

  1. a directory of the personal data the system uses to define individual users (think of it as an ID repository);
  2. a set of tools for adding, modifying and deleting that data (the access lifecycle management stuff);
  3. a system that regulates user access (enforcement of security policies and access privileges);
  4. and an auditing and reporting system (so you’ll have a way to verify what’s actually been happening on your system).

From here evolved the Federated IDM:

Federation lets you share digital IDs with trusted partners. It’s an authentication-sharing mechanism designed to allow users to employ the same user name, password or other ID to gain access to more than one network. commonly referred to as “single sign-on.” A single sign-on standard lets people who verify their identity on one network or website carry over that authenticated status when moving to another. The model works only among cooperating organizations—known as trusted partners—that essentially vouch for each other’s users.

So a big consideration/challenge for Redd-ID would be to become trusted to the point where other platforms are happy to integrate.

The federated model relies on the security assertion markup language specification, (SAML)
I’m not from a technical discipline so I wouldn’t be able to describe the ‘problems’ of SAML which Redd-ID could possibly solve. Im a project manager so can understand on a design & infrastructure level what the pitfalls in UI/compliance may be in existing IAM frameworks.

Here is the current considerations for any IAM system:

Access management
Features, such as authentication, authorization, trust and security auditing, are part and parcel of the top ID management systems.

An identifier employed by the user to gain access to a network. ie - user’s password, public key infrastructure (PKI) certificate or in a physical environment: biometric information (fingerprint, retinal scan).

The process of removing an identity from an ID repository and terminating access privileges.

Digital identity
Description of the user and his/her/its access privileges. (“Its” because an endpoint, such as a laptop or a cell phone, can have a digital identity.)

The set of attributes that specify the access rights and privileges of an authenticated security principal.

Identity lifecycle management
Buzz phrase. Like access lifecycle management. It refers to the entire set of processes and technologies for maintaining and updating digital identities. Identity lifecycle management includes identity synchronization, provisioning, de-provisioning, and the ongoing management of user attributes, credentials and entitlements.

Identity synchronization
The process of ensuring that multiple identity stores—say, the result of an acquisition—contain consistent data for a given digital ID.

Password reset
Common for all ID management systems - allows users to re-establish their own passwords, relieving the administrators of the job and cutting support calls. The reset application is done by a set of questions to verify the user’s identity.

The process of creating identities, defining their access privileges and adding them to an ID repository.

Security principal
A digital identity with one or more credentials that can be authenticated and authorized to interact with the network.

Is there anything missed?

So basically a good place to start would be to go over the above IAM considerations/facets and identify the problems with each component + which one’s and how Red-ID solves.