-
I've been running a signet mempool for some time and it works fine, if I recall correctly it was as easy as setting However I haven't had success running this mempool instance with the "signet styling", meaning the mempool looks like it is mainnet, the URLs do not start with I wonder what additional setup needs to be done to get this working (likely in the frontend part?). I couldn't figure it out with the available documentation. Running 3.0.0-dev8 on both backend and frontend. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
This is because the frontend only use the Signet UI if the URL is /signet, we solve this with Nginx routing in production. We would need to add a new frontend config where we can specify the default network so that / can be the network of choice. |
Beta Was this translation helpful? Give feedback.
-
Yeah I noticed that e.g. https://sigpool.bitcoinbarcelona.xyz/signet/block/0000022812b0feb768e847a785d54a0e3696919a4df8ac79f8bb2acba982b65a renders fine, except that it doesn't find the data to populate the page unless you then remove the /signet prefix from the URL. It feels like a strategic URL rewrite somewhere in the Edit: Just remembered now that there is indeed a |
Beta Was this translation helpful? Give feedback.
-
Running with this Pull request should solve your problems. It will treat Signet as the main net. |
Beta Was this translation helpful? Give feedback.
-
Ok @1ma please try the PR now again. All issues should be resolved. Please test and reply back if everything works fine. Note that I updated the config name to ROOT_NETWORK |
Beta Was this translation helpful? Give feedback.
Running with this Pull request should solve your problems. It will treat Signet as the main net.
#5156