Skip to content

Commit 4ec0765

Browse files
committed
feedback: indirection (another attempt)
1 parent cd62d32 commit 4ec0765

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/blog/2025-09-05-memorable-wallet-addresses-custom-domain.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -199,7 +199,7 @@ Aside: The Web Monetization API doesn't inform websites which wallet address was
199199

200200
### `MonetizationEvent`
201201

202-
Let's say, instead of using a wallet address that our provider gave us, we alias it to a custom address as shown above, and add it to our webpage. This sort of indirection can also arise from using the [probabilistic revenue sharing generator](https://webmonetization.org/tools/prob-revshare/). The wallet itself can provide a wallet address alias, for example, as it's shorter or promotes the brand better.
202+
When we add such an aliased wallet address to our website, there's an indirection involved. This sort of indirection can also arise from using the [probabilistic revenue sharing generator](https://webmonetization.org/tools/prob-revshare/). The wallet itself can provide a wallet address alias, for example, as it's shorter or promotes the brand better.
203203

204204
When a `monetization` event is emitted, how do we know what wallet address was actually paid? And how do we know what wallet address we originally provided? This is even more relevant if your webpage includes multiple monetization link tags.
205205

0 commit comments

Comments
 (0)