LogoLogo
Exchange
Exchange
  • Introducing: LX
  • Main Features
    • Social Features
  • Reliability
  • High Liquidity
  • High Performance
  • Simple Trading
  • Diversity
  • Interoperability/Bridge
  • User Support
  • Transparency
  • Security
  • The Problem
    • Negative Consequences of Centralization
  • The Solution
    • Security Solutions as a Decentralized Exchange
  • LX: A Decentralized Social Trading Platform
    • Lux Exchange DAO
  • Decentralized Application
  • User Experience
    • Easy to use
  • Accounts, Wallets, and Keys
  • Authentication
  • Features
    • Hardware Wallets
  • Portfolios
  • Social Trading
  • People Based Portfolios
  • Copy Swaps
  • Trading Charts
  • Indicator Alarm Manager
  • Smart Search
  • Watchlist
  • Community Support
    • Decentralized community service
  • Rewarded Content Production/Trading Bots
  • Token Curated Customer Service
  • LX Architecture
    • LX Architecture Comparison
  • eToro
  • EtherDelta
  • 0x Protocol
  • LX
  • Lux Protocol
    • Lux as a Distributed Autonomous Organization (DAO)
  • Governance
  • Lux Consensus
  • Terminology
  • Election Triggers
  • Attacks
    • Tragedy of Commons
  • Collusion
  • Censorship
  • ASIC Attacks
  • Long Range Attacks
  • Treasury and Bounty
    • Budgeting
  • Bounty
  • Lux Tokenomics
  • Decentralized Liquidity Pool (DLP)
  • Market Maker Fees
  • LX C++ Application Programming Interface (API)
  • Permission Mapping
  • Permission Evaluation Applied to Copy Trading
  • Parallel Permission Evaluation
  • LX Key Capabilities
  • Atomic Swaps
  • Facilitating Liquidity
  • Exchange Traded Funds
  • Crypto-asset Custody for Gateways
  • Cold Wallet
  • Smart coins
  • Crypto-asset Volatility
  • Gold as Collateral
  • Incentives
  • Interest Rate
  • Development Roadmap
  • LUX Constitution and Ricardian Contracts
  • Lux Protocol
  • DEX Core Platform
  • DApp UI/UX
  • Hardware Wallet Integration
  • Quality Assurance
Powered by GitBook
On this page

Was this helpful?

Quality Assurance

PreviousHardware Wallet Integration

Last updated 2 years ago

Was this helpful?

All code must be tested by ’s tools to perform CERT and IEC 61508 Quality Assurance.

The (Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems), is an international standard widely used in Industrial Automation. The IEC61508 standard also requires use of coding standards, such as and .

CERT is maintained by the Software Engineering Institute (SEI), a research and development center primarily funded by the U.S. Department of Defense and the Department of Homeland Security. The CERT Division at SEI is operated by Carnegie Mellon University and responsible for publishing these standards. The CERT® Secure Coding Standards for C and C++ are standards that provide rules and recommendations that target insecure coding practices and undefined behaviors that can lead to exploitable vulnerabilities.

It is our goal to maintain IEC 61508 and CERT compliance in all code design and development. There are many existing and emerging standards that might be applied but the IEC 61508 and CERT specifications align closely with our commitment to provide quality services and error free processing. It achieve this goal the C++ code must be tested to assure that:

Quality Assurance of all C++ code must be ensured for and compliance.he

The C++ code must also be tested against:

  • Application level vulnerabilities

    • Cross domain information leakage (Onchain name servers for domain registry)

    • Client side logic and data storage vulnerabilities

    • Cloud configurations vulnerabilities

  • Blockchain level vulnerabilities

    • Input validation and representation

    • API abuse

    • Access control mechanisms

    • Memory management

    • Time and state

    • Error and exception handling

    • Encapsulation and hidden defects

    • Flaws at browser runtime

    • Insecure JNI

    • Unused variables after assignment

QA-SYSTEM
QA-C and QA-C++
IEC61508
MISRA
CERT
IEC 61508
CERT