Pirichain Whitepaper
🌍 Pirichain🔮 Explorer🧰 API
  • 👋What is Pirichain?
  • Overview
    • 🔮Upcoming Projects
  • PIRICHAIN INFRASTRUCTURE
    • 🛤️Pirichain Infrastructure
      • 🅱️1.1. Pirichain specific block fields
      • ⏩1.2. Pirichain-specific transaction fields
      • 📒1.3. Pirichain Wallet Structure
        • 👤Personel Wallet
        • 💼Business Wallets
      • 👉1.4. Creation of Pirichain Transaction
      • 📎1.5. A New Concept in Blockchains! Adding Data to the Blockchain
      • 💠1.6. Pirichain's Web Server Services Structure
      • 🤝1.7. Consensus at Pirichain
  • PIRICHAIN SMART SCENARIO
    • 💡Pirichain Smart Scenario
      • 🌀2.1. Pirichain Smart Scenario Virtual Machine
        • ⚗️2.1.1. Pirichain Example Smart Scenarios
          • 🩺2.1.1.1. A Scenario on Health
          • 📦2.1.1.2. A Scenario on Inventory
        • 🎓2.1.2. Scenario of calculating the semester average with course grades and coding example
  • PIRICHAIN PLATFORMS
    • 🖥️3.1. Pirichain Desktop Wallet & Database Bridging Application (Wallet & DataBridge Application)
  • PIRICHAIN TRANSACTION TYPES
    • ⛓️4. Pirichain Transaction Types
  • PIRICHAIN COMMISSION
    • 🔥5. Pirichain Commission
  • PIRICHAIN REWARD DISTRIBUTION
    • 🎁6. Pirichain Reward Distribution
  • PIRI Coin Holders
    • 👥PIRI Tokenomics
  • 📍Pirichain Projected Roadmap
  • ⬆️Updates
    • 🚀New Fee Mechanism in Pirichain
  • REFERENCES
  • 🌎Pirichain Showcase
  • 🔎Pirichain Explorer
  • 🌐Pirichain Scanner
  • ✒️Pirichain Master Thesis
Powered by GitBook
On this page

Was this helpful?

  1. PIRICHAIN INFRASTRUCTURE

Pirichain Infrastructure

PreviousUpcoming ProjectsNext1.1. Pirichain specific block fields

Last updated 2 years ago

Was this helpful?

As seen in the system in Figure 1.1, end users and companies send requests to the server side. The system first puts it in a queue, the processing queue processes the incoming request and sends it to the nodes. After processing by the nodes, the result is sent back to the servers. In these transactions, each request and registration transaction is queued by queuing (FIFO).

Each block generation period is 10 seconds. And a result related to that transaction is expected from the node within a maximum of 30 seconds. When we test it practically; It takes approximately 150-400 milliseconds for a transaction to be sent from the server to the nodes and returned to the server side. In case of too much traffic in the system, different results are obtained depending on the hardware configuration of the node and internet speed.

OS
CPU
Memory
Network
Avg. Response Time

Windows 10

2

4

~ 10mbps

~ 8000 ms

Ubuntu 20.4

1

2

~ 10mbps

~ 5200 ms

🛤️
Figure 1.1: Relationship Between Pirichain Server and Nodes