In our commitment to offering both privacy and transparency within our decentralized application, we introduce the Historical CSV Data Export feature. This functionality allows users to voluntarily export a comprehensive history of all transactions associated with their zAccount. Notably, these transactions are not linked to the public addresses of the dApp users, ensuring privacy is maintained.
Complete MASP Transaction History: Users can access a full record of their transactions, neatly compiled in a CSV file. This includes details of all activities conducted maintaining a transparent and traceable personal record.
User-Controlled Disclosure: This feature embodies our Protocol's core principle of voluntary disclosure. Users have complete control over the generation and sharing of their transaction history, empowering them to maintain privacy or provide transparency at their discretion.
Viewing Transaction History: Users can view/search their past transaction via the interface within the History tab. This action triggers the compilation of their transaction history.
Export: Users can click the export button and download transaction history in csv file.
Compliance and Reporting: For users requiring transaction history for compliance or reporting purposes, this feature provides a detailed and verifiable record without compromising privacy.
Personal Record Keeping: Users seeking to maintain personal records of their digital asset movements can utilize this feature for organized and accessible transaction history.
Note on Privacy and Security While the Historical CSV Data Export feature is designed to offer detailed transaction history, it is crucial to note that user privacy remains our paramount concern. All exported data is handled with strict privacy measures, ensuring that user identities and their association with public blockchain addresses remain confidential. Users are encouraged to safeguard their exported data with the same diligence they apply to their private keys and other sensitive information.
Panther uses Zero-Knowledge, ZK proofs to flip the issue of compliance on its head. Rather than users sharing their personal information with every institution or Protocol they interact with, Panther instead allows them for each use case (e.g. one for proof of address, one for identity, etc.) to interact only once with only a single trusted party (a Trust Provider) which can verify their information and issue a signed cryptographic attestation.
Users can then use these attestations to issue an unforgeable mathematical proof, verifiable on- and off-chain, which Service Providers can reference and verify. This indicates that the user has the attributes, credentials, or reputation needed to participate in a transaction, with selective sharing of personal data. The user can make a given Panther Reveal (carrying no personal data) or non-ZK (carrying personal data). Both would be verifiable by anyone if submitted on-chain. Furthermore, ZK Reveals are generalizable across other segments such as private identity, insurance, credit scoring, Web3 authentication and other services.
Once a Service Provider (such as a KYC verifier, Institutional DeFi service, or Web3 Protocol) receives a Panther ZK Reveal, they do not get to learn what the underlying information is, only that the proofs are valid and the users’ claims are true. Also, the Trust Providers who issued the attestations never learn anything about when or how users use those attestations when interacting with Service Providers.
Status | Entrypoint |
---|---|
In development on testnet
*Description coming soon.