codexlink / folioblocks

From the Scratch Implementation of "Credential Verification System using Blockchain Technology" Thesis. | FastAPI as Backend, Vue.js 3 + Quasar SPA as Frontend. Deployed in Azure and Github Pages.

👋 Hello! I'm Janrey Licas (CodexLink)

return (is_day ? "(Backend) Python(-developed) Data Engineer" : str(<object 'Future'>.result())) # type: ignore

Path: C -> [C++ -> Rust (TBD)] -> Python (PyQt5 -> Django -> (Transition to Pure Backend) -> Django REST -> Flask -> (Touch up to Misc. Libraries) -> OpenCV -> (Data Science Libraries) -> FastAPI -> Litestar (Soon) (Current)) <-> Vue.js -> React (Incomplete)

I usually contribute to OSS in a different way, such as creating examples of specific tech stacks. Currently inactive.

📜 Knowledge Table

Discontinued (Knowledge Degraded)	Knowledge Retained (Considers Bare-Minimum Familiarity)	Currently Learning/Focusing at	Halted

This does include more than programming languages. It includes SaaS, IaaS, PaaS, and anything else tech-related.

🤔 Agendas? ▶️ Passively Reviewing for PCEP/PCAP (Python) ▶️ Designing TradingView Indicators for Personal Usage ▶️ Developing my personal project "Elysium Monolithic" ⏸️ (Paused) (Considering to refactor) Discord Activity Badge.

📊 Statistics Updated via GitHub Workflows or through HTTP Requests. 🕙 Coding Activities Updates every week. From: 10 May 2024 - To: 17 May 2024 No activity tracked

folioblocks's Issues

Data Scraping to Static Site

With a system with a dead backend system (this was due to expenses, and I don't have a job yet to sustain the backend system), I would want to data scrape the last state of the backend system right after presenting the thesis from the final defense since last June of 2022. With that, I have the following tasks to do:

• Data scrap, literally
• Data Clean
• Data Integration
• Frontend Adjustment with a new branch of ??? for the hosting (*)

So far, these will be the rough tasks that I will be doing with the front end to ensure that everything is viewable. This will be executed after the following task:

• #3 .

Documentation of Possibly Everything

As the paper is not available due to transferring of ownership to the Department of the Computer Engineering of my school, I cannot use it as a whole to provide information about my thesis, therefore, documentation of a specific thing or two is needed in order to leverage or provide more information as this thesis as a repository does not provide anything other than being a relic example of implementation of blockchain; with that, a following set of items will be done:

• README
• • Disclaimer
• • How
• • Demo
• • FAQ
• • Members
• • References
• Wiki
• • The Baseline Idea to a System with a Blockchain System
• • • Identifying the Problem for the Proof of Concept (PoC)
• • • The Strict Objectives to Meet the Goal of the System
• • • The Ideal and the Realistic Participants
• • • Incorporating the Credential Verification System with the Blockchain System
• • • The Constraints and Problems behind finalizing the Tech Stack
• • • The Opinionated Idea of Creating the Blockchain System
• • • The Obscured Ideas for the Security of the System
• • • The Thrown-Away Concept Ideas for Implementing the Blockchain System
• • The Flow of the System and Its Interconnection between Services
• • The Local Testing and Development: Caveats
• • The Actual Deployment from Development: Experience and HOW-TO
• • Semi-Detailed Contribution of Every Members for both Documentation and Development
• • • Disclaimer, Please Read Before Proceeding
• • • The hardships went through by the team Lead Developer
• • • Their Real Credibility to the Project
• • • Post-Thesis: No Justification
• • • The Negative Impacts to the Mental and Physical Health of the Lead Developer
• • • Conclusion

Please note that this will take a while as a lot of information was still archived and has to be re-understood once again in order to be delivered properly.