Blockchain Freedom,
Cloud-Like Simplicity
It just needs to do its job: enable decentralized applications.
while fully preserving data privacy.
Data-Rich Apps, Privacy-Rich Solutions
The crux of most products and services lies in utilizing a wealth of data - business proprietary algorithms, business logic, customer and partner details, and customer personal information (PII). But this bounty of data is not without risks.
This is where Seneca steps in. Our unique environment allows you to fully leverage private data in your applications without compromising its security - it remains exclusively with the owner. This means you can create data-rich applications while maintaining privacy-rich solutions.
Build ZK Environments as Easy as Standing up Instances:
- Built-in cloud integration
- Work directly with raw data (while preserving privacy)
- Personalize products & services
- Privacy and user agency enforced by default
ZK Environments: Key Features
Build a Hyper-Personalized, Trusted dApps
Data Validation Tools
For use in Smart Contracts, ensure data is accurate and verified with programmatically stacked certificates.
Connect SDK to your dApp
All the tools to build directly on Seneca or build on other environments and connect with a few lines of code.
Start
Building
Today
Q&A
The goal is agency: a user can store data in any method that suits their business or use case the best. In many cases, information should be private. But privacy of the past has meant ‘trust us, we won’t do anything bad with your data.’ On Seneca, we are removing the need of trust from the system.
Smart contracts on Seneca can interact directly with zero knowledge proofs of private data from private data sources or from the public blockchain state.
Users can submit data in predefined credential and zero-knowledge structures to smart contracts, in order to enable easy processing of their private data.
We are also working on truly private, confidential and privacy-preserving on-chain smart contracts.
We have the benefit of watching others build for the past half-dozen years, see what has and hasn’t worked, and taken the best ideas to build onto our platform.
Seneca is written in Rust, by default a very fast programming language, and in the Substrate framework, which is also built for speed and high transaction throughput.
On top of that Seneca is implementing adaptive state and network sharding and on-chain ZSTARK rollups to achieve even higher TPS numbers.
There are multiple components that allow Seneca to include private, trusted data in blockchain transactions:
- Verifiable credentials allow you to prove your ownership of structured private data. Seneca hasn’t built typical VCs, rather a rich-data format that is more flexible and programmable.
- Zero knowledge proofs enable you to share certain details about your identity without revealing the underlying data.
- Private computing lets you interact with others and use your private data without ever revealing the data to them. This could exist in a private ledger (such as on your computer), in the cloud or any other environment useful or necessary to build the application or function.
All user data is privately stored as verifiable credentials in user-owned private ledgers. This data is easily accessible within the Seneca ecosystem through wallets, dApps and smart contracts.
To exchange data with Web2 legacy systems (like HTTP APIs) and other Web3 ecosystems (EVM, Polkadot, Cosmos etc…) we are building specialized adapters that let you pull Seneca-issued data into e.g. EVM smart contracts or push data from external sources e.g. HTTP POST requests into the Seneca blockchain and the users’ private ledgers.
Seneca has big plans for what is possible with consensus. Right now we are running a permissioned testnet, but are working on a novel consensus called Proof of Algorithmically Stacked Reputation for our permissionless mainnet. This is another way to say, the more trusted a person is, the more they are… trusted. Can a system trust someone without sharing any of their personal information? We think yes. Compared to traditional consensus algorithms, PoASR is environmentally friendly, consumes little energy, has a very low financial barrier of entry and still enables fully decentralized consensus. Stay tuned for more here
We are building adapters that allow an exchange of the Seneca-native, DID-enabled credentials, zero-knowledge proofs, and credentialed data between Seneca, private data storage systems, Web2 APIs, and many popular Web3 blockchains.
Any meaningful interaction between individuals and/or organizations requires private data to be shared e.g. identity information, authentication data, payments, and many others.
Right now any data submitted with a blockchain transaction (e.g. on Ethereum) is posted publicly on-chain for everyone to see. This greatly limits the actual use cases and real-world applications of blockchains.
Seneca allows you to “layer” meaningful, private data around blockchain transactions without revealing the underlying data to the entire world.
We believe that data should always be user-owned and that data owners should have as much agency and control over their data as possible. We also think that data should always be encrypted at rest and be protected from theft and accidental loss.
We have already launched our publicly available testnet ZENO, the first Seneca-native wallet (Vault+) and Mantis, a set of tools to help you create credential schemas. We launched a number of interoperability adapters, and there are already nearly a dozen early apps building off of our tools.
Seneca is the mainnet blockchain. Zeno is Seneca’s testnet. SERV is the company with a mission to build tools and resources to support Seneca and the growing community.
