Closed steveluscher closed 3 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
explorer | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | May 17, 2024 9:09pm |
I got tired of Explorer not working with the output of --dump-transaction-message
.
Can you update the inspector's text here with the supported byte data?
Can you update the inspector's text here with the supported byte data?
I'm so afraid to, because that would mean committing to keeping that working forever, when really I have half a mind that we should just eliminate support for decoding wire transactions altogether.
To be clear, pasting a valid base64 legacy message into Explorer today will break it. Try the ‘legacy message’ with Explorer in prod right now.
ie. This is not a ‘feature’ PR, it's a bug fix.
What do you think about adding the following somewhere in the UI?
support for tx.serialize() will end soon, please transition to tx.message.serialize()
or
supported formats Message, VersionedMessage, and (deprecated) Transaction, (deprecated) VersionedTransaction
What do you think about adding the following somewhere in the UI?
I think that would be a fine thing for someone else to do, who's actually going to see that through (ie. not me).
Test plan
Visit
/tx/inspector
and paste in the following.A legacy transaction
A version 0 transaction
A legacy message
A versioned message