idealmoney.io
Open in
urlscan Pro
89.106.206.214
Public Scan
URL:
https://idealmoney.io/
Submission: On July 13 via automatic, source certstream-suspicious — Scanned from NL
Submission: On July 13 via automatic, source certstream-suspicious — Scanned from NL
Form analysis
1 forms found in the DOMGET search.html
<form id="rtd-search-form" class="wy-form" action="search.html" method="get">
<input type="text" name="q" placeholder="Search docs" aria-label="Search docs">
<input type="hidden" name="check_keywords" value="yes">
<input type="hidden" name="area" value="default">
</form>
Text Content
Zellular Sequencer 0.1.0 * Integration Guide * The Protocol Zellular Sequencer * * Zellular Sequencer * View page source -------------------------------------------------------------------------------- ZELLULAR SEQUENCER Replicating centralised services across multiple nodes creates a decentralised system that remains robust, even if some nodes fail or act maliciously—this is the essence of Byzantine Fault Tolerance. The first phase in decentralizing a centralized service using this approach is to replace the conventional username/password login with signature-based authentication at every place where users send their requests to enable each node to independently verify those requests. In the second phase, ensuring that all replicated nodes maintain the same data or state is crucial. This requires all nodes to receive and process user-signed requests in the exact same order. If nodes process updates in different orders, they can become out of sync. The Zellular Sequencer addresses this challenge by making sure that every node in the network processes every request in the same sequence. In Zellular Sequencer, one of the network nodes, the Sequencer, takes the leader role for sequencing tasks. User-signed requests received by a node are applied to the database only after being sent to the leader and received back along with other nodes’ requests in a consistent order. If the Sequencer malfunctions—by going offline, censoring requests, or sending inconsistent orders—other nodes can challenge its actions. Should enough nodes agree, the Sequencer’s role will seamlessly transfer to a new leader. This mechanism makes the Zellular Sequencer a Byzantine Fault Tolerant (BFT) service, facilitating sequencing without a single point of failure. Note This project is under active development. CONTENTS * Integration Guide * Python Code for a Simple Order-Book * Setting up the Environment * User Authentication * Order Submission * Order Matching * Applying Signature-based Authentication * Identifying Users by their Public Keys * Authorising Users by their Signatures * Sequencing orders before applying them * Sending orders to the Sequencer * Receiving sequenced orders from the sequencer * The Protocol * Design Principles * Proposer Rotation * Gossip Propagation * The Workflow * Posting * Finalising * Disputing * Switching Next -------------------------------------------------------------------------------- © Copyright 2021, Graziella. Built with Sphinx using a theme provided by Read the Docs.