Define who can act
Connect users and application workloads to the organization and the authority they have been granted.
AN LF DECENTRALIZED TRUST LAB
Shared blockchain networks.Defined boundaries.
A shared network
A view shaped by policyTEGARIS / APPLICATION PRIVACY
Application privacy for a world that builds together. Tegaris brings participant access, contract permissions and data visibility all into one policy control plane for shared EVM blockchain networks.
Open source · Apache 2.0 · Application-layer privacy
IDENTITY / POLICY / VISIBILITYOPEN TECHNOLOGY. SHARED PROGRESS.
THE PROJECT
Participation should not mean unrestricted access.
Shared blockchain infrastructure links organizations. Their decentralized applications themselves still require their own individual permissions, responsibilities and views of the data. Tegaris makes those boundaries explicit at the application layer, bringing identity, policy and runtime enforcement into a single connected workflow.
Control what is visible
Treat the permission to perform an operation and the permission to see the results of that operation as two separate decisions.
Make decisions explainable
Connect an access decision to the effective policy, the participant context and the inputs that went into it.
EXPLORE THE PRIVACY MODEL
One record.
Different permitted views.
A participant's identity and their permissions will dictate what an application is able to reveal. Switch to see a simple example of a settlement.
VIEW AS
Illustrative policy scenario using synthetic data. This is an explanation of the model, not a live network or product console.
APPLICATION RESPONSETX / 0042
Settlement record
VisibleAmount250,000DEMO UNITS
Sending participantParticipant A
Receiving participantParticipant C
Business referenceINV-2048
Disclosure purposeSettlement review
Example policysettlement-view / v1
A view within your authority
Participant A is a party to this record. The example policy allows access to its settlement details.
HOW TEGARIS FITS
A policy layer between
applications and the blockchain network.
Applications use governed interfaces. Tegaris evaluates the caller, the requested operation and the applicable policy, and then controls what action is permitted and what data is returned.
01 / APPLICATIONS
Your participants and workloads
Business applications · Services · Administrative tools
02 / TEGARIS
Identity → Policy → Decision
Participant context · Operation permissions · Disclosure rules
03 / SHARED EVM NETWORK
Your contracts and execution layer
Contract calls · Transactions · State · Events
Conceptual request path. Enforcement is governed by the configured interfaces, policy and deployment.
A clear privacy boundary
Tegaris controls access via configured application interfaces. It doesn’t encrypt the data on the public ledger or hide it from someone who has unrestricted access to the nodes. The operator has to secure direct access to the underlying infrastructure. The cryptographic confidentiality of transactions and the privacy of the execution are achieved through complementary technologies.
POLICY AS AN OPERATING DISCIPLINE
From an intended rule
to an accountable decision.
Privacy is all about what you enforce. The Tegaris project links policy changes to runtime state and the evidence that would be required to understand an outcome.
Define and simulate
Describe the permitted operations and the disclosure. Run the allowed and denied cases prior to requesting the change.
Review and approve
Submit the policy version for independent review so that the change and its authority can be reviewed in tandem.
Publish and verify
Publish the approved version and then check activation at the runtime targets. A publication request in itself is not evidence of enforcement.
Explain and investigate
Follow the decision history in the context of the participant, with the policy version and the relevant inputs available for investigation.
APPLICATIONS
Where shared systems
need distinct permissions.
Patterns to explore with Tegaris. Each implementation will require its own policy design, integration testing and operational validation.
Shared financial networks
PARTICIPANT ACCESSDefine how each institutional participant's applications interact with the shared contracts and what transaction data they are able to receive.
Controlled service access
WORKLOAD AUTHORITYGive an integration or service workload the operations it needs within the organization's authority and provide it with access that can be reviewed and revoked.
Purpose-limited investigation
SCOPED DISCLOSURESupport the operational review via governed access to the records and decision evidence, with disclosure restricted to what the reviewer is permitted to see.
OPEN DEVELOPMENT
Build the boundaries.
Shape the project.
Tegaris is an open source LF Decentralized Trust Lab. Application developers, network operators, security researchers and technical writers are able to contribute to the work of making application privacy easier to understand, implement and test.
Code and examples
Help to develop focused integrations and reproducible application workflows.
Privacy and testing
Look at cross-participant access, revocation and failure behavior.
Documentation
Make the setup, the privacy assumptions and the policy behavior easier to follow.
Initial source contribution in preparation
The public repository is established under Apache 2.0. The implementation code and release notes are being put together for contribution. Follow the repository and the Lab page for publication updates; installation instructions will be included with the source release.
Resources
Explore Tegaris.
Documentation, developer guides and project resources, maintained in the open.
01 / DOCUMENTATION
Project documentation
Architecture, privacy boundaries and operating guidance.
Explore the documentation 02 / DEVELOPERSDeveloper documentation
Integration guides, API references and examples as they are published.
Explore developer resources 03 / OPEN SOURCEThe project on GitHub
Source, project activity and contribution resources.
Visit the repositoryGitHub is the source of truth for project documentation.
QUESTIONS
Understand the scope.
What does application privacy mean in this context?
Its about means governing what an individual participant or workload is able to do and see via the Tegaris interfaces. Permissions can vary by organization, resource and operation. Having a access to an operation does not necessarily mean you have access to all of the associated data.
Does Tegaris replace a blockchain or a private execution system?
No. Tegaris is the application level privacy and policy control plane for shared EVM networks. It sits on top of the execution layer. You need a dedicated privacy control plane and integration design for confidential transactions, private smart-contract execution and protection from the infrastructure operators.
Can I deploy Tegaris in production today?
The initial source contribution is being built up as a dev baseline. Evaluate the published release scope, supported configurations and validation results when it becomes available. Production use will require separate security, integration and operational qualification.
How can I follow or contribute to the project?
Start with the public repository and the approved LFDT Lab proposal. Follow source publication and open project discussions. Contribution and setup guidance will be provided as part of the implementation. All code contributions will be made under the project's Apache 2.0 license and Developer Certificate of Origin requirements.