You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use XVerse for testing purposes on my custom signet network. XVerse allows selection of Mainnet, Testnet and Signet networks, but all of those are "pre-deployed" networks. I want to use my own custom network.
I successfully started bitcoind with my custom signet, started mempool, ensured correct configuration and made sure my mempool API is available over HTTPS.
But when I open XVerse Chrome Extension, I select "Signet" network, then paste url of my mempool API, it keeps showing me "Invalid URL" error.
Component
XVerse Chrome Web Extension.
Severity
Minor.
Summary
I want to use XVerse for testing purposes on my custom signet network. XVerse allows selection of Mainnet, Testnet and Signet networks, but all of those are "pre-deployed" networks. I want to use my own custom network.
I successfully started bitcoind with my custom signet, started mempool, ensured correct configuration and made sure my
mempool
API is available over HTTPS.But when I open XVerse Chrome Extension, I select "Signet" network, then paste url of my mempool API, it keeps showing me "Invalid URL" error.
I traced that to this code:
xverse-web-extension/src/app/utils/helper.ts
Lines 159 to 178 in 7c5a8e7
Here, xverse fetches hash of a 1st block from 2 sources: from default url, and from a custom url that user provided.
If hashes are different, XVerse Chrome Extensionshows "Invalid URL" error.
But hashes are expected to be different, because I am using my own custom signet network.
Expected Fix
Please add a bypass for this check (maybe a checkbox?), such that XVerse Chrome Extension will "just accept" my whatever custom URL is provided.
This will add a support for custom signet networks.
Thank you.
The text was updated successfully, but these errors were encountered: