Okay so you can use datacarriersize to increase the byte limit on your own user node? Is that what I’m understanding based on your comment?
So basically the node operator can just manually configure their own node to have a higher byte limit and choose to not filter BIP47 etc ?
Again- thank you for your patience because I’m new to some of this
i don’t know the specifics of how whirlpool tx or BIP-47 tx work, unfortunately.
theoretically if the only constraint is the data size in the OP_RETURN, then adjusting datacarrier and datacarriersize to be large enough would be enough to see/propagate both forms of tx.
again, do not know if this is the case, sorry!
Thank you! You were super helpful :) great conversations happening on nostr
Much better than a cooldown on GitHub
Centralization you know what I mean 😉
