Try   HackMD

ICRC-1 Compliant Payment Library

Overview

  • Status: Open
  • Project Type: Traditional - One worker contributes, and one worker is paid
  • Time Commitment: Weeks
  • Experience Level: Intermediate
  • Size: USD 5'000 (client) + USD 2'500 (canister) in ICP (at time of distribution)

Description

One of the advantages to deploy a service on a blockchain platform is to be able to receive payments without the usage of a 3rd party service provider. In order to simplify the development of services that want to receive payments, we need libraries that can be integrated into client software and canisters. The base ICRC-1 standard supports the client-orchestrated transfer/notify flow, i.e. the client (payer) transfers the token to service-designated subaccount and notifies the service (payee) about the transfer. This process should abstracted by a library.

High-level flow diagram

        

    

    

      Image Not Showing
      Possible Reasons
      
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported

      Learn More →

Notes

  • The diagram shows one possible abstraction for a "Payment client library"
  • The client library would utilze agent-js to perform (transfer and notify) calls.
  • The abstraction of a "Payment service library" is not illustrated.
  • The invoice and its relation to a subaccount will probably need to be standardized at some point. Allowing for different compatible payer and payee implementions. We hope that this implementation will inform a potential standardization.

Acceptance Criteria

  • Must support ICRC-1 token standard
  • JavaScript/TypeScript payment client library implementation
  • Motoko and/or Rust library to be integrated into canisters
  • Unit and E2E tests
  • Documentation
  • Sample application

Further Information

If you’re only skilled in one of the programming languages, please apply anyway, we might be able to split the grant among different grantees.

If you want to work on that bounty you should participate in the Ledger & Tokenization Working Group.

References

Last changed by 
 
Dominic Wörner
0
193

Read more

ICP IBC integration

One of the core capabilities of ICP is threshold cryptography (Chain-Key Cryptography). Currently ICP subnets use Threshold BLS signatures to authenticate state and responses, and allow smart contracts to request ECDSA (over the Bitcoin curve secp256k10) signatures. Each smart contract has a dedicated path in the key derivation tree and can derive public keys and request signatures accordingly.

Jan 29, 2024
Bitcoin Bounties

Decentralized Inscription Service

Jul 21, 2023
ICP Hackathon Cheat Sheet

Hey fellow hacker :wave: , great that you want to explore the capabilities and possibilities of the Internet Computer Protocol. We've compiled a list of resources to make starting off as simple as possible, and provide you a quick reference to find more information, tools and help. General Introduction Tweet thread sized pitch of ICP Introduction to ICP Introduction video from ETHDenver Comparison between different blockain platforms

Apr 25, 2023
BNT-X - Decentralized Exchange Data Interface

Overview Status: Draft Project Type: Cooperative - Multiple workers can submit work, and the bounty is shared Time Commitment: Weeks Experience Level: Intermediate Size: USD 25'000 in ICP (at time of distribution) Description In order to provide more visibility of the Internet Computer DeFi ecosystem, ICRC-1 tokens and decentralized exchanges should be listed on the popular financial data provider websites of the cryptocurrency industry, such as CoinMarketCap and DefiLlama. For this, the IC ecosystem needs to define and implement standard interfaces that meet the requirements of the financial data providers. The goal of this bounty is the creation of interface standards and implementations for AMM and orderbook-based decentralized exchanges (DEXes).

Apr 6, 2023
Read more from Dominic Wörner
Published on HackMD