RDDL Network
  • 👋Welcome to RDDL
    • 💡What we do
    • ✨Our Features
  • Basics
    • ✅Understanding RDDL
    • 🎭Actors
    • ⛓️Networks
    • 🪙Tokens
      • RDDL on Liquid
      • Conversion Rate
    • 🎆Types of Nodes
      • 👛Wallet Management
      • 🔐Key Ceremony
    • 🤝Token Services
      • Machine Identity Attestation
      • RDDL Purpose Tokens
      • Wrapped Tokens
      • CID Asset Notarization
    • 🏁Proof of Productivity
      • 👩‍🎤Actor Selection
      • ⁉️Challenge-Response
      • 💰Rewards
        • 🔢Reward Calculation
        • ⌚Clearance Process
        • 🪙Claiming Rewards
    • 🤝Reissuance & Distribution
  • Getting Started
    • ❓How can I participate?
    • ⚡The EnergyAgent
      • ▶️Installation
    • ⚓Trust Wallet
    • SMD (Smart Metering Device)
  • Workflows & Governance
    • Converting RDDL to PLMNT
    • Voting on chain parameters
  • ⚒️Infrastructure
    • 🧁Services
Powered by GitBook
On this page
  1. Getting Started

Compatibility Requirements

A list of requirements that qualify a device to be RDDL-compatible.

Last updated 11 months ago

RDDL Network maintains a reference implementation of , supporting all the basic functionalities to participate in the RDDL Network protocol.

  • Support of a unique machine identifier (Machine ID) in the form of a public-private key pair. This key pair works as the anchor of Trust and can reside in a hardware-based or within a unique firmware.

  • Network configuration needs to be possible so that the Testnet and Mainnet can be configured for the device:

    • ChainID: the chainid of the network the device is connected against.

    • API: the API of a node or validator

    • Denominator token: TRDDL vs RDDL

    • Key initialization: setting of a Mnemonic to recover in the case of disaster recovery.

  • Behavioural configuration

    • Machine Attestation configuration

    • Asset attestation periodicity

  • Actionability

    • Export public keys to enable account funding on Planetmint

    • Attest itself to the network

    • Attest assets/CIDs

    • Store CIDs and corresponding data for at least 45 days

    • Implement the command for MQTT/XMPP as defined in the reference implementation at the repository.

🤓
Tasmota
Trust Anchor
PoPChallenge
RDDL-Tasmota