-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to build RevokeSponsorshipOp on txbuild? #3001
Comments
That's one good option. Alternatively we could reuse the func RevokeTrustLineSponsorshipOp(SponsorshipRevocationTarget)
type SponsorshipRevocationTargetType int
const (
SponsorshipRevocationTargetTypeAccount SponsorshipRevocationTargetType = iota
SponsorshipRevocationTargetTypeTrustline SponsorshipRevocationTargetType
SponsorshipRevocationTargetTypeOffer SponsorshipRevocationTargetType
SponsorshipRevocationTargetTypeData SponsorshipRevocationTargetType
SponsorshipRevocationTargetTypeBalance SponsorshipRevocationTargetType
SponsorshipRevocationTargetTypeSigner SponsorshipRevocationTargetType
)
type SponsorshipRevocationTarget struct {
Type SponsorshipRevocationTargetType
Account *string
TrustLine *SponsorshipRevocationTargetTrustLine
Offer *SponsorshipRevocationTargetOffer
Data *SponsorshipRevocationTargetData
ClaimableBalance *SponsorshipRevocationTargetClaimableBalance
Signer *SponsorshipRevocationTargetSigner
}
type SponsorshipRevocationTargetTrustLine {
AccountId string
Asset Asset
}
[...] |
@abuiles are you taking up this one? (i.e. implementing the |
@2opremio no. I thought you were doing it as part of the integration test work. Let's do the implementation first in the internal txnbuild and we can work on the official one next week. |
Sure |
RevokeSponsorshipOp
requires users to build aLedgerKey
or a struct for signers sponsorships. We need to expose a helper or helpers to make it easy for users to create such operation.A possible approach could be to add functions for each ledger key. For example:
The text was updated successfully, but these errors were encountered: