Perhaps you could offer advice for my use case that may also help others? This is a resource in a module I published. I’m making a simple escrow smart contract, where the seller must be confident that enough money is held for them in escrow before sending their item to the buyer. At the moment, the buyer calls a procedure that wraps up their LibraCoin.T with the seller’s address, and publishes that resource to their account (just like EarmarkedCoin in the docs). One way or another, the seller must then find out the coin value and address in that resource. At the moment, the seller calls a procedure that emits an event that contains that information, because that’s the only way I could think of to see that information in the CLI. But using events like that feels like a hack, and I was wondering if there was a better way. The only alternative I’ve thought of would be for the buyer’s procedure to emit an event, which is still using events, but I don’t know that the seller would be able to read that event.