Skip to content

Propose ArtizYou Trust Lab #325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Propose ArtizYou Trust Lab #325

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
317ea4d
Create artizyou.md
SamDrissi Jun 16, 2025
2736e4e
Update labs/labs/artizyou.md
SamDrissi Jul 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions labs/labs/artizyou.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
layout: default
title: ArtizYou
parent: LFDT Labs
grand_parent: Active Labs
---
# Lab Name
ArtizYou Trust Lab


# Short Description
Decentralized platform connecting creative professionals with blockchain-verified credentials, smart contract agreements, and AI-powered plagiarism detection for images and text.


# Scope of Lab
Develop core components for:
- Decentralized identity verification for creatives
- Smart contract templates for creative collaborations
- Cross-chain reputation system
- NFT-based portfolio authentication
- AI-powered plagiarism detection and automatic similarity alerts for images and text


# Initial Committers
- https://github.com/MuhammadRizwanMughal
- https://github.com/SamDrissi
- https://github.com/rgagnon
- https://github.com/Artizyou-inc


# Sponsor
- David Boswell (dboswell@linuxfoundation.org) – Maintainer, LF Decentralized Trust Labs

# Pre-existing repository
- https://github.com/Artizyou-inc/artizyou
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make this repo publicly visible? We need to check for license and DCO before we can approve.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @tkuhrt thank you for the feedback!

At the moment, our repository is private due to limited dev resources and security expertise. We're only two developers managing the infrastructure, and we're cautious about exposing the server or database without proper access control.

We're fully committed to making the project open source and public, but we’d appreciate guidance or support from the community to ensure we do it securely, especially regarding best practices for repo visibility, license integration, and avoiding exposure of sensitive backend configurations.

Would it be possible to get help from the LFDT team or be pointed toward the right process or template for a safe transition?

Thanks again for your support.