-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
NFT issuer is inadvertently creating a trustline due to third-party transactions(Version: 2.1.0) #4925
Comments
Do you have any example transaction(s)? |
You can find gist code in the supporting files. |
Yes, that's the code you used to generate transaction, but what I'm asking for is transaction IDs that have already been validated, and which network they're on. |
This NFTokenAcceptOffer transaction creates a trustline for NFT's Issuer account. NFToken issuer account |
Yep. Confirmed that this is a legitimate issue. |
Fix bugs in interactions between NFTokenOffers and trust lines. Since the NFTokenAcceptOffer does not check the trust line that the issuer receives as a transfer fee in the NFTokenAcceptOffer, if the issuer deletes the trust line after NFTokenCreateOffer, the trust line is created for the issuer by the NFTokenAcceptOffer. That's fixed. Also if Alice issues an IOU and also mints NFTokens with a transfer fee, Alice's IOU cannot be used to pay for transfers of those NFTokens. That's fixed. Resolves XRPLF#4925. Resolves XRPLF#4941.
Fix bugs in interactions between NFTokenOffers and trust lines. Since the NFTokenAcceptOffer does not check the trust line that the issuer receives as a transfer fee in the NFTokenAcceptOffer, if the issuer deletes the trust line after NFTokenCreateOffer, the trust line is created for the issuer by the NFTokenAcceptOffer. That's fixed. Also if Alice issues an IOU and also mints NFTokens with a transfer fee, Alice's IOU cannot be used to pay for transfers of those NFTokens. That's fixed. Resolves XRPLF#4925. Resolves XRPLF#4941.
Fix bugs in interactions between NFTokenOffers and trust lines. Since the NFTokenAcceptOffer does not check the trust line that the issuer receives as a transfer fee in the NFTokenAcceptOffer, if the issuer deletes the trust line after NFTokenCreateOffer, the trust line is created for the issuer by the NFTokenAcceptOffer. That's fixed. Also if Alice issues an IOU and also mints NFTokens with a transfer fee, Alice's IOU cannot be used to pay for transfers of those NFTokens. That's fixed. Resolves XRPLF#4925. Resolves XRPLF#4941.
Fix interactions between NFTokenOffers and trust lines. Since the NFTokenAcceptOffer does not check the trust line that the issuer receives as a transfer fee in the NFTokenAcceptOffer, if the issuer deletes the trust line after NFTokenCreateOffer, the trust line is created for the issuer by the NFTokenAcceptOffer. That's fixed. Resolves XRPLF#4925.
Fix interactions between NFTokenOffers and trust lines. Since the NFTokenAcceptOffer does not check the trust line that the issuer receives as a transfer fee in the NFTokenAcceptOffer, if the issuer deletes the trust line after NFTokenCreateOffer, the trust line is created for the issuer by the NFTokenAcceptOffer. That's fixed. Resolves #4925.
Fix interactions between NFTokenOffers and trust lines. Since the NFTokenAcceptOffer does not check the trust line that the issuer receives as a transfer fee in the NFTokenAcceptOffer, if the issuer deletes the trust line after NFTokenCreateOffer, the trust line is created for the issuer by the NFTokenAcceptOffer. That's fixed. Resolves XRPLF#4925.
Issue Description
Since the NFTokenAcceptOffer does not check the trust line that the issuer receives as a transfer fee in the NFTokenAcceptOffer, if the issuer deletes the trust line after NFTokenCreateOffer, the trust line is created for the issuer by the NFTokenAcceptOffer.
Steps to Reproduce
Expected Result
NFTokenAcceptOffer transaction fails with
terNO_LINE
Actual Result
NFTokenAcceptOffer transaction succeeds and a trustline is created for the issuer.
Environment
rippled 2.1.0
Supporting Files
https://gist.github.com/tequdev/f5cfd3f3cfbfcf4a22205052962e6cfe
The text was updated successfully, but these errors were encountered: