Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Full Lifecycle Testing for Real Apps on Polkadot: Developing Fly Wallet for an FAA Trusted Issuer for Credentials in a Self Sovereign Identity Wallet.
Self-Sovereign Identity Wallet for the Substrate Ecosystem (Android and iOS), a bridge for institutional traditional businesses and governments, to use and rely on web3 technology.
Developed and Proposed by Peranto and Hope Clary Media LLC - establishing Peranto SSI North America in Wyoming, USA
November, 2025
The Aura Wallet is Public Infrastructure with Open- Source Code for Decentralized Identity on Polkadot. We believe technology matters and it is transparency that is required in order to move forward in the Digital Identity space. Our goal is to showcase how this technology can help humanity, through real world needs and fixing real problems.
Peranto is an ecosystem for the transition to a circular economy playground. To achieve this, True Self-Sovereign Identities and its applications must flourish to democratize and make Web3 accessible technologies available for system upgrades, without harm to humanity in the process.
Use cases for identity are boring and endless, and are part of everyday critical operations in Governments, Institutions, Businesses, etc. Usually, the security part is delegated to the server side, the business logic side, which carries problems to the real true owners of their data.
Our Polkadot Web3 ecosystem, powered by the Polkadot SDK, puts the security on the server and client side; this means our approach to a Digital Identity through the Aura SSI Wallet will provide a universal wallet for substrate ecosystems. To empower the $DOT economy our wallet will be using Asset Hub for all payments and as we grow through partnerships we will be bringing additional business models through our verticals onto Polkadot.
The current core team is made up of 3 people from the America’s with a PBA Alumni as our subject matter expert in the Technical Architect leadership role. All agents working on this project are located in different countries of the America’s: United States 2, Mexico 2, and Chile 2, all of us with different experiences and expert backgrounds. All of our skills are needed for the achievement of the current Development and Deployment of this proposal, at precise stages in its lifecycle.
We request the Polkadot Treasury to fund the Development and Real-World Deployment Testing with code fixes of the 2 use-cases for the Aura Wallet’s open-source core as an essential public infrastructure for the Polkadot ecosystem, with the collaboration of our trusted entities and trusted business partners. With World Wide Web Consortium (W3C) standards for DIDs and verifiable credentials currently supported by Kilt Parachain with Polkadot Infrastructure. We will be showing how Web3 comes to life with practicality and problem-solving, as our soul mission.
Our current Roadmap Vertical of Stakeholders and Collaborators:
Aura Wallet fills this gap. Our trusted entities, allies for testing and adoption:
- FlyGateway (USA) - A flight school seeking FAA-aligned digital credentials for pilots and curricular verification approval (acceptance).
Our full cycle production test use case will be conducted with FlyGateway in the United States and follow Federal Aviation Administration (FAA) regulations and standard practices. We hope that through this use case of testing and coding we can bring forth a product that is seamless for the FAA Regulatory Facilitators and the agency (government body).
- Federación de Andinismo de Chile (FEACH) - A national sports federation with 5,000+ members and 50+ clubs, ready to issue verifiable certifications for mountain guides and high-performance athletes.
- Polkadot Ambassador Fellowship (PAF) - A global network needing to vouch for contributions to governance and community building, while preserving privacy and accountability on General Data Protection Regulations (GDPR) metrics.
What Problems Are We Solving?
Sep V0 Peranto Ci.Go Beta Program: Digital Transformation for FlyAdvanced
Sustainability Goals:
Our team is focused on financial sustainability for ourselves and for the health of Polkadot, we will be doing this through the initial ask for these funds listed, in addition to seeking out other partners after this initial kick-off phase. Our current focus is listed below for the kick-off phase:
- Regulatory Precedent: First SSI use case in the U.S. through FAA Regulatory Agent FlyGateway. Initial kick off goal with proven tech and data in hand is to onboard 44 License Flight Schools.
- Chilean Mountaineers Product Licensing.
Team Peranto SSI NA, LLC Team:
- Edgar – Founder & Lead Developer: Architecture, open-source development, KILT integration, long-term maintenance.
- Hope Goodman – Product Representative, BD Representative (USA) and Liaison with FlyAdvanced, pilot testing, FAA alignment, product documentation.
- Mike Devine - Business Development and FlyAdvanced Director of Flight Logistics, FAA compliant www.flyadvanced.com
Core Developing Team
- Edgar Salinas - Founder Peranto
- Dev 1 - To be determined
- Dev 2 - To be determined
Team Web3Chile (Peranto FEACH) Team
- Edgar – Founder & Lead Developer: Architecture, open-source development, KILT integration, long-term maintenance.
- Francisco Albornoz – Community Coordinator (Chile): Engagement with FEACH, mountaineer testing, federation standards, product documentation.
- Carolina Palma - Mountaineer expert and FEACH member
- César Escobedo - Product tester for Chile and Mexico
❌ Not Funded by OpenGov (Covered by Partners)
- Full iOS app development (beyond evaluation/testing)
- Branding versions of (Fly Wallet, Andino Wallet)
- Private backend services or infrastructure deployments for specific business cases
- FAA certification costs
- Post-launch support or Service Level Agreements
Seeking OpenGov Support Financially for:
Infrastructure
- Tools, 1 Mac Pro, 1 Android Tablet and 1 iPadOS
- Tester Tools to be useBuilding of 2 Customized SSI Wallet Applications, Android and iOS Apple, for use by non-technical users (pilots, mountaineers)
- Equipment supporat FlyGateway: 2 Android Tablets, 2 iPadOS, 2 Android Phones & 2 iPhones
- Deployment and real-world testing costs
Our commitment is to deliver a wallet for SSI, with Apache 2.0 licensing, with the following characteristics:
- Compliance with regulated environments (e.g., FAA)
- Capable of secure cryptographic presentation
- Extended communication capabilities (NFC, QR, WiFi Connect)
- Supporting $DOT, $USDC (initial tokens), or any native or wrapped token from the Substrate ecosystem (long term)
- Geo Location
- Verifiable Credentials management
- Secure key management through keychain | keystore
- Data Storage within the wallet custody to user only
- Signatory Software - user-flows with substrate crypto primitives
- API configuration within the wallet and the proof of service
- Public GitHub repo, modular architecture, basic DID management (Authentication, Encryption)
- One potential public use case for the Polkadot Ambassador Fellowship (demonstrate a verifiable experience for the agents in the field)
- Stable release of open source for Aura SSI Wallet, full documentation, final UX report.
General Communication Schema
Figure 1. Intended Aura Wallet basic communication flow for API and P2P framework
Figure1 shows the wallet methods for sharing archives and data, being cloud services the last ones to be considered for data redundancy. A feature for any SSI Wallet should be P2P data redundancy, share big files through WiFi connect with the person in front of you, verify the data against the signed metadata, and verify the hash on the blockchain in case it’s timestamped there as well, or communicate with a trusted entity on a secure API for diverse validating services.
Based on real-world demand with our trusted entities stakeholders, built for technology reusability, and designed for global impact, we are focused on turning SSI from theory into practice for Polkadot. This is not a single custom app—it is “Public Infrastructure for Identity on Polkadot”.
Operation Method:
- Multisig 3/3
- Milestones Payments
- Each milestone should begin with an allocation budget for its completion
The signers must evaluate the available resources and Work in Process (WIP); if it fits, they will release Kick off Funding, Contingency, Milestone 1 & Hardware equipment funding required. After Phase 1 Milestone is met a release of Salary Funds along with next Milestone funding should be released. This will allow the team to budget and keep going as Milestones are further met in the development and testing process of the project achieving delivery and documentation.
- The multisig account will have restricted access to the Contingency Drawer after the estimated runway, having two possibilities.
- The team delivered and accomplished all milestones, and the team gets equally rewarded with shares of this drawer automatically distributed into all core connected wallets 3/3, as a bonus.
- If the team didn’t deliver by the estimated runway date. The signers will assess the situation and, based on the viability of the delivery, the drawer will be used to finish the job, or these remaining funds will be returned to the treasury.
Economic Considerations
The team is decentralized, and three countries are involved (Chile, Mexico, and the United States) average income is different, so the living and operational costs vary.
Other Considerations
- Why We Prioritize DIDs & Verifiable Credentials Over Proof of Personhood: Proof of Personhood (PoP) aims to prove that a digital identity corresponds to a unique human being, often for use cases like one-person-one-vote governance or sybil-resistant airdrops. However, PoP does not verify who that person is, nor does it convey any regulated, verifiable attributes—such as a pilot’s license, medical certification, or flight hours.
In contrast, Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs)—as standardized by the W3C—allow trusted issuers (like FlyGateway, acting under FAA oversight) to cryptographically attest to specific, legally relevant facts about an individual. These include:
“This person holds a valid Private Pilot License (PPL),”
“This pilot has a current Class II Medical Certificate,”
“This graduate completed all required flight exams.”
For regulated industries—especially aviation, where compliance, auditability, and legal liability are paramount—uniqueness alone is insufficient. Authorities like the FAA need to verify credentials, not just personhood.
Therefore, our project starts with DIDs and Verifiable Credentials because they:
- Meet real-world regulatory requirements (FAA, KYC, AML)
- Enable selective disclosure (e.g., show PPL without revealing full identity)
- Support revocation and updates (critical for suspended licenses)*
- Are already interoperable with Polkadot via KILT Protocol
- Provide a foundation upon which PoP-like mechanisms can be added—if and when needed.
In short: We need to prove compliance through already established KYC funnels for regulated credentials. We need to prove they are “I am a Licensed Pilot or I have Passed Mountaineer training.” These Credentials are Issued and not proven, just as a human exists.
That’s why DIDs and Verifiable Credentials are the right starting point—and the right public good—for Polkadot’s identity ecosystem.
Less trust, more truth. Dapps, not chains.
🔗 Resources
- Live Signature Document Credential Verifier: https://beta.peranto.app/verify
- Aura SSI Working PoC Demo for Logbooks and Digital Signatures: https://www.youtube.com/watch?v=eOGxZ8nWW3w
- Visual Pitch Deck (PDF): https://docs.google.com/presentation/d/1L16EYEhaEhrldNUodpl8bIzeQUHM2Cmy/edit?usp=sharing&ouid=110353380380132837700&rtpof=true&sd=true
- Technical SOW (FlyAdvanced Beta Program): https://docs.google.com/document/d/1O5_mdxHO4sGH_qXp9N4ojbmgsSt-dDiUPMykKD2BI7g/edit?usp=sharing
Thank you for your time and vision.
We’re not just building tech.
We’re building trust — on Polkadot.
— Edgar Salinas
Founder, Peranto SSI NA, LLC
México | Miami | Wyoming | Delaware | Pensylvania
Comments (1)




Hello Edgar, hello Peranto team,
I appreciate the clarity, the real-world use case, and the fact that this is a production deployment rather than a conceptual experiment.
I do have one important question regarding the underlying infrastructure:
Given the recent announcement from the KILT Foundation (stepping down, lack of operational funding, and the potential sunset of the protocol if no successor is found by November 18), could you clarify how this affects your technical roadmap for Fly Wallet and FlyGateway?