Skip to content

Decentralized file vault#504

Closed
EbukaMoses wants to merge 458 commits into
ChianLojistics:mainfrom
EbukaMoses:Decentralized_File_Vault
Closed

Decentralized file vault#504
EbukaMoses wants to merge 458 commits into
ChianLojistics:mainfrom
EbukaMoses:Decentralized_File_Vault

Conversation

@EbukaMoses

@EbukaMoses EbukaMoses commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Description

Large files (manuals/PDFs) are currently in centralized silos.

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 🔧 Code refactor (no functional changes)
  • 📚 Documentation update
  • 🧪 Tests (adding or updating tests)
  • 🔒 Security (security-related changes)
  • 🚀 Performance (performance-related changes)
  • 🎨 UI/UX (user interface changes)
  • 🛠️ DevOps (deployment, CI/CD, infrastructure changes)

Changes Made

Code Changes

Documentation Updates

Database/Schema Changes

Testing

Manual Testing

Automated Tests

  • Unit tests pass
  • Integration tests pass
  • E2E tests pass (if applicable)
  • Performance tests pass (if applicable)

Test Coverage

Screenshots/Videos (UI Changes)

Before After

Breaking Changes

Checklist

Code Quality

  • Code follows project style guidelines
  • Code is self-documenting or properly commented
  • No console.log statements or debugger breakpoints left
  • No unused imports or variables
  • Code passes linting checks

Testing

  • Unit tests added/updated for new functionality
  • Integration tests added/updated if needed
  • Manual testing completed
  • Edge cases considered and tested
  • Tests pass locally

Documentation

  • README updated if needed
  • API documentation updated if needed
  • Inline code documentation added/updated
  • Comments added for complex logic

Security

  • Security implications reviewed
  • No sensitive data exposed
  • Input validation added where needed
  • Authentication/authorization considered

Performance

  • Performance impact assessed
  • No performance regressions introduced
  • Bundle size checked (frontend)
  • Database queries optimized (backend)

Deployment

  • Environment variables documented
  • Database migrations included
  • Backward compatibility maintained
  • Rollback plan considered

Legal/Compliance

  • DCO (Developer Certificate of Origin) signed
  • License headers added to new files
  • Third-party dependencies reviewed
  • GDPR/privacy implications considered

Related Issues

Close #467

Additional Context

Abidoyesimze and others added 30 commits March 25, 2026 17:44
Finalize contract test coverage and timeline integration; pass CI
feat(frontend): input sanitization, a11y, error handling, event validation
Fix #129, #120, #137, #123, #21AH: implemented frontend and backend i…
…ad-more

Add paginated timeline loading and fix frontend CI deps
…nt-ids

Issue/paginated product event ids
EbukaMoses and others added 16 commits May 2, 2026 02:02
- Add step to install @rollup/rollup-linux-x64-gnu in CI workflow
- Add step to install lightningcss-linux-x64-gnu in CI workflow
- Remove npm aliases from package.json overrides
- This approach directly installs missing native modules in CI environment
- Unit tests pass with 14 test files and 94 tests
- Switch back to standard tailwindcss + autoprefixer PostCSS configuration
- Update CI workflow to install tailwindcss-linux-x64-gnu instead of lightningcss
- This approach avoids Lightning CSS native module issues in E2E tests
- Unit tests pass with 14 test files and 94 tests
- Switch from npm ci to npm install --include=optional in CI workflow
- This approach should install optional dependencies like @rollup/rollup-linux-x64-gnu
- Remove separate native module installation steps
- Test if this resolves the Rollup native module issue
- Fix tailwindcss-linux-x64-gnu to lightningcss-linux-x64-gnu in CI workflow
- The correct package name for TailwindCSS native modules is lightningcss-linux-x64-gnu
- This package exists and will be available in the Linux CI environment
- Rollup Linux package installation is working correctly
- Switch back to @tailwindcss/postcss plugin as required by the error message
- Update PostCSS configuration to use @tailwindcss/postcss instead of standard tailwindcss
- Update package.json to use @tailwindcss/postcss dependency
- CI workflow remains the same since we still need Lightning CSS Linux package
- Unit tests pass with 14 test files and 94 tests
…anchoring.

Introduces Soroban content anchors with CAS dedup, SDK storage bridges for direct decentralized uploads, and a backend verification worker with tamper alerts for manuals up to 50MB.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown

@EbukaMoses is attempting to deploy a commit to the Ebeleokolo's projects Team on Vercel.

A member of the Team first needs to authorize it.

EbukaMoses and others added 5 commits June 23, 2026 22:18
…feature.

Resolves add/add conflicts by taking main as base and integrating integrity anchors, IPFS/Arweave SDK bridges, and the verification worker on updated backend structure.

Co-authored-by: Cursor <cursoragent@cursor.com>
Bump Next.js to 16.2.9, refresh lockfile dependencies, and apply rustfmt to integrity anchor modules.

Co-authored-by: Cursor <cursoragent@cursor.com>
Add required description field to test mock and clean up verifier imports and integrity anchor cast.

Co-authored-by: Cursor <cursoragent@cursor.com>
…istry module.

Root re-exports are gated off for wasm32 targets, so stellar contract build failed in CI.

Co-authored-by: Cursor <cursoragent@cursor.com>
Place product_registry import with other crate imports per rustfmt.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Lynndabel

Copy link
Copy Markdown
Collaborator

@EbukaMoses please resolve conflict

@Lynndabel

Copy link
Copy Markdown
Collaborator

@EbukaMoses, nice work. However, I noticed you're likely working with an older local copy of the project. Please delete the old project, sync your repository, reclone it, and then create a new project. The current setup is causing deleted files to be pushed, which can lead to unnecessary conflicts.

@EbukaMoses EbukaMoses closed this Jun 27, 2026
@EbukaMoses
EbukaMoses deleted the Decentralized_File_Vault branch June 27, 2026 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Decentralized File Vault with Integrity Proofs