Sameh Abouel-saad

Thank you, Dylan. It's much clearer now!

**Update:** After researching this, I found that relying on the next block author check in this case is unreliable and can cause more harm than good. Let me explain why....

**Update:** The is_next_block_author function was removed, and the verification now happens at runtime. If the caller is a validator, the transaction fee is waived. This change allows any validator with...

**Update:** I conducted some tests on the new approach, and what works well now is that all validators who call billContractForBlock are exempt from transaction fees, regardless of whether the...

**Update:** I observed weird behavior while testing, when offchain worker transaction fails with low priority error every 600 blocks / era. So contacts that suppose to bullied at index 599...

### Update: I experimented with an alternative approach that introduces a SignedExtension to the pallet-smart-contract module that ensures unique transaction processing for the `bill_contract_for_block` function by setting a provides tag...

Burning tokens in tfchain can happen in one of three scenarios: 1- **Voluntary Token Burning**: Users can voluntarily burn their tokens using the `Burning` pallet( `burnTft` call). 2- **Cultivation Rewards...

> The plan now is to end the burning of TFT on TF Chain as part of the billing flow so we can have a supply of precisely 1B TFT....

> I don't think it makes sense to automate this process on the bridge. We can just perform a manual burn of Stellar TFT to remove the supply burned on...

@scottyeager Is there any update on this?