<p>On the Waves platform, it is possible for transaction fees to be paid in tokens. To do this, a full node with mining capabilities (anyone can run a node, but at least 10,000 WAVES is required to generate blocks) has to accept the particular token as a fee.</p>

<p>Thus, Burger King Russia could either host a full node or persuade another full node to accept Whoppercoin. Burger King Russia plans to have an app on both the Apple Store and on Google Play for the loyalty program. 
These apps will likely make use of the Waves Node REST API by specifying the fee asset as Whoppercoin.</p>

<p>Here is the relevant API:</p>

<pre><code>POST /assets/broadcast/transfer
</code></pre>

<p>Here are the relevant parameters:</p>

<pre><code>"type" - Transaction type (4 for TransferTransaction)
"id" - Id(hash) of transaction, Base58-encoded
"assetId" - Asset ID in Base58 format, effectively equals transaction id 
"timestamp" - Transaction timestamp
"sender" - Sender account's address, Base58-encoded
"senderPublicKey" - Sender account's public key, Base58-encoded
"recipient" - Recipient account's address, Base58-encoded
"feeAsset" - Asset ID of transaction fee, currently is null, i.e. WAVES
"fee" - Amount of transaction fee
"attachment" - Attachment, Base58-encoded
"signature" - Signature of all transaction data, Base58-encoded
</code></pre>

<p>Here is a request JSON example:</p>

<pre><code>{
  "type": 4,
  "id": "3xPyT73TGV7c5PKEJpicwSsX7PXyi3Lm1JFNQivFRLuy",
  "sender": "3NBVqYXrapgJP9atQccdBPAgJPwHDKkh6A8",
  "senderPublicKey": "CRxqEuxhdZBEHX42MU4FfyJxuHmbDBTaHMhM3Uki7pLw",
  "recipient": "3Mx2afTZ2KbRrLNbytyzTtXukZvqEB8SkW7",
  "assetId": "E9yZC4cVhCDfbjFJCc9CqkAtkoFy5KaCe64iaxHM2adG",
  "amount": 5500000000,
  "feeAsset": null,
  "fee": 100000,
  "timestamp": 1479222433704,
  "attachment": "BJa6cfyGUmzBFTj3vvvaew",
  "signature": "2TyN8pNS7mS9gfCbX2ktpkWVYckoAmRmDZzKH3K35DKs6sUoXHArzukV5hvveK9t79uzT3cA8CYZ9z3Utj6CnCEo"
}
</code></pre>

<p>On Waves platform right now, you can buy Whoppercoin on the Waves DEX, and the fee is 0.003 Waves. I demonstrated this here: <a href="https://youtu.be/ZAFZNEwIooM" rel="nofollow noreferrer">https://youtu.be/ZAFZNEwIooM</a></p>

<p>Additionally, you can transfer Whoppercoin between accounts, and the fee is 0.001 Waves. I demonstrated this here: <a href="https://youtu.be/OYHPlgj0HjY" rel="nofollow noreferrer">https://youtu.be/OYHPlgj0HjY</a></p>

CC BY-SA 3.0
2017-09-06T18:23:14.560Z
So the full node with 10,000 Waves will pay for the fees in Waves while taking in WhopperCoin? Is there more technical details of how this would work when paying fees in the child coin?
Patoshi パトシ
CC BY-SA 3.0
2017-09-06T23:00:38.787Z
The full node with mining capabilities can be configured to accept Whoopercoin as a fee.
See this link for details on the API: https://github.com/wavesplatform/Waves/wiki/Waves-Node-REST-API#post-assetsbroadcastbatch-transfer
deeplizard
CC BY-SA 3.0
2017-09-07T16:05:41.067Z
But this is assuming that miner is its turn to mine. What if that miner doesnt mine the current block. Does the whoppercoin user that sent the coin have to wait until that particular miner mines it?
Patoshi パトシ
CC BY-SA 3.0
2017-09-06T01:28:15.690Z
2017-09-06T22:49:13.003Z
2017-09-06T22:49:13.003Z
deeplizard
<p>Whopper Coin was recently released in Russia using the Waves platform, but what is the native fee a user has to pay when sending the Whopper coin back to the establishment? If a customer receives Whopper coin from Burger King, now the customer would have to redeem these coins by sending it back to Burger King. How are the fees paid? Are the fees in Whopper Coin or the main Waves coin? How did they solve this inherit problem when issuing coins like this on top of an existing blockchain platform.</p>

<transaction-fees><altcoin><colored-coins>
How does Whopper Coin released in the summer of 2017 on the Waves platform solve the native fee problem inherit with many colored coin approaches?
Patoshi パトシ
# How does Whopper Coin released in the summer of 2017 on the Waves platform solve the native fee problem inherit with many colored coin approaches?

(Asked by: username_0 on 2017-08-31)

Whopper Coin was recently released in Russia using the Waves platform, but what is the native fee a user has to pay when sending the Whopper coin back to the establishment? If a customer receives Whopper coin from Burger King, now the customer would have to redeem these coins by sending it back to Burger King. How are the fees paid? Are the fees in Whopper Coin or the main Waves coin? How did they solve this inherit problem when issuing coins like this on top of an existing blockchain platform.

**Tags:** transaction-fees, altcoin, colored-coins


---

## 1 answers

### Answer by username_1 on 2017-09-06. Score: 2

On the Waves platform, it is possible for transaction fees to be paid in tokens. To do this, a full node with mining capabilities (anyone can run a node, but at least 10,000 WAVES is required to generate blocks) has to accept the particular token as a fee.

Thus, Burger King Russia could either host a full node or persuade another full node to accept Whoppercoin. Burger King Russia plans to have an app on both the Apple Store and on Google Play for the loyalty program.
These apps will likely make use of the Waves Node REST API by specifying the fee asset as Whoppercoin.

Here is the relevant API:

```
POST /assets/broadcast/transfer

```

Here are the relevant parameters:

```
"type" - Transaction type (4 for TransferTransaction)
"id" - Id(hash) of transaction, Base58-encoded
"assetId" - Asset ID in Base58 format, effectively equals transaction id 
"timestamp" - Transaction timestamp
"sender" - Sender account's address, Base58-encoded
"senderPublicKey" - Sender account's public key, Base58-encoded
"recipient" - Recipient account's address, Base58-encoded
"feeAsset" - Asset ID of transaction fee, currently is null, i.e. WAVES
"fee" - Amount of transaction fee
"attachment" - Attachment, Base58-encoded
"signature" - Signature of all transaction data, Base58-encoded

```

Here is a request JSON example:

```
{
  "type": 4,
  "id": "3xPyT73TGV7c5PKEJpicwSsX7PXyi3Lm1JFNQivFRLuy",
  "sender": "3NBVqYXrapgJP9atQccdBPAgJPwHDKkh6A8",
  "senderPublicKey": "CRxqEuxhdZBEHX42MU4FfyJxuHmbDBTaHMhM3Uki7pLw",
  "recipient": "3Mx2afTZ2KbRrLNbytyzTtXukZvqEB8SkW7",
  "assetId": "E9yZC4cVhCDfbjFJCc9CqkAtkoFy5KaCe64iaxHM2adG",
  "amount": 5500000000,
  "feeAsset": null,
  "fee": 100000,
  "timestamp": 1479222433704,
  "attachment": "BJa6cfyGUmzBFTj3vvvaew",
  "signature": "2TyN8pNS7mS9gfCbX2ktpkWVYckoAmRmDZzKH3K35DKs6sUoXHArzukV5hvveK9t79uzT3cA8CYZ9z3Utj6CnCEo"
}

```

On Waves platform right now, you can buy Whoppercoin on the Waves DEX, and the fee is 0.003 Waves. I demonstrated this here: <https://youtu.be/ZAFZNEwIooM>

Additionally, you can transfer Whoppercoin between accounts, and the fee is 0.001 Waves. I demonstrated this here: <https://youtu.be/OYHPlgj0HjY>

> **Comments:**
> **username_0**: So the full node with 10,000 Waves will pay for the fees in Waves while taking in WhopperCoin? Is there more technical details of how this would work when paying fees in the child coin?  
> **username_1**: The full node with mining capabilities can be configured to accept Whoopercoin as a fee. See this link for details on the API: https://github.com/wavesplatform/Waves/wiki/Waves-Node-REST-API#post-assetsbroadcastbatch-transfer  
> **username_0**: But this is assuming that miner is its turn to mine. What if that miner doesnt mine the current block. Does the whoppercoin user that sent the coin have to wait until that particular miner mines it?  

---

