Secure presentation links (signed/encrypted, not plaintext base64)

[DanielCotoJ]

Effort: L — Estimate: 10-14 h — Dependencies: #36 (pairs with #35 for signing) — Unlocks: #40 (public verification)

Context

Today a share link is plaintext base64url JSON with no encryption, no signature and no server-side persistence. See apps/credit-history/src/lib/presentation-token.ts and the SEAM in apps/credit-history/src/app/share/page.tsx:

// SEAM: the real ACTA sharing will be wired here (encrypted off-chain payload / ZK).
// Today we only generate a mock token. Missing: encryption, persistence, real expiration.
const payload = { ids: selectedIds, exp: expirationTime };

Anyone can decode or tamper with the token, and expiration is only enforced client-side.

Goal

Share links carry a tamper-evident (signed and/or encrypted) presentation created via ACTA, with expiration that can't be bypassed by editing the token.

Step by step

1. Replace the PresentationPayload codec with an ACTA-backed presentation: build a verifiable presentation from the selected credential ids, signed by the holder (signTransaction from Integrate a real wallet (Freighter / Stellar Wallets Kit) #35 if the flow requires an on-chain/off-chain signature).
2. Persist the presentation (ACTA off-chain payload or vault reference) so the verify side fetches it by an opaque token/id instead of trusting the URL contents.
3. Enforce expiration on the resolving side, not just the client; keep the existing preset UX (1h/1d/7d/30d/custom/never).
4. Keep the /share UI and result screen intact; only the token generation/resolution changes.

Out of scope

• The verifier rendering + on-chain revocation check → Real public verification (verifyVc against the vc-vault) #40.

Acceptance criteria

• The token can't be decoded to raw credential data nor edited to extend expiration.
• A presentation is created/persisted via ACTA; verify resolves it by opaque reference.
• Expiration is enforced server/resolver-side.
• /share UX unchanged; pnpm lint && pnpm typecheck && pnpm build pass.

[heymide]

I'm interested in contributing to this feature because it strengthens the security and integrity of the credential-sharing flow while preserving the existing user experience.

My approach is to replace the current plaintext presentation token with an ACTA-backed verifiable presentation, ensuring the shared link contains only an opaque reference rather than raw credential data. I'll integrate the required signing flow where applicable, persist the presentation through ACTA, and update the resolver to fetch and validate the presentation server-side, including enforcing expiration independently of the client.

I'll keep the existing /share workflow and UI unchanged while focusing on the underlying token generation and resolution logic. Finally, I'll verify the implementation through testing and ensure the project passes linting, type checking, and production builds.

I have experience building secure TypeScript applications, integrating authentication and cryptographic workflows, and implementing reliable backend/frontend integrations. I'm confident I can deliver a solution that aligns with the project's architecture and acceptance criteria.

[AlonsoFi]

Hi team! I'd love to work on this. I'll implement the encryption and signing flow for the presentation links to replace the plaintext base64.

Could you assign it to me?

[Fabiana1504]

I’d like to work on this issue. I’m interested in cybersecurity, web security, and Web3, and I think improving the current presentation links would add real value to the project. I’d focus on signed and encrypted links, expiration, and protection against tampering while keeping the implementation compatible with the existing codebase.

[SudiptaPaul-31]

Hey Maintainer!!! My name is Sudipta Paul a very old contributor of GrantFox and other platform having quite a lot of experience in open source and working with full stack issues as well as very much proficient in writing contracts and would love to work on this issue and contribute to your project, May I be assigned to this task

[naninu123]

I've thoroughly analyzed the ACTA codebase — I understand the current plaintext base64url token in lib/presentation-token.ts and the SEAM at share/page.tsx. I've built a plan to: (1) replace the codec with ACTA verifiable presentation signed by the holder via Stellar SDK, (2) persist tokens to off-chain vault (opaque payload), (3) enforce expiration server-side, (4) keep /share and /verify UIs unchanged. Expert in TypeScript/crypto, 59 merged GrantFox PRs (T2 Builder), can submit within 5-7 days of assignment.