BUK Protocol v1
  • 📖Introduction
  • Whitepaper
    • Whitepaper
      • Executive Summary
      • Industry Overview
      • Problem Statement
      • Solution - Tokenized Travel assets
        • What benefits does Tokenization offer for the Travel industry?
      • How was it solved it earlier?
      • Introducing Buk
        • Buk Protocol
          • Core components of Buk Protocol
        • Buk Products
          • BukTrips - The first tokenized travel marketplace
        • Buk Ecosystem
      • Ecosystem Participants
      • Target Market Solutions and Future Use cases
        • Tokenized Marketplace
        • Trading Engine for Travel agents
        • Resellability-as-a-Service
        • Price-lock on travel assets
        • Index Funds for city/stars/other categories
        • Pool in investments for asset liquidity
        • Travel Insurance integration for price protection
        • Buy back gurantee and Insurance pool creation
      • Go to Market and User Acquisition
      • Competitive Landscape
      • Technical Architecture
      • Roadmap
      • Governance Council
      • Enhancers, Partners & Ecosystem
      • Key performance Indicators for traction and success measurement
      • Buk Token $BUK
        • Token Utility / Revenue Sharing
        • Token Distribution
        • Token Vesting
        • Booster Tokens - Investors as Users
      • Conclusion
  • Overview
    • 💡Protocol Architecture
    • 🎫BUK NFTs
    • ⛓️The BUK Protocol
    • 🛠️BUK Toolset
  • Product Guides
    • 📪Interacting with the BUK protocol
    • 📎Using APIs and SDKs
  • Fundamentals
    • 🛠️Getting Started
      • 📝Hotel Industry jargon
      • 🧑Web3.js and BUK Protocol
  • Use Cases
    • 🎒Travellers and Guests
    • 🏨Hotels & Accommodation operators
    • 👨‍✈️Travel agents, Tour operators and travel ecosystem
    • 🖥️Travel and Hospitality Tech
    • 👩‍💻Innovators and 3rd party app Developers
Powered by GitBook
On this page
  • Architecture overview
  • Target Architecture
  • Current Architecture
  1. Overview

Protocol Architecture

This document is divided into two section - our current architecture and our target architecture towards which we plan to evolve as we re-tool the Hospitality distribution ecosystem using our protocol

PreviousConclusionNextBUK NFTs

Last updated 2 years ago

Architecture overview

BUK protocol's architecture consists of the the following key components:

  • The BUK Protocol (Smart contract)

  • Authentication and DID (Distributed ID) layer

  • Payment layer

  • Hotel Integration layer / (in future) Supply APIs and SDK

  • Booking engine / (in future) Demand APIs and SDKs

Target Architecture

The BUK protocol is a smart contract deployed on the Polygon Ethereum blockchain which can be invoked by various dApps deployed by Hotels and Travel vendors. The Hotel integration layer shall provide necessary services to synchronize inventory from hotel systems to the blockchain, while the Booking Engine shall provide services to buy-sell-trade this inventory.

In addition, payment layer integrations - both for blockchain based payment methods as well as FIAT currencies - shall also be provided through a partnership with other Web3 projects operating in this space. If you are a web3 payment processing project providing on-ramp / off-ramp solutions and would like to collaborate with the BUK team, drop a line at hello[at]buk[dot]technology.

Current Architecture

BUK's current state includes the following 3 components under development:

  • BUK Protocol Smartcontract

    • New property registration

    • NFT generation for all inception bookings

    • Listing NFTs for sale

    • NFT Trading

    • Commission and payout management

    • Cancellation and check-in

  • Booking Engine microservices

    • Built-in inventory management

    • Cron-job for synchronization with the blockchain

    • APIs for Booking, Trading, Check-in workflows

  • Booking engine frontend on top pf Booking engine microservices

All NFTs shall be stored on (Filecoin storage network), while any ancillary metadata shall utilize web3 infrastructure such as Decentralized databases and web3 storage systems. For enhanced performance for web2 based systems, dApps can choose between using a distributed database or a web2 document storage database such as MongoDB. With an open architecture philosophy, the BUK team intends to support all forms of caching and performance enhancement layers.

💡
NFT.Storage