GateUser-de0b9e3b

In the past few days, the NFT royalty debate has flared up again, essentially about creators' income versus secondary market liquidity pulling in opposite directions. Others think that just adding a royalty toggle can "fairly distribute" income, but in actual trading paths, inserting an extra condition makes routing immediately more complex. In the end, market makers or aggregators will bypass it first, and you'll have to track which hop takes the royalty or skip it altogether.
I sympathize with creators, but it's also hard to expect the secondary market to voluntarily pay... On-chain, transac

Lately, I've seen people complain again about "still waiting for confirmation" on cross-chain bridges. I actually think this step shouldn't be skipped. Multi-signature, simply put, is a group of people pressing buttons together; no matter how many there are, they can't prevent the same set of risk control logic from making the same mistake. Oracles are more like mouths feeding prices and states; once the data source is biased, even if the bridge is more "automated," it just speeds up the mistake. Waiting for confirmation actually gives time for finality on the chain and for anomaly windows, no

I just reviewed a failed swap, and honestly, it’s not that the contract was too complicated, but that I lost track of my rhythm. In the past, I would quickly chase after price jumps, and when slippage widened, I’d treat it as “insurance.” As a result, I ended up in a low-liquidity route segment, couldn’t handle the depth, and while the quotes looked fine, the actual transaction was distorted. Now I’ll first break down the path and check whether each pool is deep enough, preferring to split into two transactions or wait a block or two, rather than forcing everything through the same route; I al