[PA RFC-0006] Deck native fee

peerchemist · September 18, 2017, 9:05pm

PeerAssets/peerassets-rfcs/blob/master/0006-deck-native-fee.md

# Deck native fee

- Status: proposed
- Type: new feature
- Related components: 0001-peerassets-transaction-specification.proto
- Start Date: 27-08-2017
- Discussion: https://talk.peercoin.net/t/pa-rfc-0006-deck-native-fee/5994
- author: Peerchemist

## Summary

Deck native fee allows for card transfer fee expressed in the deck's native token. Per-deck fee is set upon deck spawn and becomes the requirement of each valid card transfer on the deck. Procedure is the same as if every card transfer on the deck also included a card burn transaction for some amount of cards (tokens) which means that each fee is deducted from the total supply of the card on the deck.

## Conventions
- The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119).

## Motivation

There is utility in having a deck native fee, notably as card transfer fees act as deflationary force on the card supply allowing for creation of dynamic economic system revolving around token in question.

This file has been truncated. show original

Nagalim · September 18, 2017, 9:44pm

Yes please. Of course, I will ask about making it a % fee on all outputs rather than just a static amount.

Edit: I see that you leave the ‘fee’ open to be multiplied, but I’m unclear how this is chosen based on your deck spawn.

peerchemist · September 19, 2017, 10:49am

This is just the simplest fee structure possible, static fee per bundle. Naturally we can expand on the topic.

Sorry I do not understand what are you saying.