docs: Add transaction tips documentation

[amaury1093]

Description

Closes: #10426

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[alexanderbez]

I personally like the approach Osmosis is taking, where you accept governance-approved fees (via an accept list) and send those fees to a dedicated module account, where you can then swap for native asset(s) later to be distributed to stakeholders.

cc @ValarDragon

But this approach is also interesting and useful too :)

[amaury1093]

I personally like the approach Osmosis is taking, where you accept governance-approved fees (via an accept list) and send those fees to a dedicated module account, where you can then swap for native asset(s) later to be distributed to stakeholders.

Is there a plan adding this to the SDK? It would be nice to have a pros/cons of the 2 different approaches for SDK users. Maybe Emeris can argue why tips suit their use case better.

[julienrbrt]

Interesting read :)

[alexanderbez]

I personally like the approach Osmosis is taking, where you accept governance-approved fees (via an accept list) and send those fees to a dedicated module account, where you can then swap for native asset(s) later to be distributed to stakeholders.

Is there a plan adding this to the SDK? It would be nice to have a pros/cons of the 2 different approaches for SDK users. Maybe Emeris can argue why tips suit their use case better.

Yeah its a two part thing. One is ante-handler middleware, the other is the actual swapping. The former I can add easily. The other requires oracle over IBC, probably via osmosis. Or maybe even using IA to execute a swap.