Projects | Bloxico Software Solutions

Home • Projects

Projects we did are a proven track record

We established some well known projects in the Web3 space.

90+

years of founders’ experience in IT, management and finance

1152%

growth since inception

100+

highly skilled professionals

9th

on the Deloitte Technology Fast 50 Central Europe

PROJECT BREAKDOWN

Check out our portfolio

Tixbase

Tixbase (formerly NFT TiX) is a decentralized ticketing platform with the aim to revolutionize the ticketing industry and provide long-term solutions against fraud, scalping, and an out-of-control secondary market.

The technology that underpins NFT TiX Marketplace is undeniably complex. We are standing on the cusp of a revolution: for the first time ever, highly advanced algorithms have made it possible for buyers and sellers to process transactions between themselves, without involving any intermediaries. What this means for all of us is greater efficiency, more convenience, lower costs, increased security, and an all-around superior experience.

It is important to understand, as well, that while the background technology for NFT TiX Marketplace is complex, the front-end does not have to be. We have designed our platform so that it is easy for anyone to use, even if you have never tried purchasing an NFT before. Everyone, including true novices to the blockchain, only needs to follow these instructions, to buy or sell tickets via NFT TiX Marketplace.

FLARE

It is a Layer 1 like Ethereum, with added data acquisition functionality. Flare can therefore offer developers decentralized access to high-integrity data from other chains and the internet. This enables the creation of dapps with new use cases and monetization models. It also allows these dapps to serve multiple chains through a single deployment.

Flare is Ethereum Virtual Machine (EVM) based, meaning any applications written in Solidity to run on any other EVM chain can also be used on Flare.

Flare has two data acquisition protocols which are secured by the Layer 1 network.
They are native to Flare, so developers don’t need to rely on other third party data oracle solutions, which can be centralized and expensive.

The Flare Time Series Oracle (FTSO) delivers highly-decentralized time series data feeds to dapps on Flare. Currently, the FTSO provides digital asset price pairs and updates every 3 mins.

The State Connector enables Flare to safely and trustlessly come to consensus over an event that has taken place externally to the network, for example a blockchain transaction between two parties or the content of an API on the internet.

Together, these protocols give developers decentralized access to high-integrity data from other chains and the internet. That’s why we call Flare the blockchain for data.

Both the State Connector and FTSO are used in the recent demonstration of purchasing an NFT on Flare using the token of a different blockchain.

Atala SCAN

Atala SCAN v1 is a Mobile application through which users can authenticate the origin of the product by scanning an NFC chip attached to the product. We were utilizing Cardano blockchain as a “database” where we stamped proof of product authenticity.

We also developed GUI for producers through which they could generate and stamp those proofs in one click. We were integrating NXP 424 tag as well as Cardano PSG Services in order to achieve this.

The system consisted of three main components. The Mobile Application served as the primary entry point for users, allowing them to scan products using an NFC reader to check their authenticity. After scanning, users were presented with the authenticity status of the product.

The Atala SCAN Backend supported the mobile application by validating the UID and CMAC of the scanned product and checking it against metadata stamped on the Cardano blockchain.

The Product Stamping GUI/CLI was developed for producers and brands to stamp batches of their products on the Cardano blockchain, providing them with the ultimate confidence that their products would remain intact. Together, these three components formed a robust and reliable system for product authenticity verification.

Atala SCAN v2

Evolution of Atala SCAN v1 existing solution and its components by integrating Tangem Wallet cards as supported hardware for product authentication and implementing supporting UX/UI for Atala SCAN mobile application.

Catalyst Voting System

The main goal of this project is to set the system for voting for Cardano holders’ engagement in order to hand over control of Cardano in a safe way and to represent their interests in the future of Cardano. This is the evolution of the existing mobile application that will give users more flexibility and user-friendliness.

Catalyst Voting Platform functionalities

The voting system consisted of several main components. The Voting Center Homepage provided users with information about the Global Voting Campaign (GVC) as well as access to the dReps page, which allowed them to search all registered dReps. The Wallet Dashboard featured dashboard pages for three different types of voters, including Active Voters, Passive Voters, and dReps. The Vote Delegation page enabled voters to delegate their voting power to dReps, manage previous delegations, and cancel delegations. The dRep Registration page allowed users to register as dRep voters. Finally, the DApp Voting Proposals page enabled voters to search and browse through challenges and proposals, as well as vote on them.

Together, these components formed a comprehensive voting system that provided users with all the necessary tools to participate in the GVC.

System Test Matrix

The Filecoin System Test Matrix is a dashboard with a detailed list of Venus features and behaviors and a mapping between those features and test suites, systems, and subsystems that those features are related to. The main goal of this project is to close the discrepancy between the specification and the actual state of implementation. The System Test Matrix can be used to evaluate the state of Venus at a glance and help new contributors understand how the Filecoin network works.

System Functionalities:

1. A catalog of unique expected behaviors of a Venus node. This catalog is in YAML format and acts as a specification of how different subsystems and subsystems of Venus should behave in given situations with different inputs and is a starting point for writing tests. The Bloxico team provided the base catalog of Lotus behaviors and supported the Venus team with extending the catalog with Venus specific behaviors, and guided the process of exploring and understanding how the architecture of Venus can be mapped to STM systems and subsystems. The quality of this catalog highly impacts the quality of the end results of STM. The Bloxico team was expected to provide a starting point and support for the Venus team.

2. Integration of Go test crawler with the Venus codebase. The Test Crawler scans the repository for tests and parses test annotations (written in our custom format) that map test functions to test behaviors from the previous step. It outputs a JSON report. The Bloxico team supported the Venus developers with adding test annotations to existing test files and helped out with building the habit of annotating future test files, so we can keep the System Test Matrix up to date with each new release. With support from Bloxico test engineers, the Venus developers, for the purpose of documenting the rationale behind existing tests and what behaviors were already tested, annotated all of the test files and produced test crawler reports that are now used to visualize the state of Venus.

We deployed a new Venus-specific dashboard to venus.systemtestmatrix.com. This dashboard should help the Venus developers visualize the current state of Venus, and it’s rendered using the behavior catalog and test crawler output from the previous steps. The dashboard provides a UI for browsing, searching, and visualizing all of the existing behaviors, tests, subsystems, and components of Venus.

The goal was to do a detailed analysis of the existing test suites and craft a dashboard of test cases (not metrics, at this stage) that breaks down test scenarios by subsystems and components. Each test case should carry a status indicating if it’s not implemented, in progress, succeeding, or failing (per branch) which will show the current state of Lotus tests, that can be used as a baseline to evaluate future improvements.

Increase the integration test assets coverage using the current integration testing kit developed by the Lotus maintainers, in coordination with PL team as main Protocol Labs approvers of the tests Bloxico will create and improve.

Improve and craft new Acceptance & E2E tests that will be used to evaluate new Lotus releases.

Improve the current state of tooling used by the QA team by proactively identifying valuable additions/improvements, proposing them to the PL team, and implementing them based on agreed prioritization.