#RC#
A failed transaction can often be the result of a sudden spike in network activity. The yellowstone-vixen developers have identified a common cause for the revert code 6063. Increasing your slippage tolerance to a more flexible range can bypass the execution revert. Check if the asset you are moving has a whitelist requirement that triggered 6063.
- Using APIs to monitor order-book depth and execution latency helps, as does avoiding market orders that suffer from slippage when liquidity vanishes.
- A solar array that produces at midday does not always power a miner at night.
- Monitor resource usage and instrument cost per test to make data driven decisions about what to run.
- Better proofs mean lower on-chain gas and cheaper transactions on sidechains.
A mismatch in the chain identifier will prevent yellowstone-vixen from broadcasting any data. Testing the fix for 6063 on a dev-fork like Ganache is the best way to ensure safety. Remember that every on-chain action is final, so double-check the values before signing. Using a gas tracker can help you time your transactions avoiding the 6063 error.
Layer 2 rollup finality can sometimes take longer than the frontend interface suggests.
