Opencampus
  • Intro
  • Executive Summary
  • Scalability Audit
    • Current System
    • Issues Metrics
    • Scalable Architecture
    • Recommendations Explanation
    • Conclusion
Powered by GitBook
On this page
  • Consistency / Inter-operability recommendations
  • Security recommendations
  1. Scalability Audit

Recommendations Explanation

PreviousScalable ArchitectureNextConclusion

Last updated 1 year ago

Rivera uses latest standards in smart contracts. No critical issues were detected on that front. Moreover the use of Gelato is a good choice keeping in view the current alternatives available. However, moderate improvements are needed and some general recommendations which will be discussed one by one.

Consistency / Inter-operability recommendations

Cross chain communication using CCIP

ROI: 5x

Blast radius: High

Time-to-market: 1 week

Rationale

As of now the TinyTap NFTs are on ETH chain and Opencampus is working on BSC. Opencampus claims that tinyTap is using opencampus protocol but at this point there is no mechanism of communication between TinyTap ETH NFTs and Opencampus ecosystem on BSC. The only thing tinyTap is using that if you are on TinyTap have your wallet connected and also owning EDU token of opencampus on BSC then you can use TinyTap platforms and some other games.

There is no cross chain communication and we will not recommend a bridge but rather the usage of Chainlink CCIP . This way the web3 products using opencampus protocol on any EVM chain can communicate and build more features using the EDU token further enhancing the utility of EDU token.

Royalty mechanism by Opencampus

ROI: 5x

Blast radius: High

Time-to-market: 1 week

Rationale

Royalty mechanism via Opensea can be improved by replacing it by Royalty Mechanism of DAO itself using smart contracts deployed and owned by DAO. We donot have to reinvent the wheel and simply can use easy to deploy and modify contract provided by thirdweb here :

Onchain voting instead of on snapshot ( offchain )

ROI: 5x

Blast radius: High

Time-to-market: 1 week

Rationale

Security recommendations

Record Keeping Contract

ROI: 5x

Blast radius: High

Time-to-market: 4 days

Rationale

n the original roadmap Opencampus mentioned that the Course Certificates are backed by Blockchain. But for now, there is no on-chain contract for verification of Certificates upon Course Completion. We recommend a “Record Keeping Contract” that keeps tracks of all Courses that a User has Graduated from. And the Certificate and Graduation is added by the Partner Platform backend to IPFS and the Record Keeper Contract respectively.

Foundation treasury contract

ROI: 5x

Blast radius: High

Time-to-market: 4 days

Rationale

Decentralized storage for Opencampus

ROI: 5x

Blast radius: High

Time-to-market: 4 days

Rationale

Publisher NFTs Factory

ROI: 5x

Blast radius: High

Time-to-market: 4 days

Rationale

Publisher NFTs Factory that keeps track of All Publisher NFT Contracts because right now there is not tracking mechanism onchain which connects EDU directly to NFTs, and partner platforms onchain.

Content Revenue Contract

ROI: 5x

Blast radius: High

Time-to-market: 4 days

Rationale

Content Revenue Contract is also missing which should be onchain controlled by DAO and not by 3rd party platforms. Currently all of these are being handled by the Partner Platform which arises the Problem of Not using the Opencampus Protocol and also giving more control to Partner Platform than to Opencampus DAO

Voting is a critical action and should be onchain, controlled by DAO. Changing offchain voting to snapshot to onchain is also easy using thirdweb simply follow the steps as shown by thirdweb

Opencampus should have a foundation treasury contract which takes all the funds and grants. This will enable the transparent funds collection and distribution mechanism so any community member can see where and how funds are used. Making and deploying the treasury contract is easy using thirdweb platform. Read more here :

For decentralized storage a straightforward platform is IPFS but also is a good option which ensures forever availability of data.

https://chain.link/cross-chain
https://portal.thirdweb.com/solidity/extensions/royalty
https://thirdweb.com/thirdweb.eth/VoteERC20
https://blog.thirdweb.com/guides/build-treasury-and-governance-for-your-dao/
arweave