Reference application for connecting to the TAPLE DLT network.

Related tags

Cryptography sustainability blockchain distributed-ledger taple
Overview

⚠️ TAPLE is in early development and should not be used in production ⚠️


TAPLE Client

TAPLE (pronounced T+ 🍎 ['tapəl]) stands for Tracking (Autonomous) of Provenance and Lifecycle Events. TAPLE is a permissioned DLT solution for traceability of assets and processes. It is:

  • Scalable: Scaling to a sufficient level for traceability use cases.
  • Light: Designed to support resource constrained devices.
  • Flexible: Have a flexible and adaptable cryptographic scheme mechanism for a multitude of scenarios.
  • Energy-efficient: Rust powered, TAPLE is sustainable and efficient from the point of view of energy consumption.

TAPLE Client is the reference application for connecting to the TAPLE DLT network. It is written in Rust and internally uses TAPLE Core to implement the TAPLE protocol.

AGPL licensed

Technology | Develop | Core | Client | Tools

Build From Source

$ git clone https://github.com/opencanarias/taple-client.git
$ cd taple-client
$ cargo install --path client
$ taple-client --version

Docker images

Prebuilt docker images are available at Docker Hub.

Usage

Refer to our quick start guide and developer documentation to learn how to set up and run the application.

License

This project is licensed under the AGPL license.

You might also like...
A network application framework for Rust

This crate is deprecated! This crate is deprecated without an immediate replacement. Discussion about a successor can be found in tokio-rs/tokio#118.

Tokio 700 Dec 12, 2022
Diem’s mission is to build a trusted and innovative financial network that empowers people and businesses around the world.
Diem’s mission is to build a trusted and innovative financial network that empowers people and businesses around the world.

Note to readers: On December 1, 2020, the Libra Association was renamed to Diem Association. The project repos are in the process of being migrated. A

Diem 16.7k Jan 8, 2023
The Nervos CKB is a public permissionless blockchain, and the layer 1 of Nervos network.

Nervos CKB - The Common Knowledge Base master develop About CKB CKB is the layer 1 of Nervos Network, a public/permissionless blockchain. CKB uses Pro

Nervos Network 1k Dec 30, 2022
The Phala Network Blockchain, pRuntime and the bridge.
The Phala Network Blockchain, pRuntime and the bridge.

Phala Blockchain Phala Network is a TEE-Blockchain hybrid architecture implementing Confidential Contract. This repo includes: node/: the main blockch

Phala Network 314 Jan 6, 2023
A distributed, cryptographically-verifiable blog / social network

FeoBlog FeoBlog is a distributed blogging platform. It takes a lot of its inspiration from Mastodon and Scuttlebutt. It aims to solve a couple of prob

Cody Casterline 71 Dec 11, 2022
Employ your built-in wetware pattern recognition and signal processing facilities to understand your network traffic

Nethoscope Employ your built-in wetware pattern recognition and signal processing facilities to understand your network traffic. Check video on how it

Vesa Vilhonen 86 Dec 5, 2022
A value transfer bridge between the Monero blockchain and the Secret Network.

Secret-Monero-Bridge A value transfer bridge between the Monero blockchain and the Secret Network. Proof-of-Concept Video Demonstration: https://ipfs.

null 28 Dec 7, 2022
Substrate Node for Anmol Network
Substrate Node for Anmol Network

Anmol Substrate Node 🖼 🛠️ 👷 Anmol is the First Cross-Chain NFT Toolkit, on Polkadot. Introducing: Moulds NFT Breeding Multi-Chain NFT Migration ink

Anmol Network 12 Aug 28, 2022
Scans the Ethereum network for USDT ERC-20 token transfer transactions

ethscan This is a Rust command line program for scanning the Ethereum blockchain for USDT transfers within a time span and amount span. prerequisites

Frank Buss 4 Oct 6, 2022
Comments
  • Error irrecuperable al añadir un nuevo nodo a la gobernanza

    Error irrecuperable al añadir un nuevo nodo a la gobernanza

    Hola,

    Gracias por haber liberado este producto que espero pueda ayudar en muchos proyectos de trazabilidad. Os comento un error que me he encontrado.

    Siguiendo el tutorial descrito en la web de TAPLE y descrito como "TAPLE from 0", he producido un error irrecuperable y un aparente corte de las comunicaciones entre los nodos en caso de emplear un subject_id equivocado.

    Concretamente, en el paso llamado "Adding the second node to governance", si por un error (o de forma intencionada), en los datos de la petición se utiliza un subject_id equivocado (identificador del sujeto correspondiente a la gobernanza creada en el paso justo anterior), en el nodo_0 aparece este error:

    [2023-01-26T18:16:14Z ERROR protocol::request_manager::manager] Request Manager fail: RequestError(SubjectNotFound)
[2023-01-26T18:16:14Z INFO  rest::handlers] data: Err(InternalError { source: ComunnicationClosed })

    Si tras el error se corrige el subject_id y se utiliza el correcto, la petición se queda bloqueada y sin respuesta, posiblemente por la pérdida de comunicaciones entre los nodos que indica el error.

    La única manera de recuperarse del error que he encontrado es tirar toda la red y empezar desde cero.

    El resultado esperado debería ser un error controlado indicando que no se ha encontrado el subject_id y no dejar la red en ese estado inconsistente.

    Saludos cordiales!

    bug 
    opened by bcuestav 2
  • Persistencia en caso de caida súbita de la red (Docker)

    Persistencia en caso de caida súbita de la red (Docker)

    En caso de que la red la tengamos levantada en contenedores, y hubiese una caida súbita de todos los nodos, entiendo que los datos existentes se perderían en el olvido...

    En el caso de querer persistir estos datos, o querer realizar backups, ¿en que rutas se almacenan los archivos?

    En el caso de Docker, la idea sería crear volumenes en alguno de los nodos, a modo de aportar esa seguridad.

    ¿Teneis esto contemplado?

    Saludos

    opened by rubensantibanezacosta 1
Releases(v0.1.4)

  • v0.1.4(Feb 24, 2023)

    What's Changed

    • fix(TAP-1044): Fix --version message
    • build(TAP-1037): Workspace dependencies
    • hotfix(TAP-1032): Database path env name changed to TAPLE_DATABASE_PATH. Workspace dependencies added too. by @FlorentinPG in https://github.com/opencanarias/taple-client/pull/9

    Full Changelog: https://github.com/opencanarias/taple-client/compare/v0.1.3...v0.1.4

    Source code(tar.gz)
    Source code(zip)

  • v0.1.3(Feb 24, 2023)

    What's Changed

    feat: Extensible configuration fix(998): Indication of errors more in line with the real reasons feat(TAP-1005): Support for hidden parameters refactor(TAP-1008): Public Rest Handlers chore: Public REST API routes feat(TAP-997): Pagination in GET Governances build(TAP-892): Upgdrade Workspace dependencies. by @FlorentinPG in https://github.com/opencanarias/taple-client/pull/7 build(TAP-829): Replace client by taple_client build(TAP-1028): Dockerfile added. by @FlorentinPG in https://github.com/opencanarias/taple-client/pull/8

    New Contributors

    • @FlorentinPG made their first contribution in https://github.com/opencanarias/taple-client/pull/7

    Full Changelog: https://github.com/opencanarias/taple-client/compare/v0.1.2...v0.1.3

    Source code(tar.gz)
    Source code(zip)
Owner
Open Canarias
Open Canarias
GitHub https://www.taple.es
An example CosmWasm contract for connecting contracts over IBC.

CosmWasm IBC Example This is a simple IBC enabled CosmWasm smart contract. It expects to be deployed on two chains and, when prompted, will send messa

ekez 64 Jun 21, 2023
Reference client for NEAR Protocol

Reference implementation of NEAR Protocol About NEAR NEAR's purpose is to enable community-driven innovation to benefit people around the world. To ac

NEAR 2k Jan 3, 2023
Reference implementation for the Poseidon Snark-friendly Hash algorithm.

Dusk-Poseidon Reference implementation for the Poseidon Hashing algorithm. Reference Starkad and Poseidon: New Hash Functions for Zero Knowledge Proof

Dusk Network 96 Jan 2, 2023
Reference client for NEAR Protocol

Reference implementation of NEAR Protocol About NEAR NEAR's purpose is to enable community-driven innovation to benefit people around the world. To ac

NEAR 2k Jan 4, 2023
A reference NFT Staking Program & Client for Solana NFTs

This is a reference NFT Staking Program & Client for Solana NFTs. This program is compatible with both Candy Machine v1 and Candy Machine v2 NFTs.

Tracy Adams 73 Dec 19, 2022
Twinsies is a specialized reference-counting pointer where the item is jointly owned in 2 places

twinsies Twinsies is a special shared pointer, similar to an Arc, where two specific objects (called [Joint]) share joint ownership of the underlying

Nathan West 17 Feb 1, 2023
Cross-chain bridge message delivery network. We are hiring, [email protected]

Introduction Implementation of a https://darwinia.network node in Rust based on the Substrate framework. This repository contains runtimes for the Dar

Darwinia Network 225 Nov 8, 2022
ARYA Network is a polkadot/substrate based chain for Non-fungible Token platform on which we can own sell and buy the NFT's on polkadot network.

ARYA Network ARYA Network is a polkadot/substrate based chain for Non-fungible Token platform on which we can own sell and buy the NFT's on polkadot n

Pankaj Chaudhary 6 Dec 20, 2022
The Zenotta Network Protocol (ZNP), the network that supports the Zenotta blockchain

Zenotta Network Protocol A repo for the development of the Zenotta Network Protocol (ZNP). We will regularly be updating links and easter eggs inside

Zenotta AG 10 Apr 2, 2023
dWallet Network, a composable modular signature network is the home of dWallets

Welcome to dWallet Network dWallet Network, a composable modular signature network is the home of dWallets. A dWallet is a noncollusive and massively

dWallet Labs 8 Feb 26, 2024