We can extend the DB_NFT contract so that multi-sigs can create their own private datasets with access control if the user is the owner of the multi-sig and give them the ability to make that dataset mintable us an NFT so then also people that mint that NFT can gain access to the Database contents.
That removes the need for the private repos and private datasets can get handled by multi-sigs( companies ) where only the owners of the multi-sig can add files on it. Private Datasets will require data format validation but the merge of the CIDs and the create DB NFT does not require signature validation the multi-sig owners need to just confirm the proposed transaction to create the DB_NFT
Private Groups will not require data format validation.
Using multi-sigs the company can create open datasets but also jobBounties with proposals
Recap
We can only use private and open datasets for HackFS and of course BacalhauExecutions on OpenDataSets
The main thing in the UI should be the jobs and bounties pages
But also the multi-sig page where we can see all the proposals and confirm proposals and execute transaction proposals ( for example). (To create a JobBounty) or (to assign a winner for a bounty) or (add/remove a member) or (make a private dataset mintable and decide the mint price)
New ideas To Brainstorm
@tse-lao
Recap
We can only use private and open datasets for HackFS and of course BacalhauExecutions on OpenDataSets