fix: epin docs

[RishabhS7]

Summary

Update new E-pin Documents

Summary by CodeRabbit

• New Features
  • None
• Bug Fixes
  • Corrected QR code links so operative and inoperative documents resolve to the appropriate pages.
• Chores
  • Refreshed credential identifiers and status token IDs for both operative and inoperative documents.
  • Updated digital proof timestamps and signatures to the latest issuance.
  • Ensured consistency between outer and embedded QR code targets in operative documents.
  • Maintained existing issuer and credentialSubject details while updating metadata.

[coderabbitai]

Walkthrough

Two static Verifiable Credential JSON files were updated: QR code URIs adjusted to point to the correct operative/inoperative documents; ids, credentialStatus.tokenId, and proof (created timestamp and proofValue) refreshed. No schema or structural changes beyond these field updates.

Changes

Cohort / File(s)	Summary of changes
Inoperative VC update public/static/electronic-promissory-note-inoperative.json	Updated qrCode.uri to inoperative path; changed credentialStatus.tokenId; updated top-level id; refreshed proof.created and proofValue; other fields unchanged.
Operative VC update public/static/electronic-promissory-note-operative.json	Updated both qrCode.uri entries to operative path; changed credentialStatus.tokenId; updated top-level id; refreshed proof.created and proofValue; no issuer changes; other fields unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix: rename ePN #18 — Also updates the same operative/inoperative VC JSONs with corrected URIs, ids, tokenIds, and proofs.
• chore: update ref documents #16 — Similar “ref documents” update touching the same fields in the same VC JSON artifacts.

Suggested reviewers

• isaackps
• rongquan1

Poem

I hopped through fields of JSON bright,
Tweaked the codes to set them right.
Operative paths now lead the way,
Inoperative ones kept at bay.
Tokens, proofs—refreshed and neat,
A tidy warren, changes complete. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 529204c and 2f3d3ec.

📒 Files selected for processing (2)

• public/static/electronic-promissory-note-inoperative.json (1 hunks)
• public/static/electronic-promissory-note-operative.json (1 hunks)

🧰 Additional context used

🪛 Gitleaks (8.27.2)

public/static/electronic-promissory-note-operative.json

47-47: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

48-48: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

🔇 Additional comments (10)

public/static/electronic-promissory-note-inoperative.json (5)

48-48: Updated tokenId acknowledged.

New 32-byte (64-hex) tokenId format looks valid for the FREE network.

---

52-52: New VC id is fine.

URN change is consistent with re-issuance; no structural issues detected.

---

55-55: Proof timestamp updated — ensure signature was produced over this exact document.

No issues spotted, but please confirm verification passes in your usual VC verifier.

---

57-57: Proof value refreshed — looks consistent with a re-sign.

Nothing to change; just ensure downstream verifiers accept it.

---

42-42: QR action URLs verified and correct
Sanity-check script confirms both operative and inoperative JSON files decode to the expected payloads (URI, chainId, redirect). No further changes needed.

public/static/electronic-promissory-note-operative.json (5)

42-42: QR action now points to the operative document — looks correct.

The encoded action URL targets the operative JSON and keeps the same redirect and chainId.

---

48-48: tokenId updated — OK, and gitleaks alert appears to be a false positive.

• The new tokenId has the expected 64-hex format.
• Note: Secret scanners often flag long hex strings; this tokenId is a public identifier, not a secret. Safe to commit.

---

52-52: New VC id is fine.

URN update aligns with a new credential instance.

---

55-55: Proof timestamp advanced — verify signature validity.

Looks good; please ensure your verification step passes with this content hash.

---

57-57: Proof value rotated — acknowledged.

No structural issues detected.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/epin-docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for tradetrust-gallery ready!

Name	Link
🔨 Latest commit	2f3d3ec
🔍 Latest deploy log	https://app.netlify.com/projects/tradetrust-gallery/deploys/68a29fc71d19bc0008288ebe
😎 Deploy Preview	https://deploy-preview-19--tradetrust-gallery.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[isaackps]

LGTM!