Documentation
Build with confidence
Every page here is written for engineers, security reviewers, and program owners who need a dependable release path. Follow the tracks, copy the examples, and ship with evidence.
Navigation
Choose your track
Direct links to the sections teams use most often.
Spin up your environment, deploy a vault, and validate the unlock path.
Trace how client encryption, IPFS, and contract logic work together.
Inspect TimeLockedVault structures, functions, and events.
HTTP endpoints, auth patterns, rate policy, and SDK entry points.
Threat analysis, encryption choices, and operational controls.
Execution path
From planning to proof
Plan
Select the right path for your team: classroom releases, procurement, or partner unlocks.
Build
Use the quick start, API reference, and contract docs to assemble your flow without guesswork.
Prove
Share CID, contract state, and audit events so stakeholders can verify each step in advance.
Reference spotlight
Core pillars to review
Client encryption
AES 256 in the browser with keys cleared after upload. No secret stays on our servers.
Chain enforcement
Unlock checks run on Polygon time. No override exists outside the contract.
Transparent trail
Uploads, voids, and unlocks emit events you can reference in audits and legal reviews.
Hands on
Deep dives with examples
Expand any module to see copy ready commands and patterns.
- Clone the repository and install packages with npm install.
- Copy .env.example to .env.local and fill secrets.
- Run prisma generate and prisma migrate dev to prepare the database.
- Start the dev server with npm run dev.
git clone https://github.com/your-org/tala
cd TALA
npm install
cp .env.example .env.local
npx prisma generate
npx prisma migrate dev
npm run devNeed direct guidance?
Reach the team for threat reviews, exam release planning, or procurement support. We respond with references you can forward to stakeholders.