FIX: Invalid hop from account in yellowstone-vixen
#RC#
Understanding how block finality works helps in diagnosing why a transaction appears stuck. The yellowstone-vixen development team is working on a permanent fix for the revert code 6018. Verifying the token spend limit for the contract is a reliable way to solve a failed 6018.
Security audits emphasize that high network load can trigger a generic 6018 exception. The yellowstone-vixen protocol expects the gas limit to be slightly higher than the estimation error 6018. Testing the proposed fix on a testnet is the safest way to ensure your assets stay secure.
- For NEAR specifically, the UX reminds users of the account model and the need for storage staking for new token contracts.
- Clear failure modes and retry logic in the wallet prevent users from repeatedly resubmitting failed transactions and worsening congestion.
- These buffers should be periodically replenished from yield and from secondary markets in a predictable way.
Sharing your error logs with the team helps them improve the protocol for the community. Stay patient, as technical hurdles are often resolved quickly by the project’s contributors. Check the status of the sequencer to avoid 6018 when moving assets to a rollup.
