#enable clawback

6 messages · Page 1 of 1 (latest)

pulsar crest
#

hey, can i set clawback enable flag using soroban after an uset established trustline to asset ?

heady quartz
#

Hi, there! two things:

  1. If you want a trustline to be eligible for clawback, the trustline must be created after the clawback_enabled flag has been set on the issuing account.
  2. At the moment, the account-level flags that control asset issuance can't be set using Soroban. They must be changed using a Stellar transaction with a setOptions operation.
ornate otter
#

if you believe that this feature enables some features/use cases that are impossible to implement now, please feel free to file a feature request against https://github.com/stellar/rs-soroban-env/issues and we'll triage it for the next protocol version. just make sure to descirbe your use case in details

GitHub
Issues · stellar/rs-soroban-env

Rust environment for Soroban Contracts. Contribute to stellar/rs-soroban-env development by creating an account on GitHub.

final sand
# heady quartz Hi, there! two things: 1. If you want a trustline to be eligible for clawback, ...

Also, not so well known, it is possible to update a trustline that was created prior to the clawback being enabled for the asset. You’ll use the set trustline flags operation targeting the specific trustline you wanna change and enable clawback for that trustline.

docs: https://developers.stellar.org/docs/encyclopedia/clawbacks#set-trust-line-flag

(Only through classic transactions)

Clawbacks | Stellar Documentation

Clawbacks were introduced in CAP-0035 and allow an asset issuer to burn a specific amount of a clawback-enabled asset from a trustline or claimable balance, effectively destroying it and removing it from a recipient’s balance.

idle jackal
ornate otter
#

I think feature requests are fine - having a CAP per every new host function would be an overkill really. we also need to figure out if we want to do that at all before spending any time on design.