Skip to content
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.

Added support for multiple royalty payments for FT tokens #188

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

chuwwwwi
Copy link

Added new types and functions for multiple royalty payments (Alice gets 10%, Bob gets 5%) in new token and manager files. These files are built off fa2_multi_ft_token and fa2_multi_ft_token_manager - they're mostly just copies of the original files with some new functionality added.

  • Added new data types that allow each token_id to have its own royalty scheme, an (address, nat) map that maps the royalty recipient to the percent of the transaction
  • Added a new entrypoint Royalty_transfer that supports tez payments in (batch) transfers of FT tokens; the user/caller of a batch royalty transfer will specify the amount of tez in each individual transfer
  • Added function to get and store the royalty scheme passed in by the user/admin upon token creation and to verify that the scheme is valid (sum of nats adds up to the specified total)
  • Added checks to prevent users from attempting to batch transfer tez out of the contract by specifying more tez than is sent with the contract call

Added new types and functions for multiple royalty payments (Alice gets 10%, Bob gets 5%) in new token and manager files. These files are built off `fa2_multi_ft_token` and `fa2_multi_ft_token_manager` (they're mostly just copies of the original files with some new functionality added).
  - Added new data types that allow each `token_id` to have its own royalty scheme, an `(address, nat) map` that maps the royalty recipient to the percent of the transaction
  - Added a new entrypoint `Royalty_transfer` that supports tez payments in (batch) transfers of FT tokens; the user/caller of a batch royalty transfer will specify the amount of tez in each individual transfer
  - Added function to get and store the royalty scheme passed in by the user/admin upon token creation and to verify that the scheme is valid (sum of `nat`s adds up to the specified `total`)
  - Added checks to prevent users from attempting to batch transfer tez out of the contract by specifying more tez than is sent with the contract call
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant