Skip to content

Latest commit

 

History

History
95 lines (64 loc) · 3.13 KB

iip-35.md

File metadata and controls

95 lines (64 loc) · 3.13 KB
Raw
iip title author discussions-to status type category created requires
35
ICON BTP Fee Gathering
Heonseung Lee (@leeheonseung)
Draft
Standards Track
IRC
2020-05-13
25

Simple Summary

It standardizes the structure in which fees can be charged from BTP network users to cover maintaining costs and activation incentives the IIP-25 (BTP) network.

Abstract

IIP-25 (BTP) Network fee is charged to users and standardize about operation policy. Defines the operating entity that gathers a fee. Defines Fee Aggregator (FA). Defines interfaces related to FeeGathering BMC message.

Motivation

In order to cover maintaining costs and activation incentives the IIP-25 (BTP) network, a structure is needed to charge fees from users who send BTP message.

The chain to which the entity operating the BTP Network belongs is defined as HUB. The smart contract, which operates with fees from the BTP service, is defined as Fee Aggregator (FA).

The BTP network user pays a fee to the BSH that provides the BTP service of the chain to which he belongs. The operating entity uses HUB's Fee Aggregator (FA) to collect the fees stored in each chain BSH and operates the BTP network. Through HUB's BMC.sendFeeGatheringMessage, you can request a BTP message that sends a fee to each chain's BMC to FA.

Specification

Terminology

  • HUB The chain to which the entity operating the BTP network belongs.
  • Fee Aggregator (FA) Smart contract to to raise the necessary financial resources for BTP network operation by gathering fees collected from other chains connected.
  • FeeGathering BMC message & Handle FeeGathering message Interface that processes the logic that transfers the fees stored in the BSH to the Fee Aggregator (FA).

BTP Message Center - Extension

Ref. BTP message center

HUB's BMC sends FeeGathering BMC message to each link when certain conditions are satisfied, and calls handleFeeGathering from the service managed each BMC of that chains.

Message Struct

FeeGathering Message

HUB's BMC.handleRelayMessage logic sends FeeGathering BMC message to each chain according to the policy.

Name Type Description
fa String BTP Address of FeeAggregator
svcs List of String list of name of service

When BMC receive this message, find the BSH using 'svcs' and then calls BSH.handleFeeGathering with '_fa'

BTP Service Handler - Extension

Ref. BTP Service Handler

Interface that processes the logic that transfers the fees stored in the BSH to the Fee Aggregator (FA).

Interface

Writable methods
handleFeeGathering
@external
def handleFeeGathering(self, _fa: str, _svc: str):
  • Description
    • Handle the FeeGathering Message.
    • Accept the error only from the BMC.
  • Params
    • _fa: String ( BTP Address of Fee Aggregator )
    • _svc: String ( Name of the service )

Implementation

TBD

Copyright

Copyright and related rights waived via CC0.