The Pocket app is a digital wallet that grants lifelong learners ownership over their learning records. We use blockchain technology to link a single identity to verifiable credentials, which are stored in the learner’s digital wallet. These credentials represent identity, courses, tests and assessments, coursework links and artifacts, skill records, or any sort of learner accomplishment that can be digitized. Pocket displays these credentials and their associated metadata and acts as an identity proof application so that the learner can always demonstrate that they are the owner of their Pocket records. The Pocket platform is an enterprise level set of services and applications that can be accessed or integrated by educational and professional institutions with their existing systems, like SIS, LMS, HR, and other administrative programs.
Pocket creates a secure identity for the learner and for each institution they’re affiliated with that is part of the Pocket network. Learners are able to access and receive secure, verified credentials from their institutions, and choose how they want to share those credentials with other educational and professional organizations. The Pocket app is currently available for iOS and Android. Administrators and program coordinators can have authenticated access to the Pocket platform via a web app.
Pocket can store any credential that educational and professional organizations choose to issue. For AU, we currently support:
The credentials added to a student’s Pocket must come from a Pocket issuance server that an institution controls and manages. Pocket integrates directly with an institution’s SIS and LMS platform to issue course enrollment, course completion, and grade credentials. The Pocket platform also models institutional structures and objects, to provide a richer experience when reviewing records. In the future, Pocket will expand to issue more lightly-weighted credentials in the form of endorsements for self-claimed credentials. Pocket uses the Hyperledger Indy blockchain platform for creating learner’s identities. Indy provides strong security guarantees; Private data is exchanged over peer-to-peer encrypted connections instead of being written on the ledger. Every relationship has a unique id that ensures that the data cannot pass from one relationship to another. Indy ensures that individuals and institutions always know who they are interacting with. This combination of privacy and trust provides a solution for digital credentials that preserves privacy.
Pocket currently operates using the Hyperledger Indy blockchain platform. Indy provides strong security guarantees; private data is exchanged over peer-to-peer encrypted connections instead of being written on the ledger. Additionally, every relationship has a unique id that ensures that the data cannot pass from one relationship to another. Indy ensures that individuals and institutions always know who they are dealing with. This combination of privacy and trust provides a solution for digital credentials that preserves privacy. Additionally, all private and protected information is stored only in the form of credentials issued to a user’s private wallet, and remains encrypted and secure on their mobile device.
Pocket is completely portable, and can be utilized by any platform that trusts institutions issuing Pocket identities. Pocket identities are secure and non-hackable, and can potentially provide access to any data the owner wants to share. Other Pocket use cases include:
Pocket owners can elect to share any of their credentials to any Pocket network member where they have any formal affiliation, either currently or in the past. A second-party institution’s access to a learner’s first-party institution data will be entirely governed by the learner, as they own the access to their credentials. Only the learner can grant access to records Institution A issues to Institution B. This is managed both when first creating identities for these institutions, and then when any data is actually transferred deliberately by the learner from one institution to another. Pocket enforces all FERPA requirements for educational record privacy, and learners must opt-in and consent to any record sharing.
Authentication and access to all Pocket credential data is stored on a blockchain in a Hyperledger Indy instance, which Pocket maintains and operates. Credentials themselves are stored in the user’s secure and encrypted wallet on their smartphone. Additional metadata around credentials, like large attachments, are stored on the cloud service designated by the user in an encrypted format and can only be accessed via access keys. Only a single Pocket app can be active on a learner’s phone at any given time, and only that Pocket app has access to the ledger chains associated with that identity.
Pocket records will remain accessible to students for as long as they have access to the Pocket wallet. Pocket’s long-term goal is to provide learners their professional and educational credentials long into their career.
Pocket identity and blockchain technology are based on the Hyperledger Indy standard, as specified by the Sovrin network. Pocket is being developed to be interoperable with multiple evolving standards and platforms as well, including but not limited to IMS CLR, Open Badges, and OMS RDS standards.
Pocket will support the ability to backup and restore the app from a cloud-based backup, and the ability to transfer the app and its data from device to device. As of this current FAQ version, this feature has not yet been implemented. Currently, the nature of blockchain requires users to record a 12 word seed phrase. The Pocket team knows this is difficult to request from students unfamiliar with blockchain security. We are actively working on designing a better experience for managing this seed phrase requirement.
In order for an institution or other organization to become a member of the Pocket Network / TLN, and be able to issue trusted and verified credentials to learners, they will need to be a vetted and established institution with existing systems to ensure their records are accurate and reflective of their learners’ actual records. Additionally, the Pocket network will set up controls and rules that govern transactions between and among member institutions that they can control and vet. Any given institution can manage their own list of trusted network members.
Should they owe any money to the college itself, when some colleges depend upon those collected fees for their operating budgets? Although Pocket course credentials contain all the information (if not more!) that a traditional transcript contains, it isn’t intended to be a transcript. Instead, it replaces the role of a traditional transcript. It is a paradigm shift where learners own and control access to all of their learning records. Streamlining and automating this process results in a reduction in overhead time and effort, which go a long way in compensating for any revenue loss. Pocket has not yet proposed any other means of monetization, as Pocket’s philosophy is to be as free and accessible to learners as possible.
By granting lifelong learners agency over their records, students with limited time and income will no longer need to spend resources providing institutions with paper transcripts or other traditional forms of proof. They will also be able to transport their credits more easily across multiple institutions during their learning journey. Additionally, Pocket provides proof of achievement regardless of the attainment of a degree. Finally, although Pocket is currently designed as a smartphone application only, we will develop web apps, so that learners without easy access to smartphones or wireless connections can also use Pocket.
Currently we expect that a community college would only have to provide access to existing LMS and SIS systems, and that the Pocket Enterprise team will implement all integrations. If the school wishes to integrate the Pocket workflow into any existing applications (e.g. logging in with the Pocket Identity, accessing any credit recognition and eligibility service, etc.), Pocket will provide SDKs and technical support for those efforts.
We plan for Pocket to be able to service selected ASU students in a limited Beta in spring of 2023, and a full open Beta roll out for ASU Fall 2023. This roadmap is subject to change.
The goal is to be interoperable with all major standards and platforms that have formats for all types of verifiable credentials. The Pocket Enterprise team is focused on ranking and prioritizing these platforms. That said, the initial focus will be credential standards like OSN that ASU as a technology community is already engaged with; we’ll also focus on the other major SIS and LMS platforms, WC3 standards, IMS CLR and Open Badges, Badgr, etc. In addition to standard learning credentials, Pocket will recognize and issue milestones, degrees, diplomas, certifications and licenses, as well as assessment scores. Pocket will also be able to manage and share Portfolio content and any other achievement or award issued by a verified institution or individual on behalf of the institution. This might include honors awards, letters of recommendation, scholarships and fellowship awards. Etc. The final vision of Pocket is that such credentials are not limited to educational and training institutions, but also include professional roles and titles, and credentials or assessments gained from professional organizations, so as to truly reflect the accumulated verified accomplishments of lifelong learning.
Pocket has three major components, the Mobile application and wallet, the Pocket Core server, which manages identity and issuance, and finally Pocket Strata, which can be accessed via an administrative console. Strata is the data and business intelligence layer of Pocket, residing outside of the Pocket Core services that simply issue and store credentials. All credential and institutional metadata tables, as well as business rules and issuance logic reside in Pocket Strata. Strata is also Pocket’s integration layer with an educational institution’s SIS and LMS implementations and data, as well as integrations with other 3rd parties such as Badgr.
Can’t find the anwsers you’re looking for? Please chat to our friendly team.