Amendment Proposal: Selective Blocking of NFT Offers

[Cavey773]

Selective Blocking of NFT Offers

1. Abstract

This proposal lets an account block specific addresses from creating new NFToken offers that target it. When a blocked address tries to create a buy offer on one of the account’s NFTs (or a sell offer with that account as Destination), the transaction fails with tecNO_PERMISSION. A blocked address may still accept an existing sell offer that the blocking account has already created. Offers from all other addresses continue to work normally.

2. Motivation

NFT holders frequently receive unwanted lowball or spam offers from the same addresses. The existing asfDisallowIncomingNFTokenOffer flag blocks all incoming offers, which is too broad for most users. A selective block would let holders stop specific bad actors from creating new offers while still allowing those addresses to accept sell offers the holder has already listed.

3. Specification

3.1. Block List

An account may create and delete records that identify blocked addresses. Each blocked address is stored as a ledger object owned by the blocking account (subject to the normal owner reserve).

3.2. Enforcement

Enforcement applies only to NFTokenCreateOffer transactions:

• If the offer is a buy offer and the Owner account has blocked the submitting Account, the transaction fails with tecNO_PERMISSION.
• If the offer contains a Destination and that Destination account has blocked the submitting Account, the transaction fails with tecNO_PERMISSION.

NFTokenAcceptOffer is not affected. A blocked address may still accept an existing sell offer created by the blocking account. Existing offers already on the ledger are also unaffected. Only the creation of new offers by the blocked address is checked.

3.3. Scope

This amendment covers NFToken offers only. Payment blocking and other object types are out of scope for this proposal and may be considered separately.

4. Reserve

Each blocked address consumes one owner reserve (currently 0.2 XRP). Removing the block returns the reserve.

5. Open Questions

• Should the block also apply to brokered offers?
• Is one ledger object per blocked address the preferred storage method, or is there a more compact alternative?
• Should a maximum number of blocked addresses be defined?

6. References

• Existing asfDisallowIncomingNFTokenOffer behavior (DisallowIncoming amendment)
• NFTokenCreateOffer and NFTokenAcceptOffer transactions
• tecNO_PERMISSION error

[Cavey773]

One of my biggest things about this is the spammers that lowball you constantly in the hopes that you will give up and give it to them or you accidently click accept. One of my NFTs that I am selling for over 12 XRP keeps getting an offer for 0.40 XRP. I "Reject" it, I "Archive" it and an hour later it is right back. I am all for someone looking for a deal, but spamming someone with a constant barrage of lowball offers is criminal and the pressure could eventually make someone do something stupid.