React

Development

Design

In the ever-evolving landscape of smart building management solutions, we are consistently committed to innovation and excellence. In this case study, we’ll explore one of our most remarkable projects – the Smart Sensor, a cutting-edge multi-sensor designed for ideal room climate monitoring. Today, we visit this groundbreaking technology to dive deeper into its capabilities and the impressive results it continues to deliver for our Swiss-based client, a leading building automation solutions provider.

![Mask group.png](https://strapi.suprabit.eu/uploads/Mask_group_017e145b33.png)

The Smart Sensor project was born out of the need to address the complex challenge of room climate and environment monitoring. This IoT system integrates an array of sensors, including those for temperature, humidity, volatile mixed gases, presence/motion, brightness (light intensity), and noise level. The real magic happens through sensor fusion, where data from these sensors is intelligently combined to provide precise information about the room's state. Mounted discreetly on the ceiling, the Smart Sensor captures critical environmental data and also communicates room status to users through an LED ring, where each color signifies different aspects of room occupancy, air quality, or cleaning requirements.

![Frame 10.png](https://strapi.suprabit.eu/uploads/Frame_10_24c5bbe3b7.png)


In this case study, we will explore the firmware, mobile application, and dashboard that make this technology a game-changer in smart building management.


## Holistic Approach
For this project, it was crucial to take a holistic approach. We needed to synchronize the embedded and IoT teams with our product designer and mobile app development team. From the project kickoff until the final bug fixes, the entire team worked collaboratively to create the perfect solution. We held team meetings with our client to discuss their needs, and then our teams planned together to ensure smooth coordination. The client’s product development team would provide the requirements, our designer would create the UI for the mobile app feature, and the IoT team would develop the firmware. At the same time, the mobile team would begin implementing the feature. This iterative approach allowed us to address any issues promptly, eliminating long waiting periods between different teams.

## Academic research
As we ventured deeper into the project, leveraging cutting-edge technology, we encountered a significant challenge with our sensors, specifically in obtaining accurate noise level measurements. Recognizing the critical need for precision, we decided it was time to elevate our approach. To achieve the highest level of accuracy possible, we visited a local university. There, we gained access to their quiet room—a space so tranquil that even the sound of a heartbeat can be heard.

![silentroom.png](https://strapi.suprabit.eu/uploads/silentroom_2acc2ccd92.png)

In this controlled acoustic environment, we diligently fine-tuned and calibrated our microphone sensors, ensuring they delivered the most reliable and precise results. This collaborative effort with academia underscored our commitment to excellence and demonstrated our readiness to go above and beyond to guarantee the Smart Sensor's exceptional performance in real room conditions.

## IoT Development
In the realm of IoT development, the Smart Sensor project represented a significant milestone for us. The primary goal of the Smart Sensor was to monitor room climate and environmental conditions, and to achieve this, we integrated a range of sensors, including temperature, humidity, volatile mixed gases, presence/motion, brightness (light intensity), and noise level detectors. These sensors were meticulously designed to work in concert, enabling sensor fusion to provide highly accurate information about the room's state.
![senzori.gif](https://strapi.suprabit.eu/uploads/senzori_2d6699f3ec.gif)

Our IoT-ready approach was a key element of this development, as the Smart Sensor implemented MQTT communication via IP/Ethernet. Additionally, we leveraged Bluetooth Mesh for seamless networking of sensors, enabling efficient communication between up to 16 nodes and a gateway device. This wireless networking capability allowed for real-time data exchange between devices through node-to-node communication. Bluetooth Beacon technology was employed to enhance interaction with the mobile application, providing precise device localization within the room.
![case study.png](https://strapi.suprabit.eu/uploads/case_study_b65d97440b.png)

Our work extended to the firmware, where we crafted a robust solution in C/C++ for the ESP32 with dual-core processing, ensuring the efficient operation of the Smart Sensor. This IoT development effort represents our commitment to innovation and excellence in delivering solutions that transform complex challenges into user-friendly, efficient, and highly functional IoT devices.


## Design
When developing the Smart Sensor mobile application, our design approach placed user experience (UX) at the forefront. Unlike many specialized applications that often neglect user-friendly design, we aimed to create an intuitive and enjoyable user journey from the very first interaction.

![App.png](https://strapi.suprabit.eu/uploads/App_4f1c2ef09c.png)

While prioritising UX over UI in the initial stages, we emphasized rapid iteration and user feedback to identify and resolve potential issues efficiently. Through constant communication among teams and a deep understanding of the possibilities and limitations of both sensor hardware and application, we crafted a seamless provisioning process for technicians, ensuring simplicity and error-proofing.

The design process involved some innovative solutions and out-of-the-box thinking, such as using unique colors and LED rings on sensors to aid technicians in precise sensor identification during provisioning. Thoughtful language choices, like replacing "Provision" with "Configure" and "Lock," were made to eliminate confusion and improve the user experience. This commitment to user-centric design not only resulted in a more intuitive application but also highlighted the profound impact of intentional language and iconography in creating a user-friendly interface.

![sensors.png](https://strapi.suprabit.eu/uploads/sensors_79eefbbaac.png)

Overall, our approach to design reflects our dedication to delivering high-quality, innovative, and user-centric applications that set new standards in the field of smart building management. You can read more about our design journey [here](https://suprabit.eu/article/smart-sensor-design).

## Mobile app development
The development of the mobile application for the Smart Sensor project was a crucial part of the solution. Our client required an app that would empower their technicians to efficiently provision the sensor, map out floor plans and networks, and configure settings effortlessly. Beyond the initial setup, the mobile app continued to play a pivotal role, enabling users to monitor and manage room conditions, as well as to update the sensors wirelessly. It acted as the essential link between users and the sensors. All of this added an extra layer of convenience to setting up and maintaining the whole system.

![Phone.png](https://strapi.suprabit.eu/uploads/Phone_3c26d79663.png)

Using the versatility of React Native with the convenience of Expo, our mobile team delivered a robust application that catered to both Android and iOS platforms. This cross-platform approach ensured that our clients had access to a wider user base, making it more accessible and user-friendly. The app seamlessly communicated with the sensor devices using Bluetooth Low Energy, providing technicians with real-time access to vital data. This capability was the key to the provisioning and setup of the Smart Sensor, making the commissioning process efficient and user-centric.

## Conclusion
In conclusion, the Smart Sensor project has provided us with valuable insights into smart building management solutions. Throughout the project, our teams worked together to develop software for an advanced IoT device that seamlessly monitors room climate and environmental conditions. We prioritized precision by consulting with academia to fine-tune sensor technology.

Our IoT development efforts, including MQTT communication, BLE Mesh networking, and iBeacon technology, set new benchmarks for real-time data exchange and device localization. Additionally, we created a user-centric mobile application that simplifies provisioning, configuration, monitoring, and updates for technicians.

The Smart Sensor project not only met the requirements of our client but also pushed the boundaries of sensor calibration, IoT development, and user-friendly mobile applications. As we look towards the future, our commitment to innovation and excellence remains, and we eagerly anticipate developing new smart building solutions.




large_case study-2.png

medium_case study-2.png

small_case study-2.png

thumbnail_case study-2.png

case study-2.png

Read all about how we reinvented the Smart Building Industry using our IOT, design and development expertise.

Smart Sensor - Case Study

Blockchain

Your token isn’t just about storing value – it’s a powerful tool that can supercharge engagement, build a loyal community, and even bring in more revenue. If you’re looking to take your token to the next level and attract more holders, staking is a proven way to do just that. It’s all about getting everyone on the same page, aligning the interests of your holders with the long-term success of your project.

Here’s the deal: when people stake your token, they’re locking it up for a bit, showing their commitment to your project. This not only makes them feel like they’re part of something bigger, but it also helps your token by reducing its supply, potentially boosting its demand and value. Plus, it gets the attention of serious investors who are looking for projects with a solid foundation.

Let’s explore how a well-designed staking program can elevate your token’s value and transform it into a dynamic force within your ecosystem.

## What is Staking?

Staking means keeping a certain amount of cryptocurrency in a wallet to help run a blockchain network. In return, participants earn rewards, usually more tokens. This process helps secure the network and encourages people to invest and stay loyal over the long term.

![staking.png](https://strapi.suprabit.eu/uploads/staking_72a5e7fc35.png)

## Why Staking Matters for Your Project

Below are some ways staking can benefit your project:

### Enhanced Token Utility

Staking turns your token from a passive investment into an active part of your ecosystem. It encourages holders to lock up their tokens, showing their commitment to the project's long-term success. When people stake your token, they’re essentially saying, “Hey, I believe in this project.” This builds trust and attracts more people who want to be part of a strong community with a promising future.

### Increased Demand & Scarcity

Staking generates excitement and momentum around your project. As more individuals stake their tokens, it reduces the circulating supply, creating a sense of scarcity. This scarcity, coupled with increased demand from potential investors, can significantly enhance the value of your token. By strategically implementing staking, you can not only drive up the price but also position your token as a sought-after asset with long-term potential.

### Active Community Building

Staking fosters a sense of ownership and shared purpose. Your token holders become more than investors; they become active participants, ambassadors, and champions of your project. This engaged community can provide invaluable feedback, support, and advocacy, driving your project’s long-term growth.

### Attracting Institutional Investors

Staking signals a mature and well-managed project, enhancing your credibility and attractiveness to institutional investors. By demonstrating stability and long-term viability through staking, you open doors to potential partnerships and investments.

### Additional Revenue Streams

Depending on your staking model, you can create new revenue streams through transaction fees, validation rewards, or other activities within your ecosystem. This additional income can then be reinvested to fuel further growth and innovation.


## Crafting Your Ideal Staking Program

Here’s the thing about staking – it’s not a one-size-fits-all kind of deal. The best staking program is like a tailor-made suit: it’s got to fit your business perfectly. So, before you dive in, let’s think about a few things:

- **What are your goals?** Do you want to pump up your token’s value? Build a super engaged community? Maybe even create a new revenue stream? Your goals are the compass that will guide your staking program.
- **Who are your token holders?** Think about what motivates them. What kind of rewards would really get them excited? The better you understand your audience, the more effective your staking program will be.
- **How does staking fit into your token’s big picture?** Consider how staking will affect the supply and demand of your token, and how it fits into the overall health of your token ecosystem.
- **What kind of rewards are you offering?** Make them attractive, but also make sure they’re sustainable for the long run. It’s all about finding that sweet spot between short-term gains and long-term value.
- **Do you have the tech know-how?** Staking involves some serious technical stuff. Make sure you’ve got the right infrastructure and expertise in place to make it happen smoothly and securely.

To guide you through this exciting landscape, our team at Suprabit is ready to offer the support you need. We specialize in creating staking programs that fit your specific needs. Whether you’re starting from scratch or aiming to improve your current program, we’re here to help you succeed.

So, are you ready to take your token to new heights? Let’s team up and build something amazing together!

large_staking that cake.png

medium_staking that cake.png

small_staking that cake.png

thumbnail_staking that cake.png

staking that cake.png

Discover how staking can boost your token's value, build a loyal community, and attract serious investors. Learn to craft the perfect staking program.

Boosting Your Token Value with Staking

## The Importance of Governance in Blockchain

Governance is vital for blockchain protocols and Decentralized Autonomous Organizations (DAOs). It ensures transparent, fair, and inclusive decision-making, giving all stakeholders a voice. Effective governance keeps the protocol's integrity, prevents centralization, and manages disputes. These processes are essential for adapting to changes, implementing upgrades, and resolving conflicts.

However, traditional governance models often face inefficiency, lack of enforceable rules, and poor dispute resolution. As a result, these issues can lead to governance attacks, where bad actors exploit loopholes, weakening the protocol's stability. To tackle these challenges, [Q Blockchain](https://q.org/about-q) offers innovative solutions.

## Introducing Q Blockchain

Q Blockchain is designed to go ["beyond code is law"](https://q.org/blog/the-future-of-dao-governance-on-blockchain#:~:text=Beyond%20“Code%20is%20Law.”%20Some%20Examples), offering a comprehensive governance framework. It includes enforceable rule sets and strong dispute resolution mechanisms. Unlike conventional blockchain governance, which relies solely on immutable code, Q adds flexibility and human oversight.

Q's governance model involves multiple stakeholders: Q Token Holders, Expert Panels, Root Nodes, and Validators. These participants ensure decisions are made together and transparently. Q Token Holders have voting rights, Expert Panels provide specialized knowledge, Root Nodes serve as the network's backbone, and Validators ensure transaction integrity.

## Shared Governance Security

One of the core innovations of Q Blockchain is its [Shared Governance Security](https://q.org/about-q#what-is-shared-governance-security) model. This model enhances governance security by spreading decision-making authority across multiple stakeholders. Consequently, it reduces the risk of governance attacks by making it unprofitable and impractical for malicious actors. Shared Governance Security ensures no single entity can control the protocol, thereby promoting resilience and decentralization.

## Q Governance Opt-ins

Q Blockchain introduces the idea of [Governance Opt-ins](https://q.org/blog/delivering-on-qs-vision-introducing-q-governance-opt-ins). This approach allows projects to choose from a range of governance features that best fit their needs. Thus, this modular approach enables projects to customize their governance frameworks.

Common Governance Opt-ins include:
- **Protected Code:** Safeguarding critical parts of the code from unauthorized changes.
- **Expert Decision Making:** Using the expertise of qualified individuals for decision-making.
- **Treasury Oversight:** Implementing mechanisms for transparent and accountable fund management.

These opt-ins provide flexibility and security, allowing projects to adopt governance structures that match their requirements and risk profiles. For more information, visit [Q Blockchain's page on Governance Opt-ins](https://q.org/about-q#how-can-projects-use-q).

## Economics of Q

Additionally, Q Blockchain's economic model supports its governance framework by incentivizing participation and ensuring sustainability. Q Token Holders are rewarded for their involvement in governance processes, thus promoting active participation and aligning interests. Therefore, these economic incentives encourage long-term commitment and stability, which are essential for the protocol's success.

## Our Contribution

In collaboration with Q Blockchain, we have played a key role in refining and implementing its governance framework. Our team has worked closely with Q's developers and stakeholders to ensure robust, inclusive, and adaptable governance mechanisms. Moreover, by leveraging our expertise in blockchain governance, we have helped Q create a model that addresses current challenges and anticipates future needs.

## Conclusion

Q Blockchain represents a significant advancement in blockchain governance. It offers a flexible and secure framework that goes beyond traditional "code is law" principles. By incorporating enforceable rule sets, expert decision-making, and strong dispute resolution, Q addresses critical challenges in conventional governance models. With Shared Governance Security and Governance Opt-ins, Q provides projects with tools to build resilient and adaptable governance structures. Thus, our collaboration with Q has shaped a governance framework that sets new standards for the blockchain industry.


large_photo_2024-06-25_11-42-03.jpg

medium_photo_2024-06-25_11-42-03.jpg

small_photo_2024-06-25_11-42-03.jpg

thumbnail_photo_2024-06-25_11-42-03.jpg

photo_2024-06-25_11-42-03.jpg

Explore how Q Blockchain revolutionizes governance in blockchain protocols and DAOs with enforceable rule sets, dispute resolution, and shared governance security. Learn about Q's innovative solutions, including Governance Opt-ins, and our role in refining its robust governance framework.

Case Study: Governance in Blockchain Protocols and DAOs


Many of us have experienced the frustration of navigating complex websites, struggling to find the products, services, or information we need due to inadequate search functions. Traditional online experiences often miss the mark, lacking the personal touch and intuitive interaction necessary for a satisfying journey. Studies show that a staggering [88% of customers](https://www.superoffice.com/blog/customer-experience-statistics/) have had poor website experiences, leading to frustration and lost business. This highlights the need for a different approach, one that Natural Language Processing (NLP) can provide. NLP-driven solutions offer the personalized attention and streamlined experience customers desire, guiding users quickly to exactly what they need. In this article, we will explore the different ways NLP is revolutionizing customer experiences.

## What is Natural Language Processing, and Why is it Crucial?

Natural Language Processing (NLP) is a field of artificial intelligence that enables computers to understand, interpret, and respond to human language in a way that is both meaningful and useful. It is crucial because it bridges the communication gap between humans and machines, enhancing interactions in applications such as customer service, data analysis, and automated systems, making them more efficient and user-friendly.

![nlp.png](https://strapi.suprabit.eu/uploads/nlp_85bcb4117d.png)

## How Natural Language Processing (NLP) is Transforming the Customer Experience Landscape
Natural Language Processing (NLP) is significantly transforming the customer experience landscape across various industries by enhancing interactions between businesses and their clients. Here are several ways NLP is being utilized to revolutionize customer experiences:

### 1. Chatbots and Virtual Assistants

Chatbots and virtual assistants equipped with NLP capabilities are increasingly common on websites and in apps. They provide instant customer service, answer FAQs, guide users through complex processes, and even handle complaints. For example, companies like Amazon and Google utilize NLP in their assistants—[Alexa](https://www.alexa.com/) and [Google Assistant](https://assistant.google.com/)—to understand and respond to user queries in a conversational manner, making interactions more natural and effective.

![chatbot.png](https://strapi.suprabit.eu/uploads/chatbot_4af33ffbff.png)

### 2. Sentiment Analysis

NLP algorithms analyze customer feedback, reviews, and social media comments to determine the sentiment behind the text. This helps companies understand how customers feel about their products or services. [IBM’s Watson](https://www.ibm.com/watson), for example, uses NLP to help businesses automatically gather and analyze customer sentiment from various digital interactions, enabling them to quickly address concerns and capitalize on positive feedback.

### 3. Personalized Recommendations

NLP is used to analyze customer data and predict their preferences, enabling companies to offer personalized recommendations. This capability is evident in various consumer sectors, including media streaming and online shopping. For instance, car AI assistants revolutionize how customers choose vehicles. A prospective buyer can simply describe their needs and preferences, such as *"I need a spacious car with great fuel efficiency,"* and the assistant, understands these requirements to recommend cars that match these specifications. This not only tailors the shopping experience to individual needs but also simplifies the decision-making process for the buyer.

![recommendation.png](https://strapi.suprabit.eu/uploads/recommendation_e9bafe345b.png)

### 4.Automated Email Responses

NLP enables automated yet personalized email responses to common inquiries, which accelerates response times and increases customer satisfaction. Many customer support platforms use NLP to categorize incoming customer emails and generate relevant, personalized responses automatically, greatly enhancing efficiency.

### 5 Voice-Activated Systems

Voice-activated technologies, such as those found in smartphones, smart speakers, and various IoT devices, rely on NLP to understand and respond to user commands. This allows users to interact with technology in a more natural, intuitive way. A notable example includes Apple's [Siri](https://www.apple.com/siri/), which uses advanced NLP to process voice commands and provide responses, making digital interactions seamlessly conversational.

### 6. Real-Time Translation Services

For global businesses, NLP-powered real-time translation tools help break down language barriers, allowing companies to offer support and services in multiple languages, thus expanding their market reach and enhancing customer support. Apps like [Google Translate](https://translate.google.com/) utilize NLP to offer real-time translation capabilities across dozens of languages, enabling instant communication for users all over the world.

![translate.png](https://strapi.suprabit.eu/uploads/translate_da4a6b3417.png)

### 7. Text Analytics for Market Research

NLP tools analyze large volumes of text data from blogs, news articles, and online discussions to gather insights about market trends, consumer needs, and potential business opportunities. This technology is crucial for companies such as [MarketResearch.com](http://marketresearch.com/), which uses NLP to sift through vast amounts of data to identify key market insights and trends, helping businesses make informed decisions.

### 8. Interactive Voice Response (IVR) Systems

Advanced IVR systems use NLP to understand and process spoken language from customers, guiding them through menu options without the need for pressing buttons. This makes customer interactions with automated phone systems much smoother and more natural. Many telecommunication companies are now incorporating NLP into their IVR systems to enhance user interaction and reduce the frustration typically associated with automated phone menus.

These applications of NLP not only enhance customer satisfaction by providing faster, more relevant responses but also allow businesses to gain deeper insights into their customer base, leading to better service and innovation.

## Benefits of using Natural Language Processing

Natural Language Processing (NLP) offers a broad range of benefits that significantly enhance the efficiency and effectiveness of customer interactions. Here are key advantages that NLP provides in transforming the customer experience:

### 1. Improved Efficiency

NLP technologies streamline interactions by automating responses and actions that would otherwise require human intervention. This reduces waiting times for customers and allows businesses to handle a larger volume of queries without increasing staff.

### 2. Enhanced Customer Satisfaction

By providing quick, relevant responses and facilitating smoother interactions, NLP tools greatly improve the overall customer experience. Satisfied customers are more likely to return and recommend the service to others, thereby boosting business reputation and customer loyalty.

### 3. In-depth Insights

Through sentiment analysis and text analytics, NLP provides businesses with deeper insights into customer preferences, behavior, and feedback. This data is invaluable for tailoring products and services to meet customer needs and for strategic decision-making.

### 4. Cost Reduction

Automating routine tasks and responses with NLP reduces the need for a large customer service team, thereby cutting labor costs. Additionally, improved efficiency and customer retention also contribute to a better financial performance.

![happy face.png](https://strapi.suprabit.eu/uploads/happy_face_17b76204c7.png)

## The Future of Customer Experience is Conversational

As AI technology continues to evolve, NLP will play an increasingly central role in customer service. In the near future, we can expect even more sophisticated conversational interfaces that mimic human interactions more closely than ever before. This will lead to faster, more efficient service where personalized experiences are the norm, not the exception. The ongoing developments in machine learning and AI will keep pushing the boundaries, making every customer interaction smarter, more intuitive, and highly personalized. As we look ahead, businesses that adopt and innovate with NLP technologies will lead the charge in setting new standards for customer engagement in the digital age.

large_cover-fin.png

medium_cover-fin.png

small_cover-fin.png

thumbnail_cover-fin.png

cover-fin.png

Discover how NLP is paving the way for a future where customer experience and interactions are  smarter, more intuitive, and highly personalized

 How NLP is Transforming Customer Experience

We've all become acquainted with cryptocurrencies like [Bitcoin](https://bitcoin.org/) and [Ethereum](https://ethereum.org/en/). Some of us have dived into the crypto market, exploring and investing in various digital currencies, familiarizing ourselves with the array of options available. Crypto investors are often drawn to volatile cryptocurrencies with fluctuating values, but ultimately, many end up converting their funds into stablecoins via pools on decentralized exchanges (DEXs). 

*Have you ever wondered how stablecoins maintain their equal value to the dollar on a distributed ledger?* USDT and USDC are two of the most talked-about stablecoins. These coins are not fully decentralized or algorithm-based, but they play a significant role in the cryptocurrency market. They are considered centralized because they are issued by specific authorities who ensure each coin is backed one-to-one by dollars, for which they charge a fee.

USDT, for example, claims to always be worth exactly one US dollar. However, there are some doubts about the actual cash reserves backing each USDT, as the issuer, Tether, sometimes lacks transparency in this area. On the other hand, USDC is known for its openness and regular audits of its dollar reserves. It's issued by Circle and Coinbase and also maintains a one-to-one value with the US dollar. Despite this transparency, the control over issuing and managing USDC remains centralized.

Now that we've briefly examined how centralized stablecoins operate, let's delve deeper into our topic.

## What are Decentralized Stablecoins?

Unlike centralized stablecoins backed by assets like fiat, gold, oil, or real estate, decentralized stablecoins are algorithmic. No central authority backs or controls them.

Blockchain technology operates on a decentralized ledger, creating a natural demand for decentralized stablecoins. These coins offer an innovative solution in the cryptocurrency world. They combine the stability of traditional currencies with blockchain benefits. Decentralized stablecoins use algorithms and smart contracts to keep their value stable, no matter the external influences. Let's explore how these principles work and how they ensure stability.

## Understanding MakerDAO: The Backbone of Decentralized Finance

In the vast landscape of decentralized finance (DeFi), MakerDAO stands tall as a pioneer, offering a unique solution to the volatility conundrum inherent in cryptocurrency markets. At the heart of MakerDAO lies a symbiotic relationship between two tokens: MKR and DAI. MKR, the governance token, empowers holders with voting rights, allowing them to actively participate in shaping the future of the MakerDAO ecosystem. On the other hand, DAI serves as a stablecoin, meticulously pegged to the value of the US dollar. But what sets MakerDAO apart is not just these tokens; it's the ingenious mechanism behind them.

The core concept revolves around maintaining the value of DAI in relation to the USD through a decentralized framework, achieved with the assistance of collateral and vaults - smart contracts that oversee collateralization.

### Here's how it Works:

A user deposits ETH or ERC-20 tokens as collateral into a vault. Based on the collateral, the user can mint new DAI tokens. However, there's a catch - the system imposes a minimum collateralization ratio. For instance, if the minimum ratio is set at 150%, the user must have at least $150 worth of collateral for every $100 worth of DAI generated. If the collateralization ratio falls below the minimum (e.g., 150%), the user must either add more collateral or face liquidation.

### Let's Illustrate this with an Example:

Imagine a user possesses 5 ETH, each valued at $200, totaling $1000. Assuming a minimum collateralization ratio of 150%, the user can generate a maximum of 667 DAI. However, for safety, the user decides to mint only 500 DAI, maintaining a comfortable collateralization ratio of 200%. In this scenario, the user secures their position, safeguarding against potential market fluctuations.

![im_1.png](https://strapi.suprabit.eu/uploads/img_1_1d36e38d5b.png)

If the value of the collateral increases, the user can generate additional DAI tokens. The system mints an over collateralization buffer of 500 DAI. In our example, if the price of ETH rises to 300 USD, the user can generate an additional 250 DAI tokens (if they wish to maintain a 200% ratio).

![img_2.png](https://strapi.suprabit.eu/uploads/img_2_6e2d1717dc.png)

On the other hand, if the value of the collateral falls to $500 (or below), the user can deposit additional collateral into the vault. The collateralization factor stands at 150%, allowing a maximum loan of 1,000 DAI, calculated by dividing 1,500 by 1.5. Another user, known as the keeper, can liquidate the contract. The actual loan amounts to 500 DAI, resulting in a collateralization ratio of 300%.

The keeper sells enough collateral to gather the DAI tokens needed to repay the vault. The keeper keeps a certain fee and returns the remaining collateral to the user's vault.

![im_3.png](https://strapi.suprabit.eu/uploads/img_3_197971a0fa.png)

Conversely, if the price of ETH drops to $150, with the collateral now valued at $750 and the ratio standing at 150%, the keeper will sell 3.33 ETH for 500 DAI and return it to the vault. They will retain 0.2 ETH as a fee, while the remaining 1.47 ETH will be returned to the user's vault.

![im_4.png](https://strapi.suprabit.eu/uploads/img_4_3a15ad08dd.png)

## Ensuring Stability and Sustainability in MakerDAO

As MakerDAO continues to revolutionize the landscape of decentralized finance (DeFi), it uses various mechanisms to maintain stability and foster sustainable growth within its ecosystem. Let's explore these mechanisms:

- **Stability Fee:** This fee has a variable interest rate applies to all vault users who generate DAI tokens. It serves to regulate the DAI supply and is crucial for keeping its value stable relative to the pegged currency (USD).
- **DAI Savings Rate (DSR):** On the flip side, the DAI Savings Rate offers a variable interest rate that DAI token holders receive. To earn DSR, holders must deposit their tokens into a specific smart contract. Note that the DSR remains lower than the stability fee, motivating users to borrow DAI instead of holding it.
-  **Debt Ceiling:** To prevent excessive expansion of the DAI supply, MakerDAO imposes a debt ceiling. This ceiling limits the maximum amount of DAI that one can generate in a particular vault, depending on the collateral type. This control helps keep the system within safe limits and protects against risks from too much issuance. If liquidation fails to cover the outstanding debt of DAI tokens, the system covers the shortfall using the collected stability fees. This mechanism keeps the system solvent even in adverse market conditions, bolstering confidence among users and investors alike.

## Governance and Initiatives within MakerDAO

At the core of MakerDAO's decentralized governance model lies the MKR token, serving as the mechanism through which stakeholders influence the protocol's parameters and direction. Let's explore the role of MKR token holders and other participants within MakerDAO.

### MKR Token Holders:

MKR token holders wield significant power within the Maker protocol. They actively participate in governance decisions, ranging from adjusting protocol parameters to voting on the distribution of surplus funds. In the event of a failure of debt repayment mechanisms, MKR token holders can mint new tokens and sell them to cover outstanding debts. However, this dilutes the ownership stake of existing MKR holders.

Additionally, in the event of system malfunctions or emergencies, MakerDAO has provisions for an emergency shutdown, ensuring the protection of user funds and the integrity of the protocol.

### Motivations and Initiatives:

MKR token holders are incentivized to manage the platform effectively, as the value of their holdings correlates with the success and stability of MakerDAO. They have a vested interest in maintaining the integrity of the protocol and making decisions that foster long-term sustainability.

Keepers, on the other hand, play a vital role in the ecosystem by executing liquidations and earning fees for their services. Users also play a crucial role by utilizing the platform for various purposes:

- Users may choose to collateralize their assets (such as ETH) rather than selling them, anticipating future appreciation in value.
- They may leverage the platform to access additional liquidity, either by minting DAI against their collateral or utilizing financial leverage to increase their exposure to assets.

###  Maintaining the DAI-USD Peg:

To ensure the stability of DAI's peg to the USD, MakerDAO implements various strategies:

- If the price of DAI exceeds $1, users can lock additional collateral to mint new DAI tokens, subsequently selling them on the market. This increases the supply of DAI, driving its price back towards $1.
- Conversely, if DAI's price falls below $1, existing users may buy DAI from the market and return it to the vault reducing the supply. MakerDAO may also increase the stability fee to incentivize users to return DAI to the vault, thereby stabilizing its price.

Through these mechanisms, MakerDAO endeavors to maintain the stability and integrity of the DAI stablecoin, ensuring its usability and reliability within the broader cryptocurrency ecosystem.

![im_5.png](https://strapi.suprabit.eu/uploads/img_5_3edbe10d03.png)

## Conclusion

In conclusion, MakerDAO pioneers decentralized finance (DeFi) with innovative stablecoin solutions and governance.
Through decentralized governance, empowered by MKR token holders, MakerDAO ensures protocol resilience. With collateralized debt positions and smart contracts, MakerDAO maintains DAI stability while fostering liquidity and risk management. Incentivizing responsible participation and upholding the DAI-USD peg, MakerDAO commits to stability and sustainability. Leading DeFi with collaboration and innovation, MakerDAO sets standards for decentralized governance and stablecoin mechanisms, shaping finance's future.

large_photo_2024-04-24_07-39-21.jpg

medium_photo_2024-04-24_07-39-21.jpg

small_photo_2024-04-24_07-39-21.jpg

thumbnail_photo_2024-04-24_07-39-21.jpg

photo_2024-04-24_07-39-21.jpg

Explore MakerDAO's impact on DeFi and decentralized stablecoins, ensuring DAI's stability and robust governance .

Decentralized Stable Coins

A cross-chain bridge is a decentralized solution that connects different blockchain networks, allowing assets and data to be transferred between them. It acts as a crucial connection point, enabling communication and interaction between blockchain ecosystems that would otherwise be isolated from each other.

Unlike a general blockchain bridge, which can refer to various types of interconnecting solutions, a cross-chain bridge is specifically designed to facilitate the transfer of assets or data across different chains. Its purpose is to overcome the limitations of individual blockchains. It aims to enhance their capabilities by enabling the movement of assets between them.

This blog will cover a high-level overview of the Hyperlane protocol. This protocol allows us to develop cross-chain DApps using their permissionless interoperability layer. This layer works across various blockchain environments.

## Importance of Cross-chain Bridges

The primary characteristic that sets a cross-chain bridge apart is its ability to establish trust and ensure secure transfers of assets or data between diverse blockchain networks. This is accomplished by employing a combination of cryptographic techniques, smart contracts, and other protocols. These measures guarantee the integrity, security, and transparency of cross-chain transactions.

Cross-chain bridges are essential for expanding the potential applications and adoption of blockchain technology. They facilitate the seamless exchange of assets, such as tokens or NFTs, between different chains, thereby enhancing interoperability and enabling new possibilities within the blockchain ecosystem.

## Hyperlane

Hyperlane is a permissionless interoperability layer. It enables smart contract developers to send arbitrary data between blockchains. This allows developers to create interchain applications. These applications can move tokens, execute function calls, and perform other tasks. Thus, making them accessible to users on any blockchain.

Users interact with the Hyperlane protocol through **Mailbox** smart contracts. These contracts provide an on-chain messaging interface for sending and receiving interchain messages. Hyperlane offers a modular approach to security. It allows applications to choose from a selection of Interchain Security Modules (ISMs). This customization helps in securing their integration with the Hyperlane messaging interface.

![hyperlane_overview.drawio.png](https://strapi.suprabit.eu/uploads/hyperlane_overview_drawio_f98aef3d5c.png)


### Mailbox

The Hyperlane **Mailbox** smart contracts provide an on-chain API for sending and receiving interchain messages. A Mailbox contract is deployed on every chain supported by Hyperlane.

Moreover, the network of Mailboxes serves as the connective tissue between blockchains. Developers leverage this network to create interchain applications and integrate interchain functionality into their existing applications.

### Interchain Security Module

Hyperlane secures its operations through **Interchain Security Modules (ISMs)**. ISMs, which are smart contracts, verify that interchain messages delivered on the destination chain originated from the correct source chain.

Furthermore, ISMs are fully customizable. Developers have the flexibility to craft their own ISMs according to the specific requirements of their applications.

For instance, application developers can design ISMs to adapt security models based on message content. They might implement a security model prioritizing safety over latency and gas costs for high-value and infrequent messages (e.g., governance). Conversely, for lower value and more frequent messages, a security model favoring latency and gas costs over safety can be utilized.

One of the most commonly employed ISM types is the **MultisigISM**. These ISMs validate that a specified number, denoted as *m* out of *n*, of validators have endorsed the validity of a given interchain message.

## Agents

The Hyperlane protocol relies on decentralized off-chain agents to observe, sign, and transmit messages actively.

For convenience, Hyperlane implements these agents as a set of binaries written in Rust, ensuring smooth operations.

1. Validators play a crucial role in attesting to the validity of Mailbox messages that use the Multisig ISM, making their signatures available to a relayer for further action.
2. Relayers, on the other hand, take charge of aggregating off-chain metadata for the Interchain Security Module interface and efficiently delivering messages to their designated recipients.

![blog-Page-2.drawio.png](https://strapi.suprabit.eu/uploads/blog_Page_2_drawio_4684203fb3.png)

### Validators

Validators observe the Mailbox contract and sign a Merkle root, if required, to facilitate message transmission to remote chains.

In contrast to many other protocols, Hyperlane lacks a dedicated validator set. Instead, anyone is free to run their own validator, provided that the receiver contract specifies a Multisig ISM that includes their validator.

### Relayer

A relayer ensures the delivery of messages to their recipients. Relayers play a permissionless but integral role in the Hyperlane protocol. Anyone can operate a relayer.

Relayers actively relay messages between two or more chains. They monitor the origin Mailbox contracts, detecting new messages. Upon detecting a new message, the relayer queries the destination chain to ascertain the recipient's Interchain Security Module (ISM).

Subsequently, the relayer gathers the required metadata for that ISM. The metadata collection process varies depending on the ISM and may involve obtaining signatures from one or more validators, Merkle proofs, and zero-knowledge proofs.

Finally, the relayer delivers the message to its recipient by invoking the Mailbox on the destination chain with the previously gathered metadata.

## Conclusion

Cross-chain bridges play a crucial role in expanding the potential applications and adoption of blockchain technology. They enable the seamless exchange of assets, such as tokens or NFTs, between different chains. Facilitating these exchanges, cross-chain bridges like the Hyperlane protocol not only enhance the interoperability between diverse blockchain ecosystems but also unlock new possibilities for developers and users alike. As the blockchain landscape continues to evolve, cross-chain bridges are pivotal in fostering a more connected and functional blockchain ecosystem, paving the way for a more integrated, efficient, and user-friendly blockchain future.

large_andro.png

medium_andro.png

small_andro.png

thumbnail_andro.png

andro.png

The Hyperlane protocol allows us to develop cross-chain DApps using their permissionless interoperability layer. Read more to see how it works across various blockchain environments.

Building Cross-chain DApps with Hyperlane

Think about how excited you get when you collect points for buying coffee or earn a free pizza after a certain number of orders. Web3 projects can take a similar approach to create a thriving ecosystem and keep people engaged. Crafting a successful incentive program in the Web3 space is no small feat. It's not just about giving out tokens; it's also about keeping everyone interested and involved over time. These incentive programs are extremely important because they help keep the community active and ensure people want to stick around.

So, the big question now is, *"Which incentive program is right for my project?"*

With so many options out there, finding the right fit can be tricky, but it's crucial for the success of any Web3 project. In this blog, we will go over some of the different types of incentive programs one can adopt for their Web3 project.

![26857375_7233601.png](https://strapi.suprabit.eu/uploads/26857375_7233601_eae5c581b9.png)

## What are incentive programs?
Incentive programs do exactly what the name suggests: they offer rewards or perks to motivate people to take certain actions or behaviors. These programs are designed to encourage participation, loyalty, and engagement by providing something of value in return. Whether it's through earning tokens for participating in a platform, getting discounts for frequent purchases, or gaining access to exclusive content or features, incentive programs aim to create a win-win situation. Participants get rewarded for their contributions or loyalty, while the organizations or projects behind these programs benefit from increased activity, investment, or commitment.

Essentially, incentive programs not only drive the growth and sustainability of the ecosystem but also foster a sense of community around your token project.

![8610412_5943.png](https://strapi.suprabit.eu/uploads/8610412_5943_1c361bf8ba.png)

## Why Incentive Programs Are Useful
Incentive programs are invaluable tools for several reasons:

- **Encouragement of Participation:** Incentive programs motivate users to engage with the platform. By offering rewards for participation, users are more likely to use the platform actively, whether it's through trading, staking, or contributing content. This increased engagement helps to create a vibrant community around the project.
- **Bootstrapping Growth**: Incentive programs for new projects can boost growth by attracting early adopters and contributors. These individuals can turn into project advocates, spreading awareness and drawing in more users through word of mouth and social media.
- **Retention**: Rewarding continued participation and loyalty aids in maintaining user engagement over time. Incentive programs, including vesting schedules, bonuses for holding on to investments long-term, or rewards for regular participation, motivate users to remain actively involved with the project.
- **Price Support**: Although not the main focus of many projects, incentive programs can indirectly uphold the token's price. They can increase demand via utility or rewards and decrease velocity as tokens are retained for staking or earning rewards.


## Different Types of Incentive Programs
Incentive programs can take various forms, depending on the goals of the ecosystem and the behaviors they aim to encourage. Here are four common types:

### Liquidity Mining

Liquidity mining is a pivotal incentive program in the DeFi ecosystem. Users, often referred to as liquidity providers (LPs), deposit their assets into a liquidity pool, which facilitates decentralized trading, lending, or borrowing. In return for their contribution, LPs earn rewards, usually in the form of additional tokens from the platform. This not only incentivizes users to provide liquidity but also aligns their interests with the ecosystem's success. A good example is [Uniswap,](https://uniswap.org/) where users can earn UNI tokens by providing liquidity to various trading pairs.

### Staking Rewards
Staking is another incentive program, especially in proof-of-stake (PoS) and DeFi projects. Users lock up tokens as a form of *"staking"* to participate in network operations, such as transaction validation or governance. In exchange, they receive staking rewards, which are typically a percentage yield of the tokens staked. This system not only secures the network and ensures a decentralized governance structure but also encourages users to hold onto their tokens, reducing market volatility. [Cardano (ADA)](https://cardano.org/) and [Polkadot (DOT)](https://coinmarketcap.com/currencies/polkadot-new/) are examples of networks that offer staking rewards to incentivize network participation and security.

### Airdrops
Airdrops are a direct distribution of tokens to users' wallets, often used as a marketing strategy to increase awareness and distribute tokens widely. They can target existing users of a platform, holders of a specific token, or participants who perform certain actions, such as signing up for a newsletter or joining a community. Airdrops are effective for bootstrapping new token projects, rewarding loyal users, or even driving the decentralization of token ownership. Snapshot-based airdrops reward existing holders, while task-based airdrops require participants to complete specific actions.

![26857153_7194075.png](https://strapi.suprabit.eu/uploads/26857153_7194075_5a88cae3d6.png)

### Community Management and Engagement
This type of incentive program focuses on building and maintaining an active and engaged community. Rewards are given for contributions that benefit the community and project, such as content creation, bug reporting, social media promotion, and active participation in forums or chat groups. Platforms like [Galxe ](https://blog.galxe.com/galxe-loyalty-points-system-redefining-web3-loyalty-programs-135a159dcb4c) offer infrastructure to manage these types of incentive programs by tracking contributions and distributing rewards. Another example is [Zealy](https://zealy.io/), which focuses on rewarding users for engagement activities within a project's ecosystem, highlighting the importance of community in the growth and sustainability of blockchain projects.

![pasted image 0 (1).png](https://strapi.suprabit.eu/uploads/pasted_image_0_1_78d138b8a6.png)

## Turning token projects into thriving ecosystems
Through incentive programs, Suprabit helps token projects to transform into flourishing ecosystems. We pride ourselves on tailoring each program to address the distinct needs of every project, guaranteeing not only immediate engagement but also the nurturing of long-term value and sustainability within the ecosystem. 

Through a combination of strategies, including liquidity mining, staking rewards, airdrops, and community engagement initiatives, your project can also foster a loyal and active community around its token.



large_blog ecxport.png

medium_blog ecxport.png

small_blog ecxport.png

thumbnail_blog ecxport.png

blog ecxport.png

Discover how to engage and retain your community in the Web3 space with effective incentive programs

Different Incentive Programs for Enhancing Web3 Project Engagement

Sauter introduced the[ Smart Sensor viaSens](https://www.sautersmartsensor.com/en) - an Internet of Things device that transcends conventional sensing capabilities and takes monitoring to the next level. By tracking key parameters such as temperature, humidity, air quality, motion, brightness and sound pressure level, the Smart Sensor provides invaluable data. This wealth of information is harnessed to empower automation and control systems, resulting in smarter and more responsive office spaces that cater to users' needs. This product is the result of a great collaboration with our Swiss-based partner [SAUTER](https://www.sauter-controls.com/en/), a premier Smart Building Automation manufacturer with a global presence. 

What sets this device apart is its incorporation of BLE Mesh technology, facilitating seamless communication among devices. The Smart Sensor isn't just a leap forward in sensor technology; it's a game-changer in creating interconnected, intelligent ecosystems for enhanced workplace experiences.


![smart-sensors.png](https://strapi.suprabit.eu/uploads/smart_sensors_f428a6fec2.png)

## BLE Mesh 

Bluetooth Low Energy (BLE) Mesh is a communication protocol crafted specifically for  Internet of Things (IoT) devices. This protocol extends the capabilities of traditional Bluetooth  Low Energy, paving the way for the creation of expansive, reliable, and secure networks.  Unlike traditional point-to-point Bluetooth connections, BLE Mesh allows devices to form a mesh network, enabling data to flow seamlessly through the network, extending both the range and the overall coverage. 

Key features of BLE Mesh include low power consumption, robust, mandatory security mechanisms, and strict adherence to Bluetooth SIG standards. These qualities collectively make BLE Mesh a powerful solution for constructing interconnected wireless networks, opening new possibilities for diverse IoT applications. 

Within this network topology, we employ a sophisticated structure featuring a primary node known as the gateway, alongside up to 15 interconnected nodes that communicate through  Mesh technology. The gateway plays a pivotal role as it acts as the bridge connecting the sensor nodes in the network to the vast realm of the Internet. It stands out with its MQTT  capabilities, assuming responsibility for the subsequent transfer of data. 

Each node in this intricate setup serves a unique purpose - collecting valuable data and establishing communication channels with the gateway. Direct communication occurs if nodes are within range, while a relay node facilitates communication when direct interaction is not feasible. This strategic architecture ensures efficient data flow and a robust network,  exemplifying the power and versatility of the BLE Mesh network design.

![network-topology.png](https://strapi.suprabit.eu/uploads/network_topology_c99f98c12e.png)

## Wireless (OTA) Update 

Over-the-air (OTA) update represents the wireless delivery of new firmware to embedded devices. This transformative technology empowers manufacturers and developers to enhance device functionality, address bugs, and fortify security - all without the need for physical access to the device. 

In a landscape where thousands of Smart Sensor devices adorn ceilings within a single building, the impracticality of manual physical updates is evident. The wireless update approach not only streamlines maintenance but also minimizes downtime, contributing to an enhanced overall user experience. 

However, implementing this feature posed a challenge as only the gateway had fast Ethernet connectivity, leaving other devices without direct access. The key question was how to initiate updates. Despite the nodes lacking Ethernet connectivity, a clever solution emerged - upon receiving a trigger, the BLE mesh nodes could activate their Wi-Fi capabilities. Leveraging their additional functionality of iBeacon advertising and scanning, we opted for a custom-made iBeacon packet as the trigger. A mobile app then became the initiator, serving as the primary source for the new firmware and orchestrating the entire OTA update process temporarily over WiFi.

![ota-update.png](https://strapi.suprabit.eu/uploads/ota_update_0571db4537.png)

## iBeacon

iBeacon is a location-based service pioneered by Apple that harnesses Bluetooth Low  Energy (BLE) for proximity sensing, indoor navigation, and context-aware applications. 

The iBeacon packet format usually consists of three integral components: UUID, Major and  Minor values. When combined, these components form a unique identifier for each iBeacon.  As a Bluetooth device enters the range of an iBeacon, it interprets the UUID, Major and  Minor values, enabling applications to trigger location-specific actions or provide context-aware information to the user, as SAUTER uses it for Mobile Building Services. 

The Smart Sensor also integrates iBeacon technology, allowing users to enable or disable iBeacon advertising. But regardless of the advertising status, iBeacon scanning on the device is always active to receive the initiating OTA updated trigger. 



## Mobile Application 

<video loop="loop" autoplay="autoplay" muted style="width: 100%;">
  <source src="https://strapi.suprabit.eu/uploads/mobile_app_5d75341fe8.mp4" type="video/mp4">
</video>

In collaboration with Sauter, we designated the mobile app as the central hub provisioning the sensor network and the primary initiator performing the OTA updates. Functioning as a server housing the latest firmware versions in binary files and also as a mobile hotspot with a predefined SSID and password, it allows sending triggers and facilitating the OTA process on the devices. 

Within the app, users first need to select the Mesh network for updating nodes and then choose the firmware version they would like the devices to update to. Users have the flexibility to choose any available version, with the caveat that updates will only occur when transitioning to higher firmware versions than those currently on the device. 

Upon making these selections, the app prompts users to enable the mobile hotspot with a predefined SSID and password. Clear instructions for enabling the hotspot are provided for both Android and iOS users. Once the hotspot is active, the app starts broadcasting the beacon packet. This signal triggers the OTA update on devices within range and of interest. Upon receiving the beacon signal, the Smart  Sensor undergoes a series of checks. The update will only proceed if the received network ID matches the one under which the device was provisioned, the firmware version is higher than the current one, and the hardware index aligns with the device's hardware index. Subsequently, the device activates WiFi, establishing a communication link with the server. After starting the OTA update the Smart Sensor will display appropriate animation and reboot. 

![orange.gif](https://strapi.suprabit.eu/uploads/orange_af53966f82.gif)

## Fallback Mechanism 
When the OTA update is initiated, the device temporarily halts all its regular functionalities to ensure a smooth and uninterrupted update process. In the rare event that an issue arises during the update, a safety mechanism is activated by triggering a safe reboot, effectively reverting the Smart Sensor to the previous firmware version. 

To provide users with visual feedback in case of an unsuccessful update, a distinctive animation would be displayed. This serves as a clear indicator, enabling users to promptly identify and address any issues that may have occurred during the update process. If everything goes smoothly, the Smart Sensor viaSens reboots with the new firmware.

![red.gif](https://strapi.suprabit.eu/uploads/red_10c9b9ee36.gif)


large_blog-cover.png

medium_blog-cover.png

small_blog-cover.png

thumbnail_blog-cover.png

blog-cover.png

The Smart Sensor viaSens, developed in collaboration with SAUTER, introduces a leap in IoT technology by incorporating BLE Mesh and iBeacon for seamless OTA updates via a mobile app, enhancing smart building automation with advanced sensing of environmental parameters. 

Effortless OTA Updates for BLE Mesh Devices  via Mobile App

There are so many books on design, helpful web tutorials, pricey workshops, and boring whitepapers. Yet, despite having access to all of that, we still come across poorly designed things all the time. Sometimes, even if you have a deep understanding of the theory and analyze all the metrics, you may still find yourself lacking the necessary tools or inspiration to create exceptional work. That’s why today, I've made a little cheat sheet that every Product designer can refer back to whenever they feel stuck.

It may not come as a surprise to most of you reading this, but I spend about 99% of my time in Figma. Figma has established itself as the gold standard for designing user interfaces, and with good reason! They offer excellent desktop apps for both Mac and Windows. Additionally, since many developers at Suprabit use Linux, Figma also provides a fantastic web application.

If you're just getting started with Figma, I suggest reading about some of its features. They can make your work a lot easier and faster. For example, the variables and new component property types that were rolled out last year have been such a time-saver for me.

Oh, and I can't forget about Figma plugins! Sometimes, I find myself spending too much time scrolling through the Community tab, searching for new plugins to try out. Lately, I've been particularly enjoying three plugins: "Mesh Gradients," "Ruri Pixels" (I hope I'm not using them too much!), and "Jitter." "Jitter" is a plugin that allows you to create stunning animations from your designs. In fact, I've even used it to create GIFs for some of my blog posts.

![Screenshot 2024-01-11 at 14.23.56.png](https://suprabit.eu/uploads/Screenshot_2024_01_11_at_14_23_56_2873bbfa97.png)

When it comes to colors and color palettes, my go-to tool is Adobe Color. It's a color wheel that you can use to create custom color palettes using nine color harmonies. And if I need something quick, my go-to is Coolors. It may not have as many features as Adobe Color, but it's a great tool for quick ideation.

![ScreenRecording2024-01-11at14.29.57-ezgif.com-video-to-gif-converter.gif](https://suprabit.eu/uploads/Screen_Recording2024_01_11at14_29_57_ezgif_com_video_to_gif_converter_2f25b8b733.gif)

Sometimes, I struggle with finding inspiration, and I believe this is something that every designer can relate to. When I experience a lack of inspiration or want to see how others have tackled a similar problem, I typically turn to platforms like Dribbble and Behance. In my opinion, if you're seeking UI/UX inspiration, Dribbble is the best option, although I usually browse both. If I'm really stuck, I spend some time scrolling their Popular/Discover pages until inspiration strikes.

![Screenshot 2024-01-11 at 14.27.49.png](https://suprabit.eu/uploads/Screenshot_2024_01_11_at_14_27_49_30b6d59fe9.png)

I must also mention Designspiration. While you may not find much UI/UX inspiration there, you'll come across a ton of great designs that could inspire you to reconsider your approach to the problem you're trying to solve.

Last but not least, I always keep a writing pad and a black pen on my desk for quick sketching of wireframes or ideas. While I know I can do it quickly in Figma, there are still times when using pen and paper is better and faster. And trust me, the paper has to be dotted!

All of these tools help me achieve the best results, whether it's for designing a UI/UX for an application or creating a quick and entertaining product showcase video. Is there any tool that you use that I might have overlooked?

large_thumb.png

medium_thumb.png

small_thumb.png

thumbnail_thumb.png

thumb.png

Forget about dull design books, web tutorials, expensive workshops, and tedious whitepapers. This article has everything you need to overcome an artist's block as a product designer. Dive in!

How To Get To a Great Design? Tips From a UI/UX Designer

As we step into 2024 with new resolutions, our team has been reflecting on the technologies that are poised to make a significant impact in the coming year. Among various innovations, Artificial Intelligence (AI) and Blockchain have particularly captured our attention. Let's explore what the future may hold for these transformative technologies.

## **Blockchain: Paving the Way for a Decentralized Tomorrow**

Several team members are enthusiastically shifting their focus towards Blockchain technology. They recognize its potential beyond cryptocurrency and envision Blockchain as a key player in creating secure, efficient, and transparent systems across various sectors. In 2024, their dedicated efforts will be focused on enhancing their full-stack development skills, with a particular emphasis on mastering design patterns relevant to Blockchain and other emerging technologies.

![BlockchainAgency2024.png](https://strapi.suprabit.eu/uploads/Blockchain_Agency2024_545999260a.png)

## **AI: The Vast Realm of Possibilities**

When we asked one of our team members what he thinks, he simply replied with "AI stuff". The term "AI stuff" may sound simple, but it represents Artificial Intelligence's immense and mostly unexplored potential. Our team sees AI not just as a tech trend but as a game-changer in the making. From making everyday tasks easier to tackling complex challenges, AI is set to revolutionize our workplaces and daily lives. The real challenge and opportunity lie in turning theoretical AI concepts into practical and impactful business solutions. We're jumping on the bandwagon by providing our partners and clients with personalized AI experiences tailored to their business needs.

![AISolutionsAgency2024.png](https://strapi.suprabit.eu/uploads/AI_Solutions_Agency2024_02be6f5d17.png)

## **AI and Blockchain: The Dynamic Duo of 2024**

The merging of AI and Blockchain technology is something that really gets us excited. The amazing analytical capabilities of AI have the potential to greatly improve the security and efficiency of Blockchain networks. On the other hand, Blockchain can provide a strong and transparent foundation for applications driven by AI. With the growing regulation and popularity of cryptocurrencies, we think that 2024 could be a big year for the widespread use of these technologies, changing the way we interact digitally and the overall tech scene.

![BlockchainAISolutions.png](https://strapi.suprabit.eu/uploads/Blockchain_AI_Solutions_b0977e70e8.png)

As we welcome 2024, these insights not only showcase our excitement for the future but also demonstrate our dedication to remaining at the cutting edge of technological advancements. If you're looking to enhance your business with innovative AI or Blockchain solutions, don't hesitate to reach out. Send us a message through our [contact form](https://suprabit.eu/contact), and let's explore how we can propel your business into the future together.

large_Trends in 2024.png

medium_Trends in 2024.png

small_Trends in 2024.png

thumbnail_Trends in 2024.png

Trends in 2024.png

Discover the Future of AI and Blockchain in 2024! Our team shares insights on Blockchain's role in creating decentralized systems and AI's untapped potential in transforming businesses and daily life. We also explore the exciting synergy between AI and Blockchain and how this powerful duo can enhance digital security and efficiency.

AI & Blockchain in 2024: Embracing the Future

## Introduction to ESP32 and ESP-IDF Framework

The ESP32 is a popular series of low-cost, low-power microcontrollers with integrated Wi-Fi and dual-mode Bluetooth. These microcontrollers have gained popularity in the IoT world due to their robustness and cost-effectiveness.

To complement the hardware, Espressif developed the ESP-IDF (Espressif IoT Development Framework), a software development framework for the ESP32. ESP-IDF offers tools and libraries to efficiently develop applications for the ESP32 hardware, but perhaps the most crucial aspect of ESP32 and ESP-IDF is their approach to memory management.

The ESP32 microcontrollers feature both internal and external memory options, with internal memory being limited and precious. Managing this limited resource efficiently is key to ensuring smooth and reliable operation of applications, particularly in embedded systems where memory constraints are always a concern.

## Memory Management Challenges in Embedded Firmware

Memory management in embedded systems like ESP32 is a complex task. A typical issue revolves around the allocation and use of Internal RAM (IRAM) and External RAM (SPIRAM -external flash memory).

### Case Study: Troubleshooting Reboot Issues

My journey into memory management challenges began with a peculiar case where a network of ESP32 devices in an office setup experienced repeated reboots. The network consisted of one gateway (GW) and three nodes. Despite various firmware updates and fixes, the GW began to experience reboots with various errors, mainly stack overflows in certain tasks. Other issues were reports of corrupted flash memory and sudden device resets caused by a Watchdog Timer (WDT):


#### Memory leak 
The biggest problem I was dealing with was a nasty memory leak. I discovered it in the first place by monitoring individual task CPU and memory usage. A certain task that the device uses to display custom LED animations was handling new animation data incorrectly. Freeing of memory allocated for animation data was not handled properly and this would eventually cause the system to reboot. I only became aware of this after executing longer tests which periodically sent animation data to this task. 

#### Internal RAM limitations
While monitoring memory usage on the system, we've also observed that the ESP32's internal RAM was nearly exhausted, with about 98% usage. This was particularly concerning since essential functions and interrupt service routines (ISRs) are typically stored in IRAM for faster access. (IRAM also stands for Instruction RAM and should not be mistaken for Internal RAM -see picture). However, by examining data statistics it showed that I have ample Data RAM (DRAM) to use and this hinted to a possible solution.

![](https://lh7-us.googleusercontent.com/A26ZobJLdyh33dpst1Y56hA_0jQF2iqgQ4-UH5RagsXKyfNTMl_KYgV_Tg1NCfAO-9jEjErj26VUxG1sMatoiElNQcdZsgY0D_QhDHdZ45giMx43Dr7FMkf_Ad6xGfrpjH4x98p9oNRIYjlnDBE7hZQ)

#### The Watchdog (WDT) Conundrum
What frustrated me the most were sudden system resets caused by WDT. The device would just reset itself without a crash and therefore without any clue where the bug originated from. I only knew upon reboot that a WDT triggered a reset on the PRO CPU core of the device.

The ESP32 features two watchdog timers (WDT) for each of its CPU cores to ensure the system resets in case of a failure. However, in this case, the WDT reset always occurred on the PRO CPU, indicating a potential issue with task scheduling or interrupt handling.

I deduced that the APP CPU was stuck in a cache error case. Reboots were caused by a "cache disabled" error. By doing some research on the web, I found that this issue occurs typically when there is some sort of concurrent flash memory access. By force printing of logs before the WDT reset occurred, I managed to get some backtrace showing that the BLE MESH stack (feature of esp-idf) was storing message replay parameters into Non-Volatile Storage (NVS -part of main flash memory). 

I could also see that a certain timer interrupt handler was invoking a function FreeRTOS function xQueueSendFromISR() that is supposed to be safe for calling within interrupts marked with IRAM_ATTR flag (stored in instruction memory for quick access and execution of interrupt handlers) but clearly in some way accesses the flash memory. My theory is that this leads to triggering the panic handler which disables all watchdogs except for the system watchdog and subsequently reboots the device.


#### The Corrupted Flash Issue
I had an issue where the flash memory of the device was getting corrupted rendering the device unusable until you performed erasure of flash memory. It occurred rarely and only on a few devices, but the issue was a serious risk in mass production. Some investigation led me to believe this was a somewhat known issue with a particular series of flash memory chips, produced by XMC, which came with some of ESP32 boards installed in devices. For some reason, even Espressif did not manage to find that the flash chip can unpredictably receive random commands with a chance of disabling the normal functioning of the chip.


### Lessons Learned and Solutions

**Stopping a memory leak**

To effectively resolve the issues with the task of handling LED animations, I had to fundamentally re-evaluate and refine its underlying logic. My primary objective was to establish a foolproof system where all dynamically allocated resources were meticulously tracked and appropriately freed upon task completion.

Originally, my approach to managing shared resources between two asynchronous tasks involved the use of static pointers. While this method provided a means of resource sharing, it inadvertently introduced vulnerabilities, particularly in the form of memory leaks. These leaks occurred due to the inadequate tracking and releasing of the allocated resources, leading to gradual accumulation and eventual system instability.

I shifted my strategy to leverage the FreeRTOS xQueue to address these shortcomings. This change represented a significant improvement in communication management and resource sharing between tasks. The xQueue, a robust queue management feature provided by FreeRTOS, offered us a more structured and reliable way to pass data between tasks. This method not only facilitated better control over shared resources but also helped in systematically tracking and releasing dynamically allocated memory.

By implementing the xQueue, I could ensure that every allocation was properly accounted for and deallocated at the appropriate time. This approach effectively sealed the memory leak, enhancing the stability and reliability of the task. T

**Reducing Internal RAM Usage**

I was already using the feature where memory for dynamic allocation with **malloc()** can be allocated from SPI RAM (Serial Peripheral Interface Random Access Memory). SPI RAM is an external memory module interfaced through the SPI bus, expanding the available memory beyond the ESP32’s internal capacity. This type of RAM is especially useful for handling larger or more memory-intensive applications that exceed the capabilities of the microcontroller's onboard memory.

To make effective use of this expanded memory resource, I had to adjust the maximum **malloc()** size for allocating memory in internal RAM. By doing so, I ensured that more memory allocations would utilize the abundant external SPI RAM instead of the limited internal memory.

Configuring ESP-IDF options to minimize IRAM (Instruction RAM, used primarily for storing executable code and critical functions) usage also proved to be an effective strategy. This approach helped in preserving the valuable IRAM space for essential executable code and ISR (Interrupt Service Routine) handling, while larger and less critical data could be stored in the expansive SPI RAM.

By implementing these changes, I increased the availability of Internal RAM and reduced the risk of exhausting internal memory resources. This adjustment has been crucial in maintaining system stability and efficiency, particularly in scenarios where memory demand is high.

![Diagram.png](https://strapi.suprabit.eu/uploads/Diagram_2e245b02ed.png)

**Escaping watchdog reboots**

In this scenario, I addressed the issue of unexpected system resets triggered by the Watchdog Timer (WDT) by implementing a strategic change in how the timer interrupt handler operates. The key to resolving this was preventing the timer interrupt handler from executing while the cache was disabled. This adjustment was crucial because the cache disabled errors were leading to system instability and triggering the WDT resets.

The solution involved modifying the interrupt flag associated with the timer interrupt handler. In the ESP-IDF framework, when you add an interrupt handler, you specify certain flags that define its behavior and priority. Initially, my interrupt handler was using the **ESP_INTR_FLAG_IRAM** flag. This flag indicates that the interrupt handler is located in IRAM (Instruction RAM) and is safe to execute when the flash cache is disabled. However, this setup contributed to the WDT reset issues I was experiencing, likely due to conflicts arising from cache disabling.

To mitigate this, I changed the interrupt flag from **ESP_INTR_FLAG_IRAM** to **ESP_INTR_FLAG_LOWMED**. This flag sets the priority of the interrupt to a level that is between low and medium. By doing so, I reduced the priority of the timer interrupt handler, ensuring that it does not interfere with critical operations or run when it's unsafe to do so - during periods when the cache is disabled.

**Flash Memory Stability**

To address the problem of XMC chips causing the flash memory to experience corruption, Espressif's support team provided a solution in the form of a firmware vendor patch. This patch locks the Status Register permanently or until power-cycle effectively preventing the setting of write protection, countering the source of the error. Even if the flash chip receives random commands in the future, it can no longer lock itself.

The XMC flash memory chip has three 8-bit wide status registers (SR1, SR2, and SR3) that can be set. I opted for disabling write protection until power-cycle by setting the bits SRP1 in status register 2 to "1" and SRP0 in status register 1 to "0".  These Status Register Protect bits are one-time programmable (OTP) bits. With this strategy, you prevent the memory chip from setting write protection during runtime, but still leave the option to write to the status registers if the need arises.

## Conclusion

Managing memory in embedded systems like ESP32 requires a careful balance between performance and resource utilization. The ESP-IDF framework provides the tools and flexibility to optimize memory usage, but it demands a thorough understanding of the underlying hardware and software interactions. My investigation into the reboot issues not only resolved specific problems but also provided valuable insights into effective memory management strategies in embedded firmware development.



medium_Neki cipovi.png

small_Neki cipovi.png

thumbnail_Neki cipovi.png

Neki cipovi.png

Explore IoT firmware development with a focus on ESP32 and ESP-IDF framework. Tackle memory management in embedded systems and resolve reboot issues, memory leaks, and flash memory stability in ESP32 devices. Key topics include IRAM, SPIRAM, FreeRTOS, and WDT handling.

Investigating Memory Management Challenges in Embedded Firmware: ESP32 and ESP-IDF Framework


Hey there!

Just a short note before the introduction: when I first started writing this blog post, I was going into great detail about each screen in the application. Then, I realized that might be a bit dull for you to read. After all, there are tons of case studies out there that cover similar topics. They probably do a better job than I could hope to so I decided to change my focus. As a result, I present to you the challenges we faced during the project.

In the end, I didn’t even talk about the application much. Maybe I’ll have to write another post. 🤷‍♂️ Nevertheless, hope you enjoy reading this one!

![different smart sensors](https://strapi.suprabit.eu/uploads/Smart_Sensors_d1277e86e2.png)

<br/><br/>

## The rise of smart sensors

In the era of rapid digital transformation, the integration of smart sensors in buildings has revolutionized various industries. These sensors enable real-time monitoring of occupancy, energy consumption, air quality, and security. They optimise resource utilization, enhancing comfort, and improving overall building efficiency.

These intelligent devices provide valuable data insights and automate processes, leading to better efficiency and decision-making. However, the seamless deployment and management of smart sensors require a well-designed provisioning* app that technicians use to set them up.

**For those who are not familiar - in the context of smart sensors, provisioning refers to the process of configuring and setting up a sensor for its intended purpose and network connectivity. In most cases, sensors can be edited or reconfigured after they have been provisioned.*

<br/>

## Collaboration and synergy

The embedded team at Suprabit was already working on the firmware for the Smart sensor. During this time, our client, a Swiss-based smart building premier solutions provider, recognized a need for a user-friendly provisioning app. This app would help their technicians deploy and manage smart sensors easily. As a result, they asked us to design and develop a mobile app.

![best IOT team](https://strapi.suprabit.eu/uploads/best_IOT_Team_b0b9846ec6.png)


We embraced the challenge and took a unique approach to the development process. We designed and developed both the application and the firmware in the same team. This is, unfortunately, often not possible with IoT devices, since oftentimes different agencies work on firmware, application and design. But, the ability to approach the design and development of the app alongside the firmware team proved great. We had a thoughtful and iterative design process by keeping apps and firmware teams in sync.

<br/>

## Team effort

Since we were already working on multiple projects before, our tight-knit team had excellent synergy, aiding frequent collaboration and problem-solving.

This allowed us to address technical questions about hardware or firmware quickly and efficiently. Either by turning to a team member or through a short Discord call if we were working remotely. During the design and development process, we used a highly iterative approach. To ensure a great provisioning experience for users, we needed to adjust the firmware code to incorporate design and application improvements. We also had to adjust the application and design to accommodate firmware improvements.

By working together so closely and having instant feedback, we were able to make the best design choices. In the end, we created a high-quality, user-friendly provisioning app that met our client’s needs and exceeded their expectations.

> Through this synergy of different fields, we were able to create a provisioning process that neither application developers, firmware developers nor designers could come up with on their own.

<br/>

## Don't ignore UX

There's this thing that infuriates me about applications that are highly specialized and made for a specific audience. More often than not, they completely overlook the importance of user experience. It is usually assumed that they can simply refer to some kind of manual or figure out how the process is working by trial and error - it’s not like they can switch and use some other application.

From the get-go, we believed that applications should always be easy and enjoyable to use, regardless of the user or number of users. The app's entire process should be understandable from the moment it is first opened. In fact, we aimed to make the app so intuitive that the process would be understandable from the first time you open the app.

![Smart Sensor Mobile App Screens](https://strapi.suprabit.eu/uploads/Smart_Sensor_Mobile_App_Screens_656920a924.png)


<br/>

## The early stages

In the early stages, we focused on iterating rapidly, emphasizing user experience (UX) over polishing the user interface (UI). This approach allowed us to identify potential issues early and make necessary adjustments. This turned out great because there were numerous changes during this process. By not spending time on UI, we were able to move faster and more efficiently.

Our approach to the development process was highly iterative. We mock-tested bad designs early on, which allowed us to identify and rectify potential issues before spending too much time polishing the UI. This approach proved to be highly effective, and we moved faster and more efficiently toward a user-friendly application.

Throughout this period, all teams communicated constantly about the possibilities and limitations of sensor hardware and application. This was a crucial step, as it allowed all the teams to work as one big team and understand the possibilities ahead of us.

With the goal of ensuring simplicity and error-proofing, we designed the provisioning process to be as seamless as possible. Our foremost objective was to prevent technicians from accidentally locking the sensor with the wrong configuration.

Unfortunately (or luckily, regarding who you ask), we couldn’t just “copy” a UX/UI design for provisioning from Behance or Dribble because no one had done anything similar before.

<br/>

## My Precious: The LED ring

The first step in designing the provisioning process was to determine the hardware's possibilities and limitations.

The first obstacle we encountered is that sensors are typically set up in two steps by two people. First, they mount and power them on, and then they provision them.

The issue here was identifying the sensors in the app during the second step. With multiple unprovisioned sensors on the same floor, the technician needs to make precise identification of the sensor they plan to provision.

After consideration and brainstorming, we came to the conclusion that sensors should advertise their unique ID in the wild until provisioning is over. The app catches the ID and assigns a color to each sensor. The, LED ring on the sensor displays the assigned color to the technician in real-time.

![Different LED sensors](https://strapi.suprabit.eu/uploads/Smart_Sensor_Design_4bddc7ff14.gif)



This makes identifying the sensor easy, showing the technicians where the sensors are located on the ceiling. This ensures that the states in the app and in the real world are consistent.

This solution seems obvious now, but it was a crucial step in designing a user-friendly provisioning experience.

<br/>

## The Locking Puzzle: The provisioning process

### The problem

The next issue we stumbled upon was the locking of the sensors. Instead of sending their data through Wi-Fi or Ethernet (eliminating the need to set up cables or access points throughout the building), the sensors create a Bluetooth mesh network that transmits data to the gateway sensor that's connected to the internet.

Since sensors are provisioned into a Bluetooth mesh, the app can only communicate with them via Bluetooth during provisioning. Once the process is complete, they begin using Bluetooth to communicate with other sensors in the same mesh network. 
If there's an incorrect configuration, someone has to manually hard reset the sensors by pressing a device button. This is never ideal, especially when sensors are mounted on a high ceiling in a commercial space.

Through this process, a backbone of the design was created: a four-step provisioning process.

<br/>

### The process

Once a project (such as a single building) has been created, technicians can create networks for sensors to communicate on. These networks can be created per floor, or according to the client's requirements.

![Designing smart sensor provisioning process](https://strapi.suprabit.eu/uploads/Smart_Sensor_Provisioning_39bba5183d.png)



1. The first step to provisioning sensors is selecting the one you wish to provision. The application displays all unprovisioned sensors in the surrounding area. Each sensor has a unique color to aid the technician in selecting the correct sensor based on real-world data.

2. The following step prompts the technician to stand beneath the sensor. This step is crucial to ensure the strongest possible connection with the sensor.

3. After confirming their position, an animation will begin that is visible both in the app and on the real-world sensor. This step is essential to ensure the provisioning of the correct sensor. While this may seem unnecessary, we want to empower technicians to be certain in their actions and minimize any potential for errors.

4. In the final step, the user can add configuration for the selected sensor.

<br/>

## Designing with intent

For the provisioning process, we designed an icon for the smart sensor that changes color based on the color of real-world sensors. In the initial designs, we were just using simple colored circles to represent sensors. At first glance, this “illustration” may seem over-complicated. However, in initial tests, we noticed it allowed first-time users to make a stronger mental connection between the physical sensor and its representation in the application.

![Designing different smart sensors](https://strapi.suprabit.eu/uploads/Designing_different_smart_sensors_476b729dd7.gif)



Sometimes we want to abstract real-world elements to their bare minimum, simplifying them to basic shapes or symbols. However, the experience we had with the smart sensor icon reminds us of the importance of designing with intent. It highlights the significance of considering the users' cognitive processes and their ability to make connections between physical objects and their digital representations. By intentionally designing icons or visual elements that align with users' mental models and facilitate comprehension, we enhance user experiences and foster a deeper understanding of the system or product. This emphasizes the value of purposeful design decisions that prioritize user engagement over mere visual aesthetics.

<br/>

## Language is also design?!

Once one or multiple sensors have been configured, they must be provisioned into a Bluetooth mesh. In this step, we learned a valuable lesson about thoughtful design and language's impact on user interactions. The irreversible nature of provisioning sensors into the network posed unique challenges which made careful consideration essential.

We firmly believe that good design goes beyond just aesthetics; it extends to the words we choose to communicate with users. The terminology used can profoundly impact how users perceive and navigate an application. Hence, we dedicated time to ponder the best way to name each action during the provisioning process.

For those not familiar with the context, provisioning refers to configuring and setting up a sensor for its intended purpose and network connectivity. 

Unlike most cases, our sensors couldn't be edited or reconfigured once provisioned, which led us to avoid using the term "Provision" altogether. We were mindful not to introduce any connotations that word might have with technicians and cause confusion. Instead, we adopted "Configure" to signify the initial setup of sensors, and "Lock" for the actual process of provisioning them into the network.

To remove any confusion, we even went a step further and displayed the word "Lock" only on the popup window informing the user about the consequences of the action they were about to perform, and used a lock icon on the button.

<br/>

## Rethinking Symbolism

However, we soon realized that our approach had unintended consequences. The term "Lock" and its icon on the button created confusion among our initial test group. The symbolism of the lock did not represent a clear action. It didn't align with the actions technicians were accustomed to, and many of them forgot to press it. This left the provisioning incomplete. Despite explanations, they frequently missed the step, making it clear that the process wasn't intuitive enough.

Recognizing the need for a different approach, we decided to revamp the buttons. Instead of the lock icon, we introduced a clear "Finalize Provision" button. By incorporating a term familiar to technicians, the significance of finishing the provisioning process became more evident, and as a result, their memory lapses ceased to be an issue.

![Locking nodes process BLE Mesh](https://strapi.suprabit.eu/uploads/Locking_nodes_BLE_mesh_78f479c5ad.gif)



This experience taught us the immense importance of user-centric design. By understanding the specific context and needs of our users, we were able to craft a more intuitive and seamless provisioning process. It reinforced our belief that language and design must work harmoniously to create a truly user-friendly application. Through constant iteration and a willingness to learn from feedback, we successfully transformed a potentially confusing experience into a smooth and efficient one for our users.

<br/>

## Conclusion

In conclusion, the process of designing a smart sensor provisioning app not only taught us the significance of collaboration and user-centric design but also highlighted the profound impact of intentional language and iconography. By addressing challenges proactively and focusing on delivering a seamless and enjoyable experience, we successfully crafted a high-quality, user-friendly app that surpassed expectations. As technology continues to evolve, the lessons from this journey will undoubtedly serve as a strong foundation for future endeavors in designing innovative and user-centric applications.

SmartSensorMobile.gif

Step into the journey of developing a smart sensor provisioning app, as we shed light on the intricate design process, the critical role of user-centric design, and how collaboration led to an app that exceeded client expectations. A compelling case study for tech enthusiasts, app designers, and IoT professionals alike.

A Journey Through Designing a Smart Sensor Provisioning process: Bluetooth mesh

At first, the transition seemed scary since the two fields appeared to be worlds apart. However, as I delved deeper, I realized that embedded and mobile development share more similarities than I initially thought. So, let's explore how these two fields intersect and the skills you can use to excel in both.

# Things in common:

## Hardware limitations

Embedded developers are accustomed to working in a resource-constrained environment where every byte of memory and every clock cycle counts. This not only helps in writing efficient and optimized code but also develops a valuable skill set that can be leveraged in mobile development. Similarly, mobile development also requires optimizing battery life and processing power, making the transition from embedded to mobile development easier.

## Debugging skills

Debugging skills are essential for any type of software development. While there are several debugging tools available, such as logic analyzers or JTAG, what separates the experts from the novices is their methodical and analytical way of thinking, combined with patience and focus. A great developer can navigate through the maze of code, identifying and resolving issues efficiently and effectively, regardless of the technology.

## Knowledge of hardware interfaces

As an embedded developer, understanding hardware components and configurations is necessary for dealing with real-time issues. Power optimization is a key objective, given that embedded devices often rely on battery power. Similarly, mobile developers need to understand hardware configuration to troubleshoot communication failures and connectivity issues. Also, battery-related issues can bring down mobile applications, and knowledge of power optimization is essential to help track and resolve battery-related issues, as it can be the difference between a successful or underperforming app. 

## Handling interrupts and callbacks

Handling interrupts is common in embedded development, where a single device can handle multiple events, such as timers, buttons, and sensors. Since every interrupt is important and any of them can happen at any time, it is essential to have strong knowledge and a deep understanding of how to handle them properly. In mobile development, user inputs are handled as interrupts. Therefore, experience in embedded development is useful in learning how to handle user events in the mobile app properly. 

Callbacks are another fundamental concept in embedded development, where they can be categorized as synchronous and asynchronous. Mastering callback handling enables developers to manage events more effectively. In mobile development, asynchronous programming is crucial since most of the user interrupts in the mobile app are event-based.

# Biggest differences:

## UI

The focus of embedded development is creating software that integrates with the system hardware. Usually, the user interface on the embedded device doesn't exist and the user can interact with the device through small screens or buttons. However, in mobile development, creating an intuitive and appealing user interface is a focused aspect of the development process. As mobile applications heavily rely on user interaction, designing a user-friendly interface is key to delivering an enjoyable user experience.

## Devices

Embedded development focuses on designing and creating software that runs on one specific device, usually having a resource-constrained environment. Most of the embedded devices are very different so the software can be used only on the device that it's made for. On the other hand, mobile development is focusing on creating software that can work on a range of devices with different hardware specifications. The user might have different devices with different screen sizes, resolutions, and processing power, so the software must be flexible enough to work on all of them. Mobile development requires more consideration of device compatibility, while embedded development can be more tailored to the specific device it's running on.

# Challenges I faced when learning mobile development

As an embedded developer, I started my career mainly using C and C++ programming languages. For mobile development, I used [JavaScript](https://www.javascript.com/) and [React Native](https://reactnative.dev/) which were unfamiliar territories. Learning a new language is always tricky at first, but as they say, practice makes perfect, and with every new task, I gained more experience and confidence in the language.

Another challenge was making an application that is working on both iOS and Android platforms. In the end, as an embedded developer, I was focused exclusively on hardware development, so there were a lot of interesting challenges with creating user interfaces. But hey, what's life without a little challenge, right? 

# Advice to embedded developers interested in learning mobile development

As always, start by focusing on the fundamentals of mobile development. Take a common framework like React Native and learn its syntax. Then, try your hand at developing a simple app like a memory game or notes app, where you can learn more about user interface and asynchronous programming. After that, give yourself a bigger challenge and make an app that uses multiple screens, databases or even a hardware integration like BLE. Remember, the best way to learn is through trial and error, so don't be afraid to make mistakes and learn from them.

In conclusion, don't let the differences between embedded and mobile development discourage you from exploring new horizons. Instead, see mobile development as an opportunity to expand your programming skills and add another layer of expertise to your repertoire. Many of the skills you've acquired as an embedded developer are transferable to mobile development, such as memory management, power optimization, and debugging techniques. Embrace this challenge and use your experience to your advantage. Good luck on your mobile development journey!

Learning JavaScript and React Native as an Embedded Developer

large_Embedded to Mobile.jpg

medium_Embedded to Mobile.jpg

small_Embedded to Mobile.jpg

thumbnail_Embedded to Mobile.jpg

Embedded to Mobile.jpg

Picture this: I'm an embedded developer who's used to working on exciting projects involving smart building management. But after some time, I decided to shake things up and venture into the world of mobile development. 

Embedded Developer's Guide To Transitioning To Mobile Development



<div style="width:70%; margin:auto;">
<h2> What are embedded systems? </h2>
Embedded systems are computer systems with a specific function within a larger system. This includes all computing systems, such as home appliances, digital watches, cameras, avionics, and medical devices, except for PCs and smartphones. When classifying embedded systems by their main computing component, two of the most common types are microcontroller (MCU) and a microprocessor (MPU/CPU) based systems. There are also DSP, FPGA and custom ASIC-based systems. 


Microcontroller-based embedded systems are typically programmed either without an operating system, known as "bare metal," or with a real-time operating system (RTOS). Microcontrollers are cost-effective, single-chip computers that include a CPU, memory, and input/output capabilities on a single integrated circuit (IC). However, their specifications are limited compared to standard PCs, with less than 1MB of RAM and less than 8MB of flash memory, and typically only one CPU core with a frequency of less than 500MHz. Many 32-bit microcontrollers today are based on ARM Cortex-M CPUs.

In contrast, microprocessor-based systems, which are based on more powerful CPUs such as ARM Cortex-A, run Linux and have specifications more similar to PCs or smartphones. These systems, known as single-board computers, feature RAM, eMMC (flash), and various peripheral chips on the board, rather than on a single IC.

![1.png](https://strapi.suprabit.eu/uploads/1_a622eb8f94.png)

While microcontroller-based systems are generally more affordable and energy-efficient than embedded Linux devices, they also have more limited computing capabilities and feature sets. This blog post will focus on the unique characteristics of microcontroller-based embedded systems. However, as part of the Internet of Things (IoT) ecosystem, modern embedded systems are expected to have a range of features such as wireless communication, internet connectivity, and advanced sensors and actuators, all while maintaining cost and power efficiency. Careful consideration of both hardware and software is crucial for the successful design and development of these devices.

<h3> Optimizing power consumption </h3>
When selecting components for a wireless embedded device, it is important to consider factors such as suitability for the intended application, software and community support, market availability and cost. The microcontroller, RF communication chip, and sensors/actuators are the main components to evaluate. Factors like deep sleep functionality, communication interfaces, security options, processing speed, and memory of the microcontroller should all be taken into account to ensure that the device's requirements are met in the most optimal way possible.

<h3>MCU</h3>
Low-power MCUs on the market can typically achieve current consumption below 1 μA in their sleep modes. Some of these include ST's STM32L0xx, Silicon Labs' C8051F98x, Microchip's SAM Lx and TI's MSP430.
In our recent project, we used STM32L051 MCU and in its Stop mode, we were able to achieve 1.3 μA with Low Power Timer and Watchdog running.



 ![Microchip.png](https://strapi.suprabit.eu/uploads/Microchip_a7739c6ed3.png)


<h3> RF communication chip </h3>
When choosing an RF communication chip, it's important to select an appropriate wireless communication protocol that takes into account factors such as power consumption, range, and throughput. Factors that will affect the power consumption of the device are protocol frequency (sub-GHz, 2.4 GHz, 5 GHz, etc.), data packet length, the number of messages being sent within a certain timeframe, and signal power. Operating frequency affects range, power consumption, and throughput. Lower frequencies (sub-GHz) have better range and lower power consumption, while higher frequencies have better throughput. It's essential to keep the number of messages sent within a certain timeframe as low as possible for battery-powered devices, usually 1-2 messages every 10+ minutes. Smaller data packet length increases the throughput and power efficiency of a protocol, as it takes less time to transmit information and keeps the RF transceiver in active mode. With greater power, the range is increased, but so is power consumption. Low-power RF chips on the market can typically achieve current consumption in the nA or few μA range in their sleep modes, making them a good choice for battery-powered devices. In our recent project, we used AX5243 sub-GHz RF chip at 868 MHz with a custom protocol. In its Powerdown mode, we were able to achieve 0.8 μA.

![2.png](https://strapi.suprabit.eu/uploads/2_d19cc36535.png)
When choosing sensors/actuators, their idle current consumption should also ideally be in nA or worst-case few μA range.

Besides hardware, software choices and optimizations can also greatly affect the power consumption of a device; choosing the appropriate sleep mode of the MCU and RF chip, minimizing time spent in running mode of the MCU and RF chip, using only the lowest-power MCU timer while the device is in idle mode, setting MCU peripherals in low-power mode, etc.



<h5>Here are some important takeaways from our recent project with STM32L051:</h5>
<div style="background-color: #1D3656; padding:10px; border-radius: 4px; width:70%; margin:auto;">

</div>

<div style="background-color: #1D3656; padding:10px; border-radius: 4px; width:70%; margin:auto;">
<ul style="font-size:16px;">
<li  style="color:#ffffff">setting all unused GPIOs as analog inputs has reduced average current consumption by a few μA</li>
<br/>
<li style="color:#ffffff">ADC needed to be powered off after each measurement, otherwise it would add ~35 μA to average current consumption in sleep mode </li>
<br/>
<li style="color:#ffffff">although Standby mode has the lowest current consumption, in this mode SRAM and register contents are lost and only certain GPIOs can wake up MCU, so we've used Stop mode</li>
<br/>
<li style="color:#ffffff">in Stop mode, LSI is the only oscillator that works (and only timers whose clock source is LSI can work</li>
<br/>
<li style="color:#ffffff">LSI is unprecise, but it can be calibrated using an internal MSI oscillator and more precise e.g. periodic interval measurements can be achieved</li>
</ul> 
</div>




Wireless embedded devices transmit data in periodic intervals and spend the rest of the time in sleep mode, which minimizes the amount of time the microcontroller and RF transceiver are running and consuming power. However, if the running time is too long, it can significantly impact the average power consumption and shorten the device's battery life. To optimize power consumption, it's important to keep the duration of running time to a minimum, whether due to a periodic interval or an interrupt.


<h5>Here are some methods that we've used to minimize the duration of running time: </h5>
<div style="background-color: #1D3656; padding:10px; border-radius: 4px; width:70%; margin:auto;">
<ul style="font-size:16px;">
<li  style="color:#ffffff">compiler optimizations</li>
<br/>
<li style="color:#ffffff"> removing printfs/serial outputs  </li>
<br/>
<li style="color:#ffffff">making sure there's no polling or register flag checking that keeps device in running mode</li>
<br/>
<li style="color:#ffffff">checking whether higher MCU frequency (with higher current consumption, but shorter processing time) is better for power consumption</li>
<br/>
<li style="color:#ffffff">using constants/hard coded values instead of calculations if possible</li>
</ul> 
</div>

It's important to select an RTOS mode that is optimized for low power consumption, especially as the number of features increases, as RTOS is often required in such cases.

Finally, tools that we've used to measure current consumption are Otii Arc and a multimeter (just to double-check Otii Arc measurements). Also, it's useful to have measurement ports on PCB for measuring the current consumption of certain components separately (MCU, RF transceiver, sensors).

![pic1.png](https://strapi.suprabit.eu/uploads/pic1_6e7794a3ee.png)


With whole PCB average current consumption being under 5 μA (idle mode consumption below 2.5 μA), these devices can ideally last on one e.g. CR2032 battery (~230 mAh) for more than 5 years.

<h2> Optimizing memory usage </h2>
As projects need to be profitable, prices of the components are very important. But with lower prices, MCUs usually also come with smaller amounts of RAM and Flash memory. For example, STM32L051 has 8 kB of RAM and 64 kB of Flash memory . As the complexity of the application increases and the feature set expands, optimizing memory usage becomes necessary for these microcontrollers.

<h5>Here are some methods of optimizing memory usage that we've used in our recent project: </h5>
<div style="background-color: #1D3656; padding:10px; border-radius: 4px; width:70%; margin:auto;">

</div>


<div style="background-color: #1D3656; padding:10px; border-radius: 4px; width:70%; margin:auto;">
<ul style="font-size:16px;">
<li  style="color:#ffffff">compiler flags</li>
<ul>

<li style="color:#ffffff; opacity: 70%;">we've used GCC's <span style="font-weight:bold">arm-none-eabi</span> toolchain: <span style="font-weight:bold">-ffunction-sections, -fdata-sections, -fno-exceptions, -fno-rtti, -Os, --specs=nano.specs</span> (for using nano version of newlib)</li>
</ul>
<br/>
<li style="color:#ffffff">check out functions with the highest memory usage and try to optimize them</li>
<ul>
<li style="color:#ffffff; opacity: 70%;">for <span style="font-weight:bold">arm-none-eabi</span> toolchain: <span style="font-weight:bold">arm-none-eabi-readelf -s elf_name.elf</span></li>
</ul>
<br/>
<li style="color:#ffffff"> disable unused RTOS features</li>
<br/>
<li style="color:#ffffff">remove unnecessary printfs</li>
<br/>
<li style="color:#ffffff">remove double and float arithmetic <span style="font-weight:bold">__aeabi_</span>functions if possible</li>
</ul> 
</div>



That wraps up this blog post on memory and power consumption optimization for microcontroller-based embedded systems. We hope it'll turn out to be helpful in your current and future embedded projects too!

</div>

large_IOT BLOG (2).png

medium_IOT BLOG (2).png

small_IOT BLOG (2).png

thumbnail_IOT BLOG (2).png

IOT BLOG (2).png

In this blog post, we'll explore various ways of optimizing power consumption and memory usage of wireless embedded devices with examples from one of our recent projects.

Optimizing power consumption and memory usage of wireless embedded devices


## Motivation
Modern Smart Building Management solutions are fairly complex, comprising of a number of software modules supporting a variety of, often proprietary, protocols. When you add in all the front and back-end devices, automation stations, sensors and gateways, it can all seem like a real pain in the neck. But there is a clear economic benefit as functional smart building solutions are able to optimize energy consumption, provide better living environments and better security for building occupants, bringing your business closer to achieving that net zero goal. However, there are new issues regarding data security popping up every day, due to complexity, Internet integration and, more often than usual, slow adaptation to the newest technology stack. Traditional solutions relied on private networks where security was not such a big deal, but now, as every smart building solution provider offers Internet connectivity, the security paradigm changed. That left most solutions vulnerable to inside and outside attacks as well as data breaches. On the other hand, with the advancement of the Internet, many new use cases emerged that have the potential to significantly improve the ROI of smart building management solutions and enable more building automation in favour of building occupants and investors.  

This presents an obvious need to introduce a new data infrastructure layer to your solutions that will guarantee data security and data availability within a smart building management market. 

## Lavsa
Lavsa is a decentralized storage solution for smart building management, developed using blockchain and IoT technology. Our solution is taking in a stream of data and then replicating that data to every node in a private blockchain network. The newly added data sets are hashed and the hash is published on permissionless public blockchains like Ethereum, Polygon etc. By using blockchain(s) as an additional layer of security, we are improving integrity, immutability and availability. This is a step up from the traditional database model because, in Lavsa, every piece of data is distributed across a number of nodes and additionally hashed on a public blockchain, making it virtually impossible to fake, change or delete the data. At the same time, smart contracts are used to improve data relevancy, white and black lists and support new use case scenarios.  




![blockchain.svg](https://strapi.suprabit.eu/uploads/blockchain_77fbf6c69c.svg)





## Lavsa Goals
- Put the building data security, integrity and availability at the forefront of the Smart Building and IoT initiatives
- Establish trust among stakeholders of the building automation projects
- Enable higher level of automation
- Support integration with third-party building automation and business solutions
- Enable new disruptive business models 
 

## Lavsa Use Cases

Lavsa puts the data produced by a variety of smart building devices at the forefront of the Smart Building economy enabling new disruptive business models like 
- Data monetization and data markets
- AI solutions based on relevant building data
- Regulatory compliance
- Support for ESG initiatives 
- M2M payments
- Building Automation Infrastructure As a Service

If you have any questions regarding Lavsa, or if you are interested in discussing various Smart Building use cases - feel free to [contact us](https://suprabit.eu/contact) and let's give it a thought together.



large_androfin-min.png

medium_androfin-min.png

small_androfin-min.png

thumbnail_androfin-min.png

androfin-min.png

Back in 2018., the blockchain hype started to gain traction outside of the crypto scene and a number of enthusiasts proposed using blockchain for different business use cases. We had a vision to provide every party with relevant and tamper-proof data delivered by smart building sensors and devices. That data has to be so good that somebody wants to pay for it. Once you bought it, you want to have it ready at your disposal for further processing. And you want to be sure of its integrity.

Lavsa - a new kid on the Block

Internship


**First thing first: the team and the brainy stuff**

Before starting the internship, I wasn’t really feeling nervous as I felt I had a good understanding of the basics of both Solidity and blockchain. Also, my colleague shared some insider information with me regarding the atmosphere, so I wasn’t surprised by the openness of the team and their willingness to help me and the other interns.
Firstly, we slowly studied the stack and the task itself. Then we got familiar and learned to work with the new blockchain technology that enables easier management of smart contracts. We were excited to start developing our own solutions!

Since blockchain is still a quite new technology, you can learn something new about it every day, as long as you know what to search for. Us interns were involved in the whole development cycle starting from the very beginning. First, we went back and forth researching the technologies and deciding which ones would be the best for this project and the internship, before deciding on Scaffold-ETH.

**You’ve heard it several times already: tHErE aRe No STuPid qUEsTioNs!**


![mulan-mushu.gif](https://strapi.suprabit.eu/uploads/mulan_mushu_9349847d61.gif)

 

Well, I’m going to say it again, there really are no stupid questions in Suprabit. Around here, everybody is eager to help each other, be it solving a bug or replacing the coffee pod. Don’t waste your time asking yourself “What will they think of me asking many questions or the same question many times?” because nobody will turn their back or roll their eyes at you. They all know the common goal is gaining understanding and moving forward.
 
The atmosphere is chill and most enjoyable. Once you've had enough of the keyboard tapping, you can make your way to our local table tennis station situated inside the office. Ask away, someone will surely join you! (Beware of the boss, you have to let him win, otherwise...).
 
 
**Future opportunities**

The internship program was well planned and adapted to students with or without previous knowledge of blockchain technology. The people were great, and I enjoyed the entire experience. I'm grateful for the things that I’ve learned during the internship and I'm happy that I was able to stay at Suprabit as an employee after the internship had finished. I know that Suprabit will continue to support my growth and make me a better blockchain developer (and a better table tennis player)!
 
![DSC00401-min.jpg](https://strapi.suprabit.eu/uploads/DSC_00401_min_4b49f3e364.jpg)



large_WhatsApp Image 2022-10-26 at 13.44.46.jpeg

medium_WhatsApp Image 2022-10-26 at 13.44.46.jpeg

small_WhatsApp Image 2022-10-26 at 13.44.46.jpeg

thumbnail_WhatsApp Image 2022-10-26 at 13.44.46.jpeg

WhatsApp Image 2022-10-26 at 13.44.46.jpeg

This summer, I decided to spend my summer-break gaining as much knowledge on blockchain as possible. After a couple of hours of research, a few interviews and one solved solidity smart contract task, I landed my internship at Suprabit.

My Blockchain Internship at Suprabit!

## What and why? 👀

For starters, what exactly is Expo? Expo is a bundle of tools created around React Native to help you start an app very fast. It gives you the means to simplify the creation and testing of React Native App. With Expo, there is no need to directly use Xcode or Android Studio. That means you can finally develop for iOS even if you are not a Macbook lover.

What’s more, if you choose Expo, you will never have to touch any native Swift, Objective-C or Kotlin or Java code. This means you can rely on just your Javascript skills for developing a real-feel native app, ready to be used on both iOS and Android!
However, sometimes you still need to add some native code. We will go over the steps on how to do that as well!

## Setting up the project 💻

You can read all about getting started on [this link](https://docs.expo.dev/get-started/installation/), here we will do just a quick overview so you can get right into the important stuff.
The first step should be downloading the Expo Go app on your phone as well as installing the Expo CLI on your computer:
```bash
npm install --global expo-cli
```

Then you should enter the following command in the terminal and choose one out of four templates:
```bash
expo init-my-app
```

After installing the project, you can start the app by entering 
```bash
expo start
```

A QR code will now pop up on the screen, then you can scan the code from within the Expo Go app if you’re using Android, or directly from the phone's camera if you're using iOS.
Now you can see all the changes you’ve made within the app right as you make them.

## Adding native modules using plugins 📌

Sometimes during your development, you will need to use native modules not directly supported by React Native. Before switching to the bare workflow, you should check if there is a plugin available for the module you need. Expo uses plugins to generate and configure all the native code for a managed project. 

If there is a plugin available, you can easily add it to your project following these instructions.
First, you need to install the plugin of your choice. After installation finishes, edit the app.config.json or app.json file. Edit the expo key and put in the following code: 
```json
{
  "expo": {
    "plugins": ["@config-plugins/name-of-your-plugin"]
  }
}
```
Before being able to fully use the native module, you need to build the application in the development mode using EAS. You can read up more about building later in the article.
Now you can start your app with:
```bash
expo start –dev-client
```

## Permissions ☑️ 

Some native modules require the user to give his permission. With Expo, you don’t have to dig into the native code to handle permissions. It is again enough to just edit the app.config.json file. Here we will be adding [this Bluetooth plugin](https://github.com/dotintent/react-native-ble-plx), but the process is the same for any available plugin. 
For Android, you need to add a new permission field like this
```json
{
   "android": {
      "permissions": ['BLUETOOTH', 'BLUETOOTH_ADMIN'],
    },
}
```
For iOS, you need to do a bit more work. 
```json
{
"ios": {
      "bundleIdentifier": 'your.bundle.identifier',
      "infoPlist:" {
        "NSBluetoothAlwaysUsageDescription":
          'Our app uses bluetooth to find, connect and transfer data between different devices',
      },
    },
}
```
And that's it! Now your app will ask the user for his/hers permission on startup.

## Adding native modules with no plugins available 🖇️

Even though by using Expo we try to stay away from native coding, occasionally there is no other way to achieve some functionality. <br/> Up until recently, if you wanted to add native code, you needed to eject Expo altogether. That means that you wouldn't be able to use the Expo Go app anymore, but more importantly, you would need to remove all your plugins and add them to the native code by hand! Luckily, now there is a workaround and that is using Expo's new feature - the bare workflow!

If you want to use custom native code that isn't already in the Expo Go app, you will need to generate the native iOS and Android projects. To do that, first, you need to switch from managed to bare workflow. You do this by running
```bash
expo run:android
```
and
```
expo run:ios
```

Using the run commands will initially prebuild your project to generate all of the native code within your project directory. Keep in mind that you need to have both Xcode and Android Studio installed to do this. 
Now, you can test your native code on simulators, and continue to use the Expo Go for all other testing and development. You can’t access native code while using the Expo Go app, but you can still access and keep all of your plugins. 

After adding a plugin to the bare workflow, you need to run expo prebuild so Expo CLI adds required permissions to the Info.plist and AndroidManifest.xml. As before, anytime you add a new plugin, you need to build the app again.

## Building the app 🔨

To build the app, we will use [EAS Build](https://docs.expo.dev/build/introduction/). EAS Build allows you to build a ready-to-submit binary of your app for the Apple App Store or Google Play Store.
First, you will need an Expo Dev account. You can register [here](https://expo.dev/).

At the root of your project, you have eas.json, where you can find the four types of builds: dev-ios-simulator, development, preview, and production.
<ul>
<li>Development builds include developer tools, and they are never submitted to an app store.</li>
<li>️Dev-ios-simulator build is used to create the development build for the iOS simulator.</li>
<li>Preview builds don't include developer tools, they are intended to be installed by your team and other stakeholders, to test out the app in production-like circumstances.</li>
<li>️Production builds are submitted to the app store, they are meant for release to the general public or as part of a store-facilitated testing process such as TestFlight.</li>
</ul>


You can change the default value of the bundle identifier in the app.config.js file. By default, the build will be of production type. You can also specify the build type in your command.
```bash
eas build --profile development
```
After that, you can select the platform for which you want to build or you can skip that step by specifying the platform directly in the command.
```
eas build --profile development --platform all
```
The Android build will start immediately. If you chose iOS, log in to your Apple account.

When the build is over, go to the given link or scan the QR code and install the app.
Keep in mind that the app won't run with build types Development and Preview on iOS devices that are not registered on your Apple account.

In the development and preview build, the result for an Android build is the .apk file, while for the production build the result is the .aab file. If you want to change the type of build file, you will need to edit the eas.json file.
```json
{
  "build": {
    "preview": {
      "android": {
        "buildType": "apk"
      }
    },
    "preview2": {
      "android": {
        "gradleCommand": ":app:assembleRelease"
      }
    },
    "preview3": {
      "developmentClient": true
    },
    "production": {}
  }
}
```

You only need to make a new build if you add new native dependencies, or if you register a new Apple device in your provision profile and you want to run the build on it. 

## Conclusion 📝

With Expo's new features, you can finally use it for the whole development process. Adding plugins and native code has never been easier. Since the building process lasts only a few minutes, your clients can now get day-to-day updates on your progress! Other than that, definitely check out [the documentation](https://docs.expo.dev/) for other commonly used features.

Have fun and stay tuned for more! 📻 😊





large_expo.png

medium_expo.png

small_expo.png

thumbnail_expo.png

expo.png

See how Expo helps you in your development and takes care of native things for you.

Using Expo with React Native



## Introduction

In today's world trust is everything, but unfortunately, different parties, more often than not, do not trust each other. Therefore, it is crucial for one party to prove something to the other party - in that case, trust is not required, but only sophisticated mechanisms that would almost guarantee the truth. 

Data anchoring with Merkle tree when implemented correctly can make a zero-knowledge proof. To find out how, first you would need to get familiar with those three terms - Data anchoring, Merkle tree and zero-knowledge proof.

### Data anchoring

Data anchoring consists in creating a timestamped proof of existence for data and storing it to a tamper-resistant blockchain.

Key point is that having the data enables the recreation of the proof, but not the other way around. This way whoever is in possession of the data can verify if the data has been tampered with since its anchoring on the blockchain.


### Merkle tree

Merkle tree or hash tree is a binary tree in which every leaf is labeled with cryptographic hash of a data block, and every node that is not a leaf is labeled with cryptographic hash of the labels of its child nodes. 

![merkletree.png](https://strapi.suprabit.eu/uploads/merkletree_78340c824f.png)
Source: [Wikipedia](https://en.wikipedia.org/wiki/Merkle_tree)

Similar to data anchoring, with knowing all data blocks it is easy to construct a Merkle tree and find the label of the root node or simply called root hash (top hash), but it is not possible to find data blocks knowing only root hash. That is why Merkle tree is used in data anchoring where root hash is the proof that the data is stored onto blockchain.

Another key feature Merkle tree has is that it can be partially created with only subset of data and a receipt for that subset. It is important to note that only those who possess all the data are able to generate such receipts. For example: if we only have L1 and L2 data blocks from the picture above, and we have "Hash 1" inside the receipt, we are able to construct the left side of the Merkle tree with data blocks, and with "Hash 1" from the receipt we are able to calculate root hash.

### Zero-knowledge proof

Zero-knowledge proof is a method by which one party (the prover) can prove to another party (the verifier) that a given statement is true while the prover avoids conveying any additional information apart from the fact that the statement is indeed true. The essence of zero-knowledge proofs is that it is trivial to prove that one possesses knowledge of certain information by simply revealing it; the challenge is to prove such possession without revealing the information itself. - from [Wikipedia](https://en.wikipedia.org/wiki/Zero-knowledge_proof)

## How is it done?

Now that you have gotten familiar with these terms, I am guessing you got a hang of it - how could Merkle tree be used to achieve data anchoring and zero-knowledge proof? First, to anchor your data you would simply order your data blocks and construct a Merkle tree. It is important to arrange data blocks in deterministic order because later data blocks will need to be ordered exactly the same. The root hash of this tree has to be stored on a public blockchain and that is it - you anchored your data.

Second thing you want to do is to ensure you are able to recreate Merkle tree with only subset of your data blocks and an according receipt. You would have to write two algorithms - first algorithm, based on the subset of data blocks and all data blocks, creates the receipt for the subset; second one, given the subset and an according receipt, recreates the Merkle tree. First algorithm is used internally when you want to share a portion of your data, and second algorithm should be open source that would be used by the receiver of the data to verify whether the data has been tampered with since its anchoring.

## Conclusion

Data anchoring is useful mechanism that finds its applications in various industries. There are a lot of ways to implement data anchoring, but in our case we used Merkle tree to do so. Merkle tree is a binary tree in which leaf nodes are labeled with hash of data blocks, and each non-leaf node is labeled with hash of its child nodes. Hence, Merkle tree algorithm can create a single hash (root hash) out of multiple data blocks. Also, root hash of a Merkle tree can be recreated either with all data blocks it contains, or with a subset of the data blocks and an according receipt. 

Data anchoring using the Merkle tree algorithm creates the ability to prove certain data is valid without sharing all the data. This makes it zero-knowledge proof.


large_blockchain-g44b9a7004_1920.jpg

medium_blockchain-g44b9a7004_1920.jpg

small_blockchain-g44b9a7004_1920.jpg

thumbnail_blockchain-g44b9a7004_1920.jpg

blockchain-g44b9a7004_1920.jpg

Find out what data anchoring is and why is it beneficial. This article will teach you basic principles and simple usage so you can start thinking of ways to apply data anchoring in your business.

Data anchoring and verification using zero-knowledge proof

## Introduction

In our introductory [NFT blog post](https://www.suprabit.eu/article/nfts-explained), we explained what NFTs are and what they are used for. In the meantime, we delivered [Suprabit Giant NFT](https://opensea.io/collection/suprabit-giant-nft) to our business partners and employees and hopefully opened a new era of NFT corporate gifts 👍. <br/>
Suprabit Giant was a small but very interesting project that included a digital artist, full-stack and blockchain devs, a business developer, and a legal officer who jointly delivered a unique experience to our partners.

This post will help you get into the technical details of the Suprabit Giant implementation. 

## NFTs

As a quick technical introduction to NFTs, we will compare fungible and non-fungible tokens with simplified pseudocodes for the most basic functions, keeping track of the account balance, adding funds to the account, and removing funds from the account. In the examples below, fungible tokens are on the left, and non-fungible tokens are on the right. Notice how we don’t distinguish individual fungible tokens on the left - we store balance as a number, while with the non-fungible tokens on the right, the balance of an account is defined as a collection of token ids - each token has its unique id. Transferring fungible tokens means just decreasing the sender’s balance, and increasing the receiver’s balance. Meanwhile, transferring non-fungible tokens means removing specific tokens from the sender’s collection and inserting them into the receiver’s collection.

<table style="font-size: 0.75em; display: flex; justify-content: center;">
<tr>
<td style="max-width: 50vw;">

```js
// Account balance - integer
account.tokens = 100;
// Add 10 funds
account.tokens += 10;
// Remove 10 funds
account.tokens -= 10;
```

</td>
<td style="max-width: 50vw;">

```js
// Account balance - set of token ids
account.tokens = [1, 3, 100, 200];
// Add tokens with id 99
account.tokens.insert(99);
// Remove token with id 99
account.tokens.remove(99);
```

</td>
</tr>

<tr>
<th>Fungible Token</th>
<th>Non-Fungible Token</th>
</tr>
</table>

<br/>

## ERC721

[Ethereum Improvement Proposals](https://eips.ethereum.org/) (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Among EIPs there are Ethereum Request for Comments (ERCs) which tackle application-level standards and conventions.

[ERC721](https://eips.ethereum.org/EIPS/eip-721) introduces a standard interface for the implementation of an NFT smart contract. It defines a set of methods that each smart contract needs to implement to be ERC721 compliant. Below we can see the simplified ERC721 interface, this is not a full ERC721 interface, we only extracted a few basic functions.


<table style="font-size: 0.75em; display: flex; justify-content: center;">
<tr>
<td style="max-width: 90vw;">

```solidity
/// @title ERC-721 Non-Fungible Token Standard
/// @dev See https://eips.ethereum.org/EIPS/eip-721
///  Note: the ERC-165 identifier for this interface is 0x80ac58cd.
interface ERC721 /* is ERC165 */ {
    /// @notice Count all NFTs assigned to an owner
    /// @dev NFTs assigned to the zero address are considered invalid, and this
    ///  function throws for queries about the zero address.
    /// @param _owner An address for whom to query the balance
    /// @return The number of NFTs owned by `_owner`, possibly zero
    function balanceOf(address _owner) external view returns (uint256);

    /// @notice Find the owner of an NFT
    /// @dev NFTs assigned to zero address are considered invalid, and queries
    ///  about them do throw.
    /// @param _tokenId The identifier for an NFT
    /// @return The address of the owner of the NFT
    function ownerOf(uint256 _tokenId) external view returns (address);

    /// @notice Transfers the ownership of an NFT from one address to another address
    /// @dev This works identically to the other function with an extra data parameter,
    ///  except this function just sets data to "".
    /// @param _from The current owner of the NFT
    /// @param _to The new owner
    /// @param _tokenId The NFT to transfer
    function safeTransferFrom(address _from, address _to, uint256 _tokenId) external payable;

    /// @notice Transfer ownership of an NFT -- THE CALLER IS RESPONSIBLE
    ///  TO CONFIRM THAT `_to` IS CAPABLE OF RECEIVING NFTS OR ELSE
    ///  THEY MAY BE PERMANENTLY LOST
    /// @dev Throws unless `msg.sender` is the current owner, an authorized
    ///  operator, or the approved address for this NFT. Throws if `_from` is
    ///  not the current owner. Throws if `_to` is the zero address. Throws if
    ///  `_tokenId` is not a valid NFT.
    /// @param _from The current owner of the NFT
    /// @param _to The new owner
    /// @param _tokenId The NFT to transfer
    function transferFrom(address _from, address _to, uint256 _tokenId) external payable;
}
```
</td>
</tr>
</table>
<br/>

But why is this even important for us? Can’t we create our own NFT smart contract without any fuss with standards? In theory, we can, no one forces us to be ERC721 compliant, in practice, a short answer - no. Now for the long answer, we need to enable interoperability between our NFT contract and other applications. A primary example of this interoperability is a wallet application. The general expectation is that users can see and manage their tokens in their wallet application - this is generally a mobile app. A wallet application can check which tokens the user owns only by reading the NFT smart contract directly. Now imagine what would happen if every NFT smart contract was implemented differently - a wallet application would need to develop an interface for each smart contract which doesn’t make sense. This is why we accept ERC721 and other EIPs and implement smart contracts accordingly. Any application can integrate with our NFT just by fetching the address of our smart contract as everything is publicly available.

Now that we have a better understanding of what we need to implement it’s a good time to introduce OpenZeppelin, an open-source library of standardized smart contracts that were developed following best security practices, and are extensively audited. Within the library, we have an implementation of the basic ERC721 compliant smart contract which tackles all the standard functionality of the NFT, minting, fetching balance, transferring, etc. As smart contracts are object-oriented, we can just inherit OpenZeppelin’s basic ERC721 contract and extend it with our business logic that is specific to our NFT.

At this point, we have a smart contract with basic NFT functionality - we have the tokens, but what differentiates them? Where is the uniqueness, the praised non-fungibility? This is where the token metadata comes into play, and if we consult the ERC721 interface we can spot the metadata extension which describes a way to attach metadata to the contract and each token individually. This allows us to attach some assets to tokens, like images, videos, and other media, or data in general. Below you can see the interface of the metadata extension. The main function here is the tokenURI which allows us to specify a distinct URI for a specific token. The idea is that the tokenURI points to a JSON file that contains all the metadata related to the specific token.

<table style="font-size: 0.75em; display: flex; justify-content: center;">
<tr>
<td style="max-width: 90vw;">

```solidity
/// @title ERC-721 Non-Fungible Token Standard, optional metadata extension
/// @dev See https://eips.ethereum.org/EIPS/eip-721
///  Note: the ERC-165 identifier for this interface is 0x5b5e139f.
interface ERC721Metadata /* is ERC721 */ {
    /// @notice A descriptive name for a collection of NFTs in this contract
    function name() external view returns (string _name);

    /// @notice An abbreviated name for NFTs in this contract
    function symbol() external view returns (string _symbol);

    /// @notice A distinct Uniform Resource Identifier (URI) for a given asset.
    /// @dev Throws if `_tokenId` is not a valid NFT. URIs are defined in RFC
    ///  3986. The URI may point to a JSON file that conforms to the "ERC721
    ///  Metadata JSON Schema".
    function tokenURI(uint256 _tokenId) external view returns (string);
}
```
</td>
</tr>
</table>
<br/>


Below is the example of the token metadata in JSON format, tokenURI should point to this data. In this example we modeled an NFT for a football player card, the metadata contains a URL to an image of a player, and a couple of attributes assigned to the token. Observant among you may have already noticed a link to an image hosted on the hns-cff.hr domain,  oh no. It’s completely valid to question the integrity of our NFT at this point, we promised you full control of your NFT, but then you find that someone else has full control of the essential part of the NFT - the digital asset it encapsulates. What happens when the owners of the hns-cff.hr domain decide they don’t want to host the image anymore a few months or even a few years after you received the NFT? They have the full right to do so, they don’t have any incentive to continue hosting the image for free. The NFT without the digital asset becomes just an id assigned to you in the smart contract, practically useless.

<table style="font-size: 0.75em; display: flex; justify-content: center;">
<tr>
<td style="max-width: 90vw;">

```json
{
    "name": "Luka Modric",
    "image": "https://hns-cff.hr/files/images/luka-modric.jpg",
    "attributes": [
        {
            "trait_type": "country",
            "value": "Croatia"
        },
        {
            "trait_type": "kit_number",
            "value": 10
        },
        {
            "trait_type": "position",
            "value": "midfielder"
        },
        {
            "trait_type": "captain",
            "value": "true"
        }
    ]
}
```

</td>
</tr>
</table>
<br/>


You might wonder why don’t just store all the metadata in the blockchain? Storing data in the blockchain is expensive, storing just 1MB of data to the Ethereum blockchain costs roughly 4 ETH which is, at the time of writing, equivalent to roughly $13,000. We won’t dig deeper into what is the reason behind this, but for anyone interested, a description of the Ethereum Virtual Machine (EVM) and its opcodes might be a good starting point. Nevertheless, don’t worry, we won’t stop here, there is a solution for the issue, this is where IPFS comes to save us.
<br/>

## IPFS

InterPlanetary File System is a protocol and peer-to-peer network for storing and sharing data in a distributed file system. It doesn’t sound like something that would solve our issues, but IPFS uses content-based addressing as opposed to location-based addressing which is a standard on the web today. If we look at the standard URL, let’s take an URL for the image of our football player as an example. Location-based addressing strictly defines on which domain is the image hosted, and where exactly is the image stored on that domain, in our example the domain is hns-cff.hr, and the image itself is located in the directory files/images/. Any change in either the domain name or the directory structure would result in this URL becoming invalid, alongside our NFT that depends on it.

![URL Example](https://strapi.suprabit.eu/uploads/URL_example_7209f2a836.png)


On the other hand, IPFS takes a completely different approach. As its name already says, content-based addressing addresses files based on their content. Imagine if the URL address for the image would be the hash of the image, it wouldn’t be convenient for humans as the URL wouldn’t be readable, and the links would be error-prone. But in our case we would greatly benefit from content-based addressing as we wouldn’t be vulnerable to any domain or directory changes, as long as someone has the original file, the URL can be resolved. Let’s try to check what would an IPFS URL look like. Content identifier (CID) is based on the hash of the file so for simplification, we can think of it just like a hash. A consequence of the CID is that any change in the file’s contents results in a different CID, which means that the file we are addressing with an IPFS URL is immutable. The file itself can be updated, but that would also update the CID so the original IPFS URL will point to the old version of the file. This is a great property for our use case, with IPFS CIDs we get addressing that preserves the integrity of the content.

![IPFS URL Example](https://strapi.suprabit.eu/uploads/IPFS_URL_1a3c9c8b76.png)

As IPFS is also a distributed file system, multiple peers in the network can host the same file, as the CID of the file would be the same there wouldn’t be any integrity violations. Multiple peers hosting the same file would only help others retrieve the file. If we try to retrieve the file from the peer that doesn’t have a file with that CID locally present, the peer will query neighboring peers if they have a file with that CID - this query propagates through the network until the file is found. A consequence of a peer-to-peer system is that the query for a file can take a long time to resolve as we need to propagate through the network until we find a peer that hosts this file.

Ok, now we know how to immutably address the metadata, but did we solve the issue if the original author stops hosting metadata? At least one peer in the IPFS still needs to host this file if we want NFT to work properly? True, at least one peer needs to host metadata for NFT to function, but now we at least have the ability to host data ourselves which is surprisingly easy as multiple cloud services offer us IPFS storage service - some of them even have free tiers that are more than sufficient to accommodate the storage of NFT metadata. This property comes from the fact that the metadata is not hosted by some server behind a domain, rather it’s hosted on IPFS, any IPFS peer should be able to find this file if at least one peer in the network hosts it.

You might be confused by some IPFS URLs looking like the example below. This link represents an HTTP gateway of an IPFS peer - ipfs.io in this example, it allows us to access IPFS files from the browser. You might wonder, didn’t we return to the beginning as we still need to use the HTTP gateway of some peer - what happens if that peer stops working? This is the exact reason why it’s strongly recommended to address IPFS files using ipfs://<cid> URL format as this allows consumers of that link to use any peer they want to access that file. We can even specify a list of IPFS peers that we use, so we have alternatives if one peer stops working.

<img alt="IPFS Peer Gateway" src="https://strapi.suprabit.eu/uploads/IPFS_peer_gateway_URL_779096ba1d.png"  height="70"/>


All in all, IPFS solves our issue of storing and linking metadata. Before deploying a smart contract we need to generate metadata, and media assets that will be linked with NFTs so that we can configure what the tokenURI method of the NFT returns. Below is the example of our metadata for one of our NFTs, we followed [OpenSea’s metadata format](https://docs.opensea.io/docs/metadata-standards#metadata-structure).

<table style="font-size: 0.75em; display: flex; justify-content: center;">
<tr>
<td style="max-width: 90vw;">

```json
{
    "name": "Suprabit Giant #0",
    "description": "This Suprabit NFT represents one of 100 unique frames of Suprabit Giant digital artwork.",
    "image": "ipfs://bafybeigp6cki2w7v26coqecxa5iohadhjg345n5b7ukkesbvq3kqeguvs4",
    "animation_url": "ipfs://bafybeig77wew3xfhejgatekmah5t46btoeteugaa2maynicyctl4zxwp6m",
    "external_url": "https://suprabit.eu/nft/giant/0",
    "attributes": [
        {
            "display_type": "boost_number",
            "trait_type": "Mobile",
            "value": 5
        },
        {
            "display_type": "boost_number",
            "trait_type": "IoT",
            "value": 10
        },
        {
            "display_type": "boost_number",
            "trait_type": "Blockchain",
            "value": 4
        },
        {
            "display_type": "boost_number",
            "trait_type": "AI",
            "value": 25
        },
        {
            "display_type": "boost_number",
            "trait_type": "Cloud",
            "value": 9
        },
        {
            "display_type": "boost_number",
            "trait_type": "Table Tennis",
            "value": 47
        }
    ]
}
```

</td>
</tr>
</table>
<br/>

The next step is to pick a blockchain network to where the NFT smart contract will be deployed to. As we used ERC721 which is an interface for Solidity smart contracts, we need to choose a network that supports Ethereum Virtual Machine (EVM). Naturally, Ethereum is the first network to be considered, but at the time of writing Ethereum’s high transaction cost due to high network traffic is not suitable for our case. Polygon is a few orders of magnitude more efficient than Ethereum at the moment so it was an easy decision to select it over Ethereum.
<br/>

## Minting

Lastly, we need to figure out an easy and intuitive way for users to claim their gifts. This is a hard task as the blockchain ecosystem introduced a new way of interaction with online services which is fairly complex for new users. We have to anticipate that a majority of users won’t even have a crypto wallet so we need to guide them through the whole process, not just the interaction with our smart contract. We utilized WalletConnect to help us connect users’ wallet applications with our NFT website where users redeemed their gift NFTs. The last thing we needed to do is to actually create and assign NFT to the user, this process is called minting. In order to mint the NFT, we need to call the smart contract and pass the token id we want to mint, and the address of the owner’s wallet. This operation is packed into a transaction that will require a small fee in order to be executed on the blockchain. As NFT is a gift we wanted to handle all minting fees ourselves which is why we created a small minting service that mints NFT at the user’s request - of course, we had to protect this service against unauthorized requests.

Along the way, we stumbled upon a hurdle of connecting a user’s wallet to the Polygon network which at the time of publishing NFT had to be manually configured in the wallet application, and this hurt the user experience a bit. Fortunately, this won’t be the issue for so long as there is already a [standard proposal](https://eips.ethereum.org/EIPS/eip-3085) that should fix this issue - the wallet applications just need to implement support for it.
<br/>

## Conclusion

To wrap it up, we successfully launched our first NFT and delivered it as a gift to our business partners and employees. It was awesome to hear positive feedback regarding the user experience of redeeming the NFT as we invested a lot of time to make it as easy, and as intuitive as possible. The general idea behind the gift was to give people first-hand experience with blockchain and introduce them to the concept of NFTs and help spark their ideas for NFT use cases. 

If you have any questions regarding this project, or if you are interested in various NFT use cases, and where can it be used in your field of work - feel free to contact us and let us give it thought together.



large_cover_nft_blog.png

medium_cover_nft_blog.png

small_cover_nft_blog.png

thumbnail_cover_nft_blog.png

cover_nft_blog.png

Making of Suprabit NFT Giant

Even among cryptocurrency enthusiasts, non-fungible tokens (NFTs) aren't the most well-known or understood piece of the decentralized ledger system. 
NFTs may seem abstract and difficult to understand, but many applications for these tokens make them essential in the crypto space and beyond. If you're unfamiliar with this type of token, you came to the right place as this post breaks down everything you need to know about NFTs! Give it a read and discover what NFTs are and how they relate to blockchain and cryptocurrency technology.

### What are non-fungible tokens (NFTs)?

Blockchain and cryptocurrency are two buzzwords that have been thrown around for a while now. Although NFTs combine both of these emerging technologies, there's still a lot of confusion about what exactly they are. Keep in mind that even though the NFTs are based on the same blockchain technology as cryptocurrencies, they are not a currency. So let’s get right on it and let’s see what Non-Fungible tokens actually are.

The term non-fungible refers to something that another similar object cannot replace i.e they can only ever be replaced by themselves — or not at all. And that is precisely what makes them unique.  **A non-fungible token (NFT) is a one-of-a-kind digital asset that represents ownership of physical or virtual items such as art, video clips, music, and so on.**  

Simply put, NFTs are digital proof of ownership for any given item. NFTs are securely recorded on a blockchain — the same technology that lies behind cryptocurrencies — ensuring that the asset is unique. To shed some light on the whole thing, let’s have a look at some of the examples of NFTs.

![Picture2.jpg](https://strapi.suprabit.eu/uploads/Picture2_45375cdc1c.jpg)
Source: [Instagram (@adamsackstoons)](https://www.instagram.com/p/CVK066CPshA/)

### Examples of NFTs

[Cryptokitties](https://www.cryptokitties.co/), [CryptoPunks](https://www.larvalabs.com/cryptopunks), [Rare Pepes ](http://rarepepedirectory.com/) are all examples of non-fungible tokens.  NFT was first introduced on the Ethereum blockchain protocol as a concept that allows you to mint and trade virtual assets that are unique, but now many other blockchains like Polygon, Cardano, or Kusama, to name a few, have also their own NFT implementations. 

Let’s have a closer look at Cryptokitties, digital cats that have unique genes. Think of them as crypto-collectables. Each is a one-of-a-kind digital asset built on Ethereum's blockchain and entirely owned by you. They can't be replicated, taken away, or destroyed. They can be, however, transferred from one digital wallet to another.

As defined by the Ethereum ERC721 standard, non-fungible tokens like Cryptokitties can be identified via a specific token ID - and only exist once within Ethereum blockchain. 

NFTs are today what football cards were back in the day - the latest collectables. While the latter was traded in person, NFTs are easily bought and sold online. Which, in turn, quickly made them a lucrative business. [The art world particularly profited from the sale of NFTs](https://www.nftsstreet.com/most-expensive-nfts-ranked/). Below are a few examples you probably heard about:

●	[Beeple](https://cryptoart.io/artist/beeple), a digital artist, sold the first purely digital work of art called "Everydays—the First 5000 Days" at Christie's for $69.3 million.
![Picture3.jpg](https://strapi.suprabit.eu/uploads/Picture3_42b577f7ff.jpg)
Source: [Wikipedia](https://en.wikipedia.org/wiki/Everydays:_the_First_5000_Days)

●	For $2.9 million, Twitter CEO auctioned off an NFT of his first tweet.
![Picture4.png](https://strapi.suprabit.eu/uploads/Picture4_aadbe91d09.png)
Source: [Twitter (@jack)](https://twitter.com/jack/status/20?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E20%7Ctwgr%5E%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fwww.cnbc.com%2F2021%2F03%2F22%2Fjack-dorsey-sells-his-first-tweet-ever-as-an-nft-for-over-2point9-million.html)

●	At Sotheby's first curated NFT sale, a CryptoPunk NFT was sold for $1.8 million.
![Picture5.jpg](https://strapi.suprabit.eu/uploads/Picture5_a062679f34.jpg)
Source: [Twitter (@Sothebys)](https://twitter.com/Sothebys/status/1402996062474760193?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1402996062474760193%7Ctwgr%5E%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fmarkets.businessinsider.com%2Fnews%2Fcurrencies%2Fcryptopunk-nft-covid-alien-draftkings-sothebys-auction-fungible-token-2021-6)

●	$208,000 was paid for 20-second footage of LeBron James' "Cosmic Dunk #29."

### How do NFTs work?
To understand NFTs, we could look at fungible and non-fungible items from a financial perspective. Today, most people think of cash as fungible—if I give you a $5 bill and you give me back another $5 bill, nothing really changed in terms of value as all the 5$ bills are the same. We don’t care about the dollar bill as a paper-based physical item, we care only about its value.
In contrast, collectables and antiques provide value as individual units; these kinds of goods aren't interchangeable with others with similar or even the same features (like dollar bills). 
Non-fungible tokens work on blockchains like Ethereum, but they are totally different blockchain assets with different features. 

### How are NFTs used?

There are three main ways NFTs can be used: as collectables, for identity, and ownership. 

**Collectibles** are non-fungible assets that can be owned and traded on NFT marketplaces. 

**Identity** refers to non-fungible personal information about an individual or business, such as educational history or employment background. 

**Ownership** refers to the possession of a physical or digital asset represented by an NFT. By trading NFT you’re actually transferring ownership of those assets. This could include things like real estate, art, intellectual property, etc. 

As time goes on, we will likely see many more creative uses for digital NFTs.

### Difference between cryptocurrency and NFTs

Cryptocurrencies and NFTs both rely on the same blockchain technology. As a result, NFT markets may also compel customers to use cryptocurrencies to acquire NFTs. 
Cryptocurrencies aspire to function as currencies by holding value or allowing you to purchase and sell items. Cryptocurrency tokens are fungible, and comparable to conventional currencies like the US dollar. 
On the flip side, NFTs are tailored to generate one-of-a-kind tokens that may be used to demonstrate ownership and communicate rights over digital products.

### Online exchange and marketplaces to buy NFTs

[OpenSea](https://opensea.io/) and [Nifty Gateway](https://niftygateway.com/) are widely known marketplaces to trade NFTs. With a user base of close to 2 million accounts on OpenSea, it is by far one of the biggest marketplaces for NFTs at the moment. 

**Foundation**: Foundation happens to be an NFTs marketplace, and in order to join the platform, a user must be invited by another user who is already a member.

**Nifty Gateway**: This is an art-focused NFTs marketplace that works with athletes, brands, and creators.

**OpenSea**: When you want to mention one of the largest marketplaces for a wide range of NFTs collectables, you can think about OpenSea.

**Rarible**: If you're looking for an art-focused NFTs platform, Rarible is an ideal choice that rewards members with its own token - RARI.  

### Key takeaways

When you think of cryptocurrencies, your mind surely jumps to Bitcoin and other alt-coins. But blockchain is more than just digital currencies; it's a protocol for creating unique data sets within a network that are time-stamped, cryptographically secured, and immutable. 
In other words, it is also about taking physical assets—diamonds, Picassos, gold, and digital assets like artwork and turning all of them into non-fungible tokens (NFTs). NFTs can be stored on an Ethereum or a number of other public ledgers. Each token would be identified by a unique ID number and tied to everything from value to ownership rights. 
In the future, the idea is that you'll have NFTs representing everything from your passport, driver's license, game collectables, real estate ownership, you name it! So, is there any reason we shouldn't extend the concept of NFT beyond its borders? We think not! Stay tuned and wait to see what the Suprabit team has been working on.

small_Picture3.jpg

thumbnail_Picture3.jpg

Picture3.jpg

We want you to enter the world of non fungible tokens! A new type of blockchain based asset is taking some of the well established markets by storm. Find out why and what is our stake in it.

Non-Fungible Tokens (NFTs) Explained



Prior to starting, I felt a little nervous because I wasn't sure if I would be able to contribute and work well with my new team. However, a few days beforehand, my team made me feel welcomed by giving me the materials needed for preparation.

**Joining the full-stack team**

The team was just starting to build a brand new website from scratch. For the first couple of days, I was learning about new technologies that I was going to use throughout the project. I was also learning about the project itself by participating in conversations, discussing features that we were going to implement and brainstorming optimal solutions.
I got an insight into front-end, content management systems, publishing and UI/UX design. The focus was on Strapi, Next.js and Figma with React being the main point of interest.
I have to admit things were challenging in the beginning, but after some time and help from my colleagues, I was able to write a clean code on my own!


> I feel like everyone at Suprabit has an open mind and a passion for helping others! The management is flexible and attentive to the needs of the developers. If you're thinking of becoming a member of the Suprabit team or are even given an opportunity to be one, I hope you take it!

**Gaining confidence**

I realized I was able to do more than I thought I could! At the beginning of the summer, I was worried that I wasn't going to contribute enough. I never would have thought that by the end of the internship, I would become a valuable member of my team. Gaining confidence also meant talking about new concepts with my colleagues and finding the courage for pitching new ideas. One of the most important things that I learned was not to be afraid to ask questions! Asking questions meant that I'm curious and that I care about the quality of the work I'm doing. Furthermore, I learned not to ask the same question twice and to make sure the time I spent asking questions was valuable to everyone involved.


**Connecting theory and practice**

Before I started my internship, I thought I had a lot of knowledge on software development from my university.  However, as soon as I started to put such knowledge into practice, I realized that there was still so much to learn! At my university, I usually had to write small programs or projects, so working on such a big project was certainly new to me. The internship had a really positive effect on my studies as it had taught me how to write clean and understandable code and work in a team, but more importantly, it had given me hands-on experience in my field which is priceless.

**Conclusion**

I feel this internship program is well planned and adapted to students with no working experience. Throughout the entire experience, everyone was open, honest and understanding. No one ever made me feel like I was any less just because I had less experience than my fellow colleagues. I'm grateful for the things I learned during my internship and I'm so happy to be able to stay at Suprabit even after the internship has finished. I know that Suprabit will continue to support me and challenge me to be a better software developer!

large_about.jpg

medium_about.jpg

small_about.jpg

thumbnail_about.jpg

about.jpg

Interning at Suprabit has been one of the most challenging summers of my life, but it's been well worth it! Besides teaching me skills and giving me an insight into the functioning of a software company, it has forced me to learn and grow like never before.

My internship at Suprabit!

These last couple of months Suprabit experienced a noticeable increase in the number of employees. Because of the circumstances, we didn’t get the chance to meet all those new faces in person as everyone was working from home. So the best thing to do was to organize a fun team building in nature.


![GH011780_1632587258727.jpg](https://strapi.suprabit.eu/uploads/GH_011780_1632587258727_aa96f8d466.jpg)




After the democratic elections with a few given options, the decision was made - we're going rafting! On early Saturday morning, we all got together and started our journey towards Brod na Kupi, a small town on the Croatian-Slovenian border. When we came there, we had great fun trying on our wet suits and boots. After we picked up all of the equipment, we sat in the car in wet suits and followed the mini kayak caravan upstream to the start of our water journey. After listening to short instructions, we were ready to jump in the river with our kayaks and immediately started bumping into each other. 




![GH011788_1632587858025.jpg](https://strapi.suprabit.eu/uploads/GH_011788_1632587858025_87f54783fe.jpg)




 The water was really cold but the weather was sunny and actually quite nice. Sadly, the water level was pretty low so we missed out on some great adrenaline rushes, but the important thing was spending quality time together, relaxing, and taking in the beautiful mountain views. We still had so much fun because who wouldn’t laugh while watching your colleagues fall into cold water. 



![GH011796_1632663478230.jpg](https://strapi.suprabit.eu/uploads/GH_011796_1632663478230_b22c299837.jpg)




By the time we finished kayaking, we were all pretty hungry, but luckily, there was a delicious lunch waiting for us. We enjoyed local specialties eating fresh food from the Gorski kotar region and finished off with amazing wild berries strudel. 





Tired but happy, we headed to Zagreb full of new memories and with tummies full with food.

![GH011805_1632662430929.webp](https://strapi.suprabit.eu/uploads/GH_011805_1632662430929_07799deb0c.webp)

You can check the atmosphere for yourself in our video!

<style>.embed-container { position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; max-width: 100%; } .embed-container iframe, .embed-container object, .embed-container embed { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }</style><div class='embed-container'><iframe src='https://www.youtube.com/embed//Nn00gVJNGDI' frameborder='0' allowfullscreen></iframe></div>




large_GH011780_1632587258727.jpg

medium_GH011780_1632587258727.jpg

small_GH011780_1632587258727.jpg

thumbnail_GH011780_1632587258727.jpg

GH011780_1632587258727.jpg

We had a great time at our recent team building!

Team Building 2021: Kayak Adventure

# We needed a change

People say that the website is the face of the company, and that is indeed true. The website is often the first thing somebody sees about your company and if they see an IT company with a bad, ugly or non-functioning website, imagine what they will think about the company itself.

Our old website was kind of out of date and since Suprabit is a company working with cutting edge technologies and following modern trends, we had to update our website to better represent us - what we do and who we are.

# Choosing what we want

Before doing a project like this, we had to agree on what we want to show on our website, how to package it and how to put emphasis on things we think are the most important. After the agreement had been made, our designer had to make a design prototype and web development team had to design application architecture and select the technologies to work with.

# Development

Our designer used **Figma**, a vector graphics editor and prototyping tool, to create the design which our development team would have to follow. For content management, we selected **Strapi**. Strapi is one of the best headless Content Management Systems, it is open source, 100% built in JavaScript and very simple to set up. **Next.js** is an open-source development framework built on top of Node.js enabling **React** based web applications functionalities such as server-side rendering and generating static websites. Since we are already experienced in developing Next.js applications, it was an easy decision to select this technology for building our website.

Following the design in Figma, the development team built React components. Next.js was important here to render as much as possible on the server side, and then serve the client with components already populated with content from Strapi. This increases user experience as the client has much fewer requests per page and pages load much faster.

# Deployment

For deployment of our web application and even through the development process, we used **Docker** containers for both Strapi API and for Next.js app. **Docker Compose** came in handy for easier management of both containers with only few command lines in the terminal. **Digital Ocean** is our selected cloud service provider and during the development phase, we had set up a dev environment and deployed our application iteratively as it was being built and as new features were being added. To do that without connecting to the server and running several commands lines every time, we created a **GitHub Action** to do all of that for us, deploying the application version on the main branch.

Once the app was ready, we needed to make it run over HTTPS protocol, instead of HTTP, and finally update DNS servers to route www.suprabit.eu to our server. 

large_Suprabit-web-1440x810.jpg

medium_Suprabit-web-1440x810.jpg

small_Suprabit-web-1440x810.jpg

thumbnail_Suprabit-web-1440x810.jpg

Suprabit-web-1440x810.jpg

Designing a new look for our website. Selecting technologies and principles to build our website on, implementing them and finally deploying the website to cloud.

Building our own website

We are helping organizations around the world to get the best out of AI, Mobile&Cloud, IoT and Blockchain tech.
Our teams, passionate about technology and sharing the know-how with the world, will overcome obstacles, find solutions and deliver exceptional results to meet your needs.

Secure your digital products investment with a partner commited to innovation and delivery.

We are helping organizations around the world to get the best out of IoT, mobile, blockchain and cloud tech.

We revolutionize industries with cutting-edge technology, pioneering in IoT and Blockchain to deliver innovative solutions across digital platforms.

Founded in Croatia with over 30 years of experience in business-critical software, we drive tech innovation at every stage of the product lifecycle.

About us

Latest from our blog

We are helping organizations around the world to get the best out of AI, Mobile&Cloud, IoT and Blockchain tech.


Our teams, passionate about technology and sharing the know-how with the world, will overcome obstacles, find solutions and deliver exceptional results to meet your needs.